Develop Bugs

[Q] Phone wll not power on into any mode.

Hello. I am running SyndicateRom 1.1.0. I have been experiencing no problems with it. However, while attempting to watch a flash video in a website recently, the phone became unresponsive. Somehow I managed to get the power context menu up, and decided to reboot the phone this way rather than a battery pull. However, the phone is now powered off and will not power on back into the ROM, or for that matter anything; Download Mode, Recovery, will not even show the battery icon if plugged in.
I'm freaking out more than a bit. I'm well aware of how to restore my phone using odin and other tools, But if I can't even get out of a powered off state, I have no idea what to do. I'm also very confused as i was not doing anything particularly dangerous at the time with odin or flashing a ROM or anything. Any help at all would be sincerely appreciated.

Were you running Vision Kernal 1.2?
http://forum.xda-developers.com/showthread.php?t=1042552

nikon120 said:
Were you running Vision Kernal 1.2?
http://forum.xda-developers.com/showthread.php?t=1042552
Click to expand...
Click to collapse
I may have been actually. I believe I saw a post sometime last week (In the ACS main thread, in the OP first post) To try that kernel if you were having problems with crashes.... worked great -.-.

Yeah found the recommendation in the 1.1.0 Changelog where i saw it and followed it...
known bug (kernel): limited numbers of users experience freezes, IF YOU GET FREEZES, READ THIS OR TRY VISIONKERNEL

Sprint will replace it. Tell them you shut the phone off and will not come back on....that is all. Most phones were being replaced for free but there new policy is $35 worst case.
Do you BONSAI?

Evo Issues Random Restarting and Freezing Power button not turning on Screen

I've been having issues with the phone turning off randomly and restarting, seems to do it when it gets hot. Also the phone not responding to power button. Doesn't matter which rom I flash it keeps happening. Thinking about converting back to stock to see if it helps. But I'm unsure why this started happening all the sudden any one else have similar issues??

How often is it happening? Often enough that you may be able to troubleshoot it? Such as.. turn of gps, mobile data, sync, then slowly add them back in one at a time to see what could be causing the problem.
Swyped from my Raided Evo

Also, are you under clocking or over clocking your kernel?
Swyped from my Raided Evo

My wife's Evo had that exact same problem, but hers is unrooted. We brought it into Sprint and she's getting a brand new phone tonight. They tried running diagnostics on it, but came up with nothing, so that was their last resort...

This seems to only happen to me on aosp roms and not sense.
Sent from my PC36100

[Q] My boot loops don't taste good...with or without milk...what is the reason?
My real questions are:
Has anybody experienced my experience and how did they solve the issue?
and
Can someone help me diagnose the issue?
I am seeking help on this topic also.
I have battled and one once before but don't know what was the actual fix.
I tried in the past, couple weeks ago, to upgrade to the new 2.3 roms and have had a lot of trouble with the ol' "random reboots". I don't recall what rom exactly that I tried to put on there but I don't believe that the rom was the issue in this situation do to flashing other roms and encountering the exact same reboot issues.
I originally undervolted using vipermod, updated to the new radios from the present "All Radios" post that was grouped together and then flashed a kernal over the rom that I was trying to use.
I got it booted up no problem, went through the setup and then when it was trying to get the reception and/or 3g established it rebooted...the white HTC boot screen appeared and rebooted over and over again.
I tried reflashing the rom, flashing a different rom and so on.
I sort of ruled out the radios after downgrading them and not getting any different results and started to think it was an overheating issue because when I would leave it off for a while it would work longer before the boot party began.
I read something on another thread that when you remove the battery for so long and boot it back up, it clears the internal memory or something similar to that. I searched the market for a boot logger program and found bootlog, I believe that was the name, and checked the log after pulling the battery and letting it boot up all the way. After reviewing the log I noticed that it had stuff like lowmem, deathpening, killing and what not. I then came to the conclusion that it was more than likely the memory, not a clue if it is internal or talking about the temporary stuff that it may store on the sdcard.
I then decided to check out the partitioning of the sdcard. I decided to raise the swap to something like 1 gig and the ext to 2 gig.
I loaded up CM7, nothing extra, and all was good besides maybe one or two reboots that ended up booting all the way up instead of doing the loop at the white HTC screen.
But now, I followed the instructions that was left on http://forum.xda-developers.com/showthread.php?t=1071547&page=1161 (no blame to the post or rom, just a reference) so I can try out a new sense rom...and...if you don't know by now...mayhem/boot loops. I cannot upload any of the logs because I followed the partition instructions.
I have upgraded and downgraded the PRI and the radios with no luck, I am now going to try the partition swap size again and report back.
I am writing this prior so I can get some helpful suggestions coming my way in the mean time, in case me and the Captain can't make this happen, or be able to post my method to fix my scenario so others may benefit.
Thanks in advance.
EDIT: I have S-OFF, HBOOT 0.97, radio 2.15.00.11.19

