[Q] Is my TF bricked? Any solution - Eee Pad Transformer Q&A, Help & Troubleshooting

I had the little symbol that I can upgrade my firmware today so I started the process and it rebooted and then stayed on that screen for like an hour and rebooted.
now it comes up and sits at the eee pad screen with the aus logo at the bottom
if I hold power and down volume it says
android ww_epad-user bootloader < e> released by "ww-epad-8.2.3.6-20110414".
Booting recovery kernel image
and sits there nothing else..
so what should I do next?

I notice the "ww" in your bootloader; are you in the US?
I would suggest reading this post about bricked:
http://forum.xda-developers.com/showthread.php?t=1051776

Our resident gurus were looking for bricks to test a potential recovery method. Let me see if I can dig up a link to the thread. Otherwise search for rayman, bumble-bee...
Edit - Dan already linked the appropriate thread. Hook up with rayman84.

damm OTA update..
I will request an RMA from newegg...
took forever to get this!

From what the other thread says, the bad update was pulled... you say you got it OTA? Which country are you in, and when was the update?
Sent from my Transformer TF101 using XDA Premium App

kingrat said:
damm OTA update..
I will request an RMA from newegg...
took forever to get this!
Click to expand...
Click to collapse
Man, that sucks! I'm sorry to hear that your FOTA didn't go as planned. I hope either NE or Asus can make it right for you.

kingrat said:
I had the little symbol that I can upgrade my firmware today so I started the process and it rebooted and then stayed on that screen for like an hour and rebooted.
now it comes up and sits at the eee pad screen with the aus logo at the bottom
if I hold power and down volume it says
android ww_epad-user bootloader < e> released by "ww-epad-8.2.3.6-20110414".
Booting recovery kernel image
and sits there nothing else..
so what should I do next?
Click to expand...
Click to collapse
I want to keep this thread short as it is a re-post. Please post here for more help regarding this issue.
I ordered mine from newegg as well and experienced the EXACT SAME issue and ended up RMA'ing with newegg. If you can please hold off on doing that though for just a few days I can contact Hai, an Asus technician who worked with me, and inform him of your issue. He really wanted my particular device in his hands to work on but I rma'd too soon with newegg. I plan on calling Hai tomorrow evening. PM me your phone number for the time being and i can give it to Hai if you feel comfortable.
Also; it took about a week from when Newegg received my device to it being refunded back to my bank account. Hai may be able to make that turnover a bit quicker and allow you to receive a replacement thus saving you from having to wait for a new one.
P.S.S. - There is no solution other than RMA for the bricked devices.

Related

Stuck at Bootlogo, no Backup/Fastboot/ADB

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.

Bricked TF300: The aftermath...

I promised I would come back and tell everyone how my repair @ ASUS would go. I first called ASUS to make an RMA, but they just reffered to their website. So I filled in the form as honost as possible: "Hi ASUS, I've bricked my TF300. First I upgraded to JB, afterwards unlocked the bootloader, replaced it and after a wipe of the settings it won't boot at all. Please have it repaired, I'm aware of any costs or warranty-loss."
They picked it up last friday in Belgium, shipped it to Czech, where it arrived on Monday. I prommised myself I wouldn't check on the status for at least a week, but I couldn't stop myself
Yesterday I checked, and it was in status: Final testing. An hour later it was picked up by DHL again to be shipped back to Brussels. This afternoon I received it, and indeed: all issues solved! The note from ASUS didn't say anything about my story, the problem description was: System hangs up :victory:
So: Fixed in warranty, picked up and returned within a week, bootloader locked again, flashed back to stock JB!
Couldn't ask for better service!
Good luck out there
Sphinix said:
I promised I would come back and tell everyone how my repair @ ASUS would go. I first called ASUS to make an RMA, but they just reffered to their website. So I filled in the form as honost as possible: "Hi ASUS, I've bricked my TF300. First I upgraded to JB, afterwards unlocked the bootloader, replaced it and after a wipe of the settings it won't boot at all. Please have it repaired, I'm aware of any costs or warranty-loss."
They picked it up last friday in Belgium, shipped it to Czech, where it arrived on Monday. I prommised myself I wouldn't check on the status for at least a week, but I couldn't stop myself
Yesterday I checked, and it was in status: Final testing. An hour later it was picked up by DHL again to be shipped back to Brussels. This afternoon I received it, and indeed: all issues solved! The note from ASUS didn't say anything about my story, the problem description was: System hangs up :victory:
So: Fixed in warranty, picked up and returned within a week, bootloader locked again, flashed back to stock JB!
Couldn't ask for better service!
Good luck out there
Click to expand...
Click to collapse
Lucky - my non-unlocked TF300TG has been away for a month and a half now. I'm generally a pretty patient person, but this is starting to piss me off. Especially considering it's just a software problem. I want to find whomever decided to lock down APX mode and slap them silly across their face.
You got lucky, hope I'll be also...
Hi,
I red your history with fate...
I bricked mine also, and I did the same call customer service, and got a RMA.
Sended it last friday, hope that the service is the same in Canada...
Thanks for your story...
But, as my wife will tell you: It won't stop me to root back my device.
In the mean time I bought a Nexus 7 tablet. It's very hard no to root....
alainlafond said:
Hi,
I red your history with fate...
I bricked mine also, and I did the same call customer service, and got a RMA.
Sended it last friday, hope that the service is the same in Canada...
Thanks for your story...
But, as my wife will tell you: It won't stop me to root back my device.
In the mean time I bought a Nexus 7 tablet. It's very hard no to root....
Click to expand...
Click to collapse
:laugh:
My gf went: How the hell did you break it after a week?? Well, my answer was: because I could Never had a softbrick I couldn't fix before, the thing I did wrong was mostly: Starting to screw around after midnight, the "Oh, let's just do this one more thing now everything went so well...". Lesson learned! By the way, it returned stocked on JB, so I'm gonna wait a little bit until NVFLASH can be performed on this as well. But indeed, it won't stop me from messing with it again (Only this time on a Sunday afternoon with some calming music on the background )

