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!
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...
I think this might have been covered before :lol:
Got a Wizard here that came with WM5 from o2 a few years back, its a work phone so doesnt get a massive amount of hammer but its slow, dead slow.
I just want something really small and quick, phones always on charge unless I'm out and about which isnt that much so perhaps oc'ing it might help?
I downloaded a WM6 rom by mfrazz (5.2.318(15342.4.0.01)) about a year ago and yes it looks nice and does more than the Wm5 that was on the phone to start with, but its irritatingly slow, I'm using the phone more than I was originally so it makes speed more of an issue.
I tried to flash a rom called "Wizard_19855_Clean_V1" but now I seem to have lost the phones ability to find a service.
The phones not bricked so I presume all is not lost but a quick shove in the right direction would be appreciated, the other option of course is to stick WM5 back on it if someone has a link to the latest (last?) o2 WM5 rom, then drop it down the stairs or something and get a new work phone perhaps :lol:
Nevermind, almost perfectly timed, 83% through flashing the phone with the 6r5 rom from Mfrazzz we've just had a power cut...
So, what do people recommend as a replacement to a bricked Wizard lol...
it is not dead. can be revived. well, if you want it to be.
get your power turned back on, then put it in bootloader after charging it completely and flash again.
I can get the bootloader RGB screen, have tried the solution here http://forum.xda-developers.com/showthread.php?t=276963 but get the "You didn't get the proper security level to download a specific image" error, just trying to sort that out now, phones on charge while I dig out the solution to that now, something to do with it being locked seems to be the problem, will see how far I get and then try again..
38% thru reflashing with the Update Utility File thing...
See if we can keep power in the building this time
Right, were back on WM5 thanks to the Wizard Love rom, when I try to stick mfrazzz's 6r5 on tho it gets to 99% and then fails, have tried it a few times now but with the same results..
try a release like amp(linkage) or a tnt thats known for speed. Ive been using amp's newer release for months on att's network, with strong service and considerable speed boosts over the older faria/mrfrazz roms i used
i have yet to need to oc this amp build but was a pretty avid overclocker of my older ones.
ps: im prolly going to cook/flash this rom when release 2 comes out(hopefully tonight) cleaner slate than amp
http://forum.xda-developers.com/showthread.php?t=415157
pss: if you're not.. try flashing with no sd card too
Yeah not got the SD in there when flashing, I've tried a few different ROMs now and it looks like I missing something as it still appears to be on the Wizard Love WM5 rom even though I'm trying to get it up a WM6 rom (Brightrom/Manilla UI/XM6r5)..
Will try the one you've linked too and see how that goes..
Somethings not right here, I've gotta be doing something wrong, usign shell tool it tells me that the Wizard Love rom has the following.
Externsion ROM
OS
GSM
Splash Screen
HTC Logo
Yet the other rom's I've been trying only appear to be the OS, and even though they seem to be uploading to the phone properly when i reset it it still has the Wizard Love rom on it..
I have an ATT Tilt, and im getting fed up with it. Ever since i updated the new rom for it, it randomly shuts down, freezes constantly, and email and things like that dont work... It consistently freezes every time i get a call, on top of just completely randomly while in my pocket...
So my real question: Would getting a custom rom fix these problems at all, or is it not worth it to risk damaging the phone? The only custom rom i have seen around is Manila i think, if there are others which ones do you think are best?
Thanks much for your help!
jeordy said:
I have an ATT Tilt, and im getting fed up with it. Ever since i updated the new rom for it, it randomly shuts down, freezes constantly, and email and things like that dont work... It consistently freezes every time i get a call, on top of just completely randomly while in my pocket...
So my real question: Would getting a custom rom fix these problems at all, or is it not worth it to risk damaging the phone? The only custom rom i have seen around is Manila i think, if there are others which ones do you think are best?
Thanks much for your help!
Click to expand...
Click to collapse
Your questions one at a time:
Would a custom ROM fix these problems?
Yes, probably. But might lead to new ones.
Is it worth the risk?
Only you can answer that. However, if an official ROM has produced the problems you mentioned, I would try to reflash the same official ROM first - redownload the file and everything just to make sure you didn't get a bad flash.
As long as you use HardSPL, flashing ROMs should be pretty safe. But you will more than likely void your warranty. Just read a bunch before you flash. I would start with
This: http://forum.xda-developers.com/showthread.php?t=396922
and then once you have that on your machine you need to surf around
Here: http://forum.xda-developers.com/forumdisplay.php?f=378
to get a good idea of what ROMs are out there for Kaiser. I saw five or so on the first page.
Which ROM is best?
Again, only you can answer that. Try a bunch and you will probably find a good one.
there are alot more roms available you will need to look under the "kaiser" rom section and you will find a pot of gold
Thanks for ur help guys.. Ill check out those links and all the roms once i get home today..
hey jeordy,
I am having the same exact problems with my tilt. I had to unlock it as I use tmobile. If you come up with any solutions please post here. I hope you do.
Thanks
Hi,
I've had my Touch Pro for about a month and I've had enough of that stupid Vodafone start-up screen and everything!
So I've been reading up on this forum and downloaded Total Commander, Advanced Config and RegEdit and I haven't seen anything on here about ROM's on a Vodafone Touch Pro...........and I'm a bit scared of bricking my phone!
So has anyone got an idiots' guide to getting a decent ROM on my Touch Pro? I mainly just want to get rid of all the Vodafone branding and then maybe start playing about with it more!
Thanks
I've just got a Vodafone one too! And was wondering the same thing
I'll await answers from the masses
I have the UK Vodafone Touch Pro and have just changed the ROM to ROMeOS 1.40.1. The speed difference is substancial, and I would recommend it if you are willing to risk your warrenty.
Just make sure you follow all the posted advice regarding flashing your rom.
hairyman said:
I have the UK Vodafone Touch Pro and have just changed the ROM to ROMeOS 1.40.1. The speed difference is substancial, and I would recommend it if you are willing to risk your warrenty.
Just make sure you follow all the posted advice regarding flashing your rom.
Click to expand...
Click to collapse
Has it improved the handsets ability to receive a strong signal.?
gjc10212 said:
Has it improved the handsets ability to receive a strong signal.?
Click to expand...
Click to collapse
I've never had a signal problem, so I wouldnt think so. Its just an OS change, not the radio.
I have a vodafone rom and I thought the slowness was normal (I mean how would I know and different?) :S If there are alternatives, I too am interested.
I had the phone for about a month before I decided to look into the other ROMs, mainly because i'd got into the habit with my old v1606 (Hermes).
After looking at a few I eventually decided to try the ROMeOS one first, and so far I havent regreted it. It seems much faster, and the changes that have been made seem to improve the operation.
You still get the initial Vodafone boot screen then an alternate ROMeOS one, however even the boot seems much faster to me (I haven't actually timed it)
The only thing I will say is that if you like to modify TF3D then uninstall the 'HTC Manila Enhancements' using Remove Programs before you install any other mods or you may get a clash as I did.
I should add that I have only flashed ROMeOS in the last 24hrs so a full 'workout' has not been given to it yet.
Also make sure you read and follow the beginners guide in the ROM Development folder before you attempt the flash.
I have my Vodafone UK Touch Pro for 2 months. Yesterday i decided to change the ROM.
There is sooo much hype about bricking the phone but all the tools out there made it very easy for me, actually i only used 2 tools!
First download and install HardSPL
Then install the rom of your choice using the supplied .exe.
Simple, where abouts you based, could poss do it for you if you want?
I did manage to change my ROM - to the afour mentioned ROMeOS ROM - which is awesome. I did download Elite ROM but it was loaded with way too many programs for me!
It is a simple process, but I still get worried!!
I would like to change my Vodafone branded device to the Romeos rom if possible but want to know how I can make a dump of my current Vodafone ROM so If for any reason the device needs to be sent back I can shove that ROM back on?
Also, when changing roms, Is there a way to not lose your text messages?
Thanks
Regards,
Neil
Yeah - use a program called PIMBACKUP. I've backed all my stuff up about 3 times now with no problems.
You can save your original ROM, I never did as you can download the stock ROM's from here.
Read the Flashing For Newbies topic - it's invaluable. It ill have the links for the downloads you need
Touch Pro's Worst Rom
Just wanted to add my vote for hating this ROM. The red theme is horrible.
I thought I would wait a bit before flashing after shelling out £370 but this ROM was totally ruining my experience. Flashed within 12 hours of the phone arriving!!!
Can anybody who has successfully removed the Vodafone Rom and installed a new one shed some light on how they managed to do it. Ive flashed roms dozens of times on my Kaiser and the Hermes and had no problems at all but so far ive had no joy with the Touch Pro. No matter how i try and install hard SPL (either via the pc or using manual install) i never get past the black screen stage and 0% progress and then when the phone restarts nothings changed and i can no longer connect to Active Sync without hard resetting the phone and restarting the computer. I cannot use the Vodaphone Rom its so awful so im desperate for some advice.
MagicAlex - I flashed my TouchPro twice and had no problems either time. I basically followed the step by step guide which is stickied to the other ROM Developement forum.
Sorry I coudn't be more help, but that's how I did it, thanks to this wonderful forum
oh yeah ive flashed mine three times now. it turned out to be some mysterious issue with my pc. after two days of getting nowhere using Vista32 i plugged my TP into my girlsfriends laptop running Vista64 & it flashed first time. I have no idea what the issue is as i flashed my Vario2 & 3 dozens of times on my pc with no problems at all. very strange!
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 :-(