I still have been having tons of issues and I've gone back to roms I ran 6 months ago n still having the same problem. It just randomly shuts off and turns back on sometimes like 5 or 6 times in a row. This is getting very frustrating I'm gonna have to put it back to stock and take it in. I want to smash my evo with a hammer and then blow torch the sh*t out of it.

I'm having the same problem, only with the Inspire 4G though. I notice mine only happens when the screen turns off.. I'm thinking mine might be an underclocking issue or something because if I have an unread message or if the led is on or flashing at all, it works fine.. Wait, no, it just did it again fml

This is why I dont want to upgrade my radios, you say you ruled out those, but your phone is still jackin up on old roms.
It jus seems I never see an issue that cant be solved by reflashing the rom or a redownload the rom and flash, unless......you mess with the radios, then u get issues like this..im no expert, but this is what I see.
....Radios scare me!
If it was me I would proly unroot it and bring it in, or
Copy SD card to your PC.
Format SD.
Run an RUU that matches your original radios.
Copy SD card data back.
Re-root.
Should be brand new then....
EDIT: Scratch that I wouldnt unroot and bring it in. Easier to runn the RUU like I said
Sent from my PC36100 using XDA App

Never flashed a radio unless a rom came packaged with one... Couldn't tell you which one because I've flashed a bunch already seeing if that was the problem or not. I'm partitioning my SD card right now to see if that helps.. Oh, and I bought my phone off eBay cause AT&T sucks at life and it's not a year wait anymore to upgrade. God how I miss Cingular.

Think i figured it out on my end... I don't think my phone likes to be underclocked so I bumped up the mhz a little for screen off and I haven't had a problem yet
Sent from my HTC Desire HD using XDA Premium App

Again I spoke too soon

URGENT help with boot screen, how to log it?

