Related
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 :-(
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Pride4u said:
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Click to expand...
Click to collapse
Does it happen on any other ROM, or only on Endymion? Have you tried Reaper and tried to reproduce the problem there?
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Pride4u said:
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Click to expand...
Click to collapse
Why use Unity kernel with Endymion when Endymion kernel is excellent on the ROM by itself?
I would suggest you try another ROM like Reaper and see if the problem persists...
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Pride4u said:
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Click to expand...
Click to collapse
Why I asked you to try another ROM is because if my hunch is correct, you have a hardware problem... I just didin't want to say it till we had ruled out the software issue. This is the exact same thing that happened to my wife's phone a month after purchasing it (Desire S) and HTC put it down to a hardware problem (mainboard) and replaced the device free of cost under warranty (wife never allowed me to touch her phone, so it was S-on, stock!!)
I hope you don't have the same problem, but it sounds exactly like the problem my wife's phone had... the only way is to flash another ROM and see if the issue persists. Make a nandroid backup. What have you got to lose?
What I've got to lose is the time spent, but I guess I have no other choice so I'll get around to it as soon as I find the time.
If it's HW problem I may encounter some trouble as I've bought the phone from an e-shop that sells unofficially distributed phones because they offer considerably lower prices, although it is true that the customer service and complaints may be rather poor.
I'd have to send the phone to them and wait like a month or so until they finally decided that my complaint wouldn't be accepted :-D Not to mention that I would have to unroot the phone and change it back to the S-ON setting.
Anyway, let's hope for the best.
Shameless bump - I'd like to ask a question about Titanium Backup.
I've backed up my installed apps but would like to know whether it will be OK if I back up the system and user data - I don't if it matters that the data will be from a different ROM - in other words, if the system structure doesn't change.
For contacts backup Google sync will be the best I guess.
EDIT:
Installed Reaper 1.6 and the problem is gone. I lost some data in the process as Titanium backup didn't back up the notes from Endymion HTC Notes, never mind, though.
EDIT2: EPIC FAIL! I was probably just unlucky not to see the phone flashing for a long time but today I've seen the screen turning on of its own accord again. Repair service, here I come! :-(
Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!
a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts
captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.
I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416
I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app
Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.
Didn't create a backup?
drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.
Please forgive me, as I have not searched the forum extensively for an answer, but I'm in a bit of a time crunch as I am leaving on a trip tonight and need to get back to some semblance of a working phone.
Some time ago I flashed some rom (I think Paranoid Android; I don't remember. I liked it enough to keep it, then I didn't worry about it again after that.) Little by little it started getting slower and buggier, but for the most part it worked fine, so I ignored it. For the last couple of weeks it started losing signal and data constantly, with no change to the phone. I kind of just lived with it because I could usually restart my phone and I would regain signal, but as of a couple of days ago, it would just drop off and not come back until it wants to.
I had the day off to prepare for my trip, so I decided I would try to go back to stock; there's almost nothing that I do that requires a custom ROM and I had no data issues on stock, nor does my wife on her Note. I looked around for a bit for instructions to restore my phone, and found some, but out of the handful of pages I went to, each one had at least one link that was dead, rendering the method useless, to me, a layman, at least.
I then decided I would just find a Stock Rom, thinking that might be the next best thing. I found Clean Rom on here and decided to try to flash that. I made a backup of my system, wiped everything, and then flashed it. Except something is wrong with the zip and keeps giving me an error message. I then tried to restore my back up that I had just made to try something else, but something happened to that, and it also wouldn't open. I tried the backup before then (quite old, as I haven't done any tinkering with my phone for quite some time) and it worked, but it tells me that my sim card is disconnected, so I have no data or signal. As it is an old restore, I'm not sure what the name of the ROM is, but I can provide all of the information needed, if someone needs that to figure it out.
Anyway, long story slightly shorter: I need to fix this today, and like as soon as possible. I will give ten dollars, count them TEN DOLLARS, to the first person who can provide a set of working links and very straightforward instructions as to how to get back to stock (or if there is a good working ROM that will give me FULL functionality with no flares that would be easier to do. Easy and fast are the key components to this request). I'm not dumb, but I am no longer immersed in the lingo of this community, as it has been a few phones back that I really cared about actually experimenting much with my phone, so non-technical language would be nice. I know what flashing and wiping means. Most of the rest, probably assume I don't.
Thanks.
Your best (easiest) option is probably to flash another stock ROM, or stock-ish ROM. There are quite a few options in the Android Development section. There are a couple of stock rooted at&t ROMs in the first couple pages, also a stock rooted Telstra ROM.
You didn't mention which carrier you're with, whether your phone is branded, or any of your important details, like your firmware/hboot details and whether you're s-on or not. If you wanted to go back to completely stock, I'd need to know those details. Going completely stock can/will be a longer process though.
Sent from my Evita
Okay, I'll try another one. I'm not sure why Clean Rom didn't work, but if another one or two don't work I'll come back here and I'll have you talk me through getting back to stock and I'll throw you a digital Hamilton.
Thanks.
Well, I tried another couple of ROMs. They installed correctly, but it says that I have no sim card, so I still have no signal. Maybe I some how deleted my radio when I did a system wipe while trying to install one of the ROMs? I'm not sure.
Anyway, for "more details" I'm on AT&T, I'm not sure what you mean by branded, but it's the HTC One X, the current ROM is 4.1.1. I haven't done S-On/S-Off, or anything like that other than unlocking the bootloader a long time ago. The kernel version says 304010-g240d4d5, the baseban version is 0.17.32.09.12_10.86.32.08L The Build number is 3.17.707.1 CL134054 release-keys.
I'm not sure which of that information is relevant or not, but that's everything I can tell you.
Never mind that last post. When I said in the first post that I'm not dumb, apparently I lied. My phone fell off a table this morning, and I guess it knocked the sim card loose, but it coincided with doing the factory reset stuff, so I thought they were connected. I pushed it back in, restarted, and now the stock ROM I'm using works great.
Thanks/Sorry!
Well, it turned out to be an easy solution (Occam's Razor FTW yet again).
But this thread made me think . . . why the heck does it seem so many people lately flash ROMs without doing a nandroid first? Its a no brainer to me. If you are trying new ROMs, and not sure how they will perform, why would you not give yourself an easy way to simply revert to your last known good config?
I couldn't agree more, but there's plenty of not-so-smart practices on here, so I'm not at all surprised.
Sent from my Evita
Yea. Nandroid ftw
Sent from my HTC One using Tapatalk 2
So I had a P9000 that got the screen smashed.
I liked the phone, it was stuck on the 6.0 with the OTA issue, but everything worked fine for me... so I went ahead and bought a new P9000 (which should be faster than getting the part and repair the older one... which I planned to do anyway and keep it as a spare in case of another accident).
It arrived with a 6.0 installed as well, and everything seemed to work fine.
While setting up the phone, installing stuff etc... it got automatically updated to 7.0
THE ISSUES:
I can barely hear anything when people call me. I've read is a pretty common issue.
I've tried every possible solution I could find online... nothing works.
The only option is to put the call on speaker... which is not so handy for EVERY call EVERYWHERE.
-
I just went on a trip and realized data roaming is not working either.
I get phone signal, data and roaming options are both active (I tried both cards), checked the APN with the providers... all options again. No way to get it to work.
As soon as I landed back it worked without issues.
With the other phone/ROM I never had issues.
SOLUTION?
I've read some time ago that rooting 7.0 on P9000 is kind of risky or doesn't work altogether.
Is this still true?
Do you recommend any specific instructions to do it? (I've rooted and installed ROM's in other phones, so not newbie but no expert either).
Which ROM would you recommend as of today?
I keep the phone pretty app-light, I use for work only... so these issues are really bad for me. And the Elephone customer care has been a total deal breaker.
I won't be buying from them anymore that's for sure, but I'd like to don't burn cash either and get some use out of the phone.
Thanks in advance