[Q][UNBRICK] TF700: Thick as a brick paperweight?

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

[Q] Error during boot-up after firmware upgrade: "No certificate to inject".

[Q] Error during boot-up after firmware upgrade: "No certificate to inject".
I updated my firmware to V10.4.2.17 WW manually. My tablet is not rooted or unlocked. The first thing I noticed was that my Transformer 300T now gives some sort of error message in the upper left corner (below the power button) during boot-up, the message is "No certificate to inject". It happens at every boot-up and doesn't seem to give any problems, but I'm curious if other people get it. Also I'm curious what it means exactly.
Any ideas?
Same issue here. I also cannot unlock bootloader or update vía OTA.
Help me too No certificate to inject, a new tablet
Same here, thanks for helping...
Same here:
I waited 2 weeks to see if I was getting it via OTA, ...but nothing, ...not even when manually asking for it via Settings -> Firmware update.
So I decided to go the manual way via the Micro SD card; all went fine BUT, now I have for 5 seconds, every time I boot, the same message:
No certificate to inject
Why ?
Thanks for your help !
Id like to add that I have the same issue with my new tf300t. Only did an update because I wanted to have the latest firmware but I kinda regret it. Has anyone found a solution?
Sent from my Samsung Epig 4G using Tapatalk Pro
Same problem
I have the US version and mine is brand new. The firmware update which was pushed to my tab VIA OTA has rendered it completely useless. I get the error, " no certificate to inject" and it does nothing but crash. If it goes to sleep or if I hit the power button to turn the screen off it will not wake up and I have to long press the power button to reboot. I can't even use it, it's basically a paper weight now. Does anyone have a clue how I can fix this? Should I try to flash the old firmware? If so can someone point me to a link on how to go about it.
I called Asus and they did not want to walk me through flashing firmware. They want to set up an RMA.
I've tried a cold boot, factory reset and data wipe.
guyute said:
I have the US version and mine is brand new. The firmware update which was pushed to my tab VIA OTA has rendered it completely useless. I get the error, " no certificate to inject" and it does nothing but crash. If it goes to sleep or if I hit the power button to turn the screen off it will not wake up and I have to long press the power button to reboot. I can't even use it, it's basically a paper weight now. Does anyone have a clue how I can fix this? Should I try to flash the old firmware? If so can someone point me to a link on how to go about it.
I called Asus and they did not want to walk me through flashing firmware. They want to set up an RMA.
I've tried a cold boot, factory reset and data wipe.
Click to expand...
Click to collapse
Wow that really sucks. If its a paper weight and they offered to do an RMA why wouldnt you? Im still waiting on ASUS to reply to my email! lol. Look it's brand new and its basically a brick. Unless they can give you a solution thats easy i would just go through the return process.
edit: they emailed back saying that doesnt sound right and to do a factory reset. While i knew that wouldnt fix it i did it anyhow since i didn't have much data to lose. Long story short they want to RMA mine as well. Ugh.
RMA
So yep I sent it in for RMA, Very disappointing that and update did this to my brand new tab.
guyute said:
So yep I sent it in for RMA, Very disappointing that and update did this to my brand new tab.
Click to expand...
Click to collapse
same here, dont feel so bad. It sucks.
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
guyute said:
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
Click to expand...
Click to collapse
Jesus. Mine is sitting at my house right now as it was delivered from Fed ex today and i am worried it will be the same ridiculousness. ugh.
nyr35blue said:
Jesus. Mine is sitting at my house right now as it was delivered from Fed ex today and i am worried it will be the same ridiculousness. ugh.
Click to expand...
Click to collapse
They want me to RMA it again. I wish I never bought this thing. It seems to be working fine, but I have a bad feeling about letting it do the firmware update.
Why didn't they fully update it when they had it? Also are they blind? It's completely obvious the error message is still there during boot up and I was very specific about it.
guyute said:
So I got it back today from RMA and guess what? On the very first start up it still says no certificate to inject. Unreal, why didn't they correct this? It seems like the only thing they did was flash the old firmware back. Now my tablet is asking me to update and I don't want to because the last time it turned it into a pile of crap.
Click to expand...
Click to collapse
guyute said:
They want me to RMA it again. I wish I never bought this thing. It seems to be working fine, but I have a bad feeling about letting it do the firmware update.
Why didn't they fully update it when they had it? Also are they blind? It's completely obvious the error message is still there during boot up and I was very specific about it.
Click to expand...
Click to collapse
apparently they ARE blind. The message is quite easy to see when you turn it on. To be honest i wish i never did the firmware update when i first got it for Xmas. Thats when this all started for me. I'll let you know what happens with mine so you can either hate me or feel a little better knowing my predicament.
HAHAHA, I hope your doesn't have the error. Now I don't want to do the firmware update, because I know what happened last time. But on the other hand what am I supposed to do, never update my tablet ever again?
Would I even be able to skip the firmware update but still take any OS update they may push in the future?
The RMA is good for 30 days so I think I'm going to see what happens. It seems perfectly fine right now, no issues with it not waking back up.
Ok little update, it still has the error message, but is working very well. It's reading my SD card (which it didn't before) and no issues with it waking back up. I also ran the update and all seems fine. I'm going to mess around with it for the next few days and see if misbehaves. If it works perfectly fine and still has the message then so be it, I'm not going to send it back in.
guyute said:
Ok little update, it still has the error message, but is working very well. It's reading my SD card (which it didn't before) and no issues with it waking back up. I also ran the update and all seems fine. I'm going to mess around with it for the next few days and see if misbehaves. If it works perfectly fine and still has the message then so be it, I'm not going to send it back in.
Click to expand...
Click to collapse
Well i got it back shockingly no error message anymore but i also notice it wasn't factory restored. No problem i did that myself. Of course it downloaded the firmware update and wants to install which i chose NOT to. Not sure if and when i will decide to do it. lol. How annoying.
nyr35blue said:
Well i got it back shockingly no error message anymore but i also notice it wasn't factory restored. No problem i did that myself. Of course it downloaded the firmware update and wants to install which i chose NOT to. Not sure if and when i will decide to do it. lol. How annoying.
Click to expand...
Click to collapse
Well I ran the update, and it seems perfectly fine. I wish they had cleared up the error message, but I've been going at the thing all day and it seems perfect. They gave me a new RMA, but if it continues to run perfectly I'll just take that as a win.
I unfortunately am having the same problem..
I have gone through 2 tablets now at Best Buy.. The first one went from stock to .20 release and started getting the error.. So I get another one.
I figure that I'll be smart now and I have 2 other TF300's and the one that I had previoiusly all had no issues.. So I figure I will update to the previous release first..
Now I'm getting the message..
It did download the latest release but when it goes to install the OTA it fails.. EXTREMELY frustrating.. A TOTAL waste of my time.. I really want to kill myself right now.
Anyway... I'll manually update to the latest version and maybe pick a different Best buy..
I of course also put my Armor Shild on this one because I figured there was no way that I got two doing this in a row..
Yeah.. 40 bucks down the drain.. .I will call Asus and make some tech supports ears bleed tomorrow.. Yeah I know it's not his fault but.. well it's his fault.
Any new info on this?
Hello everyone, just got back into tech toys and having time to play around etc. Anyway got the same error after OTA update, also Keyboard spacebar does nothing anymore and the mouse pad doesn't work at all either. Looked online everywhere and figured if there was an answer for this it would be in these forums and haven't found one. Had to make a new account on here and haven't had the time to mess with anything in a while so it's all new to me again. Any help would be great, kinda scared to try anything after reading so many different ways to brick this thing- have an email in to asus, 3 acually, and no responses back on any of them and it's been months..thanks for any info - really want to unlock/root/recover and try some of these awesome looking ROMS but am stuck with this error and no response back from asus.

