Database Develop

Need help BADLY

Please bear with me. I tried posting questions about this in the Q/A forum and received no real help.
I recently went from FRF50 to FRF83 and started getting random reboots. I'm on the 4.06.00.12_07 radio with the stock kernel. I wiped everything before flashing.
Today I wiped again and reflashed FRF50 and everything seemed to be okay aside from maybe 1 reboot.
I just flashed the stock FRF85B and rooted it and I'm back to rebooting. It's even worse now. It reboots the instant everything loads.
I got the last_kmsg:
http://pastebin.org/365407
Please let me know what's wrong. I'm dying to know. Is it hardware? Is it the battery? Am I going to have to pay a buttload of cash for HTC to fix it?
Thanks for any help

1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.

GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
Is it the wrong forum? Do people at the Q/A or general forum know about kernels/deeper info and do the people who know about that stuff venture over to those forums?
I tried getting info there, and I got none. This is the last place to turn.
What would wiping and starting from stock achieve?

No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.

S_Dot said:
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
Click to expand...
Click to collapse
How will this help me? Okay if stock works, but what about the update?

Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.

Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue

Prod1702 said:
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Click to expand...
Click to collapse
leonnib4 said:
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Click to expand...
Click to collapse
I'm going to try to go back to stock and see if it works. If not I can only assume that it is a hardware problem and I'll have to bite the bullet and pay for repairs.
What kind of a hardware problem could it be???

Can someone help me get back to stock properly?

See sticky.
Mod move to q&aplease.

leonnib4 said:
See sticky.
Mod move to q&aplease.
Click to expand...
Click to collapse
Sticky is full of bad info. I have new radio (4.06.00.12_07).
I'm assuming that if I get stock radio and the ERD79 update.zip I should be fine?

GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
You sir, are a complete asshole.
Sent from my Nexus One using XDA App

Yes the new radio won't work on 2.1 so change Ur radio and flash that update.zip and cross Ur fingers that Ur problem is fixed good luck let us know
Sent from my Nexus One using XDA App

FML. Hardware issue. Just went through CM 5.0.8. flash from scratch including re-flashing new radio and new recovery and I got a reboot during sign-in to Google.
God ****ing dammit.

Any logcat?

if you have an ext partition.. wipe that as well..

might be a battery issue. my battery had been overheated during navigation and right after boot it would give out turn off and boot again. just replaced it and worked fine.

To check battery issue, I suppose running with charger inserted would be enough.

Jack_R1 said:
To check battery issue, I suppose running with charger inserted would be enough.
Click to expand...
Click to collapse
What do you mean by this?
I'm pretty sure it is the battery. Been keeping minimal use today without USB charging and haven't had a reboot.
Any other ways I can confirm a bad battery?
Sent from my Nexus One using XDA App

If you can successfully boot and use the phone heavily while connected to a charger (preferrably AC charger - it can provide twice the current of USB cable), and you see no reboots - I believe that would point to your battery with a very high probability.

If phone doesn't boot...

Well, I was browsing around the market and my n5 just abruptly shut itself off. It hasn't been able to turn back on since. I've tried every key/charge/magic trick in the book so its DEAD!
Happy to jump in the RMA line at this point but was wondering if any others can confirm DEAD devices. The RMA thread is kinda full of nitpick issues but a dead device is a dead device.
This was the only discussion chain I could find on the issue but maybe someone from google will comment on dead devices. lol
https://productforums.google.com/forum/#!msg/nexus/lI6A3fA8bvw/d3eQlqEqabEJ
EDIT:
so it appears holding down both volume buttons + power while it's plugged in to the charger (not USB to PC) will temporarily boot the phone. You can then do a restore to stock and issue gets fixed. :good:

Damn. That blows.
Sent from the jaws of my Hammerhead!

mrro82 said:
Damn. That blows.
Click to expand...
Click to collapse
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Since I was able to get it booted tethered to the power I'm going to have it drain the battery to dead and see if it resets itself or something. Maybe a bad idea but I guess I don't care at this point it's already RMAd and I don't know what else to try. lol

