Related
Can anyone definitively explain the reason why some can and some can not unlock their bootloader? I've searched all over the forums and see reasons the span from left to right. I typically just lurk in the background and figure out methods to install custom ROMS on my own, but this unlocking situation is starting to chap my my arse. I've been trying for about two weeks to use the ASUS tool, but it ain't working for me.....I keep getting the same connection message that other's are getting.
Anybody got a good answer or an even better solution?
From what I've read it seems to be because of their method to track who unlocks. It takes your serial number and then they know so they can void the warranty. However a certain amount of numbers also got put on that list. So when you go to use it it doesn't work because it's only a one time deal to prevent from relocking /unlocking. I'm not 100% sure on this because there isn't really any information available but that's what I've heard from a bit of looking around.
Sent from my ASUS Transformer Pad TF300T using xda premium
All I did was download the apk from asus and installed on my tablet and bam unlocked the tablet took 5 minutes if that. What methods are you doing?
Ok so I found this looking around.
http://forum.xda-developers.com/showthread.php?t=1669328
That thread seems to show/explain a lot. Plus maybe reading it will stop double posting.
Sent from my ASUS Transformer Pad TF300T using xda premium
Yeah, saw that post. Tried it too......nada. I've got a C30KCT S/N too.
Just curious for those of you that have successfully unlocked your tablet.....did you happen to register your device's S/N with ASUS?
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
vel0city said:
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
Click to expand...
Click to collapse
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
EndlessDissent said:
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
Click to expand...
Click to collapse
Thanks for the heads up did not know that I guess my friends and I have been lucky then unlocking our bootloaders I mean I unlocked and rooted about 10 tablets and didnt come across this lol.
Yeah, the problem first got attention when a bunch of people weren't getting OTA notifications. Some folks went to devicetracker.asus.com and entered their serial numbers and were told that the serial number was invalid. These same people got tired of waiting for the OTA and decided to just unlock their tablets and install custom ROMs. Unfortunately, they just got a network error. Someone, at some point, called Asus support about the OTA and was told about the database problem. Apparently, it hasn't been completely fixed yet. Eventually, I think, most people either got their OTAs and/or the unlocker started working. There were also reports that downgrading to .17 and doing a factory reset solved the problem for some people but not others. Other people said that clearing data for certain services made it work, but not everyone got that to work, either. The only options you have are to either wait or return the tablet and hope the replacement doesn't have the same problem.
So, if you've received OTA's and registered with device tracker it'd be a safe bet they have you in the their db, right?
Yup. I meet both criteria and just unlocked successfully.
hello everybody!
i got my tf300t two weeks ago and was a happy camper. i unlocked it as soon as i got home, installed cyanogenmod on it and was happier than a stripper with a stack of singles! but then curiosity stroke and i wanted to try the hydro rom and give twrp a whirl. in the process of installing twrp something went wrong and my device froze. i left it there for a good half hour and still nothing. after rebooting, my sweet sweet tablet would just show the asus logo. then i tried to boot my sweet toy into recovery but tt just sat there with the asus logo staring right back at me..i tried several times to no avail..i was sad..very very sad..so sad..i couldn't get the tablet in usb mode..i couldn't do the deed with my girl..so so sad..after looking around this and some other forums my suspicions where confirmed: no recovery console = no restore, no usb mode = no fastboot. i cried myself to sleep..ask my girl..she was there..
after a night full of abandonment failure and angst-driven nightmares i decided to get in touch with the asus tech support. i'm in the netherlands so i got this certain Michiel on the line. Michiel didn't know much. Michiel had to ask me (after i gave him my serial number and device model and of course, selecting the right menu option making sure the person i'd get on would certainly know what product they are supporting) what kind of product if was. twice. i politely (always be polite when you want something from someone!) asked what was the procedure in this case and informed him that i am aware of my warranty being void because i'd unlocked the bootloader. Michiel informed me that it was going to cost me 75 euro for sure (because that's their repair fee) and whatever it might additionally cost but they'd call me to inform about the costs before proceeding with repairs. Michiel reckoned that most likely there weren't going to be any additional costs since this was clearly a software problem. he then instructed me how to rma my product. Michiel did not log the call or give me a ticket number (i've had ITIL training..i know these things..) after submitting my request i received a confirmation email. the next day (19/09) it was picked up and away my limp toy went and left me full of rooting and customizing hopes! i tracked every single move my sweet sweet device made. it stopped in amsterdam first for some spliffs, bad blow and over-expensive hookers then it passed through brussels for a beer tasting and moved on to brakislava for i don't know, i wanted to say cheap hookers but that might offend some but then again people with a sense of humor are generally smarter. anyway, my beautiful sweet toy ended up in brno, the czech republic. from my previous quests for information i gathered that is where asus ships their broken toys to get fixed here in the ol'country. so i was happy. my device was in the land of broken toys and would be returned to me within two weeks, Michiel assured me.
last wednesday (25/09), i received an email from asus happily informing that my device was fixed and ready to be shipped off. oh the joy! the wait was almost over!!! i never heard anything from asus regarding a payment. i was a happy boy again. i could once more please my lady. i once again tracked my device. every. single. step. i was giddy when i saw it had boarded on its way from brussels at 04:03! and i was overjoyed when i saw it had arrived in amsterdam at 08:45! yesterday (26/09) at 10:25 my sweet baby arrived home! i ran up the stairs and into my room! as i the asus unlocker app finished downloading i installed it and ran it. as i ran it the power went out. the app reported an "unexpected error had occurred" and that their server might be unavailable at the moment. so the unlocker app needs internet to do its magic. you learn something new everyday i guess and no power = no internet..turned out there was a powerline broken further up the road that left over 2000 houses with no power yesterday here in utrecht..lucky me..hehe
there i was, with my repaired tablet, anxious to unlock, install cw recovery, root and install hydro but unable to unlock my device..my girl was lying next to me sleeping through my curses and snoring softly. i could take a chance and run to her place (10 minutes away from mine) and check if there was power there. she wouldn't be happy waking up alone in my place with a postit on her forehead saying "no internet here. i'm at your place." but i had to play with my toooy!! so i did. i went to her place. i stuck the postit on her left boob. i like boobs..anyway, at her place there was power! YES! so i tried unlocking again. got the same error message..and again..and again..you get the gist..
again i went off on a quest for information! found out that the issue might be caused due to the fact that under settings/about tablet/statusserial number = unknown. i read several times that a device wipe might do the trick. it didn't for me. some with the same issue and after rma say that they were able to unlock after a couple of days. i also went through the official asus unknown serial thread here.
i called asus again. got Michiel on the line again. lucky me. this time i said that my device wouldn't update and it just came back from repair. Michiel asked for the serial number. i asked where i can find it. Michiel said on the box. i said i don't have the box handy right now and if i could find it in my device (see what i was doing there?) Michiel didn't know. Michiel was as useless as the first time. Michiel asked me if he device is unlocked or rooted. i informed him that it had been before the repair but that it isn't now. then Michiel informed me that my serial number (notice Michiel hasn't my serial number) has been blocked because i rooted my device therefore voiding my warranty. then pretty much blew me off..
so, basically, because i unlocked my device once and it had to go in for repairs i'm not allowed to unlock it ever again?! what the hell?! i don't have to remind anyone here how much the tablet costs..
i then found ratchet at androidroot.mobi but on the 1st step (adb push mempodroid /data/local/) i get failed to copy 'mempodroid' to '/data/local//mempodroid': Permission denied.
so i searched and searched to no avail..last night..i couldn't perform in bed again..please help this desperate geek..and his girl..
thanks in advance!
You don't lose warranty for rooting, but unlocking, supposedly yes. If its the serial you are after, it should be on a tiny sticker next to the main lower connection port. If that's gone you might be able to get it from adb or fastboot, one or the other can't remember which. Try them both... try adb devices and check the response. If its not you serial it responds with then fastboot will. Type fastboot devices and it should reply with it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
That's weird and not right. I think you should contact ASUS again and try not to talk to Michiel , you should be able to unlock your tablet if you want, it is your right to do so. Yes it will void your warranty again, but ASUS shouldn't be able to dictate what you do with your newly fixed tablet. You need to speak to another person, Michiel is right in that your serial is blocked, that means your warranty is voided for unlocking (not rooting), but if they relocked your tablet in the process you should be able to unlock again. Are you sure your tablet was relocked by ASUS? It might be that they just flashed the stock ROM and left it unlocked...
Voided warranty means that you won't get free tech fixes for your tablet and you won't be able to receive Over the air updates to the stock rom, it doesn't in anyway say that ASUS has the ability to cripple the use of your tablet.
I find it weird that you tried to view the serial in settings and it indicates unknown. That makes me wonder what file it's stored in, or was stored in.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Exactly the same here. Tablet was also bricked and repaired and now it says Serial number: Unknown. I've already mailed ASUS so now I'll have to wait for them to reply.
sparky28000 said:
Exactly the same here. Tablet was also bricked and repaired and now it says Serial number: Unknown. I've already mailed ASUS so now I'll have to wait for them to reply.
Click to expand...
Click to collapse
Please continue to post your findings and hopefully solutions. It's things like this which help me determine which company to support. That's why I don't own any apple products
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
same here
funnel71 said:
Please continue to post your findings and hopefully solutions. It's things like this which help me determine which company to support. That's why I don't own any apple products
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
So i have the same problem. I sent mine in for a softbrick here in the US. They "replaced" the motherboard and the battery (why i have no idea). I too,am now unable to unlock. The difference with me is I can see my Serial in settings...so I know alot of other people were having trouble with the unlock tool not working on devices that were never sent in for service. So Im not sure if its the tool or the serial issue. I called asus and they offered to rma to fix it...after alot of *****ing. I told them if they are going to lock my bootloader then they need to give me my warranty back..they cant have it both ways. I paid to unlock my device with my warranty...I really dont want to rma again because it took like a month before...
bjanice44 said:
So i have the same problem. I sent mine in for a softbrick here in the US. They "replaced" the motherboard and the battery (why i have no idea). I too,am now unable to unlock. The difference with me is I can see my Serial in settings...so I know alot of other people were having trouble with the unlock tool not working on devices that were never sent in for service. So Im not sure if its the tool or the serial issue. I called asus and they offered to rma to fix it...after alot of *****ing. I told them if they are going to lock my bootloader then they need to give me my warranty back..they cant have it both ways. I paid to unlock my device with my warranty...I really dont want to rma again because it took like a month before...
Click to expand...
Click to collapse
I can confirm I have the same issue -- My tablet was unlocked before, sent in for RMA due to softbrick, and now I'm unable to unlock.
Maybe the server is actually down? Who knows.
krhainos said:
I can confirm I have the same issue -- My tablet was unlocked before, sent in for RMA due to softbrick, and now I'm unable to unlock.
Maybe the server is actually down? Who knows.
Click to expand...
Click to collapse
I believe if you still have a serial number, unlike the OP, you should be able to unlock. I unlocked my tablet a couple days ago, it took a lot of tries for it to work (like 100). It just kept saying unknown server error... so my guess is that ASUS servers suck just keep trying. Also I found that I got the google account approval prompt more often when I waited a couple minutes between tries. Hope this helps good luck
Note: I might have tapped the unlock button maybe 50-100 times xD
jgaf said:
I believe if you still have a serial number, unlike the OP, you should be able to unlock. I unlocked my tablet a couple days ago, it took a lot of tries for it to work (like 100). It just kept saying unknown server error... so my guess is that ASUS servers suck just keep trying. Also I found that I got the google account approval prompt more often when I waited a couple minutes between tries. Hope this helps good luck
Note: I might have tapped the unlock button maybe 50-100 times xD
Click to expand...
Click to collapse
This gives me hope -- My serial number is visible through the About Tablet screen (C3OKCT******-series). I'll keep trying!
I just downgraded to 9.4.3.17 to see if that gives me any better luck.
---------- Post added at 04:00 AM ---------- Previous post was at 03:26 AM ----------
sparky28000 said:
Exactly the same here. Tablet was also bricked and repaired and now it says Serial number: Unknown. I've already mailed ASUS so now I'll have to wait for them to reply.
Click to expand...
Click to collapse
Who did you contact?
krhainos said:
This gives me hope -- My serial number is visible through the About Tablet screen (C3OKCT******-series). I'll keep trying!
I just downgraded to 9.4.3.17 to see if that gives me any better luck.
---------- Post added at 04:00 AM ---------- Previous post was at 03:26 AM ----------
Who did you contact?
Click to expand...
Click to collapse
Mailed to their standard mail where people who know jack **** about the actual product try to help you. They said that I would have to send it for RMA again. Then I replied in the hope they can do something else because this is their 2-3 **** up.
sparky28000 said:
Mailed to their standard mail where people who know jack **** about the actual product try to help you. They said that I would have to send it for RMA again. Then I replied in the hope they can do something else because this is their 2-3 **** up.
Click to expand...
Click to collapse
Is that [email protected] or some other e-mail address?
krhainos said:
Is that [email protected] or some other e-mail address?
Click to expand...
Click to collapse
[email protected]
sparky28000 said:
[email protected]
Click to expand...
Click to collapse
I've been tapping the Press to unlock button a couple times an hour (up to a couple times a minute) for nearly a day now.
Surely Asus isn't this crappy? Maybe they are.
Quickly losing faith in them.
krhainos said:
I've been tapping the Press to unlock button a couple times an hour (up to a couple times a minute) for nearly a day now.
Surely Asus isn't this crappy? Maybe they are.
Quickly losing faith in them.
Click to expand...
Click to collapse
I really don't know how they could screw up so badly that the device doesn't recognize a serial number and still works fine.
sparky28000 said:
I really don't know how they could screw up so badly that the device doesn't recognize a serial number and still works fine.
Click to expand...
Click to collapse
Well, mine actually recognizes the serial number -- it's visible under both the Settings and getprop ro.serialno.
If I had to guess, it's because my mainboard was replaced through RMA, but the tablet retained the same serial number -- and the unlocker server doesn't allow the same serial number to unlock twice.
EDIT: Just been told by the know-nothing over the phone support that the Device Unlock Tool service isn't experiencing any problems, and that they're unable to offer any assistence because the tool will void the warranty. Asus "support" is flipping worthless.
A small update
It appears the problem I'm having is directly related to this article : http://forum.xda-developers.com/showthread.php?p=32271197
I'm seeing the exact same things in my logcats. The frustrations seem to be endless -- Asus' initial solution appeared to be having affected owners who had both RMA'd their tablet and involved a mainboard replacement. Unfortunately, their proposed solution didn't seem to help the people unable to unlock.
My initial suspicion that their database that records device serial number and internal identifiers not appearing to match the actual hardware seems to be the cause.
Code:
W/DMC->DMService( 1683): ********** notify_end **********
D/DMC->DMService( 1683): type=1, state=1, errorCode=0
D/DMC->DMService( 1683): stop me
D/DMC->DMService( 1683): clear Asus register
D/KeyBoxService( 1617): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1617): === OTA BEGIN
E/KeyBoxService( 1617): === Connection to http://wvdrm.asus.com refused
D/KeyBoxService( 1617): === Retry after 1200 seconds.
D/KeyBoxService( 1617): === OTA END
D/DMC->DMService( 1683): stop me
D/DMC->DMService( 1683): clear Asus register
krhainos said:
Well, mine actually recognizes the serial number -- it's visible under both the Settings and getprop ro.serialno.
If I had to guess, it's because my mainboard was replaced through RMA, but the tablet retained the same serial number -- and the unlocker server doesn't allow the same serial number to unlock twice.
EDIT: Just been told by the know-nothing over the phone support that the Device Unlock Tool service isn't experiencing any problems, and that they're unable to offer any assistence because the tool will void the warranty. Asus "support" is flipping worthless.
A small update
It appears the problem I'm having is directly related to this article : http://forum.xda-developers.com/showthread.php?p=32271197
I'm seeing the exact same things in my logcats. The frustrations seem to be endless -- Asus' initial solution appeared to be having affected owners who had both RMA'd their tablet and involved a mainboard replacement. Unfortunately, their proposed solution didn't seem to help the people unable to unlock.
My initial suspicion that their database that records device serial number and internal identifiers not appearing to match the actual hardware seems to be the cause.
Code:
W/DMC->DMService( 1683): ********** notify_end **********
D/DMC->DMService( 1683): type=1, state=1, errorCode=0
D/DMC->DMService( 1683): stop me
D/DMC->DMService( 1683): clear Asus register
D/KeyBoxService( 1617): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1617): === OTA BEGIN
E/KeyBoxService( 1617): === Connection to http://wvdrm.asus.com refused
D/KeyBoxService( 1617): === Retry after 1200 seconds.
D/KeyBoxService( 1617): === OTA END
D/DMC->DMService( 1683): stop me
D/DMC->DMService( 1683): clear Asus register
Click to expand...
Click to collapse
So the server is pretty much just refusing to process your serial number? The funny thing for me is that if they would just have fixed the I/O issue and made a working jellybean rom everything would be okay but I'm getting really sick of the browser freezing every page and YouTube not loading because the I/O is stalling.
sparky28000 said:
So the server is pretty much just refusing to process your serial number? The funny thing for me is that if they would just have fixed the I/O issue and made a working jellybean rom everything would be okay but I'm getting really sick of the browser freezing every page and YouTube not loading because the I/O is stalling.
Click to expand...
Click to collapse
It has to do more with unit serial numbers with internal serial numbers (cpuid/tegraid/wifi mac) that aren't matching with what the unlock servers have recorded. This would happen if the mainboard was replaced and the unlock server wasn't updated with the information from the new mainboard.
Ex: Say my original mainboard had a with Tegra serialnumber of 3C2B, my replacement mainboard's Tegra serialnumber 1116. The Asus' unlock server is still expecting the old serialnumber(3C2B) as they haven't been told of my replacement mainboard.
Some people have gotten mainboards with the information programmed in wrong (O's for 0's, etc), and thusly are required another RMA to make sure the information is matched between the unlock server and what's actually inside. Jury's still out on if an RMA even fixes the issue.
Some people's information was wrong ever since it left the factory originally -- so this explains why some people who never RMA'd weren't able to unlock.
krhainos said:
It has to do more with unit serial numbers with internal serial numbers (cpuid/tegraid/wifi mac) that aren't matching with what the unlock servers have recorded. This would happen if the mainboard was replaced and the unlock server wasn't updated with the information from the new mainboard.
Ex: Say my original mainboard had a with Tegra serialnumber of 3C2B, my replacement mainboard's Tegra serialnumber 1116. The Asus' unlock server is still expecting the old serialnumber(3C2B) as they haven't been told of my replacement mainboard.
Some people have gotten mainboards with the information programmed in wrong (O's for 0's, etc), and thusly are required another RMA to make sure the information is matched between the unlock server and what's actually inside. Jury's still out on if an RMA even fixes the issue.
Some people's information was wrong ever since it left the factory originally -- so this explains why some people who never RMA'd weren't able to unlock.
Click to expand...
Click to collapse
Now that last part does make sense. I'm still wondering though why my device doesn't recognize a serial number of any sorts the ****ting thing is that I should be able to edit one file to make it work but because I can't unlock I can't have root so I can't edit the file...
You would think, but I'm betting the info is on a chip instead of a file in primary storage.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
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.
I finally got ASUS to help me unlock my Infinity They just don't know about it.
I have tried for months to unlock my tablet - everytime getting the famous "unknown error" error message.
At some point, I discovered that I could not egister my TF700 on ASUS device tracker web page. The error message I got was "invalid serial number"
That made me suspect that there might be a connection between the unlock problem and the device tracking problem.
I raised an issue through ASUS support pages, asking them to help me register my serial number at the device tracker system. Support could not find any problem with my serial number, so they raised the issue from support to ASUS R&D. This was about two weeks ago.
Today I received an email from support telling me that the issue was solved, and that I now should be able to register at Asus Device Tracker. Never mind that I ran the unlock tool and.... YES - It worked. I'm finally unlocked!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Gefjon said:
I finally got ASUS to help me unlock my Infinity They just don't know about it.
I have tried for months to unlock my tablet - everytime getting the famous "unknown error" error message.
At some point, I discovered that I could not egister my TF700 on ASUS device tracker web page. The error message I got was "invalid serial number"
That made me suspect that there might be a connection between the unlock problem and the device tracking problem.
I raised an issue through ASUS support pages, asking them to help me register my serial number at the device tracker system. Support could not find any problem with my serial number, so they raised the issue from support to ASUS R&D. This was about two weeks ago.
Today I received an email from support telling me that the issue was solved, and that I now should be able to register at Asus Device Tracker. Never mind that I ran the unlock tool and.... YES - It worked. I'm finally unlocked!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Congrats!
Enjoy a whole new tablet now, one that beats many, many others in many aspects
Gefjon said:
I finally got ASUS to help me unlock my Infinity They just don't know about it.
I have tried for months to unlock my tablet - everytime getting the famous "unknown error" error message.
At some point, I discovered that I could not egister my TF700 on ASUS device tracker web page. The error message I got was "invalid serial number"
That made me suspect that there might be a connection between the unlock problem and the device tracking problem.
I raised an issue through ASUS support pages, asking them to help me register my serial number at the device tracker system. Support could not find any problem with my serial number, so they raised the issue from support to ASUS R&D. This was about two weeks ago.
Today I received an email from support telling me that the issue was solved, and that I now should be able to register at Asus Device Tracker. Never mind that I ran the unlock tool and.... YES - It worked. I'm finally unlocked!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Boy you must be very very...very happy guy! Congrats!
This is a very, VERY good find -- good train of thought, I like that. Props to you!
Enjoy your unlocked 700, and may other succesfully follow your path.
You know, I found this thread because the tool was asking for my google password.... and not accepting it.
I have enhanced security turned on. So folks, if you found this the same way I did, log in to your google account, go to settings > security > Connected Apps and Services, and generate a password for the unlocker app. Use that password.
Not sure how one directed me to the other... but there ya have it.
Well, Asus Support France isn't very supportive in my case: I got a response along the lines of "there's nothing special to do, you must have entered some info wrongly".
The symptoms are slightly different with me though:
I had registered my TF700 on the device tracker before the RMA and the service worked.
Now, after the RMA, the service just doesn't work, but only as if the tablet was shut down ("command failed").
I tried setting up a different profile to re-register, but it just fails ("command failed", again).
I'll try again with a different approach.
(or I'll give up, sell the TF700 and scrap tablets altogether)
quietseb said:
Well, Asus Support France isn't very supportive in my case: I got a response along the lines of "there's nothing special to do, you must have entered some info wrongly".
The symptoms are slightly different with me though:
I had registered my TF700 on the device tracker before the RMA and the service worked.
Now, after the RMA, the service just doesn't work, but only as if the tablet was shut down ("command failed").
I tried setting up a different profile to re-register, but it just fails ("command failed", again).
I'll try again with a different approach.
(or I'll give up, sell the TF700 and scrap tablets altogether)
Click to expand...
Click to collapse
I have a similar situation here in the US. I was trying to unlock but kept getting the standard network error. After multiple emails to Asus, they told me that the Wi-fi mac address that I registered the tablet with was different than the current one on the tablet (I had to send it in for a RMA shortly after purchase, and I think that they changed the motherboard.). They asked me to RMA again so that they can fix it. It's currently there now, so hopefully when I receive it back, I'll be able to unlock it.
UPDATE: RMA didn't help. I still have the network error. im'd support. They just told me that they don't support unlock; I'm on my own. Am rightly p'od about it. I may try actually calling Support, but that's after vacation (believe me, I now need it!).
Actually I was hoping I could avoid a third RMA using Gefjon's "workaround"... Plus some reports of tablets RMAed for that exact problem (tablet can't unlock due to serial number / Wifi mac address mismatch) show that the returned tablet often still can't unlock...
Hope it'll be okay with yours!
Sent from my Xperia Neo V using xda app-developers app
Is anyone who is getting the error when trying to unlock also able to get OTA updates? I explained about 5x now to support that my tablet does not find updates when it searches, does not register with the asus web tracker, and does not work with the unlock tool. One email support said the mac address was different on the server than the one shown to be associated with my tablet. I said I'd like the ticket sent on to Taiwan so the developers can look in to it fixing it. She said that was impossible to do and to contact local support (800 number here in the states). Yesterday I called support asking to have a ticket sen to Taiwan to check what the server has my tablet. This support staff said the mac address is the one associated with my serial number and would not listen to the rest of my explanation. I had apparently researched his allotted time per call.. It ended with the default send it in to RMA because if it's not getting OTA then something is wrong with the tablet and they will fix it. He claims there is no issue with the servers in Taiwan that they know of.
Now I'm trying to decide if I want to be without the tablet for 3 weeks or just cut the hopes of unlocking it for better performance and stick with what ever firmware they release. At least I can disable bloatware with root. I did have the person add that if the tablet is being shipped back for RMA then i want all of the screen bleed fixed and will not accept the tablet back if the product is damaged. First time I sent it in for unrelated issue I got it back with metal around the plug port and dock holes bent. I got the pictures to prove it.
There is no other way to install a rom with just root access? even if it uses stock kernal?
fsured said:
Is anyone who is getting the error when trying to unlock also able to get OTA updates? I explained about 5x now to support that my tablet does not find updates when it searches, does not register with the asus web tracker, and does not work with the unlock tool. One email support said the mac address was different on the server than the one shown to be associated with my tablet. I said I'd like the ticket sent on to Taiwan so the developers can look in to it fixing it. She said that was impossible to do and to contact local support (800 number here in the states). Yesterday I called support asking to have a ticket sen to Taiwan to check what the server has my tablet. This support staff said the mac address is the one associated with my serial number and would not listen to the rest of my explanation. I had apparently researched his allotted time per call.. It ended with the default send it in to RMA because if it's not getting OTA then something is wrong with the tablet and they will fix it. He claims there is no issue with the servers in Taiwan that they know of.
Now I'm trying to decide if I want to be without the tablet for 3 weeks or just cut the hopes of unlocking it for better performance and stick with what ever firmware they release. At least I can disable bloatware with root. I did have the person add that if the tablet is being shipped back for RMA then i want all of the screen bleed fixed and will not accept the tablet back if the product is damaged. First time I sent it in for unrelated issue I got it back with metal around the plug port and dock holes bent. I got the pictures to prove it.
There is no other way to install a rom with just root access? even if it uses stock kernal?
Click to expand...
Click to collapse
1) For unlocking issue - You should use the method "ASUS device tracker" registration with Asus tech support, don't tell them anything about unlocking, and once they fixed the ASUS device tracker which allow your device to register and very possible that unlocking would work too.
2) If you only rooted, you only can manually flash stock rom and stock kernel. That's it.
nah
buhohitr said:
1) For unlocking issue - You should use the method "ASUS device tracker" registration with Asus tech support, don't tell them anything about unlocking, and once they fixed the ASUS device tracker which allow your device to register and very possible that unlocking would work too.
2) If you only rooted, you only can manually flash stock rom and stock kernel. That's it.
Click to expand...
Click to collapse
I managed to register my TF700 on ASUS device tracker website. Could even block it remotely with a password.
Unfortunately this didnt solve my unlocking problem. Contacted ASUS support, they asked for DM Server, FW, Mac Address screenshots.
Waiting for an escalation...
kemtrails said:
I managed to register my TF700 on ASUS device tracker website. Could even block it remotely with a password.
Unfortunately this didnt solve my unlocking problem. Contacted ASUS support, they asked for DM Server, FW, Mac Address screenshots.
Waiting for an escalation...
Click to expand...
Click to collapse
One guy with Asus US is trying right now to get this fixed. Send him your info as this post says to and you might get fixed in the next batch:
http://forum.xda-developers.com/showpost.php?p=40408537&postcount=567
He has already successfully helped one Transformer user as a test.
I currently have my tablet at the Texas facility for RMA. I gave up trying to explain to the phone rep that the issue is not so much with the tablet but with how it is registering on the server. I said fine RMA it but i'm not for postage. He gave me a free comp on postage this time. In box i typed up a description of what it was doing and didn't mention unlocking the tablet. One member here advised not to mention it. I figured if i'm going to be unable to unlock then let them fix it so I can at least get OTA updates and use the Device Tracker. In theory with those working my chances of unlocking may be higher. I explicitly said test the OTA download service to make sure it work, and test the device tracker website. I included screen hot print outs of the error or tablet saying it is up to date.
Since they are going to have the tablet again I'm having them do what they can to fix light bleed. Also do some frame repair from the last RMA.
I also mentioned this is my second RMA to this facility. The first time it was returned damaged. I have pictures of before it was send, when it was returned with the damage, and pictures of the device right now. I mentioned if there is more damage on the device then I return to to the deilvery guy and check return to sender.
Gefjon said:
I finally got ASUS to help me unlock my Infinity They just don't know about it.
I have tried for months to unlock my tablet - everytime getting the famous "unknown error" error message.
At some point, I discovered that I could not egister my TF700 on ASUS device tracker web page. The error message I got was "invalid serial number"
That made me suspect that there might be a connection between the unlock problem and the device tracking problem.
I raised an issue through ASUS support pages, asking them to help me register my serial number at the device tracker system. Support could not find any problem with my serial number, so they raised the issue from support to ASUS R&D. This was about two weeks ago.
Today I received an email from support telling me that the issue was solved, and that I now should be able to register at Asus Device Tracker. Never mind that I ran the unlock tool and.... YES - It worked. I'm finally unlocked!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Thank you so much for posting this. I am once again happy with my TF700. I just want to confirm that this worked for me as well. I just want to share a few other things so others might gain from it. BE PERSISTENT with ASUS!! I got excuses from them several times.
I kept getting the "Command Failed" error on Device Tracker when trying to register my device. ASUS tier 1 support attempted all their usual fixes with me but (surprise) it still didn't work. They eventually sent me to their VIP eservice site, where they said to enter another ticket and a supervisor would be able to help through this. (XDA won't allow me to paste the URL because I'm a noob). Just Google ASUS VIP eService and the first result should be the form.
The first response I got via email told me that they had a record that my device was unlocked and that device tracker doesn't work with unlocked devices. I told them that, Yes, I had unlocked my device before the RMA but they were supposed to have replace the main board and I got the device back 're-locked' so the device was not currently unlocked at this time. They then asked for my Wifi MAC Address and said they were sending this information off to the department who handles it (nothing more specific). I got another email about 24 hours later that device tracker should work now. Just like Gefjon, I immediately tried the unlock tool instead and BINGO it unlocked successfully on the first try.
Thank you again for posting your findings!
Just want to say that the exact same thing happened to me.
I was unable to register the device on the tracker website, error message was 'invalid serial'. I shot an email off to their support site. Bit back and forth with them trying the usual suspects first, like reset, reboot etc.
Then i got an email from one of the engineers, told him the same issue was present with quite a few devices. And also that a ASUS rep was looking into the problem on these boards.
12 hours later i got an email back, telling me to try again. And my tf700 unlocked happily
chzz said:
Just want to say that the exact same thing happened to me.
I was unable to register the device on the tracker website, error message was 'invalid serial'. I shot an email off to their support site. Bit back and forth with them trying the usual suspects first, like reset, reboot etc.
Then i got an email from one of the engineers, told him the same issue was present with quite a few devices. And also that a ASUS rep was looking into the problem on these boards.
12 hours later i got an email back, telling me to try again. And my tf700 unlocked happily
Click to expand...
Click to collapse
Lucky. I was successful in getting email support to send the request to whatever department checks the server information. They responded that my tablet information isn't even registered on the servers. That is why I can't do anything with it that involves communicating with Asus. I was given the option to RMA again so they can add my tablets information to the server. Haha. Not a simple, "oh there is a wrong number with the serial or mac address."
I sent it in about 4wks ago for this and all the tech did was manually install the latest firmware. All they saw was unable to receive OTA and figured flashing it there was what I sent it in for. Makes me wonder if they even read the "typed description" they ask to be sent with the tablet or the actual RMA ticket. I could flash Ice Cream Sandwich and it would not recognize the old firmware is out of date and proceed to update itself. Even sent a screen shot of the error when using device tracker to go with the typed description of the problem.
fsured said:
Lucky. I was successful in getting email support to send the request to whatever department checks the server information. They responded that my tablet information isn't even registered on the servers. That is why I can't do anything with it that involves communicating with Asus. I was given the option to RMA again so they can add my tablets information to the server. Haha. Not a simple, "oh there is a wrong number with the serial or mac address."
I sent it in about 4wks ago for this and all the tech did was manually install the latest firmware. All they saw was unable to receive OTA and figured flashing it there was what I sent it in for. Makes me wonder if they even read the "typed description" they ask to be sent with the tablet or the actual RMA ticket. I could flash Ice Cream Sandwich and it would not recognize the old firmware is out of date and proceed to update itself. Even sent a screen shot of the error when using device tracker to go with the typed description of the problem.
Click to expand...
Click to collapse
Thats really unfortunate fsured. I do not know whey they are being so difficult with this. Its clearly a problem on their end with a simple fix, and all of us have paid to have a working product.
The hit and miss of the support is just damaging their reputation and will hurt their bottom line a lot more than being a bit forthcoming in the service requests. Especially as things are with the tf700 having bad IO issues and need a 3rd party ROM to work optimally. If things was working well without a custom ROM i could better understand their attitude.
Have you tried sending a PM to the ASUS rep on here?
After sending it in a second time to repair this issue I was displeased to discover that the service center replaced the MB of the tablet thinking that would fix it. Even after I highlighted in yellow the response from Asus email support that all they have to do is add my tablets information into the server database. That is just wasted money and shows the service center has some issues. It's essentially a new tablet. But this did not fix the issue on the server side.
Have you tried sending a PM to the ASUS rep on here?
Click to expand...
Click to collapse
And here is the good news. On Tuesday I responded to the same email support member who originally informed me that the tablet information was not on the servers and explained what happened. I also emailed the Asus rep on here explaining things. ---Side note, He rocks. He has helped me with my Prime issues and now this one--- Not sure what he did or informed back in HQ but last night he responded that he was going to try something. I got another email about 40min ago asking to reboot the tablet and try to unlocked. It worked! I didn't go through the process yet. I want to read up and make sure I know what I'm doing. I'm pleased with the performance on stock but the temptation is there with all the praise the tablet receives on cromi.
After canceling out of the unlock I tried the update firmware since it was not receiving any previously. Sure enough it went to downloading the latest update. :victory:
I have now the same problem,
But then from Europe Belgium.
Last year my tablet was DEAD, it was unlocked and cromni was installed.
I send it to ASUS for a repair and they replaced the motherboard.
Now after 1 year working with stock ROM and a lot of reboots and SO SLOW I tried again to unlock and install a custom ROM.
But I have the same problem where I am unable to reboot with as comment a network error.
Reading here I tried to do the ASUS device tracker, and also there they say that my serial number is not recognized.
I then opened a ticket on the ASUS VIP Service, there when I enter my serial number it immediatly shows model and type, so it is in that database.
I just got a response from ASUS that also for them the information is incorrect (serial number and or MAC address) and they have forwared the message to TAIWAN.
TO BE CONTINUED...
Zuran said:
I have now the same problem,
But then from Europe Belgium.
Last year my tablet was DEAD, it was unlocked and cromni was installed.
I send it to ASUS for a repair and they replaced the motherboard.
Now after 1 year working with stock ROM and a lot of reboots and SO SLOW I tried again to unlock and install a custom ROM.
But I have the same problem where I am unable to reboot with as comment a network error.
Reading here I tried to do the ASUS device tracker, and also there they say that my serial number is not recognized.
I then opened a ticket on the ASUS VIP Service, there when I enter my serial number it immediatly shows model and type, so it is in that database.
I just got a response from ASUS that also for them the information is incorrect (serial number and or MAC address) and they have forwared the message to TAIWAN.
TO BE CONTINUED...
Click to expand...
Click to collapse
You are not the first one has this issue about the unlock after the RMA... You need patience and work with Taiwan to solve your problem.. Good luck..:fingers-crossed:
Hi Folks,
since October i'm a proud owner of an infinity tab.
In November i got an issue with the touch screen which stopped responding during work and i needed to set it into standby and turn it in aga in to make it work.
So i called ASUS-Support for help. After some days of mailing them and some responses they gold me, hat i have to send it to ASUS and they will take about 10 days to repair it.
It took them 43(!!!) days. In this time i got no proactive information about the progress. So i needed to ask again.
They also gave me the option to pay me the money back, i spend in this device.
But i wanted exactly that type of device.
When i got back my device i firstly was very happy, because all errors i told them were fixed.
They replaced the mainboard.
But then i considered that the device was not hit by the OTA-update and I needed to contact ASUS again.
First they asked me about the MAC of my new Main board.
So somebody missed to change it in their database for OTA-Updates.
I gave the needed information and waited for response... Nothing.
Again in asked ASUS and they told me to manually update to the actual version and wait for the next update.
Then android 4.2 got to our devices but no OTA at mine showed up.
Very angry I mailed ASUS again, and they told me to send my device back again.
I asked them, how they think to keep me online, because I already waited 43 days for the first fix.
But they didn't even react on that. It ended in the suggestion to update my device manually if I do not want to send the device in.
I now decided to never by any ASUS device again because of the bad service I get for a device for 719 € .
Cu hanswurst1979
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
hanswurst1979 said:
Hi Folks,
since October i'm a proud owner of an infinity tab.
In November i got an issue with the touch screen which stopped responding during work and i needed to set it into standby and turn it in aga in to make it work.
So i called ASUS-Support for help. After some days of mailing them and some responses they gold me, hat i have to send it to ASUS and they will take about 10 days to repair it.
It took them 43(!!!) days. In this time i got no proactive information about the progress. So i needed to ask again.
They also gave me the option to pay me the money back, i spend in this device.
But i wanted exactly that type of device.
When i got back my device i firstly was very happy, because all errors i told them were fixed.
They replaced the mainboard.
But then i considered that the device was not hit by the OTA-update and I needed to contact ASUS again.
First they asked me about the MAC of my new Main board.
So somebody missed to change it in their database for OTA-Updates.
I gave the needed information and waited for response... Nothing.
Again in asked ASUS and they told me to manually update to the actual version and wait for the next update.
Then android 4.2 got to our devices but no OTA at mine showed up.
Very angry I mailed ASUS again, and they told me to send my device back again.
I asked them, how they think to keep me online, because I already waited 43 days for the first fix.
But they didn't even react on that. It ended in the suggestion to update my device manually if I do not want to send the device in.
I now decided to never by any ASUS device again because of the bad service I get for a device for 719 € .
Cu hanswurst1979
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
You don't need "Germany" in the title. Asus support sucks period.
The usernames featured in this thread are highly amusing..
Did you contact Asus directly or go back to the shop you bought it at? Under EU law the shop is bound to give you a full 1 year warranty, you see.
Why did you refuse the money back ? With it you could have bought a completely new infinity tab with no repaired part.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
cause it was not available at my trusted shops anymore...
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I understand
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
ShadowLea said:
The usernames featured in this thread are highly amusing..
Did you contact Asus directly or go back to the shop you bought it at? Under EU law the shop is bound to give you a full 1 year warranty, you see.
Click to expand...
Click to collapse
I contacted ASUS directly because they said it wouldn't last longer than 10 days... The shop would last longer.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app