Related
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Should verizon replace your phone after you borked it? I think you already know the answer
xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.
Should they? Technically no. Will they? Sure. They would be happy to.
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.
Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?
This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.
If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse
Just say you tried to install the last update and your phone wont boot now. They won't know the difference.
dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.
xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk
Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ
xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.
My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.
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 :-(
I've read so many posts about USB woes and no PC detection. So now I'm officially a member of the My PC wont recognize my Infuse anymore club. I've tried so many cables, PCs, laptops in many combinations and nothing. Often the phone wont even alert me that I am connected via USB.
So my thoughts are that I troubleshot this to the best of my abilities. Cleaned the port, contacts points etc and still nothing.
I got my phone in August of 2011. And of course I have a great custom ROM running on it now and I cant return to stock!!!
Oh and add to that I have issues with SIM Card detection errors, lost contacts randomly and crappy sound during calls on occasion.
So here is the question...Who do I call ATT or Samsung??? And do I tell them its rooted and running a custom ROM or not admit it (will they find out). Will this cause me to not have any warranty support?
Should I just count my loss at this point and get a new phone out of pocket maybe upgrade to a newer phone... Gxy note, Skyrocket, HTC one X or S3???? unlocked on ebay or ???
Really at a crossing point here and unsure of next steps. Be gentle on me folks this aint easy to fess up on my lack of repair, warranty, return process skills!
Maybe I should just ask Who do I call for warranty support?
The local AT&T store suggested that I call Samsung as they never heard of USB port problems.
Rebelranger said:
Maybe I should just ask Who do I call for warranty support?
The local AT&T store suggested that I call Samsung as they never heard of USB port problems.
Click to expand...
Click to collapse
Go to an att store and ask where there nearest exchange center is. Then simply tell them what's wrong. If your scared if they will deny you because of the rom, then just brick it by flashing random crap to get no recovery, then they can not really tell unless if you were on gingerbread bootloaders (even then most employees dont get what the numbers mean). Make sure if you want back up all the data to the cloud or use bluetooth to connect your phone and computer to transfer data over. Remember to act stupid like you don't know what happened and you never heard of odin and such.
Ryanscool said:
Go to an att store and ask where there nearest exchange center is. Then simply tell them what's wrong. If your scared if they will deny you because of the rom, then just brick it by flashing random crap to get no recovery, then they can not really tell unless if you were on gingerbread bootloaders (even then most employees dont get what the numbers mean). Make sure if you want back up all the data to the cloud or use bluetooth to connect your phone and computer to transfer data over. Remember to act stupid like you don't know what happened and you never heard of odin and such.
Click to expand...
Click to collapse
Cool. Thanks! I visited the store yesterday and they really seemed to push for me to call Samsung. Trust me "acting" stupid comes naturally! LOL
I appreciate your thoughts.
Rebelranger said:
Cool. Thanks! I visited the store yesterday and they really seemed to push for me to call Samsung. Trust me acting stupid comes naturally! LOL
I appreciate your thoughts.
Click to expand...
Click to collapse
No problem. Happened to me too... except i wanted the data off it and i completely bricked it, so i headed over to mobiletechvideos and he figured out my usb was broken. He tried exchanging the usb hub and it did not work. Another user found that somehow the voltage was screwed up and running the wrong way, that is probably the cause. I think i was the first person to have this happen to me, it was late last year. Anyway do not take to sammy, they would probably turn you down, they have gotten pretty tough with devices lately, unless if you reset the bootloader. With this experince from sammy, im very tempted to go with the one x for my next phone. Installing custom roms are a pain on that thing, but then again it actually works a lot better the first time around, instead of installing a custom rom.
Yes the One X is very much in my eyes. And I hear you in out of the box performance rather than the need for custom Roms!
I'm hoping that I can convince AT&T to allow me to move up even though my contact ends next year, i've been a customer seems like forever.
Thanks again for the information on mobiletechvideos!!
Dunno about you but I've seen like 3 people post about it ever... And there is always two answers; either your phone's port is broken or you need to learn how to flash ROMs.
wayzata said:
Dunno about you but I've seen like 3 people post about it ever... And there is always two answers; either your phone's port is broken or you need to learn how to flash ROMs.
Click to expand...
Click to collapse
Well, since I know how to flash roms and there are several with this issue not just three as you suggest, I'd rule in favor of it being an inoperative port.
The original question was inquiring for return/warranty recommendations and not to solicite judgments of ability or lack thereof.
Ryanscool said:
Go to an att store and ask where there nearest exchange center is. Then simply tell them what's wrong..
Click to expand...
Click to collapse
Thanks for the exchange center suggestion. I went to a different store (device support) and they were fully aware of the USB port issues on many Samsung devices. They, without hesitation gave me an exchange and tested it before I left to ensure all was ok.
Problem resolved!
Mod feel free to close this thread as the question was answered and problem resolved.
Rebelranger said:
Thanks for the exchange center suggestion. I went to a different store (device support) and they were fully aware of the USB port issues on many Samsung devices. They, without hesitation gave me an exchange and tested it before I left to ensure all was ok.
Problem resolved!
Mod feel free to close this thread as the question was answered and problem resolved.
Click to expand...
Click to collapse
Thats good. And idk, maybe i can get some help on this withoit opening another thread? Anyway, would you upgrade and get a one x, or get the tablet asus tf300? For high school they recommend getting a tablet, but idk maybe i could use the one x as one? Idk.
That's a tough one for me to answer. My wife has the HTC One X and loves it. I can't say it could replace a tablet. Maybe the SS Note?
Rebelranger said:
That's a tough one for me to answer. My wife has the HTC One X and loves it. I can't say it could replace a tablet. Maybe the SS Note?
Click to expand...
Click to collapse
The tablet or the phone? Lol.
im in the club too. phone wont connect to usb for charging or for transfer. have tried with several cables (that work with other phones/devices) but to no avail. Since i bought this phone on ebay will i be able to go to att for a replacement if i am on an att prepaid account. what are the chances of fixing this by replacing the usb port as i have read about users not being able to get it fixed after doing this.
as for now i have resorted to an external charger. it works but a solution to fixing the usb would be much appreciated
WOW
Panama!! I lived there for 11 years!! I miss it!!
Im not sure if they will help you with a replacement. If not there is a place that repairs them
CLICK HERE
This is the first time im not glad im joining a club .
But as of last month, my usb is not working, returning it is out of the quiestion( im in europe) so im stuck with cwm flashes only. Btw Ryan i did test the wires with a multimeter and i get +Vcc on a wire that should never have voltage running trough. I opened the phone, checked the jack and the pcb, everytning seems factory like, so im screwed...
mikig_mkd said:
This is the first time im not glad im joining a club .
But as of last month, my usb is not working, returning it is out of the quiestion( im in europe) so im stuck with cwm flashes only. Btw Ryan i did test the wires with a multimeter and i get +Vcc on a wire that should never have voltage running trough. I opened the phone, checked the jack and the pcb, everytning seems factory like, so im screwed...
Click to expand...
Click to collapse
Hmmm... i wonder if its from flashing something improperly?
Rebelranger said:
Thanks for the exchange center suggestion. I went to a different store (device support) and they were fully aware of the USB port issues on many Samsung devices. They, without hesitation gave me an exchange and tested it before I left to ensure all was ok.
Problem resolved!
Mod feel free to close this thread as the question was answered and problem resolved.
Click to expand...
Click to collapse
Question....What did you do about having a flashed ROM and rooted phone if you returned it?
th3ju99anaut said:
Question....What did you do about having a flashed ROM and rooted phone if you returned it?
Click to expand...
Click to collapse
I removed everything that I could and when I returned it. They tried to upload a stock rom and it would not connect at all on their set.
All they were concerned about was the moisture indicator for water damage and physical damage-cracks battery contacts etc. I really played dumb as heck and asked dumb questions.
The tech told me he didn't care about custom roms since in fact the issue was a known problem with the USB port and that was what they were replacing it for.
Rebelranger said:
I removed everything that I could and when I returned it so that it would not boot. They tried to upload a stock rom and it would not connect at all on their set. All they were concerned about was the moisture indicator for water damage and physical damage-cracks battery contacts etc. I really played dumb as heck and asked dumb questions.
The tech told me he didn't care about custom roms since in fact the issue was a known problem with the USB port and that was what they were replacing it for.
Click to expand...
Click to collapse
You lucky, lucky guy. I wish i was in USA and had contract with att, so i can act as a dumb turist with bad english
Sent from my Infuse 4G running Aeon 1.3.1!
mikig_mkd said:
You lucky, lucky guy. I wish i was in USA and had contract with att, so i can act as a dumb turist with bad english
Sent from my Infuse 4G running Aeon 1.3.1!
Click to expand...
Click to collapse
Did you consider maybe sending it for repair? Or is that not an option? I have a link in a few posts back.
Or maybe ordering a port and installing it?
Greetings all! I have been a Lg optimus user for some time, being that it is my first official android phone. Sadly it was bricked and is just a very expensive paper weight now. Due to the fact that armv6 processors are becoming outdated i was considering geting a new phone, preferably an HD one, but I digress. My main problem is that I would like my LG to at least function, but I live in the Caribbean and it is out of reach of an offcial LG repair center. I very well know that it may be a lost cause but is there any advive that others can give from past experience that can help me with my present conundrum? You are well come to flame at me for this possibly inept question, as long as I can get help and move on in the mean while untill my new phone....I love the Optimus one and even so would like to have i as my little past time.:highfive:
wm526 said:
Greetings all! I have been a Lg optimus user for some time, being that it is my first official android phone. Sadly it was bricked and is just a very expensive paper weight now. Due to the fact that armv6 processors are becoming outdated i was considering geting a new phone, preferably an HD one, but I digress. My main problem is that I would like my LG to at least function, but I live in the Caribbean and it is out of reach of an offcial LG repair center. I very well know that it may be a lost cause but is there any advive that others can give from past experience that can help me with my present conundrum? You are well come to flame at me for this possibly inept question, as long as I can get help and move on in the mean while untill my new phone....I love the Optimus one and even so would like to have i as my little past time.:highfive:
Click to expand...
Click to collapse
Does it turn on at all? If you pop the battery out, put it back in and hold Volume UP+Back+Power does it get to Emergency Mode at all? If it does you might be able to recover by flashing the original/stock firmware, follow this post here:
http://forum.xda-developers.com/showthread.php?t=883314
Skellums said:
Does it turn on at all? If you pop the battery out, put it back in and hold Volume UP+Back+Power does it get to Emergency Mode at all? If it does you might be able to recover by flashing the original/stock firmware, follow this post here:
http://forum.xda-developers.com/showthread.php?t=883314
Click to expand...
Click to collapse
I've tried that a few times but to no avail... :crying:
I've held down every single button, squeezed every single part, and even shaked it a bit since some people say that it some times works. The phone is very fresh, a few months old and I haven't even taken off the screen protector yet...
I've even tried putting it to charge for some time, pressing some of the puttons while plugging in the charger or USB cable. I don't know if i can have it shipped back to the US to be fixed or otherwise.
Thanks for the input...:highfive:
wm526 said:
I've tried that a few times but to no avail... :crying:
I've held down every single button, squeezed every single part, and even shaked it a bit since some people say that it some times works. The phone is very fresh, a few months old and I haven't even taken off the screen protector yet...
I've even tried putting it to charge for some time, pressing some of the puttons while plugging in the charger or USB cable. I don't know if i can have it shipped back to the US to be fixed or otherwise.
Thanks for the input...:highfive:
Click to expand...
Click to collapse
Well if the phone isn't turning on at all then you wont be able to flash the stock rom. I guess you havent tried flashing a new baseband or rom. You might have to go ahead and send it for fixing since it is under warranty.
How many days do you have phone bricked??? Just asking because you could have a empty battery and thats why combo its not working its a long shot i now but sometimes happy things appen...
Best of luck
Sent from my LG-P500 using xda premium
just xplain man...
u r jus telling that the fone is brickd...why don't u share the condition of the fone now...nd just xplain wht u did with it bfore getting it brickd...
ajaihs said:
u r jus telling that the fone is brickd...why don't u share the condition of the fone now...nd just xplain wht u did with it bfore getting it brickd...
Click to expand...
Click to collapse
All I think I have to say about that is ...KDZ updater...During the update I got an error repeatedly so I unplug and plug it in again but it didn't work so I (this is the part that I regret the most) I just unplugged the battery and tried to do it again, and thats how I ended up like this...the point is I know it's bricked I just wanted to know if I could have it fixed without being in the USA.
Try this method http://forum.xda-developers.com/showthread.php?t=1324105 :fingers-crossed:
Was playing with my ATT One X, got root happy with it today, flashed an international ROM because I didn't read like I should have, got QHSUSB_DLOAD'd, phone won't turn on, no lights, just makes the USB noise when I plug it into the computer, blah blah blah, same old story. Spent all day reading threads from other people that have had the same issue here, and since I was on 2.20, it appears as if I'm pretty much FUBAR until some wizard much smarter than I figures out another linux hack to fix it. It sucks, I'm stupid, I know, but it's not my main device so I'm not hitting the panic button just yet. What I'm wondering is tho, is there a way to access my internal memory, even if I have to take apart the device? I've used the phone as a camera a lot so I've got a lot of pictures and some videos I'd like to get back. Is this possible with how bricked my HOX is? If not I guess I'll just have to wait until someone gets the QHSUSB_DLOAD fix working with 2.20.
Thanks!
Weston
Yep no way as of now sorry :/
a box of kittens said:
Yep no way as of now sorry :/
Click to expand...
Click to collapse
Bummer. Guess I'll just have to cross my fingers and hope someone makes a fix for it with 2.20.
Thanks tho,
Weston
Google mobile tech videos they are the only ones with a working jtag for our phone right now only thing is u gotta send it to them
http://youtu.be/yjGTP-AmEtA
Try this and see if it works for you:
http://forum.xda-developers.com/showthread.php?t=1966850
Otherwise you can call HTC and have them check the warranty. I had the same error and called them, they honored the warranty on it. I sent it in, and they sent it back all fixed up. It was a very easy process and HTC CS reps were very very nice.
If it isn't under warranty still go with what xstokerx said and send it in for jtag repair. That's about your only other option.
Here is my thread, it may help you.
http://forum.xda-developers.com/showthread.php?t=2071358&highlight=wip