Hi,
I finally gave up on trying to figure out my lag issues.
Asus finally gave me an RMA number so I could send it in to be looked at.
My question is: My TF300T is rooted with several apps installed that need root. Should I un-root the device before sending it in. And should I remove those apps. Or should I just do a wipe to totally clean off anything that is mine show it was rooted.
Or just send it in as it is, being rooted?
Thanks
Rob
PS I'm going to try and take a video of how this tablet is running now to see if you all agree that something is wrong.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2!
I'd unroot it and uninstall all root apps, just in case Hope you get it fixed.
Unroot and do a factory reset. So it won't have any personal info.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I would also take pictures of the tablet in it's current condition and in it's packaged state and keep it for your records. I know it sounds a little paranoid but better safe and protected then sorry
Big-time +1! Always take pics. Protects you from shipping disasters as well. Remember the FedX guy?
Hello folks. I've unlocked my Infinity using the Asus unlock tool. Well, all I really wanted was to root it (which I did) but I got the two mixed up and I also unlocked it first. I will never be loading a custom rom therefore I'd rather keep mine locked. This also voids my warranty and I'm afraid I won't be able to receive OTA's.
Is there ANY way to lock the bootloader back up like it was from the factory? If I should keep the pad unlocked, convince me why.
Thanks for any help!
No, there isn't. Your S/N is already in their database, too. You may use manual firmware updates from their site and they may still respect the warranty (to certain extent?).
There was enough threads on the two for you not to confuse them (as there is about what you can do with being unlocked), so you pretty much rushed into it. Most likely this will not make your life with the Infinity harder, however.
Dammit. I'm an idiot. Now no OTA for me. Well, I can still return it to where I bought it from. I wish I had paid more attention.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Completely agree. NVFlash for all.
paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse
+1
+1
There should be no lockdown code in the bootloader for "unlocked" devices.
I agree, they're surprisingly draconian about what "unlocked" means. We're not even covered under their warranty, might as well give us full access to our devices smh
Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
i
urrlyx said:
+1
get
There should be no lockdown code in the bootloader for "unlocked" devices.
Click to expand...
Click to collapse
:good: Yep. All or nothing. Don't void my warranty then partially cripple my ability to get my money's worth
Slammin said:
Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
of course nv flash would have saved all of those bricks from going back to asus.
they should be providing this tool rather then locking it down.
Hearing that the .30 bootloader is signed and won't allow flashing of unsigned bootloaders (downgrades included, since they are not signed) made me incredibly angry with ASUS. It's the wrong way to attack the problem. Even then, it's still possible to flash Jelly Bean to a TF700 in (IMHO) the most crazy of ways, by flashing the TF300 JB ROM. Even on locked devices!
There is this nvflash tool that makes it possible to recover from any brick known to man, and they just don't seem to want us to have access to it. I have unlocked my tablet to do exactly what I want with it, but even after I've voided my warranty, ASUS won't let me do it. Custom ROMs have a higher tendency to brick a device than a stock ROM, and people who've unlocked their devices should be tech-savvy enough to follow a tutorial to nvflash it back from the dead. Instead, ASUS wants them to enjoy their new shiny $500 paper weight/door stop.
ASUS, this was a **** move. The least you could do would be to provide a possibility to downgrade the bootloader (ie. a signed blob of an unsigned bootloader, for example the 9.4.5.26 one). Even better, you could actually unlock unlocked devices, or just give us nvflash for real.
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.
That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Not sure if i understood what you meant with the "wheelie" version but afaik wheelie is used just for "bootstrap" (basically is used to bypass the lock that Asus used in order to prevent us from using NvFlash) in NvFlash mode, after that you will use "native" nvflash commands (wich are different based on the device u are using) , basically what Asus should provide to us from the start.
I'm probably not using the right terms... Using the TF101 as an example, the early TF101s (SBK V1) were able to use NVFlash directly, with no restrictions. Then, Asus being Asus, they modified the SBK (Secure Boot Key?) in the newer TF101's and NVFlash would no longer work on these SBK V2 devices. That's when one of the awesome developers released Wheelie - it allowed NVFlash to be used on the newer SKB V2 TF101's.
So, I think you already answered my question!
If I understand you correctly, Wheelie is just used to get around the SBK at which point NVFlash can be used normally?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
I could be wrong but i think that on the first tf101 batch nvflash was not ready "out of the box" but was possible only after the SBK leak. And that explain why Asus used SBK v2 on the next tf101 batch... Basically they never provided full APX/NvFlash access and i guess they never will.
jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Click to expand...
Click to collapse
Pretoriano80 said:
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.
Click to expand...
Click to collapse
Lets face it, I think everyone was blindsided when .30 was released. Wasn't JB meant to be released next?? I am wondering whether the reason they have actually done this is to prevent flashing TF300 JB on the TF700. Has anyone on .30 actually been able to flash the TF300 firmware? I suspect that there were a few red faces when ASUS saw that the TF300 firmware could be flashed on locked TF700s. Also, that flashing this firmware caused TF700s to be stuck with the TF300 JB bootloader. .30 did repair the damaged TF700 bootloaders but has had the knock-on effect of not allowing us to not use NVFlash. This is not cool...
Hit the "Newsworthy Thread" thing at the top! Lets see if we can get the XDA news people to take a bit of interest in this and cause ASUS a little bit of shame This thread from the Prime forum seemed to get some attention from Tien once XDA made it public (see post 200): http://forum.xda-developers.com/showthread.php?t=1764917&page=20
paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse
+1
one more here.
Another here I was Awesomely Pleased when i have to Unbrick my Prime, but now that NVFlash is out on the Infinity I can't use it? Aww ASUS you Disappoint me..
This is a lost cause as they promised to be looking in to an official nvflash release for the transformer prime but as you can see it never came. The only access we had is when wheelie was released. This is why I cant support them with the way they are treating customers that are buying their tablets. At least with samsung products I have odin. You are just SOL with the asus now. As someone stated above, its like all they want to do is line their pockets. All they are doing is driving the customers away.
Also when yiu unlock your transformer tablet they delete the DRM Keys. Meaning any program relying on it like hulu or play movies will not work (netflix works I think).
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I RMAed my first TF300T and got another refurbished one but this one doesn't seem to want to receive OTA updates (I updated manually), the bootloader will not unlock (error), and asus device tracker tells me im entering the wrong serial. I know others have had a very similar issue and I am wondering if a fix has been found or if I will have to RMA again.
twich12 said:
I RMAed my first TF300T and got another refurbished one but this one doesn't seem to want to receive OTA updates (I updated manually), the bootloader will not unlock (error), and asus device tracker tells me im entering the wrong serial. I know others have had a very similar issue and I am wondering if a fix has been found or if I will have to RMA again.
Click to expand...
Click to collapse
Some one else had similar issue but they unlocked the device then sent it in for rma which costed them like 200 but long story short they replaced the board which caused him to lose unlocked but device still showed was unlocked in asus' system so they wouldn't help him. Maybe be similar for you because its a refurb could have been unlocked by previous owner and not fixed properly if it was by asus or something but probably still shows its unlocked in there system. I'd report to asus the experience your have and see what they say and if possible I'd probably rma again if it came that way. What the point in keeping device that came broken already especially if someone elses error. Bty no fix for that yet and probably wont be for a while. Also depending on who you have to rma with might be difficult if thats the only issue i'd start looking for other issues like random reboot, bootloop, hdmi, etc. Just something to give them for a sure replacement. All thats your choice though if it worth going through the trouble again. Took me 2 weeks went nuts without it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
i have the same issue currently it a rma that was fixed say but it wasnt unlocked or anything was random booting so i tried to update it and bricked it well now i cant unlock it just says error
long story short: it took incredible three RMAs for me to get my bootloader unlocked. gotta hate those idiots at czech repair place. but kudos goes to helpful customer care.
julian_fin said:
long story short: it took incredible three RMAs for me to get my bootloader unlocked. gotta hate those idiots at czech repair place. but kudos goes to helpful customer care.
Click to expand...
Click to collapse
i just called then trying to get help with unlocking it and no luck
Kaptinkrunk said:
i just called then trying to get help with unlocking it and no luck
Click to expand...
Click to collapse
just fill out rma req from asus.com website and have dhl to pick up your tab.
tell them that you cannot do OTAs
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
julian_fin said:
just fill out rma req from asus.com website and have dhl to pick up your tab.
tell them that you cannot do OTAs
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
Click to expand...
Click to collapse
I've already rma'd it once.. It let's me do otas...
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
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