[Warming up]
I've been having problems lately trying to figure out the problem..
So, first i suspected the SD card, doesn't seem like my original 16GB card was the problem, because i bought 2 new 32GB Micro SDHC cards already, same problem..
[Now the problem]
80% of the times when i reboot and go into recovery and flash a couple of roms, or reboots in general, i for the most part get stuck in Bootscreen, if i try to wipe Cache and Dalvik-Cache, it sometimes solves the problem and 20% of the times i can get into the system, the other 80% of the times that i actually succeed into getting the rom to load up, i mostly get stuck there aswell, untill it reboots the phone, and im back at the imfamous bootscreen...
So, i've figured, is there anyway for me to log the stuff that is happening at the boot screen? because im curious to what the problem might be..
[The things i've done already]
Everything is formated as EXT4, and has been so since Mike introduced it with his rom..
i've tried Mikes rom, Unity, Honey roms, Coredroid, RCmix, all the same on all of them.
I always wipe my phone fully before i boot the rom, mostly with Mikes Super Wipe Script, but sometimes with the wipe zip mentioned from the Rom Dev explicitly telling me to use that..
I always let the rom boot 2 times before i start flashing themes and stuff..
Just going Stock rom doesn't help either, i've tried that aswell, no change.
I've cleaned the phone, from top to toe.. (brushed and cleaned with special liquid)
I've tried different Micro SDHC cards, 1 of em was a counterfeit card, the newest one works just flawlessly, i've benchmarked, checked for errors and even done a Bluff check on it, all working 100% nominal.
CPU running at 998Mhz, just incase..
[Ending]
So, does anyone have any suggestions?.. Does anyone have any way for me to get logs of the Bootscreen (as its a wallpaper, i have no chance in actually seeing what is happening)
Are there any ADB commands i could use to check errors in bootscreen? Any diagnostics tests?
Maybe even a way to refresh the Bootloader with ADB commands?..
ANY help would be greatly appreciated!!

You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD

drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Have to agree on that
Do you still have warranty?

drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Thanks man, very much appreciated!
I'll run some logs tomorrow and see whats up with the phone, i actually got the phone running optimal again with yet another fresh rom flash and it all seems to work, have only restarted the phone 2 times, as im afraid of restarting the phone and get stuck again..
If i do get stuck, im stuck forever, and have to try above mentions i've done before, wipe cache and dalvik-cache, sometimes this works, most of the times it doesn't, and i end up fully wiping a couple of times and reflashing roms untill it works.. (I know this might sound like an SD card problem, but its not, i've gone thrue this with a couple of programs)
Anyway, a thousand thanks for that link, will probably help me quiet some..
madmaxx82 said:
Have to agree on that
Do you still have warranty?
Click to expand...
Click to collapse
Aye, this phone i have in my hands right now has already been in for repairs before and they changed the PCB of the phone, got a new IMEI number and all that..
But i do have warranty left for it, but i have to iron out the problem before i send it in, don't wanna risk being sent back to me and i have to pay lots of $ for their trouble (you know how HTC 3rd party repair centers works).. Plus they might actually scratch my screen some more as they did when i last sent it in...
Well, i have another "minor" problem with the phone aswell, not sure if its my phone or a general new cosmetic problem occurring on phones sent in for repairs, as i haven't noticed it on my earlier phone (Well theoretically the same phone).. Is that when i look at the screen in pitch black moving screens, i can see a distinct line going from Top Right to Bottom Left corner, and the Top Left side of the screen is black, and the lower right part of the screen is black/grey, you can see the difference, but not noticeable when your actually booted up, only in the Bootanimation part is it visible, i've tried different Bootanimations and everyone that has a Black background has this cosmetically problem.
Aah crap, Wall of text..

Haha just gonna add that i installed both apps you mentioned earlier, and the phone feels more like a Dev phone now, but anyway, it all worked great, not sure if it logged anything yet, didnt find anything in the app yet if it does..
I noticed something strange though, Gsensor Enabled, then right before bootup, Gsensor Disabled..
Have no idea why it does that, have no problem with Gsensor though..
Edit:
6 successful restarts!! That's something new!
I have no idea why its behaving this good.. Well time will tell..

[Q] Connection issues with pc

Okay so here is the deal. I just picked this sweet Epic up and started rooting it and I can't get it connected to the pc to get into the files. I set the phone to debugging, and even tried it with it off as well, then I connected the usb (and yes I tried alt cords too) to the pc and selected mass storage (I tried charging too). The pc says it's installing the drivers and even says completed and ready to use but on my computer screen it only shows my hard drive . I downloaded the starter sdk and tried those drivers as well. Even though I could not get it to recognize I started Odin and while phone was on it showed 2 ports, but once I turned the phone off and set it to download mode I get zero, zip, nada for ports available. Now I did see somewhere to set the code back to PDA and top to Modem so I did that as well. Still no luck. I am running stock Froyo EC05 2.2.1 and 2.6.32.9 kernel. Can someone please help me out? I had a Moment before this and never this many issues. Is there a way to just put the card in a reader and install the files and then put it back in my phone and run recovery from there? I've never had to do that before so I was wondering if it's an option if I can't fix this. Last thing is the charging time is way long and the hold isn't lasting long either. I'm no expert or developer, but I'm flashed many ROMs on my moment so I guess you can say I know a little. Please no tech jargon/lingo though to prevent unnecessary communication issues. Suggestions on GB ROMs would be nice too. I tried RandomKing but the links were no good. I hate the stock garbage on there and would love it if someone could help me get them off so I can continue with my rooting agenda.

Try with USB debugging on, connect to the computer then go into control panel and device manager, find phone entry, probably samsung android, then hit update drivers from Windows Update. Takes a while to load all drivers, sometimes more than 30 minutes. Then reboot computer and phone and try it.
As for ROMs they are ALL good. Read the description of each to find out what's in it and if you like it, try it.
Sent from my SPH-D700 using XDA App

Thanks for the reply. I tried that (unknown device) but I just keep getting windows has decided your driver is the best message when I even disabled, re-enabled, removed and re-installed all drivers. It's really bugging me and I'm not one to give up but I spent over 6 hours on this last night and I'm stumped. BTW what 2.3 ROMs do you know of that are stable with the least issues? Just suggestions of course as everyone has their own style...

Stick to the EG22 ROMs since EH06 and EH17 caused many phones to random reboot. After a few days EH17 started disconnected my calls. I have been using a ROM not listed on XDA. It is Bonsai B14 EG22 based. You can google Bonsai Android or click my signature. There are a few good ones in the development section here too.
Sounds like it is definitely a driver issue. There are samsung drivers floating around here. If you don't find a working set I will hunt them down tonight for you.
Sent from my SPH-D700 using XDA App

You can try the drivers in the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1052813

Thanks...
Cool I will try that out when I get home since work computers are usb restricted
Thanks for all your help and I'll update you tomorrow.
By the way I was playing a HD game on it today while charging and I got a charging paused, battery too hot or cold... Is this a problem with the EG22 build?

Another thing to make sure of is if your dial ##8778# it will bring up a menu, make sure your device is on pda.. believe it or not this helps some people
* PDA should be selcted under the USB Section.. the other section should be on modem
Sent from my old but still kickin Epic 4g

Yeah that's what I was talking about that I tried.
Now I did see somewhere to set the code back to PDA and top to Modem so I did that as well.
Click to expand...
Click to collapse

rooted!!!
Got Odin working and downloading now... Had to sneek my laptop into work to get her done but... LOL... Now time to get rooting!!!
Thanx guys... Will let you know what ROM I went with later today...
Working on putting on 2.3.4 EG22 v. Alpha "Hawk" [Journaled] EG22 AIO Volume/Hotspot/Lockscreen/Overscroll/Lag Fix but the download is taking over 2 hrs!

Phone isd not working at all now...
I put it through Odin and was following the prompts on the odin page that said to put victory_8G_100528.pit in pit and the tar in, hit start it went through and said something about partition and then the phone shut off and never came back on. It won't even charge now... NO life at all.

Fixed...
Okay I took the battery and sd card out, and then plugged the usb in while holding 1 & power down. That put it into download mode. From there I just put the battery and card back in and installed clockwork. BTW the only cord that would work was the one that came with the phone. Took me 12 hr to figure that one out because all the forums said to not use it. UGH
Thanks for all the help.

Also watch out for launchers that hide you notification bar, this can bork USB/sdcard detection, I just made a tip thread.

smartbeatz said:
Okay I took the battery and sd card out, and then plugged the usb in while holding 1 & power down. That put it into download mode. From there I just put the battery and card back in and installed clockwork. BTW the only cord that would work was the one that came with the phone. Took me 12 hr to figure that one out because all the forums said to not use it. UGH
Thanks for all the help.
Click to expand...
Click to collapse
There is a manufacturers cord that is the same connector but doesn't work, not sure which one but I use my old Palm Pre cable and a lot of others use Blackberry cables.

Oh so nice
Okay the new ROM is running great and is oh so sexy, fast and powerful, although I do not like the home page dock layout. I see no issues yet and I'm switching back to the Epic today after I beef up my old moment (which I had swapped to for the day because I thought I soft bricked the Epic beyond recovery) I promised to my mom. I'd like to find a stable GB build for her too but it doesn't look like the programmers have figured that one out yet.
BTW the cord I have is the one that looks a little weird on the end you plug into the phone and seems to be real stiff. I got more phones to mess with so thanks all...
Anyone know of any good tutorial sites that teaches how to develop and write codes? Flashing is one thing but getting to know the nuts and bolts to help others out is where I want to be.

Galaxy S3 bricked... sometimes??

So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?

I agree with your assessments.

I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app

what's your setup as of right now?

Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%

It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.

I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure

mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2

I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.

I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki