Related
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Hard brick, its done
Jtag or send to samsung
hedpe said:
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Click to expand...
Click to collapse
If it does absolutely nothing, i'd say you bricked it which is quite possible if you flashed something for another phone. I don't think a jig will do you any good, based on things i've read before. Not 100%. Maybe someone else will give you some better input.
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
hedpe said:
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
Click to expand...
Click to collapse
I don't know any off hand, but why would you keep bricking it?
xcrazydx said:
I don't know any off hand, but why would you keep bricking it?
Click to expand...
Click to collapse
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
hedpe said:
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
Click to expand...
Click to collapse
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
xcrazydx said:
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
Click to expand...
Click to collapse
Right, understandable. Lesson learned there.
I can't tell if this is legitimate or not:
http://www.jtagbox.com/2012/03/page/2/
$50 isn't too bad. Obviously doing it yourself, if you could, would be better. I'd be on the safe side though and have mobiletech (i'm assuming you know about them), do it.
Alright... heres the situation, I have an Samsung galaxy s2 LTE i7R2 from Rogers... rooted.. worked fine. tried to flash a rom after erasing all data... and now my phone wont turn on, cant boot whatsoever.. tried pulling battery and holding the volume buttons and plugging in usb to download boot and no dice...
ive had this thing for 3 months its for sure not the hardware... anyone know how the hell i can fix this situation without returning my phone... im not a dumby.. but i feel sort of dumb for trying to put a i777 rom on my phone and not realizing it until my phone doesnt boot anymore... uhg... someone please help me
Flashing a 777 rom is a hard brick so no you can't save it you f'd up jtag is your only hope
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
are you sure ... theres nothing i can do!
She's dead, Jim.
thejbomb87 said:
are you sure ... theres nothing i can do!
Click to expand...
Click to collapse
Yes I'm sure give up hope
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
one of you guys have to be smart enough to find a way around this
uhg... i guess ill just take it back to rogers and say it crashed..
Uh oh, here it comes....
Its just common since to not flash anything for any other phone. You learned the hard way instead of reading.
oh believe me.. i was reading up all day.. i am not a tech noob either, i deploy computers for a living... i just had so many windows open i downloaded the wrong zip because i was checking other roms and features out... blah i guess ill just make a USB jig..
Jig won't help you you have damaged your partitions and can only fix with jtag why won't you listen I'm not stupid dude I been around for a while
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
thejbomb87 said:
oh believe me.. i was reading up all day.. i am not a tech noob either, i deploy computers for a living... i just had so many windows open i downloaded the wrong zip because i was checking other roms and features out... blah i guess ill just make a USB jig..
Click to expand...
Click to collapse
But there are no i777 roms in this forum. You would not look on the MAC forums for Lenovo support would you?
Okay so the USB jig wont work at all... damn... whats jtag.. i wonder if rogers will even take my phone back
thejbomb87 said:
Okay so the USB jig wont work at all... damn... whats jtag.. i wonder if rogers will even take my phone back
Click to expand...
Click to collapse
Uhhhmmmm... have you tried google? You are not a tech noobie, right?
Sent from my Calculator with Android.
Yea i have looked through google... its a hard brick so not much i can do at this point.. i was thinking a USB jig would get me to download mode... but im being told other wise.. blah this sucks
I suggest sending it off for jtag. You knew the risk, now pay the price. Its an expensive lesson. But a lesson learned hopefully. you can probably get your phone back instead of trying to con Rogers out of a new or refurb phone.
There's another one for noobs/ people who don't listen or read other peoples mistakes! Huh way to go to make skyrocket owners look like we like bricking our phones.... :thumbdown:
Android 4.0.4 AOKP
Ok first of all relax on the hate... im not making anyone look back but myself, i clearly made a simple mistake which cost me a working phone, not much i can do now... i may still try to USB JIG and see if i get anywhere... if not then i will send it in i guess.. anyone know the cost of a Jtag... and what are the chances of rogers just replacing it.. or reflashing it
Seriously.... http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-skyrocket-jtag-brick-repair/
This was recommended in the past. Next time search before you post.
Well i appreciate all the suggestions and help.. and sorry for the hostile people who clearly need to get girlfriends.. like calm down its a question first of all, second of all not everyone has time to spend 9 hours researching bricked phones, I agree i should have taken better steps towards not bricking my phone.. my bad, i guess JTag will get this one... or i will send my phone in to rogers most likely for repair..
It only takes 10 seconds to GOOGLE. Just saying. Its just thread after thread after thread of people flashing the wrong rom, asking for stuff that is right in front of them, or posting threads in the wrong forum all together.
I think my ATT htc one x may be hard bricked...
I was playing around with ROMs and lost track of time. The last recovery I had on there was clockworkmod (was going back and forth between it and twrp).
I was trying to install the new jellybean rom and it kept on giving me an "assert failed" error. At this point, I deleted the assert lines from the recovery script as advised by one of the posters, and ran the install again. Went through... rebooted and...
The phone is completely dead now. I think it may have discharged? I plugged it in to the wall socket and nothing... absolutely no lights, no screen..... Power+ vol down does not work either....
Please help me, is there any way to recover from this situation?
Wrong subforum.
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Rusty! said:
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Click to expand...
Click to collapse
Doesn't seem like a rare thing occurring. Either people are overseeing this or they are not really aware that for you can't flash a rom made for a tegra quad core device onto a dual krait.
I used this....
http://forum.xda-developers.com/showthread.php?t=1763240
Sheesh..... Is this meant for the tegra? I never thought I would do such a thing.... I was aware of the issue/hardware differences....
Is there any hope? Actually, in device manager it shows up as QHSUSB_DLOAD and I heard thats a bad sign?
If it cannot be fixed, does anyone have an estimate about how much HTC would charge to reflash/fix it?
My signficant other is as po'ed at me as can be... especially since I had really pushed for the upgrade.... man...
Yes it's meant for the Tegra One X, that's why it wouldn't install (that, and it's not in the AT&T One X section). You bypassed the check the install script does to make sure you're installing it on the right phone.
In short, yes you have buggered it, QHUSUSB_DLOAD is a state where you can write things to the phone, but whether anyone as done any research into it on the S4 One X I don't know.
As for getting it fixed, I have no idea on cost, however... if you convince HTC that you didn't do it yourself, it might be possible to get it done under warranty.
Edit: Did a bit of research and /system on the Tegra One X is is HBOOT on the S4 One X, that's why it's ruined your phone.
htc would just replace the motherboard and charge for that - loads of people have reported the cost its something like £169 to replace motherboard, which would of course un brick it.
Have you tried to keep it plugged in to a charger for an hour or so? My HOX was dead too but started to flash red light after an hour, moment after solid light and it booted
Sent from my HTC One X using Tapatalk 2
He doesn't have an HBOOT any more, there is nothing he can do.
This is why people should stop being stubborn and call that phone HTC One XL. These kinds of situations would happen sooner or later.
Sent from my HTC One X using xda app-developers app
I guess I did... I actually had come to that page via google and since, perhaps I was a bit sleepy, did not verify the source... should have....
Is there any fix at all? Like loading the drivers and reformatting it or something?
Im a bit confused about the motherboard replacement: since its a software issue, cant HTC fix it with a software update? Ill call them today and post the answer on this group as well, but knowing what I am dealing with may help in talking with them.
Thanks to everyone again
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Rusty! said:
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Click to expand...
Click to collapse
Thanks... Someone in that section has kindly agreed to see if he/she can help me... Keeping fingers crossed... doent feel right to tell att that my phone stopped working for a replacemenf...
Hate to say it but your phone is dead. It's not revivable ar this time and so your only option is jtag or warranty replacement because you overwrote the Hboot.
Sent from my Inspire 4G using xda app-developers app
Don't let morals get you on that one. Lie to them, if not for yourself than for me.
Sent from my HTC One X using xda app-developers app
RobertX1 said:
I used this....in device manager it shows up as QHSUSB_DLOAD ..
Click to expand...
Click to collapse
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Not quite, there is a debricking method for the Sensation that can recover from it.
In most cases though, you're right.
Castellano2 said:
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Click to expand...
Click to collapse
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Please move this thread to the XL subforum
miniterror said:
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Click to expand...
Click to collapse
Thanks... any hope for this being possible for the one XL? Also, could the mods please move this thread to the ATT section (sorry for posting it in the wrong section... but I really didnt know the importance of the difference.... wanna look at my phone? )
Thanks everyone. I think I might send the phone to HTC to get it repaired.... although the s***ty thing with that is that Ive heard they take that opportunity to replace the motherboard instead of just replacing the software, and hit me with a big bill rather than a reasonable/fair price....
So.... trying to be honest (by not returning the phone as defective to HTC) ensures that I get scammed by them... :victory:
Possible? Yes of course, that's the point of that mode as I understand it, with some other HTC phones you can hook it up to a RIFF Box and load it up.
Likely? Probably not, as it'll take people looking into it in depth to figure it out and as far as I can see, no-one has/is looked/is looking into it on the OXL.
It really does look like you'll need to send it to HTC, which (as you sound quite honest) will probably be expensive.
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