Develop Bugs

HELP!!!!!! Rooted phone wont turn on

My rooted HTC Evo wont turn back on. it happened when i tried to flash something and my phone just turned off. i cant even get to recovery mode. Please Help!!!!

what happens when you hold vol down and power?

mrono said:
what happens when you hold vol down and power?
Click to expand...
Click to collapse
nothing happens.

Brohr said:
nothing happens.
Click to expand...
Click to collapse
What did you try to flash and explain the entire situation please
Sent from my PC36100 using XDA App

Have you pulled the battery?
Sent from my PC36100 using XDA App

=craigbailey1986;10446711]What did you try to flash and explain the entire situation please
Click to expand...
Click to collapse
the radio combo zip

Brohr said:
the radio combo zip
Click to expand...
Click to collapse
what happened after it turned off? it is normal for it to restart if flashing through the recovery but it should have came back afterward

xHausx said:
what happened after it turned off? it is normal for it to restart if flashing through the recovery but it should have came back afterward
Click to expand...
Click to collapse
it just turned off and it never came back on. it never happened to me before

Brohr said:
it just turned off and it never came back on. it never happened to me before
Click to expand...
Click to collapse
do any of the leds work? If your battery completely dies the red light should start flashing when you try to turn it on

xHausx said:
do any of the leds work? If your battery completely dies the red light should start flashing when you try to turn it on
Click to expand...
Click to collapse
nothing works

Brohr said:
nothing works
Click to expand...
Click to collapse
can you give a little bit more info like what exactly you where flashing, what you were using to flash it with etc
In the mean time try pulling the battery and letting it sit for awhile or using a spare/batt charger if you have one

Did you happen to pull your battery while trying to flash the updated radios??
If so head down to sprint and just tell them your phone won't come on..... because its officially bricked!
Sent from my PC36100 using XDA App

took my phone to the sprint store and i am getting a new phone in 4 days.

What should i do with my brick?

So, i think i bricked my device. Downloaded caulkin rom and tried to flash it. when i booted into rogue rootbloater i flashed the rom from my downloads. my bad. why does it matter though whether or not i flash from internal or external memory. annnd ?

It doesnt matter if the rom is in the internal or sd unless dev says something about it in op. As far as your brick, im not understanding fully what you mean
Sent from my SPH-D710 using xda premium

What makes you think you're bricked? What happens when you try to power the phone on?

Rob4828 said:
It doesnt matter if the rom is in the internal or sd unless dev says something about it in op. As far as your brick, im not understanding fully what you mean
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
If I would have had a sd i would not have a brick right now though :/
I think. cause the new rom switched bootloaders and the new one only recog'ed the sd i think.

undefine4 said:
So, i think i bricked my device. Downloaded caulkin rom and tried to flash it. when i booted into rogue rootbloater i flashed the rom from my downloads. my bad. why does it matter though whether or not i flash from internal or external memory. annnd ?
Click to expand...
Click to collapse
what happens when you try to boot your phone?

_MetalHead_ said:
What makes you think you're bricked? What happens when you try to power the phone on?
Click to expand...
Click to collapse
It means my phone is locked in a "permanent" state of existence.

undefine4 said:
It means my phone is locked in a "permanent" state of existence.
Click to expand...
Click to collapse
so lets say after you pull battery you press the power button....nothing happens?

Pull the battery
Put it back in
press power and see what happens
-- You can also...
Pull the battery
Put the battery back in
press vol down + power and try to get into odin mode
If you can get into Odin mode, then you're not bricked.

no phone - cake.

undefine4 said:
no phone - cake.
Click to expand...
Click to collapse
Do you speak English ? They have ask what happens when you power on the phone and you respond with idiot junk .... Congratulations throw your phone out of a moving car jack a$$
Sent from my SPH-D710 using xda premium

undefine4 said:
no phone - cake.
Click to expand...
Click to collapse
Do you want help or not? The E4GT is a very difficult phone to brick and 9 times out of 10 when a noob thinks their phone is bricked, it's actually easily recoverable. But if you don't help us help you, you might as well just toss the phone down the garbage disposal.
Can you get into download mode?

Hahhahhahahahaa that's all I wanna say
Sent from my SPH-D710 using Tapatalk

Lol if you don't want to be helped then sell the phone to me. Should the bidding be started at ummm lets say $20.
$20 is a very expensive paperweight I think I'm offering more then enough lol
Epic 4G Touch perfected by Calk!

I think we're being trolled.

Great add one more thread that made me dumber for reading it. Stop it guys the last thing I need more of is dumb.
Sent from my SPH-D710 using Tapatalk

_MetalHead_ said:
I think we're being trolled.
Click to expand...
Click to collapse
We got samsunged
Sent from my SPH-D710 using Tapatalk

35$
10char...

Oh so you didnt want actual help, great thread OP.
Sent from my Galaxy Tab 10.1 using XDA Premium HD app

Is this sextape's way of leaking a new FC** ICS ROM?

sfhub said:
Is this sextape's way of leaking a new FC** ICS ROM?
Click to expand...
Click to collapse
LMFAO ha +1 made my day. Still, I think it must be hard to drop to this level of brain capacity.

Splash top 2 brick?

Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?

Its bricked?
So you put it in the trash or sent it back to ASUS?

I'm going to go out on a limb here and say this is not related to splashtop.

I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.

Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium

tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium

Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium

Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.

Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...

sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.

PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.

my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:

Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.

xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:

Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?

Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers

I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.

qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.

Phone keeps resetting randomly

Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.

okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.

How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA

Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium

Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium

Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA

Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!

What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2

Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA

Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA

g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app

You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817

tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.

Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).

Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.

milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium

[HELP!!] Might be Sudden Death Issue not sure

Hi my new Note II has just decided to reboot and it's sitting on the Samsung Logo. I'm only running the stock ROM. It's been sitting there for 10minutes now. I'm worried it might be SDS but I don't want to take battery out and reboot it as I'm scared it could be? it wouldn't be automatic updates? They don't take that long do they??
Someone help please!

DaBountyHunter said:
Hi my new Note II has just decided to reboot and it's sitting on the Samsung Logo. I'm only running the stock ROM. It's been sitting there for 10minutes now. I'm worried it might be SDS but I don't want to take battery out and reboot it as I'm scared it could be? it wouldn't be automatic updates? They don't take that long do they??
Someone help please!
Click to expand...
Click to collapse
If it was sudden death you wouldn't even see Samsung logo.
Sent from my GT-N7100 using xda premium

rodrigoyasuda said:
If it was sudden death you wouldn't even see Samsung logo.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
An update shouldn't take this long right? It's been 15minutes like this. I haven't flashed anything on the device only run Expynos abuse to root it and put Xposed framework for multi app but that's it. Nothing else. Guess it softbricked itself somehow wtf?
EDIT: I took battery out and put it back in and rebooted. It's back!! but why the hell did it do this??

DaBountyHunter said:
An update shouldn't take this long right? It's been 15minutes like this. I haven't flashed anything on the device only run Expynos abuse to root it and put Xposed framework for multi app but that's it. Nothing else. Guess it softbricked itself somehow wtf?
Click to expand...
Click to collapse
I don't know what happened there but 15 minutes is a lot of time. You'll probably need to remove your battery or hold power button until it reboots.
If it still gets stuck on samsung logo you'll probably need to wipe
Sent from my GT-N7100 using xda premium

rodrigoyasuda said:
I don't know what happened there but 15 minutes is a lot of time. You'll probably need to remove your battery or hold power button until it reboots.
If it still gets stuck on samsung logo you'll probably need to wipe
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
That's what I was thinking hmm.