Database Info

True Brick...QHSUSB_DLOAD

Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt

Just swayed my decision on wether to root or not.

So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?

Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.

Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.

Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt

Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.

Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.

Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).

Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt

it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.

nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much

vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt

Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?

vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt

Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?

vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2

not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.

Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(

Viper 2.0.0 & 1.8.0 issues

Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.

S1L3nTShaDoWz said:
Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.
Click to expand...
Click to collapse
First thing. Before you ever take a update... Have you ever heard of a nandroid...
Second. Did you check your md5?
Third. Actually try wiping your data partition... When switching ROMs or even doing a update to a ROM with a new version such as 4.4.3 from 4.4.2 it's smart to wipe data and everything except internal and external SD card.
Forth. Why did you install a new GAPPS? That WILL cause crashes...
Fifth. We don't have updated firmware for 4.4.3 with a 2.22 base. That will cause some issues. It's a given.
Sixth. Have you tried a clean flash of viper 2.0?
Seventh. Have you tried installing another ROM. If so did you have the issues there.
Sent From My HTC One M8 Running Insert Coin. S-OFF.

I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.

Tigerstown said:
I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.
Click to expand...
Click to collapse
I didn't really read up too much on 4.4.3 other than it was a security patch I believe? & I considered that but I had tons of messages which I would lose that were important beyond what I'm willing to explain. In the end I said f*** it and just restored my 12 day old backup. Really the only thing stopping me from doing that is my WhatsApp account, I have it setup to use one of my old phone numbers so I never have to disclose real information when I want to give someone my WA. Losing that would mean giving a lot of people something I really don't want to give out...
Now onto the person above me and his idea of my Nandroid doings, yes I have some but I don't have the storage to keep making them everytime I flash something which is practically every week knowing me. & before someone tells me to quit being a lazy "idiot" I simply don't want to spend the time deleting my backups every month when I run out of storage, much un-needed inconvenience. Yup could put them on PC, too bad I'm also running out of storage there too. Could use cloud, no, not into putting my private information and files onto a highly vulnerable privacy invading idiotic creation. In before someone insults me for calling the cloud idiotic, yes it is. I stand by that and have no intents on replying to anyone that may bring that up.
Onto the /data topic, it shouldn't have even touched my data partition if it was just a mere "update". & just now I went and read up on 4.4.3/4.4.4 and the differences = Bug fix & Security update (4.4.4). Most ROM's I've seen actually tell you you don't have to wipe /data unless coming from another ROM, simply that it's better to do it. If it was really such a necessity it should've been stated or stated more seriously/obviously. If 2.0.0 was like Jellybean to Kitkat or Kitkat to Lollipop then yeah i'd understand. If someone with a higher knowledge would like to enlighten me as to why my /data was ruined from such a minor update then feel free to tell me (no more cocky responses after this please, civil only.). Maybe 4.4.2 to 4.4.3 really is a big deal and I just don't realize it & actually it could be the firmware thing the guy above mentioned could be a good reason for it but something I read tells me otherwise, just can't remember it at the moment.
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed

You can easily store text on cloud well factory reset. Just FYI. But glad your all set.

There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap

S1L3nTShaDoWz said:
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed
Click to expand...
Click to collapse
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.

pball52998 said:
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
Click to expand...
Click to collapse
Yes I'll back up the apps tomorrow, I used to do that with titanium and make a flashable zip but It rarely occurs to me to use Titanium anymore. Matter of fact 90% of the time I don't even realize I have it or it even exists. Last time I did it I did the wrong option which probably turned me off from it anyways soo I'll just have to pay attention this time.
I'll install 2.0 another day, too traumatized after my last experience to mess with it again LOL.
On the GAPPS topic yes it makes sense, I was unaware HTC had their own as it doesn't really say anywhere that they do or at least I haven't found anything stating such yet up until your response but yes it makes 100% sense.
& yeah I understand, I was quite frustrated and angry at the time and probably should've waited til I calmed down before originally posting this thread. Anyways my bad for even calling you out on that, I didn't originally plan to respond due to my natural urge to wanna retaliate when I feel I've been insulted, mocked or other words "attacked". Not literally attacked but you get what I'm saying, felt like I needed/wanted to be on the defensive. If that even makes sense, oh well.
Lastly, as to the "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again." I may have just skimmed over that and maybe just completely ignored the data part in my head. Having read so many I don't really bother to read anything other than the features and some other stuff anymore. I'd say what other stuff but I'm tired and can't think of it at the moment.
Anyways, thanks for trying to help even though my original post sounded like it was made by an idiotic jack***. How frustration & anger makes you change eh? & apologies for responding to what I thought was a "snarky & offensive" reply with attempt to try the same thing. Night!

My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.

Roefastford said:
My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.
Click to expand...
Click to collapse
May I ask if you wiped your /data when you installed it? (clean installed)

S1L3nTShaDoWz said:
May I ask if you wiped your /data when you installed it? (clean installed)
Click to expand...
Click to collapse
No I dirty flashed from 1.8 to 2.0.0 then I dirty flashed from 2.0.0 to 2.0.1 because the ota kept coming back corrupt download so I just flashed the full rom to get from 2.0.0 to 2.0.1

teddyearp said:
There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap
Click to expand...
Click to collapse
SD cards cheap? Um buy a class 10 scandisk ultra 64g top of the line not cheap by any means it might cost you 70 bucks like mine did but well worth it. Viper ROM needs no gapps its a sense ROM so I'm confused with that.

ANY way to keep root when updating to 23.4.A.0.546?

So my phone is now prompting me to update (and I can't even tell it to got to hell like I could on my S4 Mini ) but I refuse to do so until I know I can keep my root intact (or until Kingroot becomes capable of rooting that version).
Is there ANY way of keeping my root intact? Maybe by using the PC companion to update (this used to work before ICS didn't it?)? Or doing something to the phone (besides flashing firmware) to preserve the root ahead of the update?
I don't want to be installing a custom rom (and yes, I still count generic stock as a custom rom because it would get onto my phone just like any other custom rom) just to update and I absolutely need root for Link2SD so if I can't keep root in some way and Kingroot doesn't catch up then I'm going to stay on my current version forever, security be damned.

SCHUMI_4EVER said:
So my phone is now prompting me to update (and I can't even tell it to got to hell like I could on my S4 Mini ) but I refuse to do so until I know I can keep my root intact (or until Kingroot becomes capable of rooting that version).
Is there ANY way of keeping my root intact? Maybe by using the PC companion to update (this used to work before ICS didn't it?)? Or doing something to the phone (besides flashing firmware) to preserve the root ahead of the update?
I don't want to be installing a custom rom (and yes, I still count generic stock as a custom rom because it would get onto my phone just like any other custom rom) just to update and I absolutely need root for Link2SD so if I can't keep root in some way and Kingroot doesn't catch up then I'm going to stay on my current version forever, security be damned.
Click to expand...
Click to collapse
No. You can make prerooted 546 and flash it in recovery and it's only way how to retain root. As soon as you update using OTA you will loose root as system will be overwritten.
Sent from my D6603 using Tapatalk

Thanks, guess I'm waiting then.
Any way to temporarily disable the update message/get it out of my notification bar?

SCHUMI_4EVER said:
Thanks, guess I'm waiting then.
Any way to temporarily disable the update message/get it out of my notification bar?
Click to expand...
Click to collapse
Maybe you can disable the Software Update app in settings...
By the way, however it`s your decision, I don`t understand reasons behind why not flashing latest software with Flashtool. There are sometimes nasty issues with upgrades, like people loosing LTE with OTA upgrades to 5.1.1 and so on. I would just backup everything and flash latest .570/.580 firmware (yes, even .546 is now getting outdated as upgrade to .580 becomes available to address MMS based vulnerabilities). Flashing software in flashmode is the same like flashing it through PC Companion and provides for clean way how to do system updates. You can even download version intended directly for your market/provider instead of generic one.

Flash the pre-rooted .546 zip. It has been posted weeks ago.

ondrejvaroscak said:
Maybe you can disable the Software Update app in settings...
By the way, however it`s your decision, I don`t understand reasons behind why not flashing latest software with Flashtool. There are sometimes nasty issues with upgrades, like people loosing LTE with OTA upgrades to 5.1.1 and so on. I would just backup everything and flash latest .570/.580 firmware (yes, even .546 is now getting outdated as upgrade to .580 becomes available to address MMS based vulnerabilities). Flashing software in flashmode is the same like flashing it through PC Companion and provides for clean way how to do system updates. You can even download version intended directly for your market/provider instead of generic one.
Click to expand...
Click to collapse
Because the phone isn't even two weeks old. Nowhere near time yet to risk bricking it doing non-standard things, I've already tested my luck enough by rooting it. And my region doesn't have 580 yet anyways. The inability to remove the battery makes me even more nervous about this sort of stuff, and yes I know there is a simulated battery pull, but that's still software and software gets fudged up which is the whole reason to actually physically remove the battery from your phone.
Not gonna happen thank you very much. Besides I'm never in a hurry with updating Android, it's always 2 steps forward one step back, never an all-round improvement. Some monkey of a programmer inevitably always rips out some base function every device should have, just look at ICS and the mess it's caused by choosing to ignore SD cards. Even Lollipop lacks things prior Android versions had for utterly no reason. Stagefright can kiss my you know what. Not gonna update till I can root with the click of a button avoiding almost all risk (in my mind anyways).

SCHUMI_4EVER said:
Because the phone isn't even two weeks old. Nowhere near time yet to risk bricking it doing non-standard things, I've already tested my luck enough by rooting it. And my region doesn't have 580 yet anyways. The inability to remove the battery makes me even more nervous about this sort of stuff, and yes I know there is a simulated battery pull, but that's still software and software gets fudged up which is the whole reason to actually physically remove the battery from your phone.
Not gonna happen thank you very much. Besides I'm never in a hurry with updating Android, it's always 2 steps forward one step back, never an all-round improvement. Some monkey of a programmer inevitably always rips out some base function every device should have, just look at ICS and the mess it's caused by choosing to ignore SD cards. Even Lollipop lacks things prior Android versions had for utterly no reason. Stagefright can kiss my you know what. Not gonna update till I can root with the click of a button avoiding almost all risk (in my mind anyways).
Click to expand...
Click to collapse
Well, seems you are new to XPERIA`s because there is hardly any way you can brick it. Battery pull is not a problem, because in addition to Power+VolUp reste, there is a push button hidden on the side of SIM card that triggers hard reset and switches the phone off.
But I aknowledge that you have your rights for your fears. However I wonder that with all your fears you would allow to install and run undocumented chinese app, that although roots your phone, may do other things and you will never know. Everyone is responsible for his own luck.

ondrejvaroscak said:
Well, seems you are new to XPERIA`s because there is hardly any way you can brick it. Battery pull is not a problem, because in addition to Power+VolUp reste, there is a push button hidden on the side of SIM card that triggers hard reset and switches the phone off.
But I aknowledge that you have your rights for your fears. However I wonder that with all your fears you would allow to install and run undocumented chinese app, that although roots your phone, may do other things and you will never know. Everyone is responsible for his own luck.
Click to expand...
Click to collapse
Yes and no. I had a neo but that was a very different device and I never felt the need to do anything custom to it (although I did check XDA for it) so it remains stock even today. Then I went to Samsung cuz everything Sony sucked at the time, at least in my price range. And now I'm back with Sony cuz there's something wrong with Samsung, dunno what, but I just don't like them so unless they're far ahead on paper I won't touch them again. (unless Sony tanks).
I didn't know about that button but I'd still rather not.
And I don't have anything sensitive on my phone so Kingroot can spy all it wants to. Of course I'd prefer it didn't, but if they absolutely have to then they're welcome to any and all info. Simply running an APK on my phone (that thousands have run before me) just seemed like the least brickable way of getting root (since I didn't have to do anything special like stuff up in the recovery or mess up an ADB command or anything like that). When I'd read about there being no root methods for 5.1.1 yet I erroneously took that to be all of Lollipop so I thought my phone was unrootable anyways when I turned it on and found it had lollipop (it was sealed so I thought it would still be on KitKat and easily rootable) so Kingroot was basically just a hail mary at the time. And since it worked so well I see no reason to ever do anything else.

Is my Nexus 5 dying?

In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?

nimdy said:
In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?
Click to expand...
Click to collapse
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.

Aurey24 said:
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.
Click to expand...
Click to collapse
I have upgraded and downgraded the software but that doesn't seem to help. Apps are the normal social networking and utility apps. No fast paced games or other battery sucking apps. I haven't messed with custom kernels and OCing on this device.

Hmm that is weird, u even tried clearing the cache too hunh? Let's see, have u ever taken a look inside then? Maybe cleaning it out? I've had to clean my phone before because it wouldn't turn on due to dust and whatnot inside it. That's really strange that you've even factory flashed and that didn't help, usually that'll clear up the problem, the reason I could think of is its reaching that eol point because it's just that time or u didn't take care of it (this obviously isn't the case I assume), or maybe it got damaged somehow, or maybe a good clean. Idk I'm just throwing out ideas. But really tho factory flashing should've solved that problem, flash it 2 times in a row lol

Android OS corrupting itself?

Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.

iceman4357 said:
Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
Click to expand...
Click to collapse
For me this sounds like a hardware failure and I'd try to get the phone replaced.

Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.

dirtyreturn said:
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
Click to expand...
Click to collapse
I agree and think it could be hardware. I have Factory reset the phone twice already.

The firmware flash may have become corrupted therefore factory resets are useless.
Flash data has a limited lifespan usually this doesn't become an issue but it can.
Reflash and see if it holds. Otherwise it's likely a memory chipset or mobo failure.

This happened to me. Was running one of the developer previews and chalked it off to that. lost everything I didn't back up the night before (out of habit from messing with my phones I do daily backups of the important folders and phone data). The only thing that worked for me was re-flashing factory image and start fresh. Hasn't happened again for me.,

I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.

EvilRubberDuck said:
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
Click to expand...
Click to collapse
For the system to go corrupt by itself is rare unless there's a hardware fault.
More than likely it was 3rd party software that caused it. Launchers, power management apps are prime suspects.
Androids are typically a very stable platform.