Related
Hi All,
I have a G Tablet and have gotten myself into a right mess.
I had bricked the device to a point where the logo splash screen would appear, but it wouldn't progress any further. I couldn't get into CW restore or anything.
I got the unit into APX mode, installed the driver and managed to get a connection.
Then I accidentally ran the "nvflash_1gb_lcd.bat" file.
Now the unit doesn't want to even go into APX mode, so I can't reflash the unit with a different boot/restore/system img set.
Is there any way that I can get back from this?
If so, how do I go about it?
Mark
Take it back
Return it and tell them its defective.... they will have to replace it. I mean especially if you show them it won't turn on properly.
alynch75 said:
Return it and tell them its defective.... they will have to replace it. I mean especially if you show them it won't turn on properly.
Click to expand...
Click to collapse
Are you serious? You screw things up and then hand the mess over to someone else? And some people wonder why return polices at certain places are so crappy for the rest of us.
To the OP, please don't do what alynch75 suggested. I would help you if I knew how but unfortunately, I don't. Hopefully, this bump will get your thread some more attention from people who potentially do know what to do.
If you can get it back into APX mode (and you should be able to), then try bekit's nvflash image:
http://forum.xda-developers.com/showthread.php?t=861950
If you cannot get it into APX mode, then you might be SOOL.
bobwagner said:
Are you serious? You screw things up and then hand the mess over to someone else? And some people wonder why return polices at certain places are so crappy for the rest of us.
To the OP, please don't do what alynch75 suggested. I would help you if I knew how but unfortunately, I don't. Hopefully, this bump will get your thread some more attention from people who potentially do know what to do.
Click to expand...
Click to collapse
Nah, I wouldn't do this even if I was in the US. I am in Australia.
We'll see how we go.
M
Not to worry. Did you get clockwork recovery installed? Go to WWW.droidpirate.com and go to g tablet section. You,LLC find all the files you need there. Had the same issue today and got it resolved following the tutorials there! If not maybe we can setup a remote session and get it resolve. Send me a pm and we can go from there. Don,t lose heart, your device is not bricked!
come on i dind't know he screwed it up. I thought this was something that the device was supposed to be able to do. I am new to android... give me a break .. i didn't mean any harm....
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
I've unlocked, rooted and ROM'ed probably 100 times on 25 different Android phones and tablets, this looks like my first official TF700 paperweight.
I saw another thread with a couple of people who did the same boneheaded thing I did: tried to install CWM the wrong way. Can't get into the ASUS recovery any more, either I hold volume down and get "Booting into recovery" (then hangs, no adb), or I hold volume up instead and I get a blank screen but it IS recognized as an APX device.
NVFLASH can't do anything at this point, the other thread had no good news either. Why ASUS can't have a "reset to factory recovery and bootloader" option is beyond me. Too late to return to NewEgg.
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20). I have a second TF700 that I unlocked, rooted, and installed CWM the right way. Is there any way using NVFLASH to get the blob from there and putting it on my bricked TF700 or is the blob encrypted to the device? I'm likely out of luck if I try to take the S/N sticker from my second TF700 and put it on the bricked one, ASUS will croak on that most likely.
Are there ANY other options? Short of just opening it up and looking at what's inside? That's a $600 visit I'd like to avoid.
Thanks.
ScaryBob said:
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20).
Click to expand...
Click to collapse
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply.
I used to keep EVERY original box... and yes, I do remember the serial number being there, but the ONE TIME I need the serial number, and all it is is a flimsy sticker on the device itself... And the ONE TIME I don't have the box.
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
It also seems like they would have SOME WAY to just let the end user put back a stock bootloader on the device, then we would all save a lot of time! Other than the fantastic learning experience here, I really want to find a way to salvage this completely useless but fascinating piece of technology.
I wonder if NVidia could help with this... probably not. I guess I'll look.
There must be some way to get a stock bootloader back on my TF700!!!!
Wait a minute man can you boot on Fastboot mode? When you turn on with volume down you can choose the mode to start?
ScaryBob said:
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
Click to expand...
Click to collapse
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
MartyHulskemper said:
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
Click to expand...
Click to collapse
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
ScaryBob said:
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
Click to expand...
Click to collapse
I haven't heard of anyone coming back from where you are. I wish you luck. If you are able to recover somehow on your own, you will be giving this community a great gift by sharing your secret.
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi:
My tf700t is bricked, no fastboot, only apx after a bad CMW installation, is there any way to restore or re flash using the tools and obvious understanding that you guys have. I really don’t want to send the device back to asus, and will be willing to donate to your site / cause / developers account if you guys could assist me in this matter. Thanks in advance for your time.
jtrosky said:
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I suppose that is an option -- it's not doing me any good as a brick, the worst they can do is send it back.
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
danger-rat said:
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
Click to expand...
Click to collapse
In the OP that was mentioned as well, but with the sidenote he didn't really want to open it up.
Mmmh... fastboot not working is not good... not good at all. I don't see any other option then than sending it back and see what ASUS does with it. As you said, the worst they can do is send it back... No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
MartyHulskemper said:
No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
Click to expand...
Click to collapse
...and charge $380 for it (there was some quote in another thread).
_that said:
...and charge $380 for it (there was some quote in another thread).
Click to expand...
Click to collapse
No, that's if they do absolutely nothing but write a check. (In that thread, at least in my memory, nothing was even actually done on that 700. )
when you guys mean "bad CWM install" what exactly does that mean so we can make sure we can save a few extra souls from doom?
Im pretty sure that is when they install CWM through the Rom Manager app.
mj23kb24 said:
Im pretty sure that is when they install CWM through the Rom Manager app.
Click to expand...
Click to collapse
Yes, since a few days after release (at most), we've known that Rom Manager is not compatible with the TF700. That's why you do not see it in any tutorial. Failure to read before doing leads to bricks in very, very many cases, and the 700's case is no different.
As we've concluded before, in terms of OP relevancy, I guess that sending you expensive baby in anyway would we the way to go (now if you'd only have fastboot available...).
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
WoodenAnts said:
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You need to provide some more info, are you on Jelly Bean or ICS? When this issue started? More details = higher chances to get help and solve your issue.
Lol sorry, i should know this by know. Was a long day. Uhh yes i was on a JB custom rom When the issue started. The rom had a couple hickups so i wanted to go back to my old one, so i did the nornal, nandroid, titanium backup, etc and flashed new rom. I believe what it did was delete the recovery image that it had, and then attempt to put on a new recovery as some roms do (to much annoyance) but this particular time it failed to install the new recovery for one reason or another. So i had no recovery for a while till i flashed it with fastboot, cwm 6.0.14 i think. So i tried doing a restore before this all happened, and recovery said it successfully restored, but when i reboot, it holds on the asus splash screen. Same with any Roms. And yes I wiped everything as well. Is that enough info?
Sent from my GT-I9300 using xda app-developers app
Hey guys,
So i did something silly. I rooted my galaxy nexus, nothing went wrong and thought "hey, while im at it i should go root my transformer!"
So i booted it unlocked it using the app, booted it into recovery, and flashed cwm to it using fastboot.
Tried to open cwm to actually root it. Wouldnt work. Stupidly thought "hey im going to press delete data, that will fix it".
Now i have a tablet which is stuck on the asus loading screen and wont go past it nor can i seem to get it back into adb mode.
Please tell me i can rescue it somehow? Ive only had it for 3 weeks!
Any help would be appreciated, and i apologize if this has been posted elsewhere. Im just freaking out its going to burn itself out before i can fix it.
cheese510 said:
Hey guys,
So i did something silly. I rooted my galaxy nexus, nothing went wrong and thought "hey, while im at it i should go root my transformer!"
So i booted it unlocked it using the app, booted it into recovery, and flashed cwm to it using fastboot.
Tried to open cwm to actually root it. Wouldnt work. Stupidly thought "hey im going to press delete data, that will fix it".
Now i have a tablet which is stuck on the asus loading screen and wont go past it nor can i seem to get it back into adb mode.
Please tell me i can rescue it somehow? Ive only had it for 3 weeks!
Any help would be appreciated, and i apologize if this has been posted elsewhere. Im just freaking out its going to burn itself out before i can fix it.
Click to expand...
Click to collapse
Lots of people have run into this problem. You would've found out had you searched with some key terms. If you "wipe data" from the recovery screen, chances are slim that you'll be able to restore your unit. However, do not despair. Given the mysterious ways this thing works, try this LINK to see if it helps. Some have done what you did but were able to recover, others couldn't. Good luck and remember whatever happens, it ain't the end of the world.
graphdarnell said:
Lots of people have run into this problem. If you "wipe data" from the recovery screen, chances are slim that you'll be able to restore your unit. However, given the mysterious ways this thing works, try this LINK to see if it helps. Some have done what you did but were able to recover, others couldn't. Good luck.
Click to expand...
Click to collapse
Dont tell me that I cant afford to buy another one. Best i could do is try and sell the dock and make a huge loss. Thanks for the link though - trying to get into apx mode now..
Not to mention the blasted thing keeps automatically rebooting itself.
OH HEY APX MODE!
Now what do i do??
Alright pretty sure its screwed beyong my repair. Think asus will fix it if i take it to them? for a fee ofcourse.
cheese510 said:
Alright pretty sure its screwed beyong my repair. Think asus will fix it if i take it to them? for a fee ofcourse.
Click to expand...
Click to collapse
They will fix it for a fee undoubtedly. Whether you can afford it is another question. It's weird they should provide the app. which if used would void the warranty. What kind of double-bind is that? You should inquire with them first and find out how much. Once ascertained, you should look around to see if you can get a motherboard for less. It would be different if your device doesn't work at all. I'm not telling you to do anything; I'm just wondering aloud how ironic this is where a completely dead tablet is worth more than a repairable one, 'cause if they can't see a thing on the screen, then they can't see a thing. And no-see tells nothing - no-thing voids nothing.
graphdarnell said:
They will fix it for a fee undoubtedly. Whether you can afford it is another question. It's weird they should provide the app. which if used would void the warranty. What kind of double-bind is that? You should inquire with them first and find out how much. Once ascertained, you should look around to see if you can get a motherboard for less. It would be different if your device doesn't work at all. I'm not telling you to do anything; I'm just wondering aloud how ironic this is where a completely dead tablet is worth more than a repairable one, 'cause if they can't see a thing on the screen, then they can't see a thing. And no-see tells nothing - no-thing voids nothing.
Click to expand...
Click to collapse
I like the way you think! It is kind of a joke that using their app voids warranty, but hey, i did press i accept.
I shall see how much it is. If i replace the motherboard is it liable to work straight away and is it a hard job?
Im sure they have a generator and all they do is enable apx mode and fix it like that. Wish it was a flat fee of under $100 because if so i would be on that in a flash..
Hey cheese,
I dont know if it helps, but I also was stuck on the asus screen and adb didnt worked.
I wrote a small story how I managed to bring my tf back to life.
I was out of hope and was willing to try everything before sending it back to Asus so I tried this.
Dont know if it helps, but I know your situation and if nothing works Asus will repair it for a fee...
Good luck! :fingers-crossed:
p.s. one thing which you always have to concern about is making sure to have the correct bootloader (jb/ ics).
graphdarnell said:
They will fix it for a fee undoubtedly. Whether you can afford it is another question. It's weird they should provide the app. which if used would void the warranty.
Click to expand...
Click to collapse
its not an app that if used void the warranty, its an app that _CERTIFY_ that you chosed, knowing what it entail, to broke the software "warranty seal".
and the warranty cover only construction defects, it wont ever cover damages thaty you cause by yourself.
why they shoud spend money (as paying the tecnincian costs asus) to fix your errors?
cheese510 said:
I like the way you think! It is kind of a joke that using their app voids warranty, but hey, i did press i accept.
I shall see how much it is. If i replace the motherboard is it liable to work straight away and is it a hard job?
Im sure they have a generator and all they do is enable apx mode and fix it like that. Wish it was a flat fee of under $100 because if so i would be on that in a flash..
Click to expand...
Click to collapse
Replacing the MB with a working one is not very hard, and will get it up and running right away. Just follow some of the hardware guides around.
---------- Post added at 08:10 PM ---------- Previous post was at 07:43 PM ----------
NixZero said:
its not an app that if used void the warranty, its an app that _CERTIFY_ that you chosed, knowing what it entail, to broke the software "warranty seal".
and the warranty cover only construction defects, it wont ever cover damages thaty you cause by yourself.
why they shoud spend money (as paying the tecnincian costs asus) to fix your errors?
Click to expand...
Click to collapse
Heheh. This is not the place for this, otherwise i don't think you're gonna win in light of the existing body of consumer law and the reason therefor. Just think of this: what are Asus's interest and motive in releasing such app.? Why did they do it? You want to be law-abiding, that's your prerogative. I'd like to right what's wrong, legal or not, like "too big to fail" crap or corporate shamelessness. You live in a place with no public transportation. They sell you a Pinto-like car that's liable to blow up in your face when you use their special gas not sold anywhere else. But they are clever enough not to disclose that hazard when you buy it. Then they make you sign a disclaimer that you know the risk and assume it AFTER you already bought the car! The warranty should follow conceivable uses of the merchandise. It's the standardized cost of doing business. Especially when they provide the gas that you put in the car's tank. What did you alter or modify on your own that "breaks the warranty seal"? You see the point...
graphdarnell said:
Replacing the MB with a working one is not very hard, and will get it up and running right away. Just follow some of the hardware guides around.
Click to expand...
Click to collapse
Alright anyone know where i can find one of these? Or should i just try and snag a "broken" transformer and salvage the board? A quick look on ebay revealed nothing.
graphdarnell said:
Heheh. This is not the place for this, otherwise i don't think you're gonna win in light of the existing body of consumer law and the reason therefor. Just think of this: what are Asus's interest and motive in releasing such app.? Why did they do it?
Click to expand...
Click to collapse
have you ever seen on the back of any item an adhesive seal that cover a screw that says "warranty void if broken"?
exactly the same.
you can broke it and do wathever you want, its your choice, but dont ask them to fix it for you if you screw up with your modifications, that's not covered by warranty.
btw if you unlock your tf300 and then discover an hardware defect you're still covered by warranty, asus dont want to screw you up, just dont want to pay for your mess.
cheese510 said:
Alright anyone know where i can find one of these? Or should i just try and snag a "broken" transformer and salvage the board? A quick look on ebay revealed nothing.
Click to expand...
Click to collapse
If you can manage to get fastboot to work at at all, I can save you the trouble of doing any messy hardware replacements. Download the most recent update from asus' website. Unzip the package and pull out the blob file . Run this command where "blob" is the name of the blob file fastboot -i 0x0B05 flash system blob You need fastboot installed on your computer of course. Now if you want to can flash TWRP or whatever, or just use your tab as is.
---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------
NixZero said:
have you ever seen on the back of any item an adhesive seal that cover a screw that says "warranty void if broken"?
exactly the same.
you can broke it and do wathever you want, its your choice, but dont ask them to fix it for you if you screw up with your modifications, that's not covered by warranty.
btw if you unlock your tf300 and then discover an hardware defect you're still covered by warranty, asus dont want to screw you up, just dont want to pay for your mess.
Click to expand...
Click to collapse
While the fact of the matter is warranties do only cover manufacturing defects, this isn't a thread for this type of discussion. This guys is asking for help not a f*cking debate where you like to play lawyer on developer forums.
Spark1223 said:
If you can manage to get fastboot to work at at all, I can save you the trouble of doing any messy hardware replacements. Download the most recent update from asus' website. Unzip the package and pull out the blob file . Run this command where "blob" is the name of the blob file fastboot -i 0x0B05 flash system blob You need fastboot installed on your computer of course. Now if you want to can flash TWRP or whatever, or just use your tab as is.
Click to expand...
Click to collapse
I dont think i can get it to work since all i manage to see on the screen is the asus logo and it freezes. It has the wrong recovery on it now so i think fastboot is out the window. Im assuming the wipe data button wipes recovery too?
The only mode ive managed to get it in is apx mode and thats useless to me.
Thanks for your help though.
cheese510 said:
I dont think i can get it to work since all i manage to see on the screen is the asus logo and it freezes. It has the wrong recovery on it now so i think fastboot is out the window. Im assuming the wipe data button wipes recovery too?
The only mode ive managed to get it in is apx mode and thats useless to me.
Thanks for your help though.
Click to expand...
Click to collapse
Fastboot and recovery are too totally different things. Even if recovery is totally botched you can still use fastboot. Its on the same screen where you wipe data. If you can still get to that, you're still fine. http://i1359.photobucket.com/albums/q794/shiznoroe88/TF700T ROOTING/fastboot_1_zps39542550.jpg
Looks like that. With the unit completely off Hold down the volume down button and then press power button. Select the USB icon, and connect to PC, that's called Fastboot.
Spark1223 said:
If you can manage to get fastboot to work at at all, I can save you the trouble of doing any messy hardware replacements. Download the most recent update from asus' website. Unzip the package and pull out the blob file . Run this command where "blob" is the name of the blob file fastboot -i 0x0B05 flash system blob You need fastboot installed on your computer of course. Now if you want to can flash TWRP or whatever, or just use your tab as is.
Click to expand...
Click to collapse
So I'm in a similar situation to this gentleman. My tab, boots to the Asus Logo where in the corner it tells me The Device is UnLocked. I know how to access fastboot and recovery, I tried what you instructed, however it still only boots to the same screen.
My problem was I stupidly didn't follow the proper instructions to flashing the new Cyanogenmod 10.1 where it says I had to have the new JB bootloader, which I am guessing I do not have. So before I flashed it I made a nandroid of my old system, tried to restore and it won't boot back into the old system. So I wiped data, cache, davlik. Nothing, it won't boot past the Asus screen.
So right now, I've just downloaded a stock rooted rom of the latest asus rom. I am going to try to flash that from fastboot if I can. Any other suggestions I'm open to.
I had a problem getting my PC to recognize and fastboot my tab too. What worked for me is to plug tab into PC while off. Start adb then turn on tab, as soon as I turned on tab then I repeatedly try to see if adb recognized tab while it was powering up. After a few tries it worked. It was like it had to check at just the right moment to catch the tab. Hope this helps, good luck
Sent from my ASUS Transformer Pad TF300T using xda premium
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
FordPrefect said:
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
Click to expand...
Click to collapse
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
MartyHulskemper said:
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
Click to expand...
Click to collapse
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
adelancker said:
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
Click to expand...
Click to collapse
Yes, rooting should still work -- I haven't really looked into the downgrade path options and if it requires a custom recovery, though. I'd root it if possible, and then tweak the hell out of it.
I fear as you do, but you might drop ASUS a line anyway -- you've got next to nothing to lose. Take care, and good luck!
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
What has been said about the MAC address is correct. The success rate of people shipping their tablets into RMA to fix the MAC address issue does not seem very high. People are reporting they get the tablet back with the same issue regarding the unlock tool and unable to get the device tracker or OTA updates to work.
Email Asus support and flat out ask them to check the servers in Taiwan and find out if the MAC address listed in your tablet is the same one on the servers. They have the serial number already will just need you to supply the MAC address. If it comes back saying it is not and you need to RMA it, good luck. Question then becomes did the person responding to the email really check or just saying to RMA it so they can close out your email ticket.
The response I got last week was my tablet not matching what they have on the server and send it in. I'm debating if it's worth spending 15-20 bucks to mail it in, wait 2-3wks, only to get it back with them saying there is nothing wrong with the tablet and still be unable to unlock. That seems to be general outcome. In the email I explained I'm unable to use device tracker, receive OTA updates, or use the unlock tool. I explained the issues with MAC addresses for devices being incorrect on the servers in Taiwan as a known issue causing these problems. I supplied my MAC address that the tablet gives and asked to have them verify what they have.
Sorry to say but only Asus can fix this problem. If you search the forums for this topic you will find threads on it. Some had mentioned trying it with the sd card removed has worked. Give that a try. If you disabled the two tracking programs Asus has in their stock build, turn them back on when you try to unlock. Just keep trying a few times randomly and you might get lucky.
If I ever get my issue resolved I will for sure post in the forums for others.
We had already a thread for this, albeit for new devices:
http://forum.xda-developers.com/showthread.php?t=2146543
Mine works now.
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
sbdags said:
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
Click to expand...
Click to collapse
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
adelancker said:
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
Click to expand...
Click to collapse
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
DarkFire1985 said:
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
Click to expand...
Click to collapse
Be careful here - the problem is not always the MAC-address.
For my TF700, Asus had the correct MAC-address stored, but OTAs, Device Tracker and unlocking did not work nevertheless.
From my Logcat entries I saw that the server refused to 'talk' to my tablet, so I assume that the Asus server in Taiwan just didn't know my tablet.
The issue is fixed now BTW, Asus Germany forwarded the ticket to Taiwan.
So if you talk to Asus support, do not insist that the problem is the MAC-address - if your MAC address is correct and you still insist that it is wrong the Asus support won't take you serious anymore.
sbdags said:
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
Click to expand...
Click to collapse
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
adelancker said:
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
Click to expand...
Click to collapse
To get that $125 from you a second time?
MartyHulskemper said:
To get that $125 from you a second time?
Click to expand...
Click to collapse
Hahaha ^^
They haven't charged me yet!
Maybe because I was super mega angry in my mail and mentioned the EU-consumer law a million times.
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
NegativeOne said:
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
Click to expand...
Click to collapse
What can I say? I am a good negotiator I guess...
Just kidding. If you're European, you can always use this EU consumer protection law, which always has your back for the first 6 months after purchase.
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
NegativeOne said:
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
Click to expand...
Click to collapse
If you're from the US, I can only recommend you to buy a third party warranty such as the Square Trade one.
After that, you can do whatever you want and you'll never have to worry about losing warranty after unlocking your tf700 ever again.
As a side note, unlock your device as soon as you have time! It makes your device that much quicker.
Just sucks that Asus somehow prevents me from unlocking it after the RMA.