Hey guys I was trying to unlock my bootloader, and when I booted into fastboot, my phone shut off and my phone was detected as QHSUSB_BULK on my PC and will not respond to anything. Any help would be appreciated. Thanks.
AFAIK (personal experience on other devices) it's dead. Until someone comes up with a JTAG, you're gonna have to try your luck with OPO customer service.
Thanks
rani9990 said:
AFAIK (personal experience on other devices) it's dead. Until someone comes up with a JTAG, you're gonna have to try your luck with OPO customer service.
Click to expand...
Click to collapse
Thanks for responding. Do you know specifically what causes this issue (For future reference)?
Man, anything to do with QHUSB is never good from pretty much everything I've read about it here on XDA. We can't help you on this issue. QHUSB is the very definition of a hard brick. My friend, you're going to have to suffer through the agony that it OnePlus Customer Service. Best of luck.
Can you tell us exactly what you did so other people don't end up with the same outcome as you? Really sorry to hear this, man.
When I have seen this on other devices it often is due to loss of or corruption of firmware that has to do with the boot sequence such as bad bootloader or radio. I was messing with LOGO partition and nearly bricked my OPO the other day, got the same driver coming up. But luckily it rebooted back to os on its own and I just had to dd the partition back to stock in order to get bootloader back and functioning.
So other than JTAG you most likely can't do anything without shell commands available to you
Eshraq said:
Thanks for responding. Do you know specifically what causes this issue (For future reference)?
Click to expand...
Click to collapse
Typically, bootloader corruption is the cause of a phone entering QHUSB (Qualcomm High-Speed USB) mode. QHUSB is a very low level, extremely basic level of functionality that your phone can have with your computer; hell, it's so low-level, no one has been able to find the significance of it or how to reverse this mode yet (with the exception of a few people with a few legacy HTC device, and having some very lucky breaks, like Demkantor above me). Think of it as your phone being brain-dead. All of the things that made your phone yours (data, pictures, apps, pretty much everything having to do with data) is gone. Only the basic functions (USB connectivity through QHUSB, battery) are still functioning.
This is truly the worst-case scenario of development. Very sorry to hear.
treChoy said:
Man, anything to do with QHUSB is never good from pretty much everything I've read about it here on XDA. We can't help you on this issue. QHUSB is the very definition of a hard brick. My friend, you're going to have to suffer through the agony that it OnePlus Customer Service. Best of luck.
Can you tell us exactly what you did so other people don't end up with the same outcome as you? Really sorry to hear this, man.
Click to expand...
Click to collapse
What I said is what literally what happened. I booted into fastboot. Crashed and the end result is there. I'm not sure what else to say. I'm definitely going to try to return it and just get the next nexus. Whatever.
demkantor said:
When I have seen this on other devices it often is due to loss of or corruption of firmware that has to do with the boot sequence such as bad bootloader or radio. I was messing with LOGO partition and nearly bricked my OPO the other day, got the same driver coming up. But luckily it rebooted back to os on its own and I just had to dd the partition back to stock in order to get bootloader back and functioning.
So other than JTAG you most likely can't do anything without shell commands available to you
Click to expand...
Click to collapse
Wait what do you mean it rebooted back on its own?
Alright I long pressed the power and it turned on
Nice People of OPO Channel
So I went into the OPO channel. They told me to long press power. It worked. I think I might be lucky. Or something else maybe.
Related
So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on
wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?
Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.
thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement
In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed
Anybody out there with a solution?
I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.
Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!
KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.
I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App
SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?
Ddi you ever get your phone sorted ? I'm now in the same situation !
Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.
Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......
Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.
Hi guys,
No able to turn the device on,
to switch to a download mode, (tried all methods),
when connect to computer via ODIN comp doesn’t recognize device.
(battery charged, used other device for charging)
Help please!!!
thank you!
Eugg_ said:
Hi guys,
No able to turn the device on,
to switch to a download mode, (tried all methods),
when connect to computer via ODIN comp doesn’t recognize device.
(battery charged, used other device for charging)
Help please!!!
thank you!
Click to expand...
Click to collapse
You either have a severe hardware failure or a corrupt bootloader.
Since it's nearly impossible to corrupt bootloaders on our device I'm guessing hardware failure. Take it in for warranty service.
What were you doing with it before it died? Provide details.
Entropy512 said:
You either have a severe hardware failure or a corrupt bootloader.
Since it's nearly impossible to corrupt bootloaders on our device I'm guessing hardware failure. Take it in for warranty service.
What were you doing with it before it died? Provide details.
Click to expand...
Click to collapse
I'll see your corrupt bootloaders and raise you a 10 kiloton explosion.
Gentlemen, we can rebuild him. We have the technology.
I have had two people now that have had completely dead batteries and did not know. Try to charge your battery. See if the emblem comes on while charging. If it does leave it alone for at least 4 hrs then try to enter download.
Sent from my SAMSUNG-SGH-I997 using xda premium
If you are using a Windows PC to run Odin, make sure that you have installed the correct drivers to connect with your phone. I believe these are proper:
http://downloadcenter.samsung.com/c...ATT_SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip
You can also spend $1.99 on eBay for a resistor jig:
http://www.ebay.com/sch/i.html?_nkw=jig+download
I once had something crazy happen after a bad crash with an experimental overclock kernel for the vibrant on my captivate. the screen went black even in download mode. but the phone was infact in download mode just no screen image. it flashed in odin and restored me back to stock.
I know its an off chance but if you happen to have had a similar error and your drivers in windows aren't installed right then it may look like a hardware failure.
if you have insurance get another one. if you haven't voided the warenty send it to Samsung. if you want to help out development donate it to Adam outler. he wants something not restorable by normal means.
My Infuse recently did the very same thing. DEAD ON ARRIVAL! I tried all forms of CPR but she died an untimely death while attempting to flash back to stock. I had done that many times before so it wasn't anything I did wrong. I took it back to the ATT Store and they sent me to the device support center to get a new one. The new one is far more stable ans performs better than my original out of the box model. So just take it back and get another one or call warranty and they will ship you one overnight.
Product F(RED) said:
Gentlemen, we can rebuild him. We have the technology.
Click to expand...
Click to collapse
Nice one. Lmao
Sent from my SAMSUNG-SGH-I997 using xda premium
Blackberrynomore said:
My Infuse recently did the very same thing. DEAD ON ARRIVAL! I tried all forms of CPR but she died an untimely death while attempting to flash back to stock. I had done that many times before so it wasn't anything I did wrong. I took it back to the ATT Store and they sent me to the device support center to get a new one. The new one is far more stable ans performs better than my original out of the box model. So just take it back and get another one or call warranty and they will ship you one overnight.
Click to expand...
Click to collapse
Yeah, you just got a bad model, it happens.
At OP, if you have warranty with AT&T, take it back to the store, and ask for another one. If not, call Samsung, you can ship them your phone and then they'll either fix it, or send you another one.
Sent from my phone. :3
Eugg_ said:
Hi guys,
No able to turn the device on,
to switch to a download mode, (tried all methods),
when connect to computer via ODIN comp doesn’t recognize device.
(battery charged, used other device for charging)
Help please!!!
thank you!
Click to expand...
Click to collapse
Depending on what you were doing, you may have hard bricked your phone. A usb jig may work for a soft brick but since your phone has no response whatsoever, chances are its hard bricked. Go to "mobiletechvideos.com" they provide a JTAG service that unbricks hard bricked phones. give it a shot
Why pay for JTAG service when his device is still under warranty? Contact AT&T or Samsung. One of the two will hook you up.
hi guys,
thank you for your help
i like what he said better
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 :-(
Sorry if this is the wrong place to post - just wanted to share my unpleasant experience.
I've bricked my phone in a peculiar way - it appears to be a hard brick, non-responsive to any buttons. Plugging in to the computer gets me the dreaded qhusb_dload QPST download mode. Not a good sign.
It wasn't due to faulty ROM flashing, either. I made a bad edit to /system/etc/vold.fstab fiddling with the way the internal and external SD cards get mounted - mmc1 instead of mmc2. After one reboot, I had some sd card corrupted errors. Proceeding to format the card may have been my fatal error. By the second reboot, I was bricked. D'oh. I imagine I had accidentally mounted a partition of the internal emmc that is critical to normal operations, then tried to wipe it.
From what I've read, a USB jig won't do much good, but it's worth a try.
Anyone messing around with their /system folder, be warned.
That's sux, but on a good note, $50 and a little waiting will get your phone back, or you could just warranty that sucker ;-) give more refurb units to some other xda members lol
I sense another refurb sale on ATT.com. Sorry to hear about that, sounds bad. No guts no glory right?
I purchased this as a refurb, too. The cycle continues...
Not sure how the whole exchange process will work in this case. I mean, I can exchange for a different phone, or a new Skyrocket and pay the difference, but I really had my heart set on a cheapo skyrocket. Perhaps if I take this up with Samsung instead?
Ur 90 warranty is over already? That sux then. I personally would pay $50 and get it de-bricked, its the cheapest/best option.
I didn't expect much in the way of warranties because I purchased this refurbished. With Samsung customer service I didn't have much luck. However, I just got off the phone with AT&T, and they're overnighting me a replacement, which is cool. They have a 30 day policy on any web store items, so I'm covered. Anyways, lesson learned
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
RussianBear said:
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
Are you in thw process of bringing that to the skyrocket?
silver03wrx said:
Are you in thw process of bringing that to the skyrocket?
Click to expand...
Click to collapse
we need all the help we can get. just a bunch of curious noobs, ya know
the main discovery we did with sensation was to make the emmc visible to any pc it's connected to, then overwriting whatever was messed up (like the hboot) with a stock version of that file.
in theory, you should be able to do this to any phone running on a qualcomm chipset once it's in the qhsusb_dload mode. still lots to test, but anyone is welcome to participate, of course!
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
silver03wrx said:
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
Click to expand...
Click to collapse
nope, just sensation. they both run on a qualcomm chipset though, so i'm just speculating here.
the bricks we're "saving" right now are for people that executed s-on without fully reading the instruction, thereby leaving them in qhsusb_dload mode. your cases might be specific to a different area, but the principal is still the same:
find what is messed up and replace it with the correct file via open emmc
Big progress made for APQ8060 and MSM86xx processors. Sensation hard brick solution coming very soon and SkyRocket/T-Mobile Galaxy S II solutions already solved...
What's this I smell? Possible de-brick
Sent from my SAMSUNG-SGH-I727
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
amnher said:
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
Click to expand...
Click to collapse
i have the same problem xperia miro
any updates ?
Hey guys,
after some research I found one suggestion that I can't test yet so maybe until my battery runs out one of you can help me:
I unlocked my TF300T ICS 4.0.3 and had CWM running. Probably because of some mistakes of mine it stopped booting at some point and now I can't access recovery, Fastboot, and when I was able to get into CWM, the internal storage didn't work, which is where the NAND backup was stored. Now it only shows the flat white ASUS logo with "device is unlocked" in the corner. When I try to turn it off it automatically reboots.
ADB shell can't find the device so I'm all out of ideas, except that I just read that that once it runs out of battery life the bootloader automatically resets. Maybe that'll help.
Does anybody have any ideas as to how or if I can actually fix this mess?
crstn said:
Hey guys,
after some research I found one suggestion that I can't test yet so maybe until my battery runs out one of you can help me:
I unlocked my TF300T ICS 4.0.3 and had CWM running. Probably because of some mistakes of mine it stopped booting at some point and now I can't access recovery, Fastboot, and when I was able to get into CWM, the internal storage didn't work, which is where the NAND backup was stored. Now it only shows the flat white ASUS logo with "device is unlocked" in the corner. When I try to turn it off it automatically reboots.
ADB shell can't find the device so I'm all out of ideas, except that I just read that that once it runs out of battery life the bootloader automatically resets. Maybe that'll help.
Does anybody have any ideas as to how or if I can actually fix this mess?
Click to expand...
Click to collapse
I let mine discharge all the way, and then I recharged it. I can confirm that it does NOT reset the bootloader.
jrfaulkin said:
I let mine discharge all the way, and then I recharged it. I can confirm that it does NOT reset the bootloader.
Click to expand...
Click to collapse
Ya it didnt work for me either. So is that thing bricked or what? :/
crstn said:
Ya it didnt work for me either. So is that thing bricked or what? :/
Click to expand...
Click to collapse
Well, not totally. We are going to need a whole lot of help though to be able to get bootloader flashed. We can access the device via APX. I think we need the partition table information and the secure bootloader keys (which ASUS has to release to us) in order to use NvFlash to flash the bootloader. Word is that the developers who came up with this procedure for the TF201 are working on this, and have been for a couple of months. Hopefully, a bunch of people bricking their devices all of the sudden will turn up the urgency on this. I'm not holding my breath, but I am keeping my fingers crossed!
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Count me in on the bricked parade. Except I did mine a while back. I may be missing something but how do you get to APX mode? I just reformatted my computer so I haven't got drivers or ADB set up yet. I probably should try before asking, however I don't ever remember getting into it before.
Sent from my SCH-I535 using Tapatalk 2
enomele said:
Count me in on the bricked parade. Except I did mine a while back. I may be missing something but how do you get to APX mode? I just reformatted my computer so I haven't got drivers or ADB set up yet. I probably should try before asking, however I don't ever remember getting into it before.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You can get in to APX mode by switching it on, holding the volume up button and than use the pinhole reset while keeping the volume up button pressed. If you have it connected to your PC, it will show up. No drivers tho, so it probably won't bring you far.
The problem with waiting for an NVFLASH solution is that we probably need an adapted bootloader to start with for it to work. Since its impossible to make any changes to it without fastboot, I wonder if any solution will become availlable. I will wait another month or so, and then send it to ASUS if no solution is provided here.
I'm sure the costs for repair will be less than the $200 that the nexus costs (and to be true, although the Nexus is a great machine, it's not comparable to the wonderful TF300 )
Sphinix said:
You can get in to APX mode by switching it on, holding the volume up button and than use the pinhole reset while keeping the volume up button pressed. If you have it connected to your PC, it will show up. No drivers tho, so it probably won't bring you far.
The problem with waiting for an NVFLASH solution is that we probably need an adapted bootloader to start with for it to work. Since its impossible to make any changes to it without fastboot, I wonder if any solution will become availlable. I will wait another month or so, and then send it to ASUS if no solution is provided here.
I'm sure the costs for repair will be less than the $200 that the nexus costs (and to be true, although the Nexus is a great machine, it's not comparable to the wonderful TF300 )
Click to expand...
Click to collapse
I was quoted between $87 and $100 to "repair the OS" on my tablet. It's still at the Asus RMA center, so I have no update on what they did with it. I've been posting progress over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Yeah, I saw your posts somewhere else as well... All the best, I've been hearing horror-stories about having to replace the mainboard etc. That would be a bit too much, I imagine :-|
just a quick update:
i sent the transformer back to amazon and they took it back no questions asked.
phew...
Same happened to me, I sent it to Asus about a month ago, they just replayed to me with a mail, saying that is out of warranty because of the bootloader unlocked, and that is gonna cost me $122 for the mainboard, and $65 for labor, it seems that the mainboard got really bad bricked, and they are replacing it....
Really bad for me, but at least I would have it back...
jrfaulkin said:
Well, not totally. We are going to need a whole lot of help though to be able to get bootloader flashed. We can access the device via APX. I think we need the partition table information and the secure bootloader keys (which ASUS has to release to us) in order to use NvFlash to flash the bootloader. Word is that the developers who came up with this procedure for the TF201 are working on this, and have been for a couple of months. Hopefully, a bunch of people bricking their devices all of the sudden will turn up the urgency on this. I'm not holding my breath, but I am keeping my fingers crossed!
Click to expand...
Click to collapse
Unfortunately NVflash will only run on unbricked ICS Bootloader devices. You have to flash some files before you can use the special APX for TF300. So if you are already bricked it will not help.
Sphinix said:
Yeah, I saw your posts somewhere else as well... All the best, I've been hearing horror-stories about having to replace the mainboard etc. That would be a bit too much, I imagine :-|
Click to expand...
Click to collapse
I've just been quoted $122 + $65 + $10 shipping. Which comes out to a shade under $200 total.
End of the line, folks.
I'm not paying Asus $200 to fix a $300 tablet, and I'm basically going to be throwing in the trash at this point if I get it back.