Zenoran said:
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Click to expand...
Click to collapse
Do you have a backup you can attempt to restore?

Have you tried to adb into it?

Delete damn it

I would never install twrp.

There is a stock rom in here somewhere. Flash it boot loader and see what happens.

Synyster06Gates said:
Do you have a backup you can attempt to restore?
Click to expand...
Click to collapse
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.

Zenoran said:
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Click to expand...
Click to collapse
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701

caribouxda said:
I would never install twrp.
Click to expand...
Click to collapse
Why wouldn't you? In situations like this, it is extremely helpful. Do you expect him to install CWM or something? From my understanding, at least when I first got my phone and flash a custom recovery, CWM wasn't booting. If you are here to try and press your opinion on which custom recovery you prefer, go to their official thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app

floxrin said:
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.

Zenoran said:
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Click to expand...
Click to collapse
That's good to hear man. I couldn't imagine how I'd feel if that happened to me. Thankfully XDA us the place that it is and the members, for the most part, have the ability to help us troubleshoot most of our issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Hard Brick .... PLEASE help, I've tried everything

So, I've tried literally every video, or walkthrough I could find via youtube or this site and I am still stuck in a boot loop right now at the unlock custom screen.
I've tried using odin to go back to stock completely, i've tried the battery removal / wipe data etc option, I don't know what else to do here.
If anyone could help, I'd really appreciate it. At this point I'm pretty desperate.

Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom padlock icon?
Have you tried giving it a few minutes to boot up before pulling the battery? I thought my phone was bricked once, but all it needed was ~5 minutes to get going. Give it a good 10 minutes or so to boot up. If that doesn't work, report back with the information I requested and we'll go from there.

Face_Plant said:
Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom splash screen?
Click to expand...
Click to collapse
MJ5 ... flashing FireNote Rom
Problem I was having is I was using KnoxRaid Rom, well that rom is dead / thread locked so I figured I would try FireNote. When I rebooted to flash FireNote, I noticed Safestrap wasn't there anymore. I tried re-installing Safestrap a few times with no luck. After a factory wipe / reset, Safestrap magically re-appeared and was available for me to use. I figured what the hell, I'll flash FireNote. When I did, I noticed it was more or less a hodge-podge of the two Rom's and not a clean install. When I did the wipe again to re-install FireNote, I'm now stuck at the spash screen and have been since early this morning.

And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.

daigled said:
And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.
Click to expand...
Click to collapse
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)

BeastSpencer said:
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)
Click to expand...
Click to collapse
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?

Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Edit- here's the link: http://forum.xda-developers.com/showthread.php?t=2559715

daigled said:
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?
Click to expand...
Click to collapse
really? are you sure you followed all steps? what happened when you finished? worked for my brick

Face_Plant said:
Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Click to expand...
Click to collapse
I think you're right. I was on the KK version and FireNote is on JB.

daigled said:
I think you're right. I was on the KK version and FireNote is on JB.
Click to expand...
Click to collapse
bad idea :/

BeastSpencer said:
really? are you sure you followed all steps? what happened when you finished? worked for my brick
Click to expand...
Click to collapse
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.

Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.

daigled said:
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.
Click to expand...
Click to collapse
as a last resort, you can call at&t i guess :/
try flashing MJ5 images from sammobile.com in odin

Face_Plant said:
Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.
Click to expand...
Click to collapse
I found that thread, followed it EXACTLY and still am having the same outcome =/

Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.

Face_Plant said:
Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.
Click to expand...
Click to collapse
Ok, I'll try that next... Thanks bro, i'll check back in after and let you know.

No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.

Face_Plant said:
No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.
Click to expand...
Click to collapse
Yea, I've used different ports and only used the cable that came with it from the start.

Good. I'm betting it's a bad file or something didn't install properly that's causing your problem. I've used the MJ5 restore several times to get off of KitKat versions of Knoxraid with no problems, so I don't see why it shouldn't work for you.
Here's a tip: when you place the CSC file and the 28whatever file on your external SD card, rename them to "flash first" and "flash second" or something like that to avoid mixing them up. Renaming them won't hurt anything.

