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?

How to COMPLETELY unroot

So I posted a thread about how my 3G wasn't working, and it's still not working. So after talking with Sprint for about 2 hours yesterday, I'm getting a refurbished phone. They told me when I get the refurb, to send back the one I have now, which is rooted. So I need to completely unroot the phone I have now. Is there a tutorial online that will show me how to completely unroot my phone?
Thanks
EDIT: Will this do it? If I just run this file with my phone connected to the computer?

Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.

chromiumleaf said:
Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.
Click to expand...
Click to collapse
Nice, also, I saw what you posted in my other 3G thread. I'm gonna give that a shot. The update profile thing I tried a few times (a few times myself as well as with the Sprint rep), but I never tried the airplane mode. Thanks for the info.
EDIT: Thanks, but it didn't help..still the same thing. I don't get what could be wrong though, I literally tried everything. I even factory reset my phone twice, still no go..I wonder if it's a hardware error, I don't know what else it could be at this point.

Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?

spatel9114 said:
Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?
Click to expand...
Click to collapse
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602

chromiumleaf said:
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602
Click to expand...
Click to collapse
Wow, you are just helping out left and right today, aren't ya, lol
Thanks, the first post on the first link you posted did the trick, thanks again.

QHSUSB_DLOAD mode??

Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?

Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.

Already tried, no luck. Tells me the device has not been found.

I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.

Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse

I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One

Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!

Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app

I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app

lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.

same here
Any idea how to fix it?

Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk

My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.

Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..

QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry

My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..

danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?

My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.

danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far

Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:

Stuck at padlock screen then reboots into recovery

i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.

prelude91sit said:
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
Click to expand...
Click to collapse
Dear Brother !!
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Brother!!
Please let us know how it goes. I think there are many brothers on here in the same predicament.

HTC m7 died - no red LED

Hi there,
i just want to know who had the same experience as i had.
We're talking about an HTC m7ul, CyanogenMod, Unlocked
I was trying "Dubstep Hero" as the phone suddenly freezed, even the sound was stuck.
Then it turn off without any warning.
First i tried to reboot it normally, nothing happend.
I guess, the battery should have had about 40%.
Next Chance i thougt would be to reboot into the Bootloader / Recovery (VolUp+Pwr).
Nothing happend. Then i tried to charge the Phone, no red LED came on.
I let the phone on the stock power adapter over night and gave it another try.
Still no reaction.
After that my last attempt to get it back to life with attaching it to my computer.
Nothing was recognized, "lsusb" wasn't able to find anything attached, which could be some kind of phone.
I also tried the variant with pressing buttons for several minutes, without success.
The Phone was about 365 days and 2 hours old.
Here in Germany there is a warranty of 2 years so i returned the phone where "Saturn" will send it to HTC or some other authorized Service Partner.
Hoping that it will be back soon and i don't have any issues about the custom ROM or stuff like that.
btw...
I tried to get an OnePlus One from Coolicool.com. Don't ever buy anything there.
I still got nothing, my only luck is that i paid with paypal.
They even have not shipped it since 3 weeks! Support promised, shipping has already been done...
Next Tuesday i will try to get my Money back.
Finally my Question to u:
Have u or Have u Had the same problems / issues?
Did your Phone came back to life?
What have you done to bring it back to life?
Sorry for my english, it's not that great
Hope you figure out, how things are meant to be..