Okay, i'm here again,
but this time i'm really sad.
a couple of things to know.
i have a Lg Thrill (P925) from Usa
i'm in Italy, and i'm quite able to root,install CWM,try Roms etc.
and now i was using the Promethius project, changed from acura V20P for a strange battery draining.
when i've tried to update my phone and change the baseband with the V21E, something gone wrong.
i've had to disconnect the phone and put it in OMAP4430 style to continue installation but it stops and nothing happened.
i've tried to switch it on again and nothing happen, as if it is bricked.
i've pulled out the battery, waited an half-hour and re-assembled. and nothing happened.
i've tried to connect to the ac charger ,and miracle it switched on.
after a couple of tries i've had this issues :
- the phone switch on perfectly,goes in recovery mode from Rom manager or using the Three button sequence, just if is connected to the cable (i will try connecting to the computer) everything is fine.
if i disconnect from the cable,it doesn't switch on at all,it has just a little buzz of vibration,as the same happen when you connect as a OMAP.
so here are the questions:
is bricked? or there is a procedure i can try to ripristinate it as was?
i think i had a problem with the light sensor, this probably is the cause of drain the battery, may be connected to the issues?
is possible that when i disconnect the phone cause the computer program blocked the procedure something is now settled as an OMAP style?
thanks to all for your answers.
per tutti gli italiani che magari usano un Thrill convertito in Optimus 3d, avete consigli?
grazie a tutti
Read my post at the end of the page
emilianopaz said:
i've tried to connect to the ac charger ,and miracle it switched on.
after a couple of tries i've had this issues :
- the phone switch on perfectly,goes in recovery mode from Rom manager or using the Three button sequence, just if is connected to the cable ( just with AC cable works) everything is fine.
if i disconnect from the cable,it doesn't switch on at all,it has just a little buzz of vibration,as the same happen when you connect as a OMAP.
Click to expand...
Click to collapse
ok a little update,
i've tried to flash from kdz, flash with bin, but nothing can let it happen.
when i connect the phone on the computer also if it is switched off it doesn reach the Battery status,nor vol up + power status.
i'm quite desperate, i probably need to flash it in an arcaic way.
how is it possible to return it to stock if it cannot reach the status it needs to be recovered?
please help m
i don't want to stay in this limbo,if it is switched off it cannot be switched on without pluggin it on the wall... is freak ...
probably to much handling on it, i know, but please help me, i'm quite desperate.
thanks to all
last update.
with the "downloading procedure" i finally reach a state and i flashed a different baseband.
i think now i'm on the v20b.
phone started again,everything fine,cwm mode,app installed.
now i'm on Acura Ginger Euro v8.
but the phone is slow,and lagging.
also the Ram Cleaner is ever over 75-80%.
i'm thinking to some hard damage.
i will try using another rom, and i see.
in the meantime,if someone know a procedure to test the fully functionality of the phone, please let me know,
many thanks to developers,and to xda forum.
emilianopaz said:
last update.
with the "downloading procedure" i finally reach a state and i flashed a different baseband.
i think now i'm on the v20b.
phone started again,everything fine,cwm mode,app installed.
now i'm on Acura Ginger Euro v8.
but the phone is slow,and lagging.
also the Ram Cleaner is ever over 75-80%.
i'm thinking to some hard damage.
i will try using another rom, and i see.
in the meantime,if someone know a procedure to test the fully functionality of the phone, please let me know,
many thanks to developers,and to xda forum.
Click to expand...
Click to collapse
Test promethius rom and kernel. Works great and fast for me
please hit thanks if i helped
emilianopaz said:
last update.
with the "downloading procedure" i finally reach a state and i flashed a different baseband.
i think now i'm on the v20b.
phone started again,everything fine,cwm mode,app installed.
now i'm on Acura Ginger Euro v8.
but the phone is slow,and lagging.
also the Ram Cleaner is ever over 75-80%.
i'm thinking to some hard damage.
i will try using another rom, and i see.
in the meantime,if someone know a procedure to test the fully functionality of the phone, please let me know,
many thanks to developers,and to xda forum.
Click to expand...
Click to collapse
use LG Update Tool and install drivers and update. itll bring you back to stock and unroot it and install origional baseband. just re-root and phone should be working normal.
What a Wonderful World
thanks to all, for your advices,comments and suggestions on how to fix this
and thanks to Xda to be a so perfect island, a safe place, for all of us "smanettoni" that cannot stay quiet with a stock rom.
i think this is the epilogue :
yesterday i've found an half solution,quite good for an half bricked phone
but to day, simply following this thread
http://forum.xda-developers.com/showthread.php?t=1448803 (Big Thanks to who wrote this)
i put the v21e files and something happened, probably i've just flashed the baseband, but something happened to the phone.
i've downloaded Ril to check and now i have the v21d baseband ( don't tell me how )
i was using a quite stock v21e rom,but now i've done a backup and i'm trying the Xplay Rom that is based on the v21d, and guys, oh my god is fast and stable (is just a cople of hours that i have it ) and thanks to Titanium i have allll my stuff.
now i just wanna test it or i'll come back to my previous or to the Promethius, but all this stuff teach me something and i would like to write it down for all the noobbie like me that became dangerous with all this knowledge so..
a little list of
"what to do if"
1- i know you feel great, i know you feel intelligent, and i know you feel so smart, but please like me, check all the things three time.If you do it, is Better.
2-if a kdz file or a rom file don't work, download it again and check with antivirus, if a package here in xda is corrupted or a link is dead said it or try again, or ask to the developer, but in first sight please read read read all the fxxxxxn pages.
if are 200 pages, read it all and please be patient. you do it, is Better.
in Italy we said that Patience is the Virtue of the Strongest. so think and wait, count until 10 or 20 too before cry.
3-desperation don't help thinking, so as i 've done just putting my phone in download mode, there is a procedure to put it out, just read, and read or ask.
if you have a question, probably the answer is yet written,use the Search Function. if you do it, is Better.
4-developers have no time to waist,so if you feel that you are not able to do something,please don't do it,but read all info around the forum, i've discovered that if you stay calm and read,link to link you understand things and how they are connected, and there is also more than a guide about terms and specific info.if you read,you learn.if you do it, is Better.
5-and last, if you think that all is simple, just think that this is the result of people using their time working for pleasure,compiling rom and kernels,testing on different phones,so don't be rude, just cause using oneclick you have rooted your phone,or just installin a CWM, all this simple(now are simple thanks to developers) don't allow you to be a developer,so don't be presumptuous
if you use your knowledge to your phone,noone may say anything,and you can discuss with people that know much more ,and like a spiral you understand more and more, and you can play even harder with your phone.
but above,remember that anything you can do it, if you stop in time is not irreversible,the most part of things written over there may cause brick,but over a million of people have cooked room on their phone and also using beta version, so it's not so dangerous, pay attention to what you do, and don't be catched by the fever of wallpapers or killer app.
remember that is a Smartphone, you don't have to waist time on it,using it to call your friends and have a beer if you do it, is Better.
that's it, i was like you, but now i've calmed down my anger of roms, give to them a try, using it for a couple of day, and don't install roms on roms, just to check how it goes, here you have tests and comment,so use the CWM sparingly.
a Big Ciao From Rome to all Xda Forum
Related
i originally had faria's wm6 on my phone, but then i wanted to try xplore core 2.0. i flashed it, but when it finished it would start. it wouldnt go past the second splash screen. i tried a hard reset using the hard keys, but when i try it, it says format failed. i have tried to reflash using bootloader using the OEM carrier roms from both t-mobile and cingular. i am having the same issue no matter what i do. if there is anything i can do to fix this.. please help me because i constantly use my wizard and i don't no what i can do without it. i really appreciate any input. thanks
im not sure what to do but i figured i'd respond just so you know people are trying to help. I've heard of the format failed problem, but im not sure what the solution was. Good luck!
What device do you have ? A G3 ?
How I fixed my Format failed problem...
This is a quote from thread
http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
I followed these steps with an SD card fresh from the package...
Drug_Store said:
...
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY_updateROM.exe (http://wiki.xda-developers.com/uploads/romupdate.rar). After open, on Port selection, choose \\.\WCEUSBSH001 and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
Thanks to all and hope this helps more people with this problem
Click to expand...
Click to collapse
thanks guys... im going to try that.. and just so all of you know, its a g3
thanks everyone who helped me out. my wizard is working perfectly again. i appreciate all the help
wow that's awsome
idd, mtty is last chance weapon.
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
yes, i edited it.
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
You sound like Faria...LOL!
Really, that's why I put what I did in my thread about saying "My phone is stuck in bootloader..." (remember the fillet knife?) ROM's DO NOT MESS UP A PHONE UNLESS THEY ARE CID LOCKED, THE FLASHING PC HAS ISSUES, OR BECAUSE OF OTHER OPERATOR ERRORS.
Don't let it get you down. You're doing a good work and if one or two people out of a thousand can't get it right, then they need to be running carrier ROMs, and you can stay calm and happy helping those who really need it.
See, that's not so bad now is it?
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
jawnsixteen said:
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
Click to expand...
Click to collapse
Nope, flash went to 100% then the phone tried to reboot and nothing happened.
I do all my flashing on that machine because it's stable and I have never had a problem flashing until the Core 2.0 rom. That is the first and only rom I have had any trouble with.
golfernutnflorida said:
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
Click to expand...
Click to collapse
OMG, he used a naughty word.
Like you don't hear it daily?
Get real.
GldRush98 said:
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
Click to expand...
Click to collapse
I do my rom as I please, you can't question that.
For YOU to know all roms have 3 (boot =NOT) splash screens You're just too SMARTass to notice.
You can quote multiple post in same message, in case that slipped your soo full-of-knowledge mind.
I used old WM6 build ? Please explain to me what you mean ...i am not that wize
I did not called my rom STOCK ! I called it Core . But you are probably too smart to actually even read anything.
In case you don't understand the word "CUSTOM", then let me explain it to you : I can change whatever i want in it. All of it if I like to.
Ah yeah, and i almoust forgot ... please read this
http://forum.xda-developers.com/showpost.php?p=1241040&postcount=1
It's been there from day 1, just made it bigger now, so that you can see too
And next time, keep your opinions to yourself. No need for public -> "Ooh, look at me how tough I am ! " stunts.
....
whether you like it or not...
I'm confused by people who choose to post cooked ROMs in a public forum, invite people to use and comment, but them complain if the feedback it not all roses and accolades.
You may have done this for free, and many if not most, appreciate your time and effort. That being said, some have legitimate complaints and are posting them because they have experienced problems with your ROM. I’ve been reading your reaction to any negative feedback and you are highly defensive, never conceding that there may be issues to address.
All cooks say that you are not responsible if the ROM bricks someone’s device or if they have problems, and no one has asked for you to pay for their repairs or replace their devices.
There is no place for foul language or insults in such a forum. It's childish and may simply help support the complainant’s point.
If this is your reaction to complaints, then yes do us all a favor and stop posting and keep your work for your personal enjoyment and benefit.
If you can't stand the heat, then get out of the kitchen. No pun intended.
Well if it doesn't work for you then try a different ROM. I tried all the ROMs and pretty much gonna stay with Faria The Real Thing
I tried Xplore 1.0 and i had alot of troube so I dont think im gonna try 2.0. If it works dont change
Funny thing is I have flashed this ROM to my wizard 6 times, and each time something else didn't work. But let me explain...
I want a stripped version of windows, I don't do any messaging at all. And since the Explorer ROMS are known for their stability, it seemed a logical choice. So I have been using package tools, to create packages with option.XML files for each package so you can choose, what parts of the OS get installed.
But back to the point...
Each time I flashed something went wrong... Something I did, a "tmail not found warning when activesync starts", to once I got a 260(?) error once when flashing at 63% so I started it while holding the voice command button. It booted into Bootloader, I flashed it to Cingular 2.25.11 and immediately flashed back to the same ROM successfully.
There are hundreds of people Ecstatic with the Xplorer ROMs, for each one of you here complaining. I for one would think it a travesty, for a few unappreciative people to ruin it for hundreds of others. By pissing off one of our cookers. Maybe had you posted your problems here we would have been able to help you.
But please don't be so accusing, just read, and if you can't find an answer. Then ask nicely, and thank the cook for the time he spends cooking for us! If you don't like the answer you get or you decide you don't like this ROM try one of the many others...
Hello, I have an Axim X51v that I bought off someone who didn't want to deal with it anymore. Anyway when you turn it on it hangs at the dell logo or sometimes at the windows start up logo, rarely it makes it into windows but it freezes up after a little while. I've tried flashing several different roms on it (so did the previous owner) but each time it's the same result. I've checked diagnostics mode (record+power+reset) and everything seems to check out (flash has a green zero) and every time I flash a rom it makes it through without any problems. Also the bootloader is a10_g3 is this version known to be unstable? Could it be flashed wrong? That's the only thing I can really think of.
You know this forum is for HTC devices?
Im not familiar with Dell PDA's but i cant imagine flashing roms willy nilly will work on a dell which are designed for HTC devices. Give me a link for the ROM which you are currently trying to use.
Have you tried flashing original rom back on, thats wm5 yes?
Yeah I know it's for htc devices (this is where I get roms for my kaiser). But I've also seen roms for the x51 here too and I assumed someone may know something about em here. Anyway I have the "stock" wm5 rom flashed right now (flashed with sdloader) and it's pretty much in the same shape.
We don't frown upon answering questions for other devices. This forum is meant to help people. If you can get your answer here.. cheers on that.. hope you will.
mbannick said:
Yeah I know it's for htc devices (this is where I get roms for my kaiser). But I've also seen roms for the x51 here too and I assumed someone may know something about em here. Anyway I have the "stock" wm5 rom flashed right now (flashed with sdloader) and it's pretty much in the same shape.
Click to expand...
Click to collapse
sorry wasnt meaning to sound sarcastic, ive had some experience of axim but mostly wm5, just wasnt too clear on ur issues, what exactly happens? you say it freezes but what do you do that makes it so?
Well that's the thing it freezes randomly, even just sitting there it will freeze. I want to say its the flash but every time I check it the test comes out clear. So the the only thing I can think of is the bootloader is messed up.
Ive just been to the dell support site and wow, alot of un happy people, i can see why your friend didnt want it anymore...
After doing some reading there i can only suggest you download their official rom and rom updates and see if you can get it running normally. What i dont understand is flashing a new rom should clear everything, i dont think it is the bootloader if the system boots up fully correctly, it has to be a rom issue (or hardware of course).
check out these sites, doesnt make good reading im afraid :
http://search.euro.dell.com/results...~srd=False&ipsys=False&advsrch=False&~ck=anav
http://en.community.dell.com/forums/3530.aspx?PageIndex=2
good luck and let me know how you get on.
Well as I said it takes several tries to get into windows (sometimes it wont work at all until I leave it without the battery for an hour or so) so its not booting up normally at all . Anyway I had the wm5 a12 rom on there for a while but it still has the same problems (I used sd flash since I really cant sync and flash with the way it freezes). So yeah I'm not sure what I can do
mmm.....
If youve had several different roms on it, including official ones, it could mean a hardware problem too.......
Im no chef, but i would have expected a bootloader issue to be resolved with a known working official rom?
How old is the Dell? Just a thought, have you tried the online help with a technical rep from Dell, they were good when trying to sort out an issue with my 4 year old laptop? Sorry but im running out of ideas........
Hey I think I got it! Seems the previous owner modified the battery latch. After messing around a bit I stuck a toothpick on the "button" that is depressed when the door is closed and it seems to be running perfectly stable! I even did a few resets and each time it boots just fine. Thanks to everyone who replied and offered advice.
hoorah! saved by a tooth pick, now ive heard it all haha. congrats!
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 :-(
Last night I switched my SD card (16GB Class10 Kingston) in my O3D and checked the "Use external/internal sd" in CM settings and rebooted my phone.
The /root/sdcard path was located to the INTERNAL sdcard before the switch.
I think that the option was NOT checked BUT when it check it, it became "Use internal" which is incorrect.
Anyway, my phone wont boot, not even when holding down VolUp+Power.
I will keep trying but just a warning to you all, don't do any hardware change with the Nightly builds (assuming that the sdcard is hardware)!
I'm using linux so I'm not sure that it's possible to use any software like the softwares on windows.
have a look at this thread http://forum.xda-developers.com/showthread.php?t=1433274 , they have the same problem as you. Apparently its because you switched the internal/external.
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
gamesz2 said:
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
KurdX said:
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
Click to expand...
Click to collapse
Ow iam sorry man i read it wrong iam from holland :0
Sorry
Sent from my LG-P920 using XDA App
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
lrpvo said:
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
Click to expand...
Click to collapse
You don't need XP, will work on 7 aswell.
Haven't had time to fix my phone yet but I will fix it through 7 so I can post the result here when fixed.
same problem here, too.
any solutions yet?
omgomg said:
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
Click to expand...
Click to collapse
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Marcovecchio said:
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Click to expand...
Click to collapse
My point exactly all these people are getting big headed if they opened it up people can fix stuff and get it done much quicker but i guess they get money for it.. I'm going to have to let go of this phone shame was a good phone though..
I had almost same thing I formatted my ad card on cm7 38 build for p925g. Total brick it's in a disconnect reconnect loop and no comm conection so very. Close to a full brick taking it in tomarow.
Posted from my crap ass slow as f*** 3GS iphone
Phone in unusable state.
Same issue here coming from CM7 build 16. All I see is the disappearing/reappearing OMAP4430 device in device manager.
THIS PROBLEM SHOULD BE STICKIED]
Any idea what to do guys??
Yes it should i was lucky my phone was under the 30 days still so they just handed me a new phone on the spot wich was nice but im going to stay away from cm7 like the plague yes this should be sticked her andin the thrill forum as well.
I had to take mine in there was no way to get the computer to see the phone to flash it.
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Indeed, he says he reads it, but that forum is completely DEAD, no posts for 2 weeks. I already reported this bug, had not a single answer. And the nightlies have no P920 specific work for weeks. And since arcee seems to be the only mega-master-guru around, a person no one can talk to, this is what we have: a dangerous half-working CM7 that will destroy many more O3D around, and there´s nothing we can do.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Im. Just posting hear so every one else. Dosent make the same misstake as me and end up with a paper weight on tbere desk.
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: