Database Users

On a subject totally unrelated to anything else going on:

Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?

dood, Nandroids are for pansies.

Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!

@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....

Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo

phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.

I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.

you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.

Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.

[Q] dual booting

I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App

The short answer is: no.

mysteryemotionz said:
I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?

muyoso said:
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?
Click to expand...
Click to collapse
I wanna dual boot with 2 separate sets of android for testing purposes
Sent from my Emotionless Beast of an Epic using the XDA App

I think yes, it would be possible. I wouldn't know how, but its been done on android before, and there is an alpha version being worked on already for the Sammy Moment at SDX and Samdroid.
And if this could be achieved it would be a great to help to developers.

I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.

RKight said:
I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.
Click to expand...
Click to collapse
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO

daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App

daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I'm aware of that process but if I'm just wanting to tinker with a new rom, I really don't want to go through all that trouble. If I want to try a new Linux distro on my PC, I'm not going to ghost it, install the new distro, then restore the old image later. I'm going to throw the new distro on a second hard drive and dual boot while I decide if I like it. That way, I have a known stable OS, configured the way I want, just a reboot away.

mysteryemotionz said:
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
I have noticed this as well, and a flash with odin plus reinstalling clockworkmod is the only thing that prevents it from corrupting your backups for future use.

daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I don't know. That's fine if you just want to try out a ROM one time, and quickly, or if you can do without your main ROM for a long time. I had a windows phone before I switched to Android. Having the "dual boot" was key to my switching to Android. I was able to install Android, set it up the way I wanted to (which took lots of time) and "play" with it whenever I had time, but at other times I needed to be able to switch back to my main phone. I'd switch a couple times a day sometimes (just a single click to go either way). After a couple of weeks of being able to work with Android I knew I'd be happy switching.
You could do something like this with backups and restores, but I honestly think it would get overly cumbersome. You'd have to backup your main ROM and then the second ROM. Every time you changed a setting or moved something around in either ROM you'd have to remember to make a new backup, or the next time you switched into that ROM all of your changes would be reverted back.
In any case, I don't know how possible it is to have dual boot, but I can certainly see a lot of advantages for some people.

HARET is what makes the WinMo android boot possible and is based on work done with soft/hard SPL. No Android equiv to HARET exists yet. However, a lot of work is happening with HBOOT due to the Vision G2 eMMC situation. I wouldn't be too far off if I were to speculate that an android HARET may be in our future.

Go check out this thread from the Eris forums. - Dual boot recovery hack
As I'm not intimately familiar with the inner workings of Clockwork, I don't know how plausible it is on the DX. It could either be really easy to port since we're already bootstrapped, or nearly impossible. That's a problem for a dev much smarter than me to conquer.
I will say that I tried it out on my Eris. The stock class 2 card was unbearably slow, a class 4 was tolerable, and a class 6 (which cost a small fortune) ran as if it was installed internally. Kinda neat, but not terribly practical for daily use.

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.

Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.

I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App

Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App

aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.

It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.

I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.

Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.

akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.

Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.

Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.

Try removing the SD card and booting.
Sent from my PC36100 using XDA App

rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!

It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.

bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?

Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.

herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.

Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?

Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol

akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

can flash to miui or restore to stock htc root but .....

This is my first post in XDA.I hope this is the right spot for this questions.
I have searched everywhere for the answers to this question before posting. I flashed to CM7 with the tiamat kernel awhile back. I love CM7 but was curious to see what other rom developers are doing.
I ALWAYS do a back up before doing any flashes. I backed up my CM7 and my base rooted HTC downgraded 2.2 through RM. I was able to flash to synergy with no problems and restore to CM7. I decided to check out MIUI over the weekend. I flashed it with no problem. Last night I wanted to try mikshifted-g and Supreme Sense . I could not install either of them . The both stalled once CWM started to install. It was stuck on updating. There were no errors. I took the battery out and tried to restore CM7 backup through CWM. The restore went as expect but when I went to reboot it was only the HTC logo. I took the battery out and went back to MIUI through CWM and the phone booted. I then did a restore of my original rooted 2.2 the phone booted. I tried to install the above again on a fresh HTC stock rooted phone through RM and still had the same thing happen.
My question, is why I am not able to flash any other roms successfully other than restoring to MIUI and stock rooted htc 2.2 ? Installing Synergy works !
I do a full flash of system,data, cache and dalvik cache. I am not sure what I am missing.
If I understand correctly MIUI is a GB kernel as well as the others so there should not be a problem of compatibility ? I am assuming I still have root ? My HBOOT does say S off and PG 06001. I will try downloading CM7 through MIUI again to see if it works through RM. Sorry for the long post. I wanted to give as much detail as possible. Thanks in advance for any help
Richard

My suggestion would be don't use ROM Manager to flash, wipe or make nands. Do everything manually through recovery. I've seen too many people have the same type problems when using ROM manager.

what I have noticed is the progress bar in cwm doesn't work with sense roms, at least it never did in the mikshifted roms i tried and they take a LOT longer to install than cm7. How long did you let them sit at the install screen with that blank progress bar? Try clearing all your data/caches then install a sense based rom but leave your phone alone for like 10 minutes while it sits at that screen with the blank progress bar that says mikroms or whatever it says (been awhile since i used one). It shouldn't take 10 minutes but if your phone sits at that screen for that long then you know for sure it isn't working. I pulled my battery a couple times before i realized that's what was happening. I read about it somewhere online.

I have tried both RM and CWM. Both have the same results. 99% of the time I prefer the manual CWM method. Sorry I did not make it more clear.
I did re-flash CM7 with no problem. I do let the rom flash sit for a while but I will try longer since you say it takes longer with the roms in question. I let it sit for a few minutes. That seems like it should be more than enough. CM7 is pretty quick to install as well MIUI like you said. I love the layout and features of MIUI but since I am in a 4G area seems to defeat the purpose of having 4G if you can't use it. To be realistic though 4G is spotty in Atlanta and I mostly end up for 3G or using my wireless at home. I will probably end up with CM7 again since I like it equally as much as MIUI. If I wait longer for it to install and it does not work is there anything I should be looking at as the culprit other than myself

you were right, it just took a LONG time to install. I thought I was losing it. It took over 5 minutes. I am used to the install times of the MIUI and CM7 . Thanks for telling me to wait a little long. It's always the simple overlooked things like patients

My advice is just make sure you do a FULL Wipe before flashing a Rom. Like on THIS GUIDE, saves headaches later. Aslo, as you've learned Sense Roms usually take quite a bit longer than MIUI ,ASOP, or most others. But yes patience is important .

I definitely do a full wipe . I used all the guides here to make sure I did everything correct. I did not realize that the sense roms took longer than the CM or MIUI. I love the layout of MIUI. I wished it at some point 4G was going to be a part of it but I understand why it will not be .
4G in Atlanta, GA is not reliable, at least on my shift with sprint. I hate to pay for a feature that I am not able to use on regular basis. It's so spotty here I have gotten used to it.
I was never a big sense fan but it seems like if you want to have the 4G feature you use either use CM or another Sense rom right ? I got the shift because of how solid it's built and many reviews favor the EVOs or Galaxy S on Sprint
Thanks for all the feedback
Richard

Well you might want to give [AOSP ROM] S.O.A.P. ROM (sense-ish on android phones) a try. Sounds more like what your looking for. It's by one of the Shift members here.

[Q] NEED HELP!!! Boot/loading screen wont stop!!!

A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...

I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.

k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!

Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??

k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium