Related
I'm rooted, unrevoked; I'm currently stuck in a boot loop. I can not reach recovery. I can not get to my rom. I can only access bootloader.
So far I have taken these steps to cure my problem:
Ran RUU software in Windows (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Cleared Storage using fastboot in command prompt
Cleared Recovery and then Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
Flashed Sprint Lover's as PC36IMG in hboot
Flashed eng-PC36IMG from Toastctfh's Old Root Tutorial as PC36IMG in hboot
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Before the bootloop this is what I was doing:
I had the initial CM7 nightly installed for about 2 weeks. It was buggy, and a few days ago restarted and deleted all my texts, and desynced from google. On rebooting, google apps acted as if I had never ran the phone before - it asked me to enter google account info, etc, upon reboot.
I decided CM7 was too unstable and so I wiped data and davlik, and flashed CM6. When CM6 booted google apps was already on, before I had even flashed it! Anyways I figured I wanted to give MIUI a run, so I wiped data and davlik, and flashed MIUI. It ran fine for about two hours, and then rebooted out of nowhere... and never came out of the boot loop.
I'm really starting to sweat this as I have gone three days now without a phone. Does anyone have any ideas that may help me? Thanks.
hmm, you could flash recovery through bootloader i think
davidc23 said:
hmm, you could flash recovery through bootloader i think
Click to expand...
Click to collapse
thanks for the suggestion!, but thats what i meant by
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
all i need to know can u get into recovery? cause if u can flash calkulins format all and flash the rom and ur good
Nope, I can't reach recovery
idk what to say hopefully a expert drops by im sorry that i cant help
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Jimdog420 said:
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Click to expand...
Click to collapse
I had same problem, the radios messed my phone and was stuck in a boot loop and mess with my usb drivers as well so I couldnt charge my phone...i had to buy spare battery charger and flash different radio and rom through hboot
I'm pretty sure Sprint Lover's and RUU have the latest radios in them
You shouldnt be bricked and if you flashed an RUU, you wont have root anymore, nor will you have a recovery img. I would suggest running the RUU again. As long as it finishes without errors, you should be fine. Now, just a quick question, what are you seeing that makes you think you are in a bootloop??
Are you sure RUU removes root? I've RUU'd through my computer, as well as flashing an RUU zip as PC36IMG, and I still have S-OFF. If it would turn it to S-ON, that would be amazing.
your ruu file could be bad as well .. it happened to me once and had to redownload...for some reason it wasnt as big as it should of been
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
BrashL said:
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
Click to expand...
Click to collapse
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
k2buckley said:
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
Click to expand...
Click to collapse
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Lol, I gave him detailed instructions on how to flash it using the bootloader, don't worry. I was pm ing with him.
Sent from my PC36100 using XDA App
r916 said:
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Click to expand...
Click to collapse
He uploaded a recovery image in a PC36IMG, so it NEEDS to be flashed in the bootloader.
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
100proof said:
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
Click to expand...
Click to collapse
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Think we have different problems. Every time I try to flash something new it completes fine, but it still boot loops. Hell, yours might be fixable.
I've tried everything now with no luck. Everything updates and completes but has absolutely no effect on the boot looping. This is really insane and my advice to anyone would be to stop using CM7 immediately as it seems to be confined to that ROM.
If anyone else has had this exact problem please post, I want to get a tally of how many people are affected and try to find a commonality.
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
But my phone ran for a month without any problems except for some random reboots which seem to be common with this phone in general. I didn't add software or flash anything before this happened, it just happened. That seems to be the experience most people are having, the only thing in common is that they were running CM7 or had been running it recently and tried to flash to a different rom.
What software problem wouldn't be corrected by a successfully completed reflash with a stock RUU? That's the major question.
Hmm, that is awkward; at that point, I would just take it in if you're still getting random reboots. Been on CM7 for the longest and no random reboots on my end.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I agree, that is exactly what they should.
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
BrashL said:
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
Click to expand...
Click to collapse
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
teh roxxorz said:
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
Click to expand...
Click to collapse
Already tried it, no dice. Goes through fine but then keeps bootlooping. On a side note, is there a way to get S-On through the bootloader since I can't access recovery?
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
teh roxxorz said:
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
Click to expand...
Click to collapse
Did that buy still S-Off
http://www.shipped-roms.com/shipped/Supersonic/ Did you run the right RUU for your software version?
And I'm heading tot he gym for ~1hr; you can pm me in the meantime and I'll answer when I get back if you still need assistance.
dougjamal said:
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
I'm sorry I wasn't clear . Days of reading every post in any thread I can find has left me running on no sleep. The huge problem is that no matter what recovery rom is flashed it wont let me boot into RECOVERY MODE. It flashes fine whether it is from the sd or through cmd using fastboot (Ive tried almost every version including the newest of both Amen RA and Clockwork). This gets me stuck in the white HTC screen boot loop. If I flash a RUU it will at least hang with a partition error and get stuck in the four triangle error, which will at least let you charge the battery so I can start all over again. Is there maybe a way to wipe the partition or reformat in fastboot as that is really the only thing working (regular adb wont detect). It seems a ton of people have been popping up with this same problem out of the blue the last few days.
So my phone now will only reboot up to the HTC Incredible white screen. I'm not even sure what the issue is, all i did last before it got stuck was erase data on an old sd card i had in the phone. Then I just did a reboot and it froze on the white screen.
I'm running GB evervolv 2.3.2 with 2.6.37.4 incredikernel.
I can get into HBOOT but when i click on recovery it takes me into fastboot everytime.
What can i do to fix this????
Sorry please move this thread to the Q&A section, i thought that's where I was posting it, my bad.
Go to the Clockwork Recovery thread and download the update for a different version and try getting that to flash via bootloader. That way you can at least get into recovery if you need to flash new. Just to clear it up, did you use your phone to delete stuff off the old card, by using Astro or ES file explorer? I know ES file explorer has root access so is there a chance you could've deleted a system file on accident? All it takes is a click of the SD card icon and you're in root instead of SDcard. Also this is probably a thread more for the Q&A subforum, just an fyi
i deleted an old sd card that i don't even use for my phone, i was just putting it in there to clear out whatever was left on it. so i could use it new.
And it still bootloops even when you put your normal SD card back in?
yup, i dunno what it's deal is.
I remember an older version of cm7 on the nook color warned against formating sd cards because it accidentaly formats the boot partition, this may be a bug that exists in the rom your using.
at least you can get into hboot, you should be able to download ruu image and flash it in hboot. this would get you back to stock, then root and install clockwork, and then restore your latest nandroid.
Flash this recovery in hboot
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
It should at least give you a working recovery.
i have to rename things as update.zip in order for hboot to flash them right??
facedown41 said:
i have to rename things as update.zip in order for hboot to flash them right??
Click to expand...
Click to collapse
NO leave it PB31IMG.ZIP.
hboot can only see that name. if you rename it hboot will not see it at all.
also make sure your card is formatted as FAT32
got it into recovery so i'm just wiping and restoring, thanks for the help!
ok now i'm getting a bootloop on the cm7 boot screen...i just went to flash that new instead of my nandroid because the nandroid was from an older rom.
Did you wipe everything? Davik, Cache, Data, etc?
wiped data and cache...didn't do davik because i've never had to in the past. but i'll give it a try.
would i need to update CMW from version 2.0+ to 3 in order for cm7 to work? because it's still bootlooping
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
JWorth said:
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
Click to expand...
Click to collapse
Are you getting errors when you wipe?like when you wipe data does it say error can't mount or anything like that.... I have a feeling you may have to flash an Ruu and then reroot
Sent from my Incredible using XDA App
no, no errors. but i flashed the RUU and rerooted and everything works just fine. I flashed MIUI again and it worked perfect
thanks!
I figured that's what you would have to do glad you are back running
Sent from my Incredible using XDA App
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
rynosaur said:
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
This tends to be things go as far as ROMs partitioning my sd, always back it up externally and format/partition before transferring stuck back over to it while in phone.
I loaded a backup of CM7 and when it rebooted it went into a bootloop and I cant get into recovery. I've tried everything even flashing CWM again and also the stock ROM image. Still bootloop!
Please help
You didnt brick it, if you bricked it, it wouldnt start. You should still be able to get into recovery, by holding the power button and volume at the same time, and getting into Hboot, then go to recovery. Im also guessing it happened because you didnt whipe cache or data before you did this. First time i ever installed a new rom i got a bootloop,
Thank you for responding. I cant get into recovery it starts bootlooping once I select recovery. I tried loading the PB image of CWM and I also tried flashing the stock RUU. Cant get past HBOOT or initial bootloop. I CAN get into fastboot ADB though. Tried flashing a backup system.img, boot.img, data.img but boot.img said error
Your welcome, im not perfect at all this so excuse me a bit lol. So your saying when you select recovery, it boots up normally to the splash screen, or am i wrong? If your able to flash things them im pretty sure your able to get into recovery. Maybe also try another version of CM7? Transferring it to your phone.
No I select recovery in HBOOT and it goes straight to the white HTC INCREDIBLE screen and begins the bootloop process. I've pushed the CWM 3.0.0.8 in a pb13img file and still wont go into recovery. I cant get the phone past HBOOT
Thats really really weird that it wont go into recovery and it starts the boot. Hopefully someone can come with some extra assistance. It isnt bricked tho, i know that. So did you try formating data and cache then before doing anything either?
No I was busy and messed up. applied a backup without wiping data/cache. Came back to a powered off phone. Tried turning it on and it was bootlooping. I cant do anything now. Even if I can get S-ON i'll just get a replacement
There's a data wipe option in hboot, have you tried that?
Sent from my ADR6300 using XDA App
Goto Doug piston's web site and follow the go back to stock. You should be able to put the stock RUU on the root of your sd card named pb31img (not sure the exact file name but it is on dougs site). When you load in HBOOT, it should recognize the file and install. If I am not mistaken, this will unroot your phone as well.
http://dougpiston.com/?page_id=108
Pb31img file is there.
I tried the stock rom PB31IMG.zip and it continues to bootloop. If I cant get it fixed I want to at least get S-On
Probably aren't gonna be able to get S-ON cause that needs to be done in recovery..
Sent from my ADR6300 using XDA App
There is also the unrevoked forever s-on tool which you flash through recovery
Sent from my DROIDX using XDA App
Yeah cant get to recovery so I'm boned.
I got VZW to send me a replacement and also got Asurion to get my an Inc2. Not sure which to send back. Free replacement with a gamble getting caught S-On, or $99 free upgrade to Inc2
what radio were you running
try flashing alternate recovery?
i also seem to remember there being a way to root through adb isnt there a way to unroot like that too?
I tried amon ra and a another one no difference. I also tried everything I could adb wise to flash different systems and erase everything. Im running the new GB radio
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
CSamson said:
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I got excited thinking there was a way to unbrick because of a step I missed. So I went to make sure the radio was right. I HAD the GB Leak 2.15.10.05.06
Right now in HBoot it shows 2.15.00.07.28
I know its not considered a brick because it still turns on but there is NOTHING I can do to get it out of bootloop or past HBoot
hmm new GB radio this has been happening with thunderbolt users to.....but in greater numbers.....I'd advise against using the GB leaked radio...
Your backup. Rec2.x. and now. 3.x?
Sent from my Optimized Inc using XDA App
I've noticed, that once you flash a rom. It loads folders onto your sd root folder. which are usually
battery history
rosie_scroll
.android_secure
LOST.DIR
media
etc..
*************
I flashed billions of roms over and over, but after my most recent attempt to flash a new rom. it says load complete. but nothing is loaded onto the sd card. (i mean nothing)
I've wiped, re wiped, super wiped, partitioned, formatted sd everything. still, the roms load jack onto my sd card.
1). Is my phone hopeless?
2). Should i just turn s-on back on and turn it in? Or it there a trick around this?
redm1st said:
I've noticed, that once you flash a rom. It loads folders onto your sd root folder. which are usually
battery history
rosie_scroll
.android_secure
LOST.DIR
media
etc..
*************
I flashed billions of roms over and over, but after my most recent attempt to flash a new rom. it says load complete. but nothing is loaded onto the sd card. (i mean nothing)
I've wiped, re wiped, super wiped, partitioned, formatted sd everything. still, the roms load jack onto my sd card.
1). Is my phone hopeless?
2). Should i just turn s-on back on and turn it in? Or it there a trick around this?
Click to expand...
Click to collapse
Did you try using a different recovery? Not sure which one you are using at the moment. Amon ra, CWM or TeamWin not sure if it will sole your trouble but its worth to try. Did you try flashing an AOSP? Or Sense? is this happening with both types?
DrDr3z85 said:
Did you try using a different recovery? Not sure which one you are using at the moment. Amon ra, CWM or TeamWin not sure if it will sole your trouble but its worth to try. Did you try flashing an AOSP? Or Sense? is this happening with both types?
Click to expand...
Click to collapse
I flashed a sense rom, only flash sense roms.. Ive first noticed my phone not booting up after i flashed "r3charged_FINAL" rom. I didnt pay it to much attention. So then i flashed "kings bliss beta3" it worked fine, flashed "r3charged" again, and the same crap.
Flashed "Noctunral rom" it worked, phone died, later on got home, partitioned my sd. format all, wiped, super wiped, flashed those custom flashes "FR_Boot/Recovery_CustomMTD" the rom "r3charged"
Still nothing loading on the card, I checked, i even let it reboot in hopes it might load, but nope.
And yes, I went through all three recoveries in hopes of that might make a difference.
cant get S-On to flash. It keeps showing
unrEV0ked forever S-ON patch v1.3
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in/sdcard/unrevoked-forever-son.zip
(Status 42)
****************************
"S-OFF LOG"
unrEVOked forever S-ON patch v1.3
Verifying system type...
.
.
Got device:
@PID: 73,"SUPERSONIC_C"
Got radio version:
2.15.00.05.02
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
redm1st said:
I flashed a sense rom, only flash sense roms.. Ive first noticed my phone not booting up after i flashed "r3charged_FINAL" rom. I didnt pay it to much attention. So then i flashed "kings bliss beta3" it worked fine, flashed "r3charged" again, and the same crap.
Flashed "Noctunral rom" it worked, phone died, later on got home, partitioned my sd. format all, wiped, super wiped, flashed those custom flashes "FR_Boot/Recovery_CustomMTD" the rom "r3charged"
Still nothing loading on the card, I checked, i even let it reboot in hopes it might load, but nope.
And yes, I went through all three recoveries in hopes of that might make a difference.
Click to expand...
Click to collapse
Custom MTD is your problem I went through the same thing yesterday.
Flash Team win recovery from bootloader and then flash any sense room do not flash the MTD recovery zip.
Anything beyond that would be above my paygrade.
Good luck
DrDr3z85 said:
Custom MTD is your problem I went through the same thing yesterday.
Flash Team win recovery from bootloader and then flash any sense room do not flash the MTD recovery zip.
Anything beyond that would be above my paygrade.
Good luck
Click to expand...
Click to collapse
Tried that, I'll give it another whirl. pulled out all the stops last night. hopefully the phone just needed a nap and it's good to go today. LOL!!
!!Yells!! "S. O. B"
It's working again. And that move, was tried the day before. Guess it just needed a day break of all the flashing.
DrDr3z85 = 20th. thanks!