Database Develop

PLEASE HELP!!! Wont Boot - Red/Green/Blue Screen

Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow

and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows

Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.

Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.

grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?

If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.

GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).

Actually, ill just message you tomorrow or something.
Ive been really busy this week.

well did you get it fixed? what did you do?

Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.

I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it

You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!

this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse

dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse

dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.

GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?

I Hard-Bricked my SGS 3 Mini

Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM

TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.

[Q] A very strange rebooting problem.

Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.

Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.

Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!

Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.

Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)

Lumia 710 bricked. Any help?

Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!

Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.

droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...

Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.

S3 Mini GT-I8190 [Bricked]

Greetings, for the first time ever in my life I never experianced getting a Bricked phone, it did not happen while flashing or doing something wrong. I just did a normal flash, it was sucessfull was running the custom Rom there since months. I just woke up grab my phone while it was charging (It was at 100%) used the Instagram app and it randomly froze, I was just thinking it's normal, every Android phone freezes sometimes somewhere , plugged out the battery plug in and tried to boot it up, but nothing no vibration, no lights nothing. After some time, in the holidays I decided to plug in the phone into my PC, I heard noises that my win10 laptop tried to reconize something, so I had still hopes for it that it still works. I heard about that a JIG will may work for it, so I bought one that was "inteded" to be for my S3 Mini GT-I8190 waited for it to arrive and plug it in finally, well you could guess it, nothing happend. I knew a friend who had the same phone and I asked him if I may plugin the JIG inside, all it done was just vibrate and nothing else. On other phones it just works flawless. I tried to look up for a debrick image for the phone but it seems there is nothing like it, like it never existed, only the S3 somewhat got it. The only thing now I could help people is, is how to get your system back while TWRP/CWM/Recovery is still there or get the recovery back while the system is still there. My only option now is create some how a own JIG, buy a JTAG and get a debrick.img but the third option appears nowhere here nor in a search engine (Or maybe only mine).
If you have questions, please aks and don't be shy. The current state of the battery right now is 2.8V (Must be at ~60%)​