daigled said:
Yea, I've used different ports and only used the cable that came with it from the start.
Click to expand...
Click to collapse
try restoring with N900AUCECMLG_OneClickBin.exe ...i think it should work. http://forum.xda-developers.com/showthread.php?t=2619941

Battery Stuck at 100%

So after 8 hours my battery still said 100% and even shut off due to dead battery and it still said 100% full. In TWRP it also shows 100% full. Any ideas? I have it on the turbo charger now, since it died, and will wait about 2 hours then try to reset battery stats. Not sure what else to try. Nothing new installed, phone is stock other than rooted and TRWP.

This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B

Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
huh?
The phone was rooted the day I got it, Nov 9th, and it just started doing it today. So how does root automatically cause the issue?
Anyway, any ideas would be great I think resetting the batterystats has worked just curious what may have started it.

Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
I've never had issues from just rooting. Rooting a phone doesn't cause issues but rather installing root apps and changing things causes issues. I would try to flash back to stock (backup data first) and then root it again to see of that fixes it.
Also did you use CF-Autoroot or one of the tool kits?

I fixed the issue, after that battery died I let it charge for about 4 hours with the quick charger and then reset the battery stats by using an app that deletes the batterystats.bin file. Then did a reboot and now the battery level is no longer stuck on 100%.

Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.

lifeisfun said:
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
Click to expand...
Click to collapse
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.

Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
root has nothing to do with breaking your phone. all root does is give you superuser permission. what breaks phones are dirty hacks that you yourself chose to use.

danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?

lifeisfun said:
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
Click to expand...
Click to collapse
I would just put it down to "OS Confusion "

danarama said:
I would just put it down to "OS Confusion "
Click to expand...
Click to collapse
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?

lifeisfun said:
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
Click to expand...
Click to collapse
Yeah maybe battery firmware confusion. I don't know where TWRP gets its reading from.

Still Works!
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
Thanks.

[Q] Constantly reboots to blank/black desktop

My friend recently gave me her old HTC One, and I've been trying to fix it, but I can't quite figure it out.
She said it started bootlooping randomly after she plugged it in to charge. When I first received it I plugged it in and mashed the power button until it turned on. Booted up just fine. But now it's in a stupid bootloop that takes me to a blank desktop with no dock or wallpaper,and then reboots after a few minutes.
Can a battery issue cause this? A complete factory reset from recovery is not an option because I'm trying to save her photos. I don't know how I can get 11gb worth of them off when it's not booting properly.. Any ideas for fixing this or getting the photos off?

Have you tried to wipe data factory reset from recovery ?
That doesn't erase photos

Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.

rha_december said:
Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.
Click to expand...
Click to collapse
in stock recovery try and erase cache .. Don't factory reset ... everything would be gone

Ughh,... A bit too late. Lost everything and it didn't even fix my problem. Ah well. I think I need to replace the battery anyway. That, and my computer doesn't even detect the phone when I plug it in.

rha_december said:
Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.
Click to expand...
Click to collapse
Oh I'm sorry , i didn't know it was stock recovery.
I assumed custom recovery.

rahulsethi said:
Oh I'm sorry , i didn't know it was stock recovery.
I assumed custom recovery.
Click to expand...
Click to collapse
It's fine. I jumped the gun. Losing some photos had never killed anybody haha..
I should have remembered.. But I haven't done anything with Android for so long because I had been stuck with a locked S4 for a while..
Anyway, I'll replace the battery and see if that helps.

rha_december said:
It's fine. I jumped the gun. Losing some photos had never killed anybody haha..
I should have remembered.. But I haven't done anything with Android for so long because I had been stuck with a locked S4 for a while..
Anyway, I'll replace the battery and see if that helps.
Click to expand...
Click to collapse
you realize the One is a 9 out of 10 on difficulty to disassemble

clsA said:
you realize the One is a 9 out of 10 on difficulty to disassemble
Click to expand...
Click to collapse
Yeah, but I've disassembled phones before and I have faith in my hands haha.