Develop Bugs

HTC Boot Logo Brick (Devs please make sticky untill solved)

Recently I had a brick on my Desire, which caused that I couldn't boot past the HTC Boot logo. I already made a thread about it, but without a solution. I sent my desire back for repair, but I think it wouldn't be a good idea if we all had to do this. So I would advice everyone to unroot, untill one of the genius devs has found a solution.
Symptoms:
-Boot stuck at HTC Boot Logo
-Going in to recovery takes a long time
-Recovery usually doesn't even work
Posible Solution:
-Some users are reporting, they can boot without SD and SIM (dont know if repartitioning the sd totally solves everything)
-Some users report, say that the situation is solved if you flash a diffirent rom (didn't work for me)
Finally I would like to motivate my opinion why people should unroot.
When I posted my first entry I though I was the only one, but now more and more people are getting this problem.
This problem is as said above probably something which can be solved but right now its a dangerous development.

This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.

I have rooted my phone and flashed about 20-30 ROM's and haven't had a single problem.
I must have been lucky to get a phone that don't brick so easy. I hope that you who have problem with this get a solution soon.

socktug said:
This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.
Click to expand...
Click to collapse
I've read about 5 diffirent posts about this. All the post are on the first two pages i think. I was running DeFrost, and used r5's recovery. And I was running the most recent radio that is now availible

@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.

khoaitaychienvn said:
@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.
Click to expand...
Click to collapse
I'm really sorry if i made you or anyone else feel like that. I've always have great respect for the devs who work their asses of to make great roms for us. and always look forward to new cooked roms made by them. The only reason the I made this thread is that i don't want other people to get bricked.
Could you please tell me where i implied that the devs were a fault here?
And finally, if anyone is to blame its HTC who are working so strongly against people putting custom roms on their phone, who ust want to make their user experience better.

I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.

Giland said:
I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.
Click to expand...
Click to collapse
Ok guys i'm sorry for posting this thread, clearly it isn't really a problem. I just wanted to post it because these instructions dind't work for me. But i will gladly remove this thread (If its possible)

hi mate .
I have the exact problem and I think it is a real problem - see my thread
Can someone help me - stuck on htc boot - very strange situation -- I was not allowed to put the link to it...
I did everything do get it started but no luck at all. is strange that can access fastboot, the pc recognize the device but the recovery didn't work at all, even one time I couldn't get it: when I push the power button the logo htc screen just appear and get stuck there.
so if every one has any idea what could be please help us,there are more than a week I tried every day to get it work again.
many thanks.

I had this problem months ago I was running my desire on a custom rom had a2sd installed formated the sd card and the phone wouldnt boot reflashed a fresh rom and everything worked fine again.

I too had this problem...
You didn't by any chance apply the unrevoked recovery did you? If so, did you also use ROM Manager.
If you read the top page of the unrevoked thread you'll see that it says that the two combined cause a problem with flash memory. To fix the brick I ran an offical HTC RUU, re-rooted using Paul's method, and then re applied unrevoked. I now definitely DO NOT use Rom manager.
Hope it was some help mate.

Yes best option if u can access hboot is to go back to stock using ruu
then re root it shd solve all probs

in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???

RUU
When I flashed a RUU, it was still stuck at the bootloop.

Milioo said:
When I flashed a RUU, it was still stuck at the bootloop.
Click to expand...
Click to collapse
If you can do a logcat of the boot-loop and pastebin it. We'll see what the problem is...
In terminal or command, write adb logcat or adb-windows logcat and then run it for the duration of the loop.
laupc said:
in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???
Click to expand...
Click to collapse
Yea the RUU upgrades your H-boot, Does just running the RUU achieve anything, you should just have a fresh clean non-rooted ROM load up on your device straight after running it?

Pop onto irc and visit the modaco chat room....we can have a talk about possible fixes
chat.freenode.net
#modaco
Feel free to look for me, and message me

just give the adb logcat comand while in bootloop and saying waiting for device and that's all

Have you tried restoring a good misc image? Just incase this could be related to that like other forms of brick are...

how can I restore the misc?

laupc said:
how can I restore the misc?
Click to expand...
Click to collapse
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
Although... with the mention of recovery taking an age, is that standard recovery, unrevoked or fake flash?
The above method uses the standard HTC recovery image, similar to fakeflash does. Worth a try *if* you can get it to work... May or may not resolve the issue though (I'm just guessing here) but could possibly in a weird kinda way help you to do a successful RUU restore using the PB image method...

[Q] A100 Is it bricked?

Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:

Yeah eMMc is a goner.
Sent from my Galaxy Nexus using xda app-developers app

filking said:
Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:
Click to expand...
Click to collapse
Adb commands don't work in fastboot mode, you need fastboot devices instead, so adb devices not working doesn't mean anything. If it did work that's odd though lol. Also, booting in fastboot is the wrong mode anyways, use the other volume key for recovery, for now remove the external sd then boot recovery and report back what happens there.
Tapatalked from my HTC DNA

Ok, removed the usb and external SD.
Do the other boot I get a quick message saying 'erasing cache before sd-update'
Hold on...
While typing this, it's changed..
Before I had the 'droid' then he fell over when '!'... it's done that again, but straight away it's got loads of messages.
E:Can't open /dev/block/mmcblk0p5
(no such file or directory)
that is repeated several time for dif files/directories...
Then it displays the recovery menu.....
reboot,
apply update
wipe data
wipe cache
apply update
1st time it's shown that....
Next step??

Anyone help??
I have the Android system recovery utility...
What now?

filking said:
Anyone help??
I have the Android system recovery utility...
What now?
Click to expand...
Click to collapse
You can try wiping but that error is usually a dead or dying emmc.
Also, have some patience, we have lives to live we answer when we can.
Tapatalked from my HTC DNA

lol, sorry... 2nd post wasn't meant as a 'hurry up and fix mine, because i'm more important'.....
I was typing something else in, then i decided that was stupid, so i deleted and put that instead....
my bad...
:angel:

just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....

filking said:
just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....
Click to expand...
Click to collapse
Fastboot commands will always work provided drivers are installed and it can boot into fastboot, it doesn't mean you aren't in the process of bricking, just hasn't gone all the way yet. When its final you won't even get a screen that lights up or vibration.
Since you asked though in recovery you can wipe cache but that will likely give errors again. The nuclear option is fastboot erase userdata but that's like massive data destruction, even internal sd I think.
As you're stock, stop now, and get in touch with acer and see if they'll cover it for warranty repair under their 1 year BS coverage.
Tapatalked from my HTC DNA

Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers

filking said:
Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers
Click to expand...
Click to collapse
I said stock because you have a stock recovery, though fastboot mode says you rooted and all that at some point. Probably ran a stock based Rom and ended up overwriting recovery which makes this harder to figure out. But its 99% likely its dying.
You can manually flash a recovery in fastboot and try to factory reset there or just do the fastboot command in my last post.
Tapatalked from my HTC DNA

Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?

filking said:
Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?
Click to expand...
Click to collapse
Read the brick thread for info on it, but short answer is emmc died.
Tapatalked from my HTC DNA

Well, acer support want £55.15 just to post it back to them, then they will call with cost of repair... lol I don't think so somehow..
Luckily I am in a good position at the mo, so i've just purchased a nexus n7...
I'll monitor this site until 1 day maybe one of the genius's on here will find a cheaper cure..
Good luck all...
(i'll be moving to the nexus section now then.. look out overthere.... :silly

[Q] Looking for ORANG001 Nandroid backup

Hey guys, anyone got a 2.17.61.3 stock nandroid backup for ORANG001 (Orange UK)?
Struggling to find it uploaded anywhere.
Need this or the custom ruu to use the downgrading trick to update my hboot.
Thanks!

Its in here
http://forum.xda-developers.com/showthread.php?t=1975140 :thumbup:

The dropbox link is broken sadly

Then you have to wait until its fixed, or when bugsy get the chance to host it on his sire

Yeah :s
Trying to update my hboot, because right now the phone randomly turns off and requires me to hold down the power button. Also gets stuck on optimizing apps.
Thought I'd ask here in case anyone had it floating around in their download folder.
Thanks though!

Maybe there is a JB firmware in the firmware collection thread to update the hboot and then restore the JB nandroid ?
Your cid and firmware is listed here + firmware download
http://forum.xda-developers.com/showthread.php?t=1957376

That could work! Would I flash the firmware in the same way as I would in the RUU/hboot upgrade guides, or can I skip locking the bootloader and stock recovery?
Like:
fastboot oem lock
reboot
fastboot oem rebootRUU
fastboot flash zip <zip>
re-unlock etc.

Yes thats it

Did all that, stock rom crashed, flashed IceColdJelly and that crashed after a while. Phone won't turn on now like before, might turn on after a while, I always have to hold down the button for a long time now.
Thinking maybe this is a hardware / battery problem although everyone was fine before I when from Carbon 1.3 -> 1.5, going back to 1.3 didn't help.
Not really sure what to do now :s

Do the firmware flash all over ! Then reflash the custom recovery, perform a real good wipe and install the rom again. Helped before when i suggested it with someone who experienced similar problems

Did all that, everything went fine until booting into system again, it crashed pretty much just after setup-up. The screen freezes and the button lights go to full brightness.
Would it be worth completely formatting the SD card too?
Trying to think of anything I'm doing wrong.. I do use the Motorola charger rather than an HTC one but I doubt that matters.
Thanks for helping thus far though!

Also for flashing ? Never use another cable then the original !
And yeah its worth the try. Did you perform a full wipe in the recovery....really all stuff ? Caches, dalvik cache....data, system, factory reset. Then install the new rom and flash the boot.img....also wipe cache after flashing the boot.img
Fastboot erase cache
It looks more like a not good wipe problem to me

OK I did a full wipe this time, system, sd card. I've got TWRP on there now which works fine. I flashed ICJ then the boot.img as well as wiping the cache.
Phone booted up fine was working for quite a while before it crashed again, the phone was plugged in using the Motorola plug charger when it crashed. I've been using a battery pack too which uses the power connection on the back.
The phone wouldn't turn on until I plugged it into USB for a while (no led) and held down power + volume down. I'm going to charge it up to full via usb in TWRP then see if it still crashes without charging and without the battery pack on.
I hope it doesn't because then it could just be I need to get the HTC plug/cable and stop using the case.
If it's a hardware problem then I'm not sure I'll be able to get it repaired as I bought this second hand (with a receipt, I could see if I can proof of purchase) and have unlocked the bootloader etc.
I suppose if the phone won't turn on though they can't know that.

Like i said ..... only use original stuff

Any update ?

It crashed in recovery while making a backup and I haven't manage to get it back on yet, I've ordered a HTC cable / plug though. If I get it on I'll just charge it then turn it off, as when I turn it off (as opposed to it crashing) it turns on normally.
Not really looking good though

Sorry to hear this

Got the HTC plug and nothing seems different, still totally dead.I think it is a hardware failure of some sort, as with all the different software combinations I tried it was crashing regardless. (At least that's what I tell myself.)
I'm going to see if I can get it repaired on warranty and hope they don't check the IMEI.
Thanks for all the help

Oke mate ! I hope you get it fixed soon

Good news! HTC have fixed it and sent it back, charging it for a few hours now before I turn it on.
I'm not sure what broke it but I was using the wrong charger for the phone and also a cheap battery case to prolong its daily usage. I'm not sure whether I want to risk flashing roms again but I really don't like sense, it depends if I bricked it or not.

[Q] Potential hardware issues/ brick / batter issue? Please help

Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.

if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?

xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.

Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?

moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.

Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...

moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?

metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.

moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.

moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.

metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.

xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.

Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.

So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.

Accidental crash

While going through the factory test pages, to check on my burn in, i accidentally switched my device in to aging mode. During Startup in Aging Mode it crashed and after a normal reboot i lost all my sensors, cameras and the system seems glichty. I tried everything including firmware up/down grade. Twrp full wipe and reinstall. newly flashed Boot.img and fresh install of Oxygen. Nothing helps. Anybody might have a wild guess ????

Malleges said:
While going through the factory test pages, to check on my burn in, i accidentally switched my device in to aging mode. During Startup in Aging Mode it crashed and after a normal reboot i lost all my sensors, cameras and the system seems glichty. I tried everything including firmware up/down grade. Twrp full wipe and reinstall. newly flashed Boot.img and fresh install of Oxygen. Nothing helps. Anybody might have a wild guess ????
Click to expand...
Click to collapse
Sry litteraly after the post and the 10 th time I tried it again and it finally worked.... DONT get to the Point were i was! Its hell and i dont wish it anyone
!

Malleges said:
Sry litteraly after the post and the 10 th time I tried it again and it finally worked.... DONT get to the Point were i was! Its hell and i dont wish it anyone
!
Click to expand...
Click to collapse
Just flash persist.img from fastboot mode
Fastboot flash persist persist.img
If it happens again:good:
https://drive.google.com/open?id=0B2p1k5sTiAMzUjkxWWZGNjlyb2c