Develop Bugs

White screen of death

Hello everybody,
I seem to have a major problem with my XDA Orbit: Not only it shuts down with no apparent reason so that I have to reset it, but it shows sometimes the dreaded "white screen of death" - from now on "WHISOD". The screen all of the sudden slowly goes white and sometimes shows dark vertical bands. After that - if I am lucky - I can reset the device, however a couple of times I already had to hard reset end even reflash it.
I have already checked software and plugin problems and would rather say that it seems to be a hardware problem. Any ideas out there. They would be highly appreciated.
Best regards,
Smack

i had the same problem and as at now my phone is dead becuase i did not flash it with the original rom. look for the rom it came with and flash it to the phone ,like how u first got the phone or u will loos ur phone very soon

I am not at all sure if it has to do with the ROM. I have tried different ROMs to check the error but it appeared with all of them. However the next time I will try again with the latest official ROM.
Thanks for the comment and your help. BTW Did you send your Orbit in for repair?
Regards,
Smack

Hi, do you use the uspl before every new rom install? Try it.
I have the same problem, my htc3300 is almost dead I think. No way I can even turn it on, allways end in the windows screen, and it was because I didn`t use the uspl before last rom install.
Give it a try, and let us know.
See ya.

Thanks. No flashing problem. I have flashed a couple of devices (always unlocking them before ;-) )and have had no problems whatsoever.
The problem I mentioned is not connected to any earlier flashing. The device works a couple of hours perfectly. However suddenly it starts to behave like crazy.
Now to your problem: If you can get into boot loader modus you will most probably be able to unlock your item. Search for uspl and download it. Then get into boot loader mode (press voice recorder button and power button while resetting the device) and you will get a three colored screen. Then connect the USB cable. You will see "usb" in small fonts on the screen of the device. Now you can run uspl. With a little luck the device starts again. However you can flash it again with a fresh ROM the same way (after unlocking it). This may (!) work.
Regards,
Smack

Hello,
I have the same problem, I already hard reset end even reflash my p3300 many times with different ROM.
I even tried running it for some time with and without the micro SD, ending with the same result: the screen of death.
Any ideas , tips, anyone ?
Thanks,
Roundi

Ok, I tried the following: Just take the battery out for six or seven hours and insert it again. The device seems to run smoother. Will keep you posted. Tell me if it works out for you.
Regards,
Smack

Ok, just removed the battery, I will leave till tomorrow morning.
I will keep you updated.
Thanks,
Roundi.

I have same problem here - though mine is the second phone and the fifth motherboard I've had. HTC just don't seem to able to fix it. I'm now trying to get a refund.

Hi, Jem.
Yes that's something I have thought about too. Did you you use the original ROM? However right now the system seems to be more stable. I have had only one blank screen after removing the battery (and one shut down).
Regards,
Smack

I have just put in the battery and switched on the phone after almost 24h.
So far so good.... I will try to use it for a while and will let you know.
Regards,
Roundi

Had the same problem again, when using Mortplayer. I have Mortplayer installed on the SD card. Could it be that the problems arise, when there is heavy usage of the SD Card?
Any ideas are welcome.
Regards,
Smack

Again it went SOD shortly after turning it on. I didn't launch any applications.
I am stuck here.....

Device start up failed due to sudden loss of power.

I have an extra Excalibur with the official T Mobile WM6 rom that isn't working. When I turn the phone on, I get a screen with a white background, red text, and blue soft key buttons that reads:
Device start up failed dueto s
udden loss of power. Please c
lick "yes" to continue.
Note:
Do not remove battery be
fore device has been comple
tely shutdown (OFF).
Yes | No
If I press yes the phone does a power cycle and hangs at either the T Mobile splash screen or the WM6 splash screen. I've had no luck with a hard reset. Anybody familiar with this issue? It isn't a huge deal. Currently I'm using a Cavalier and I also have a working Excalibur and a working Wizard, both with 6.1 roms. However, it's be nice to get this phone working.

Only time I ever seen that error is when I ws messing with editing a ROM and must of removed a file that screwed WM up. Now since you say it's the official T-Mo ROM maybe it got currupted somehow. How I fixed it was the Hard Reset the USB way. Hold down the camera button while plugging in the USB with the cell off. It'll load the boat loader and you need to reflash with an official ROM. Now I know you said you Hard Reset, but I've seen people explain a few differents methods all being explained as Hard resetting. This method worked for me during my testing.

I'm flashing the original rom and everything seems to be working alright.
I really appreciate your help man.

Okay, I wish I had better news but I'm still running into problems. After I finished installing the rom from T-MO's website, I powered the phone on. It showed the T-Mo screen, then the WM6 Screen, then played the T-Mo animation/sound. The screen stuck here, and the phone would not power off so I removed the battery and put it back in. I then got the original error message and pressed yes, and the phone lagged at the same point again.

how long did you wait for fist boot?

rickwyatt said:
how long did you wait for fist boot?
Click to expand...
Click to collapse
Like Ricky said, how long did you wait? The first boot could take a while, the flash is going to perform a "Cold Boot Config". It take a bit longer that first time to load.

I actually got it to prompt me for cold boot config once, but after finishing the phone rebooted and hung once again.

I don't know, maybe you got a hardware problem. I'd try reflashing it again and when it boots the first time don't touch it and see what happens. If it hangs for more then say 10 mins. I'd say you might be having a hardware problem.

Hmm. I guess I most definitely have a hardware problem. An error of that sort would most likely be from a faulty motherboard, correct? I have a dash that was taken into the lake not too long ago. Everything recovered okay, other than the screen. The phone no longer turns on for a completely different reason, but I think the guts are mostly good.
Is it possible to change out motherboards? If so, is it unwise to try the motherboard that went swimming with me over the summer?

Well considering neither work, what do you have to loose? lol I say try swapping aprts and see what comes of it. I have seen cells "go swimming before and servive as long as the battery is removed right away and it's allowed to dry thoroughly. They don't opperate on much voltage so short curcuits due to water is not as bad as say a 12 volt or higher device.

Also, I forgot to mention the status on the phone. Okay, I can flash an official ROM and it will boot up and run Cold Boot Config. After that the phone will power cycle. It hangs a little bit at the T-Mo splash screen, but does eventually start. At that point it basically works flawlessly, except I cannot detect it through ActiveSync via USB.
Once the phone powers off, it will not turn back on. I don't get the original error message, just nothing happens. Only way to get the phone turned on again is to hold the camera button down while plugging in the USB cord, and start all over flashing an official ROM.

Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.

drkfngthdragnlrd said:
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
Click to expand...
Click to collapse
That's exactly what i'm thinking too, sounds like a hardware error as a flash wont solve it.

So what piece of hardware is the most likely culprit?

I never took mine apart, but I would say it's the ROM Chip which should be soldered to the motherboard. If it is replace the whole motherboard...

t mobile dash
so when holding down the camera key and plug the usb do i try to also turn it on what am i looking for and how long do i hold the keys down
thank you

Anyone afraid of NAND flashing is a wuss. Check this out, its so easy..

These Instructions are out of date, and may not work anymore.
-CarComp
EDIT POST ON 5-5-2010
INSTRUCTIONS ARE IN BOLD!!!!!!!
EDITS AND MY OPINIONS ARE IN ITALICS
Want google and not winmo but can't wade through all of the confusion offered up by the supergeeks of android linux? Well just do these steps. It took me an evening to figure out these steps, and could whip it up instantly now.
BTW - it REALLY helps to have a computer with an SDcard slot adapter that handles the micro-sd cards. I don't really recommend trying all this with a USB cable, b/c once you get to linux only, you will kinda be screwed cause it doesn't quite work the same like windows CE. Also that and you can't format through the phone, so just get an adapter ok? Stop right here if you don't have one and just order one or go to walmart and spend 10 bucks and get one. BTW, your micro sd card should have come with one when you bought it, so go look for it.
Ok how to get the super Eclair android into NAND and live a happy life....
1, CHARGE YOUR PHONE UP ALL THE WAY BEFORE ANYTHING. When done charging, unplug whatever is in your USB port for the rest of this procedure. Having phone plugged in while flashing = BAD
2, get hard spl on your phone.
3, Install Hyperdragon IOlite on your phone to get the radio(1.65.24.36) that I recommend, which will improve battery life and possibly other things that I don't know about. Get it here -> http://sakajati.com/blogs/2009/02/hyperdragon-iv-iolite-based-on-htc-iolite/
4, format your 1+ GB sdcard using fat32 only.
5, download polyrhythmics dark / light build for nand and sdcard.
put that SINGLE FILE (androidinstall.tgz) into a folder in the root of the SD-CARD called "andboot" - Get it here -> http://forum.xda-developers.com/showthread.php?t=600154
6, go to http://sourceforge.net/projects/androidhtc/files/ and download KAISIMG-PANEL2-320-TILT.NBH if you have an ATT tilt. If you have something else, download that NBH.
7, Rename that NBH file to "KAISimg.nbh". Put it in the root of your storage card.
8. Now you are ready to install to nand. Get out your stylus, hold down the camera and power button and press the reset button with the stylus. It should go to an updating screen. If you don't get a white screen with a progress bar, but instead it still shows tri color and says "serial" then you did something wrong. Start over from step 1. Once you get to 100%, wait 20 seconds or something (just for shihtz and giggles) and then pull out the battery.
9. Now, put it back in, press power and wait for android to start booting. You will know cause all this random looking text will go by. You have to be quick to do it, but press the middle button on the d-pad when it says 'press the middle button to enter setup' or soemthing like that. (EDIT: I've been told that you have to just hold the d-pad center button down. Either way, just get that button pushed when it says to push it).
You will be presented with some options. Make sure the little asterisk is on the "NAND" option.
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.
Crap your pants at the speed NAND offers. Install some live desktops (I like the starfield warp drive one from the google market.)
BTW: If you mess up your phone doing this, blah blah its not my fault blah blah you probably shouldn't be on these forums etc. Just make sure you have HardSPL and you will be fine. I've flashed hundreds of roms hundreds of times. Just that one little step will make your life easier.
EDIT:
RADIO DETAILS:
I've heard a LOT about using the latest radio or whatever version 1.71 or soemthing. I run radio 1.65 just fine. I never upgraded it through out all of the android builds. I operate like this.. If you weren't having cell quality issues, GPS lock issues, or any other radio issues in WINMO, then android will be fine too. I've added a step to the process to install a specific winMO rom that has the radio that I use. If you don't like the fact that I'm telling people to use an older radio, so be it. I'm just spreading the word for what works REALLY well for me.
EDIT: (My thoughts on the panel 1 2 3 and the 320 or 428 or whatever...) Picking the right panel is like playing the 'cups and ball' game. if you know which one the ball is under, you will win. Well for you TILT users, the ball is under #2. I don't know why, but it is. If 2 doesn't work, use 1. Doesn't get simpler than that. As for the resolutions, just use the 320. Ya, some apps fit better on the higher res, but our screens don't support them really well, and its all blurry. Think of it like this..... using 4xx instead of 320 is like asking 3 pixels to display as 1, vs. one pixel displaying as one pixel very clearly. Polyrhymic has done a great job supporting our screen's native 320 size, so just use it.
EDIT: (An issue i've noticed with booting and having your phone plugged in). Android just won't do it on nand. You can charge your phone from a dead point for say 20 mins, unplug it, then turn it on, boot android then plug it back in. You can't plug it in, and turn it on. It gets stuck in some sort of USB status loop.
EDIT: (When your phone just sits there on the A N D R O I D text and won't boot). Seems like this has been happening a lot, for me too. I've found there are two ways to stop this, one is preventative... Don't let your phone go totally dead. The second, when you reboot your phone, press and hold dpad center, then just count to 10 and go to the QUIT option. 9 times out of 10 it will boot right up.
IF YOU HAVE ANY PROBLEMS, JUST REPEAT THE PROCESS.. Don't skip the full charge and installation of Hyperdragon first.

for may people on here, the fear of flashing isn't the problem. it's the missing features such as bluetooth, speakerphone and in some builds even camera.
I would LOVE to go nand. I hate not knowing if the problem is with the build or with the sucky sdcard.
but I need to revert back to winmo for bluetooth headset. once that or speakerphone works I am ON IT.

Nice, couldn't have said it better myself, a few small points, press and HOLD the centre button on Dpad, a quick press will not do it, I'd mention the radio version too, but those are not major issues, and can be sorted easily enough
Good advice about the card reader and adaptor, those two saved my ass a few times in the early days of Nand flashing, I keep a good stock winmo kaisimg.nbh on a spare SD card, you only need a 128Mb one for a stock rom.
Yes there are install instructions on the build posts, but a lot of the info is now spread though some 2000+ posts, so having it all in easy terms helps a load.

I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!

added info about panel stuff to the instructions

It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))

my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...

Disturbed21 said:
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
Click to expand...
Click to collapse
agreed, currently no gps working map that can be rely such as garmin that can work on winmo.. 1 disadvantage of android.. need to be online to get route..

Kurt Cobain said:
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
Click to expand...
Click to collapse
320-428-480 là chỉ độ phân giải đó bạn.
320 is a resolution of 240X320 and the 480 is a resolution of 320X480
Mình biết được chừng đó thôi

Created another edit to the 1st post.
I'm not saying that android doesn't have its shortcomings, I'm just offering a quick means to get to NAND without trying to comprehend the whole thing in the traditional sense of reading 200 threads.
BTW my radio is 1.65.24.36
Maranevin, try flashing Hyperdragon IOlite first. Maybe a radio switch will prod your phone into the correct direction.

Errr, for newbs who don't know how to properly unlock their device isn't this dangerous? There IS a possibility of bricking your phone if you don't know what you're doing -- right?
Anyway, I would also mention that if you or your phone can't do 3G don't flash to NAND yet. The radio can't be instructed to use GSM only with the current poly build (and any other I have tried so far)

I totally agree with mnjm9b, the problem is not flash the phone, the problem is that there are many things that do not. In particular I am very happy with the performance of 2.1g polymod to date is the best I've worked.
carcomp thanks for the help, very good summary.

aikeru, if someone is flashing a phone, they probably know the risks. Its not my fault if they do something stupid. Is it autozone's fault if I buy specialty tools and ruin my engine changing a timing chain?
Anyways, I don't get the 3g thing. We have hardly any 2g or whatever is below 3g here in Mulberry Indiana and my android works fine.
Like I said, maybe i've found that magic mix of things that works really darn good.
BTW: major argument for using android.....
First of all, i'm not borg. I have yet to really get into bluetooth. I own two earpieces and the only good thing i've found is you can talk on the phone in freezing weather with you hands in your pockets. Bluetooth to mute car radios is cool, but I have a 20 year old car. I don't need bluetooth for file transfer cause i've got wifi, and SD CARD.
Second, as for the speakerphone, it never really was that loud anyways. I came from a hermes, which has a speaker like the voice of god, so i've never been impressed with the kaiser speakerphone.
Third, the camera... I have a nikon D60 with a speedlight for taking stills and lowlights, and a Kodak Z612 in my wife's purse most all the time for the past 3 years for video and spot shooting. All this data easily goes onto the micro sd card and into the phone.....

carcomp said:
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.[/B]
Click to expand...
Click to collapse
I've done all step above, just when i did this After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power. it started back to Step 9 when i had to 'press the middle button to enter setup'.
So, i skipped that step, and then later everytime i tried to press reset button, the phone is freeze, then i had to started over again...
In some cases, my OK button became to POWER button...
And at first time, WIFI was OK, then it showed Unable to start Wi-Fi
Any suggestion for my troubles?
Thank you!!

Great!!
Hi all, Great!! I am now running Android on my kaiser and I love it!!!
Just a couple of questions for people who can answer them:
- How to change phisycal keyboard layout? I mean, some keys that I have in blue aren't the same I have on my keyboard...
- Is there any means to connect to a pc to transfer contacts and files?
Thank you all!!
Gnatto

Maranevim said:
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Click to expand...
Click to collapse
Same problem here. Someone please help. My device is now a worthless brick!!!!

Ok when this happens (its happened to me), first of all don't panick. If you've installed hardspl you are protected, and besides, just cause your phone won't boot android doesn't mean its bricked, it just means its not booting android.
There can be a multitude of things causing this, but the #1 reason I think is "Just because thats how it is"
First of all, don't boot your phone with it plugged in. Ever. Charge it first, then boot it, or charge it enough to make it through boot then plug it in when it reaches android.
Second, sometimes during boot, it just hangs where it says A N D R O I D, or some other text. You can get around this by resetting with stylus, then pressing the center dpad button, then just counting to 10 or 20 or some random number that makes you happy, then select quit. It should boot.

Thanks. Fortunately I unbricked it by putting the KAISDIAG.NBH file onto the SD card, then booted it. This unbricked it. I also put the the KAISIMG.NBH for the Android on here and it booted into the installer. My problem now is that when I click install to NAND, it says it has an error extracting from the SD card for the android installer. It then quits back to the main install screen. I think it is a permissions error since it says on the screen something about being read only. If anyone could help me, I would greatly appreciate it. Thanks.
Oh and btw, I never had usb plugged in since mine is broken.

Ok well you are on the right track. Before you do anything else though, flash a copy of windows Mobile. Either take your pick, or use hyperdragon. Its very complete ... radio / ext rom etc. Next, try reformatting your SD card using windows. Do a complete format, not a quick one. That might help. Now reflash using the link to kaisnbh that i posted.
Remember, installing windows mobile is your NAND reset. Its lot like an sdcard where you can just erase everything. You have to put something else there that is radically different. I may be wrong about this, but it seems to be the case more often than not.
You may be one of the special case people who have a weird phone that takes one of the other KAISimg.nbh files too, so don't discount that. Also since you have hardspl, and you are flashing from the sdcard, you phone is probably NOT going to brick, and even if it does screw up royally, if you can still get to tri color, you can fix it.

Ok. That's great to know. I'll try what you stated. Do I need to partition my SD card? Thanks again. I really appreciate the help.

[Q] SGT3-7" Boots up w/no logo and no pic (updated to kitkat 1 day previously)

Title pretty much says the basics.
Details however are as follows.
SM-T210R, Have had this unit for about a year, always been in a case, never dropped, not a scratch/dent/ding on it and I use it every day.
Past couple weeks I was getting update notification from Samsung, I'd always put it off till I got home then not bother when I actually got there.
Finally, a long weekend for me.. I let the update run its course, No problems (500+MB's) And I believe it was upgrade to Kitkat from Jellybean.
Can't remember the exact version details.
Soooo, I use my tablet throughout the day everything seems to work great NO problems at all.
Notice my battery is down to like 20-25% and plug it in (Original wall charger and cable)
Go to get it the next morning, open the case expecting it to flash and display my lock/swipe screen, Nothing.. Not TOTALLY Black, you can see theres still a glow.
The screen still responds to touches ( I can swipe to unlock it and hear the sound)
I tried to reset power. Nope nothing except I can hear the startup tune.
Tried hard reset, nope same thing.
Tried every button combo I could think of or contort my hands/feet into.. Nope no joy.
Hit the internet... read, read, read, read, watch videos, watch more videos..
Ah-ha take the back off, disco battery, wait, replug and voila.
Nope.. not the issue
Different milliamp chargers, nope.
WTF??
Normally I'd think I did something to it, but I did nothing that I hadn't done at least 200 times already.
I'm convinced Samsung F'd my tablet w/their update, not only that but my $1200.00 drone sits idle over my holiday because my vision app resides on my sgt3.
Ideas?

My best solution so far...
Well its been like 2 days since my sgt3 lost its mind.
Found a solution.
EVGA - Tegra Note 7. (No hyperlinks allowed for me....Yet)
nvidia.ca/object/evga-tegra-note-tablet
DAYUMMMMM.
This thing blows my SGT3 right off the map.
Still would like to find a REAL solution, there's alot of configurations on my SGT3.
But in the meantime I think this'll keep me almost content.
-D-

Just download odin and the firmware for you country and flash it if it gets stuck at the boot get in recvory and wipe and flash once more works a treat
sounds like a bad flash i never let over the air upgrades there trouble always use a pc
Ps take any memory cards out before flashing once booted and working replace memory card

jasonvoor1313 said:
Just download odin and the firmware for you country and flash it if it gets stuck at the boot get in recvory and wipe and flash once more works a treat
sounds like a bad flash i never let over the air upgrades there trouble always use a pc
Ps take any memory cards out before flashing once booted and working replace memory card
Click to expand...
Click to collapse
Thanks Jason, I've not messed w/flashing the firmware through pc on this thing yet.
I've done it w/psp's, motherboards, routers etc, but never w/one of my tabs.
Just to confirm... I dont need a display on my tablet to flash it w/Odin?

dimzin said:
Thanks Jason, I've not messed w/flashing the firmware through pc on this thing yet.
I've done it w/psp's, motherboards, routers etc, but never w/one of my tabs.
Just to confirm... I dont need a display on my tablet to flash it w/Odin?
Click to expand...
Click to collapse
No, you don't need the display on your Tab, you just need Kies and Odin on your PC.
Place your Tab in Downloadmode(VolDown+Home+Power,release All buttons when you see the warning, press VolUp) then choose your PDA firmware in Odin(Obtain firmware from SamMobile) an hit start. After this boot into recovery and wipe/factory reset your tab if it's not booting!
Good Luck
Greets Daniel

xDaniel91536 said:
No, you don't need the display on your Tab, you just need Kies and Odin on your PC.
Place your Tab in Downloadmode(VolDown+Home+Power,release All buttons when you see the warning, press VolUp) then choose your PDA firmware in Odin(Obtain firmware from SamMobile) an hit start. After this boot into recovery and wipe/factory reset your tab if it's not booting!
Good Luck
Greets Daniel
Click to expand...
Click to collapse
Hey Daniel, Thanks for the info.
I found Odin was pretty easy to flash with.
I've tried 4 different FW images for the GT3-7 and taken the unit (almost) completely apart w/the exception of removing the actual digitizer and the lcd.
Same results after each install though.
It boots, plays the boot sound, but no display.
I guess next step is removing the screen.. After that I don't know what to do except possibly getting myself a lcd replacement..
Just might drop it off to one of the local shops and get them to do it that way I won't wind up paying for something and f'ing it up.
No joy w/my sgt3..

Hey Daniel, Thanks for the info.
I found Odin was pretty easy to flash with.
I've tried 4 different FW images for the GT3-7 and taken the unit (almost) completely apart w/the exception of removing the actual digitizer and the lcd.
Same results after each install though.
Even went so far as to try Kies to do the last one.
It boots, plays the boot sound, but no display.
I guess next step is removing the screen.. After that I don't know what to do except possibly getting myself a lcd replacement..
Just might drop it off to one of the local shops and get them to do it that way I won't wind up paying for something and f'ing it up.
No joy w/my sgt3..

Weird bricked GT-I9195 stuck on black screen after Samsung logo

So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...

Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now