[Q] Unlocking without Asus's apk

Hi,
last month I sended my TF300T to Asus because I had a problem with it. The tablet wouldn't upgrade itself and the sensor for the keyboard stopped working leaving the screen on.
My tablet was unlocked. I knew that there was a risk!
But when the tablet came back fixed, with the system 4.2.1 was happy and felt very lucky.
But now, I'm not that sure.
As the warranty finished shortly after the tablet came back, I said to myself that there was no reason to not unlucked it again.
I went to Asus's web site, downloaded the apk and runned it and:
I get the answer "Unknokn connection error, please try again"
In fact it seem that Asus does not want taht I unlock the boot loader again.
Is there another way..
Thanks...
alainlafond said:
Hi,
last month I sended my TF300T to Asus because I had a problem with it. The tablet wouldn't upgrade itself and the sensor for the keyboard stopped working leaving the screen on.
My tablet was unlocked. I knew that there was a risk!
But when the tablet came back fixed, with the system 4.2.1 was happy and felt very lucky.
But now, I'm not that sure.
As the warranty finished shortly after the tablet came back, I said to myself that there was no reason to not unlucked it again.
I went to Asus's web site, downloaded the apk and runned it and:
I get the answer "Unknokn connection error, please try again"
In fact it seem that Asus does not want taht I unlock the boot loader again.
Is there another way..
Thanks...
Click to expand...
Click to collapse
Call Asus and tell them that they need to add your serial and new mac address back to their database so you can unlock it again. Keep nagging them until they do it. This is the ONLY fix for you.
sbdags said:
Call Asus and tell them that they need to add your serial and new mac address back to their database so you can unlock it again. Keep nagging them until they do it. This is the ONLY fix for you.
Click to expand...
Click to collapse
Hello,
that's what I did, and the support guy told me that its impossible to reset my serial number in the database. He told me that I'll need to send the tablet back for tech service.
For now I have a RMA for sending back my tablet.
I won't pay for shipping, as they'll pick up my tablet at my house.
I found that a little strange. But for now I'l wait to see what will happen.
Thanks for your help...
:good:
alainlafond said:
Hello,
that's what I did, and the support guy told me that its impossible to reset my serial number in the database. He told me that I'll need to send the tablet back for tech service.
For now I have a RMA for sending back my tablet.
I won't pay for shipping, as they'll pick up my tablet at my house.
I found that a little strange. But for now I'l wait to see what will happen.
Thanks for your help...
:good:
Click to expand...
Click to collapse
He's bull****ting you. There are plenty of people on XDA who have got Asus to do it.
hello please I have a place unknown serial number only.
Do you think it would work if I said mac and sn from bag.
But of registration asus I have done.
Tablet were on the servis with bad rom and unolck bootloader and there locked bootloader.
Sorry for bad English.
Thanks for the advice
alainlafond said:
Hi,
last month I sended my TF300T to Asus because I had a problem with it. The tablet wouldn't upgrade itself and the sensor for the keyboard stopped working leaving the screen on.
My tablet was unlocked. I knew that there was a risk!
But when the tablet came back fixed, with the system 4.2.1 was happy and felt very lucky.
But now, I'm not that sure.
As the warranty finished shortly after the tablet came back, I said to myself that there was no reason to not unlucked it again.
I went to Asus's web site, downloaded the apk and runned it and:
I get the answer "Unknokn connection error, please try again"
In fact it seem that Asus does not want taht I unlock the boot loader again.
Is there another way..
Thanks...
Click to expand...
Click to collapse
Have you paid for a repair? Has your warranty void by Asus?
Sorry to bring up an old thread...But does anyone know what a second error beyond the network one would be? It lets me verify my google account then sits for a long time. After that I can an error "Unable to unlock device at this time. Please try again later." Same serial number issue or something different?
Edit: after restarting a couple more times, I got it to work!

Categories

Resources