Database Info

32gb Xoom Showing 4GB Total Space

Dear Fellow Xoom Users,
I have a 32 GB, 3.1 From Factory, 3G Xoom. It is a MZ601 which was bought on a trip to Hong Kong.
It all worked fine untill I succumbed to the bug most of us have and decided to start modding, hacking and tinkering with my Xoom. There is something about the rush of possibly destroying an almost 800 Dollar tablet that cant be matched
I flased the Tiamat 2.0.1 rom and The Xoom Zone one. It all looked good and worked flawlessly. I tried messing with the stock one and creating a custom rom and kernel of my own. I am slowly getting there,I would get to a point where I messed it up, I would use fastboot to get myself back to stock ( 3.0.1 ) with files sourced from;
developer.motorola.com/xoomsoftware
I used the international ROM software, as I didnt know which version of the MZ601 I had coming from Hong Kong. The files posted on motorola funny enough take me to 3.0.1 rather than the stock 3.1 I had out of the box, but a few minutes later, 3.1 comes OTA.
I was checking the 'About Tablet' and noticed something weird with my tablet, it is showing 4GB total space, a little odd for a 32GB tablet no?? (See Pic)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What do you guys think...am I just high again and seeing the wrong thing or do you know what the problem is?? When I first got the tablet I loaded about 20GB worth of books, music and videos on it....so i DO REMEMBER it having 32GB!!!
Regards,
Joshua

something wrong. my is 28.32GB, maybe flash wrong?

mhz1000a said:
something wrong.
Click to expand...
Click to collapse
Well you are not wrong there, something is DEFINATELY wrong!! I have probably written something to its memory causing it to now show only 4GB but I was just wondering if anyone would know what.how why etc saving me the time from exploring the issue in hours of Ubuntu terminal command line!!

Maybe old clockwork recovery file and it backed up the whole system image? Make sure u have the latest recovery installed
Sent from my Xoom using XDA App

vlx600d said:
Maybe old clockwork recovery file and it backed up the whole system image? Make sure u have the latest recovery installed
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I appreciate your reply!!
Yes I do have the latest CWM Recovery from THIS THREAD so I assume that it is the optimal one to use.
Also, something to note, the above image is from STOCK. To get back to stock, instructions were followed from, developer.motorola.com/xoomsoftware.
4GB is Hilarous, and not matter what I flash, full stock, xoom zone, Tiamat....they all show the EXACT same about screen indicating I have 4GB....
Silly Tablet...

Aeren said:
Dear Fellow Xoom Users,
I have a 32 GB, 3.1 From Factory, 3G Xoom. It is a MZ601 which was bought on a trip to Hong Kong.
It all worked fine untill I succumbed to the bug most of us have and decided to start modding, hacking and tinkering with my Xoom. There is something about the rush of possibly destroying an almost 800 Dollar tablet that cant be matched
I flased the Tiamat 2.0.1 rom and The Xoom Zone one. It all looked good and worked flawlessly. I tried messing with the stock one and creating a custom rom and kernel of my own. I am slowly getting there,I would get to a point where I messed it up, I would use fastboot to get myself back to stock ( 3.0.1 ) with files sourced from;
developer.motorola.com/xoomsoftware
I used the international ROM software, as I didnt know which version of the MZ601 I had coming from Hong Kong. The files posted on motorola funny enough take me to 3.0.1 rather than the stock 3.1 I had out of the box, but a few minutes later, 3.1 comes OTA.
I was checking the 'About Tablet' and noticed something weird with my tablet, it is showing 4GB total space, a little odd for a 32GB tablet no?? (See Pic)
(img removed for quote to stay smaller ~ Cranvis)
What do you guys think...am I just high again and seeing the wrong thing or do you know what the problem is?? When I first got the tablet I loaded about 20GB worth of books, music and videos on it....so i DO REMEMBER it having 32GB!!!
Regards,
Joshua
Click to expand...
Click to collapse
You said that you bought this on a trip to Hong Kong. Did you buy it IN Hong Kong or in a store that you can return the device to?
I noticed that you said in your post that you bought if from the factory... But Where?
Reasons I ask --
If bought in Hong Kong, you might have gotten a knock off version of the Xoom.
If bought down the street at a store you can go back to, I would say reflash it with Stock and take it back and demand a refund, repair, or replace (the three R's heh...)
You could have also flashed the device with a bad sector that is suppose to display the size of the internal memory... Keep us up to date on this and I hope all goes well for you... just remember the 3 R's... helped me in many situations...

Bought it IN Hong Kong, from a rather reputable store. If it is a knock off, it is a really good one!! It had everything it should, right down to the stickers. Not a single bit of engrish either. It truly has me baffled, I think it was a poor write which in turn messed up a memory sector as I CLEARLY remember putting on 20 gigs of data before I started messing with custom roms. I shall persevere a tad more and see what I can find.
Sent from my MZ601 using XDA Premium App

Hey Guys - This may sound kinda funny but I have the exact same problem. When i got the tab, it showed the whole 32GB, but after tinkering with it, and after using Tiamat's rom (no blame game here), it shows exactly 4.11GB and the startup screen is gone from a breathing "M" logo to a custom hexagon flash...
HELP!.. Is ther anyway, I can re-partition the internal storage thru fastboot?

EXACTLY my problemmo my man!!! Good to know I am not the only one.
Sent from my MZ601 using XDA Premium App

I wonder if you are going to need to completely re-flash everything to stock, meaning that you would need to wipe everything off the internal SDD. Or maybe the rom was slightly corrupted though download? I would suggest looking into maybe going and seeing how to wipe the full SDD and reformat, partition, and start with a clean Stock Rom? That is the only way that I can see this getting fixed unfortunately... you might have had a weird switch where the OS is on the 28gbs that is free and the 4gbs that are for the OS to be stored as is the internal... (is this even possible?! I have had some weird stuff happen with computers where i have made a 1tb look like a 2 gig hdd... but I'm just saying... it is a possibility and maybe a point in the right direction?)
I would also like to note to Aeren, I was not meaning to say that you did buy a knockoff, I just now there are some out there of many of the tablets... so it was a thought process and I was just playing devils advocate on what could be the troubles... and wanted to make sure it wasn't

Right.. and how would one go about doing that? - i.e., wiping the SDD (truly).. I mean its not like we can plug it into windows and startup partition magic. There has to be a way to actually wipe the entire internal storage and bring it back to factory.
At this point i'd like to say - HELP!..

I, obviously, am curious as to whether I can reformat/partition the internal SSD of my Xoom. I have looked for it in Disk Manager and GParted on Ubuntu to no luck,I am guessing it is hidden for a reason.
I was wondering if anyone had any sort of advice, short of returning it , as to how I may access the 'drive' inside of the xoom so I could partition/format it/look at it/investigate/LOSE MY MIND!!
I guess we could just get a rather large microSD to compensate. :S

Aeren said:
I, obviously, am curious as to whether I can reformat/partition the internal SSD of my Xoom. I have looked for it in Disk Manager and GParted on Ubuntu to no luck,I am guessing it is hidden for a reason.
I was wondering if anyone had any sort of advice, short of returning it , as to how I may access the 'drive' inside of the xoom so I could partition/format it/look at it/investigate/LOSE MY MIND!!
I guess we could just get a rather large microSD to compensate. :S
Click to expand...
Click to collapse
I will look into this when i get back to my computer... but I am not quite sure... you might be able to do something by looking up how people have formatted their iphones and put android on them, or partitioned the ssd to be allowed to place a dual boot and multiboot os on the system. there have also been people that have placed ubuntu on the rooted systems to run in the back ground allowing people to do a 12.0.0.1 vnc into the os. Looking at all these and seeing how they were able to create these is worth a shot. Another way that could be able to help it move along, is maybe get a terminal emulator and run commands through it and see if there is a way to activate certain command lines... but a novice (not saying you are, just warning is all) should not try this because you can easily brick your tablet...
Also speaking of which... maybe looking at how bricking tablets are fixed might help too? I am sorry taht I can't help any more then suggest at this current moment, I am not at home with my computer to be able to look at links quickly... hurraay mobile browsers haha....
I hope I pointed you into a good direction, I will check back as soon as I can! Good luck!

Hi,
I've exactly the same problem!.
Bought an MZ601 last monday in HK at a big chain with different stores. As the build installed has no spanish language neither spanish keyboard input, I downloaded and fastbooted the EU version from Motorola developers zone.
There is a glitch when flashing userdata.img. The tablet says image file si bigger that partition, so it cannot load it.
Finally, everything seems to be ok, except the memory (in my case is 4,11 Gb!).
I spent lot of time doing different tests and trying with diferent versions. Allways the same result.
My guess is that those two things shall be related (did you experienced also trouble when flashing userdata.img?). As the tablet I bought was brand installed allready in 3.1 and I'm flashing 3.0, maybe partitions have been already shrinked and the old file does not fit.
Anyway, I will keep in contact and hope to find a fix.
Regards

ritter_xoom said:
Hi,
I've exactly the same problem!.
Bought an MZ601 last monday in HK at a big chain with different stores. As the build installed has no spanish language neither spanish keyboard input, I downloaded and fastbooted the EU version from Motorola developers zone.
There is a glitch when flashing userdata.img. The tablet says image file si bigger that partition, so it cannot load it.
Finally, everything seems to be ok, except the memory (in my case is 4,11 Gb!).
I spent lot of time doing different tests and trying with diferent versions. Allways the same result.
My guess is that those two things shall be related (did you experienced also trouble when flashing userdata.img?). As the tablet I bought was brand installed allready in 3.1 and I'm flashing 3.0, maybe partitions have been already shrinked and the old file does not fit.
Anyway, I will keep in contact and hope to find a fix.
Regards
Click to expand...
Click to collapse
Sounds pretty much EXACTLY what happened to me. Also same thing happened to another user in this thread after flashing Tiamat. I am also not playing a blame game, but I would like to suggest that there is possibly something unique with our HK xooms?? Mine was sourced direct from a genuine Motorola source, so I know its not a case of fakes but maybe the Chinese/hk xoom is different in some way....damn communism. Could there maybe be differences in algorithms, encryption etc due to their restrictiveness in china??
I am using SSH and investigating other methods of getting into the 'drive' so will keep updated,.
Sent from my MZ601 using XDA Premium App

I don't think this problem deals with encryption or so.
As far as I remember, the stock HK version (build H.6.1-17-CN-40) had more features that the actual 3.1 OTA updated. Specially I connected an USB pen and it directly readed it!.
So, what I think is that Moto just released a more avanced version in HK. As it is factory loaded directly in 3.1, probably the size of mtdblock5 has been adjusted to fit with this new release and that's the reason because it cannot load userdata from the downloadable 3.0's from the moto site. I'm not slilled in android but surely this userdata has information used by the system to map memory or to handle storage.
So, I will continue to look for an image that fits, or looking the way to adjust the partition sizes.
Hope a lote we can find a fix for this. I hope this exactli 28 Gb!

ritter_xoom said:
I don't think this problem deals with encryption or so.
As far as I remember, the stock HK version (build H.6.1-17-CN-40) had more features that the actual 3.1 OTA updated. Specially I connected an USB pen and it directly readed it!.
So, what I think is that Moto just released a more avanced version in HK. As it is factory loaded directly in 3.1, probably the size of mtdblock5 has been adjusted to fit with this new release and that's the reason because it cannot load userdata from the downloadable 3.0's from the moto site. I'm not slilled in android but surely this userdata has information used by the system to map memory or to handle storage.
So, I will continue to look for an image that fits, or looking the way to adjust the partition sizes.
Hope a lote we can find a fix for this. I hope this exactli 28 Gb!
Click to expand...
Click to collapse
I think you could be right!! It also seems out HK/CN xooms are the only ones without an image on the dev motor site, :-( I am trying to find stock images for our xooms to se if that was the issue....seems as though we had the same thought.
Sent from my MZ601 using XDA Premium App

Right, so nothing?

Right ladies, its is true I got mine from the Motowprd in HK now i'm in Kuwait and been mucking about with the xoom. Anyway, turns out you "can" mount the darn thing in buntu and win7 but whats the point?, it still shows 4.11 GB.
So unless we get a tool command line or not, to partition the drive and format it in the right filesystem, we are - how do i put it?....****ED!

The same problem
I met the same problem. There's something wrong with HK-version MZ601. After rooted , internal memory became 4.2G instead of 28G.

Asus Transformer Infinity just lost lead CM developper

This is a very sad sad day!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm sure someone else will pick it up soon. Some of his post doesn't make sense though. If you can't OTA, the unlock tool definitely won't work. These issues are one in the same. Also if he tried to unlock when the servers were not responding, that would cause it to fail. And the I/O issues are completely software related and not even present on the .26 firmware.
Edit: my tab has no build issues and received OTAs from Asus as well as properly unlocked the bootloader on the first try. Guess I'm lucky... it sounds like he's blowing these problems way out of proportion when his trouble could be fixed by an RMA. I mean he could at least try a replacement before scrapping the whole thing just cause his first one wasn't perfect.

P!X3L said:
I'm sure someone else will pick it up soon. Some of his post doesn't make sense though. If you can't OTA, the unlock tool definitely won't work. These issues are one in the same. Also if he tried to unlock when the servers were not responding, that would cause it to fail. And the I/O issues are completely software related and not even present on the .26 firmware.
Edit: my tab has no build issues and received OTAs from Asus as well as properly unlocked the bootloader on the first try. Guess I'm lucky... it sounds like he's blowing these problems way out of proportion when his trouble could be fixed by an RMA. I mean he could at least try a replacement before scrapping the whole thing just cause his first one wasn't perfect.
Click to expand...
Click to collapse
I certainly nevet got any ota updates.

P!X3L said:
I'm sure someone else will pick it up soon. Some of his post doesn't make sense though. If you can't OTA, the unlock tool definitely won't work. These issues are one in the same. Also if he tried to unlock when the servers were not responding, that would cause it to fail. And the I/O issues are completely software related and not even present on the .26 firmware.
Edit: my tab has no build issues and received OTAs from Asus as well as properly unlocked the bootloader on the first try. Guess I'm lucky... it sounds like he's blowing these problems way out of proportion when his trouble could be fixed by an RMA. I mean he could at least try a replacement before scrapping the whole thing just cause his first one wasn't perfect.
Click to expand...
Click to collapse
My first tablet has worked, too. The ones my friends got got all their update within minutes after the first start. There are always people with tough luck, and servers can be busy, no need to cry because of that.

bird11 said:
I certainly nevet got any ota updates.
Click to expand...
Click to collapse
Agreed - neither did I. When you read through all the different posts for the Prime, T300 and now T700, the same problem is there for all of them. Some people can unlock/OTA, others can't. It's a real crap shoot. And apparently Asus' response is to 'RMA' or 'Reset'. That's it - no acknowledgement that there are issues going on with about half of the units they're sending out to people. Although I absolutely love the Infinity, it may be going back as I approach the 30-day after purchase mark because of these problems.

paysen said:
My first tablet has worked, too. The ones my friends got got all their update within minutes after the first start. There are always people with tough luck, and servers can be busy, no need to cry because of that.
Click to expand...
Click to collapse
I wonder if you would say the same if your tablet wouldn't update after months of waiting for the unlock to wait.People owning the older version of transformer still waiting for their to unlock while the lucky ones are using CM 10 rom.
They paid the damn thing with the same money like you... or maybe your money is better than their money?I'm sure not.
That being sad i do feel for these unlucky folks even if my TF700 unlocked just fine,so please before you do post like this wait a moment, try to put you in their situation and then tell us how you feel.

I don't want to protect Asus but it is clearly stated that you lose OTA when unlocking.
Also it is no where stated that you will get a device that you will be able to unlock. As sad as it is.
Although I did not unlock and have not received OTA as well.
But I couldn't wait too long
The I/O that is an issue but .26 shows improvements and this just a few weeks after the release.
So let's see what they can do with the jelly bean release.
Still sad to hear that he turned his back.

That's incredibly disappointing. Having seen his work on the Nook and the Touchpad, we lost an amazing dev today. I really hope Asus gets their act together with this unlocking, because they're really starting to irreparably damage their reputation.

Well, i guess no one can be perfect. I have always had Samsung products, phones and tablets and their work for the dev community is amazing, the phone is always so easy to root, the tools are always available for the community to build on, but the updates suck big time. The Galaxy S 2 LTE had some pretty annoying issues, a lot of them and they were just never patched. But on the other hand, asus can update their hardware 2-3 times a month but they are crap when they come to helping the community. On one hand, i rather have a periodical official software update then custom roms, but i know most people think the opposite.

There will likely be others. I really enjoyed Team EOS and Wookies work on the Prime and hopefully they come on over. Not sure why he didn't try to return his device and keep trying but I guess he was just fed up with waiting.
Sent from my Galaxy Nexus using Tapatalk 2

Pretoriano80 said:
I wonder if you would say the same if your tablet wouldn't update after months of waiting for the unlock to wait.People owning the older version of transformer still waiting for their to unlock while the lucky ones are using CM 10 rom.
They paid the damn thing with the same money like you... or maybe your money is better than their money?I'm sure not.
That being sad i do feel for these unlucky folks even if my TF700 unlocked just fine,so please before you do post like this wait a moment, try to put you in their situation and then tell us how you feel.
Click to expand...
Click to collapse
I wouldn't wait months as its no problem to exchange your tablet for a new one.

paysen said:
I wouldn't wait months as its no problem to exchange your tablet for a new one.
Click to expand...
Click to collapse
Yeah, like i've said in other posts sometimes it looks like everyone live in the "electronics heaven" where you can exchange and get refunds without any reason and everytime you want. Asus doesn't consider this as an issue so is not sure you can ask a RMA for it or even worse could tell you to not cry about because unlocking is not an official feature so there's no issue.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Limited Electronics Heaven
Well, it seems that some of us are stuck with just "a little slice of heaven" in that we can rma and such but getting ahold of the electronics themselves can be discouraging. Took me a week to get my infinity from best buy because the local store doesn't have them in stock. So for me to do an exchange would be quite a long turn-around time. For others that are stuck with buying from a different state or country, the task can be even more daunting.
On a side note, I'm still on .21 with no OTAs available. It makes me wonder if I should root and unlock the bootloader just to verify that I have the "right kind" of TF700. What do you all think? Should this be part of the initial tests I should do to verify my tab?

alienedd said:
Well, it seems that some of us are stuck with just "a little slice of heaven" in that we can rma and such but getting ahold of the electronics themselves can be discouraging. Took me a week to get my infinity from best buy because the local store doesn't have them in stock. So for me to do an exchange would be quite a long turn-around time. For others that are stuck with buying from a different state or country, the task can be even more daunting.
On a side note, I'm still on .21 with no OTAs available. It makes me wonder if I should root and unlock the bootloader just to verify that I have the "right kind" of TF700. What do you all think? Should this be part of the initial tests I should do to verify my tab?
Click to expand...
Click to collapse
Well. i rooted mine the same day i bought it and you can do it without to much to worry about (i'm quite sure that OTA issue has nothing to do with rooting) because you can always unroot.
Unlocking the device will make you loose the warranty (i unlocked mine yesterday) so at least make sure that you checked your tablet for good (headphones, Bluetooth, HDMI connection., all the hw part) before you do it.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Although I understand the inconvenience of not having your device at hand for two or three weeks while it is turning around in RMA, I would like to stress that it is not a dialysis machine -- it is in no way a life-saving or system-critical device, it is a luxury item. All devices have the potency to break down, pretty much none of them is perfect and if it is, it soon will no longer be.
No offense meant, really, but if returning your device because it is faulty is too much, I do not think the initial love for the TF700 went very deeply inside.
---------- Post added at 03:31 AM ---------- Previous post was at 03:28 AM ----------
Pretoriano80 said:
Well. i rooted mine the same day i bought it and you can do it without to much to worry about (i'm quite sure that OTA issue has nothing to do with rooting) because you can always unroot.
Unlocking the device will make you loose the warranty (i unlocked mine yesterday) so at least make sure that you checked your tablet for good (headphones, Bluetooth, HDMI connection., all the hw part) before you do it.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
If so far you haven't received any OTA (neither .22, nor .26) I'd almost wager a finger that you will not be able to unlock anyway. That means I'd opt for an RMA, if at all possible.

My TF700T works perfectly other than the OTA issue. I for one am not going to RMA this thing to Asus for the OTA issue when every thing and I do mean every thing else works great. I have downloaded both .22 and .26 update files from the Asus service site and did a manual miniSD card upgrade. I am hoping that the Jelly Bean release will clear this issue up.
Maybe this is an issue that 'Gary' the Asus guy could address for us if hes watching!

Pretoriano80 said:
Well. i rooted mine the same day i bought it and you can do it without to much to worry about (i'm quite sure that OTA issue has nothing to do with rooting) because you can always unroot.
Unlocking the device will make you loose the warranty (i unlocked mine yesterday) so at least make sure that you checked your tablet for good (headphones, Bluetooth, HDMI connection., all the hw part) before you do it.
Click to expand...
Click to collapse
I definitely intend to do exactly that. Kick the tires, check the AC, make sure the toast comes out golden brown, and that the coffee has that rich texture. Kind of like fishing - you wouldn't keep an unhealthy one even if it was huge, though you'd still reminisce about how you held it in your hands for a time no matter how brief.
MartyHulskemper said:
Although I understand the inconvenience of not having your device at hand for two or three weeks while it is turning around in RMA, I would like to stress that it is not a dialysis machine -- it is in no way a life-saving or system-critical device, it is a luxury item. All devices have the potency to break down, pretty much none of them is perfect and if it is, it soon will no longer be.
No offense meant, really, but if returning your device because it is faulty is too much, I do not think the initial love for the TF700 went very deeply inside.
Click to expand...
Click to collapse
No probs as I get exactly what you are meaning :good:. However, I have lived in a few countries and see it all the time when someone buys such a luxury item in a foreign country only to find out it is lacking after returning home... The most extreme case I saw was someone that bought a Verizon phone then wondered why it didn't work in South America, not knowing the difference between GSM and CDMA. I would just like to make sure that the device can be made functional in all aspects regardless of whether ASUS chooses not to support it further and to where I am.
In any case, if the TF700 doesn't perform as expected (hardware-wise), then I can always do something else. "Go big or go netbook" I told myself. I'm really hoping that I stay at "Big" :fingers-crossed:.

Pretoriano80 said:
Yeah, like i've said in other posts sometimes it looks like everyone live in the "electronics heaven" where you can exchange and get refunds without any reason and everytime you want. Asus doesn't consider this as an issue so is not sure you can ask a RMA for it or even worse could tell you to not cry about because unlocking is not an official feature so there's no issue.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
It's no "electronics heaven". Just a law in germany you don't have:
"Since you cannot examine the goods before the purchase, you have after the remote paragraph law the right to return the received goods without indication of reasons within two weeks by return of them." (only if you buy it @ internet shops or per telephone)
Maybe unlocking is no official feature, but getting updates or registering your device is one. And if Asus tries to be awkward - there is maybe another issue you recognize, unfrequently reboots or something like that :angel:

paysen said:
It's no "electronics heaven". Just a law in germany you don't have:
"Since you cannot examine the goods before the purchase, you have after the remote paragraph law the right to return the received goods without indication of reasons within two weeks by return of them." (only if you buy it @ internet shops or per telephone)
Maybe unlocking is no official feature, but getting updates or registering your device is one. And if Asus tries to be awkward - there is maybe another issue you recognize, unfrequently reboots or something like that :angel:
Click to expand...
Click to collapse
Yes we also have that kind of law here and some big electronics retailer (Mediaworld) follow that law even for products bought directly in-store (you have 8 labour days to return it and get another product in the same price range but you will never get your money back) but with small retailers you better hope to have a good product or else it will become a neverending story.
Always had a great respect for Germany laws and always heard giod things abour warranty so thumb up.

Now that the Bootloader Unlock tool is working for all Infinity devices lets try to convince the official CM10 dev to come back into the fold. You can find the original post here
https://plus.google.com/114860410994043943287/posts/ixpfnNgpmTh

Speaking with Asus about JB issues +advice from them

Recently, I contacted Asus about the issues that we have seen since the JB update. Since I support a number of these tablets for clients, I have had lots of backlash since the update. I emailed Tien and Gary about what advice they could provide when dealing with these units. I have included the last response that I got from him that addresses factory resets and cold booting, as well as a method he recommends for installing software after a reset:
"Hi Jordan,
There are people out there who believe doing multiple factory resets works, but I do not think so. Once a device has been reset, there is no user data left on there. Everything is back to factory. There should be no way data can be conflicting. Restoring a device that has nothing on it in the first place would not make a difference. However, multiple cold-boots do seem to help. Start with a factory reset and then as you reload your data back on (apps, media, e-mail, ect), cold-boot after something has been loaded on. For example, once and app or 2 has been reloaded, cold-boot the device before you load another app. This is the same for new app s being downloaded also. You want to keep the cache clear as much as possible.
I understand that a firmware update, or even news of a firmware update would be a lot easier, but again, I apologize as I do not have that kind of information. HQ releases the updates, and for the most part, they are pretty tight-lipped about them.
Sending in a bunch of units might not the best solution - you are right. I would try cold-boots u for now. JB is still new and there are definitely some things that need to be worked out with it on the TF700. I would give them some more time to deliver a solution.
Tien"
I have yet to try this process on my tab, maybe someone will beat me to it. Hope this information helps someone out there.
The issues that I reported are:
1. Graphics related issues that show as a flicker of the top 1/3rd (sometimes the entire) screen while in landscape, also a line of black pixels flashes for a moment on that same part of the screen. I have seen this in many apps at this point including the stock browser and in the XDA developers premium app. It seems unrelated to the application since I have seen reports of it on the desktop. (this is driving our users crazy- need a fix quickly!)
2. Backspace key is not respected in many applications if the asus keyboard is enabled. There are lots of examples on xda but this worked in ICS and now, does not.
3. The auto screen dimmer does not work properly and will dim, and not increase brightness when tapped. It also seems much more distracting and does not dim as gracefully as before(I know it can be disabled).
4. When docked, a Bluetooth keyboard that is paired with the device, will not function. A usb keyboard will work, but it is odd that Bluetooth keyboards will allow no input at all while docked.
5. Crash of the device with a white screen- have seen this 3 times.
6. Wifi direct removal is a major disappointment as many users had a need for this functionality.

This is good information, thanks. The only real change I have witness that's a problem is Google navigation freezing or rebooting the TF700 during trips longer than a few minutes. Intermittent problem but it has happened on three separate trips.

I'm getting the occasional black lit screen crash/freeze

jordanmw said:
6. Wifi direct removal is a major disappointment as many users had a need for this functionality.
Click to expand...
Click to collapse
Not sure where you are seeing this. Wifi Direct was not removed with JB. In fact, I noticed it performs much better.
The option for sending a file via WiFi direct is avialable under the share options. If you are looking for it directly under the settings menu, it was just moved to a different place (not an ASUS thing.....it was moved by Google). Go under Settings -> Wifi and click on the menu button to access it (3 dots in the lower right hand corner).

Artimis said:
Not sure where you are seeing this. Wifi Direct was not removed with JB. In fact, I noticed it performs much better.
The option for sending a file via WiFi direct is avialable under the share options. If you are looking for it directly under the settings menu, it was just moved to a different place (not an ASUS thing.....it was moved by Google). Go under Settings -> Wifi and click on the menu button to access it (3 dots in the lower right hand corner).
Click to expand...
Click to collapse
Thanks for that! I had a couple of users who complained that it was not there. I emailed them to let them know it how to access it, they appreciate it.
--Would have been nice if Tien had mentioned it-- ya think?
Never even tried that feature and assumed it was removed since Asus listed it as a feature that would be removed with the update. I get it now.... they removed their custom support of it in favor of the stock android setup.

Kind of funny that an update announcement was posted today, I have been back and forth with them quite a bit in the last couple of weeks and the last email I sent to Tien and Gary said this:
"Unless you have a newer firmware with some of these issues resolved, I am not
sure how offering to send them to you will do any good....
Please let Gary know that this is effecting companies that have purchased over 50 of
these tablets at a time. We need resolution!"
Maybe I got his attention. I have to support these tablets, and so does Asus, they are an international company that is trying desperately to be THE go to hardware partner for cutting edge tech. Partnerships with the big G and M$ are evidence of that. I hope they realize that this is a defining year for them, either they will get their support in order or they will fold under the pressure of the added user base.

jordanmw said:
The issues that I reported are:
1. Graphics related issues that show as a flicker of the top 1/3rd (sometimes the entire) screen while in landscape, also a line of black pixels flashes for a moment on that same part of the screen. I have seen this in many apps at this point including the stock browser and in the XDA developers premium app. It seems unrelated to the application since I have seen reports of it on the desktop. (this is driving our users crazy- need a fix quickly!)
2. Backspace key is not respected in many applications if the asus keyboard is enabled. There are lots of examples on xda but this worked in ICS and now, does not.
3. The auto screen dimmer does not work properly and will dim, and not increase brightness when tapped. It also seems much more distracting and does not dim as gracefully as before(I know it can be disabled).
4. When docked, a Bluetooth keyboard that is paired with the device, will not function. A usb keyboard will work, but it is odd that Bluetooth keyboards will allow no input at all while docked.
5. Crash of the device with a white screen- have seen this 3 times.
6. Wifi direct removal is a major disappointment as many users had a need for this functionality.
Click to expand...
Click to collapse
On top of these i have:
1. Random reboots,
2. Wifi drops out and fails to reconnect or slows down to be unusable state

Well if looks like some of the issues have been resolved but some still remain. Has anyone had time to try the method tien suggested in my op? Unfortunately i have not gotten time.
Sent from my ASUS Transformer Pad TF700T using xda premium

jordanmw said:
Well if looks like some of the issues have been resolved but some still remain. Has anyone had time to try the method tien suggested in my op? Unfortunately i have not gotten time.
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
I also don't have the time to try, but I have my own share of doubt regarding these suggestion. Cold-booting my device after loading one or 2 apps is just too much of a hassle and I doubt that it provides any practical benefit. My friend's Nexus 7 haven't been turned off for weeks and I don't see any slow down or problems. The same thing can be said about my phone as well. I know they are different devices, but I don't think Google designs Android in such a way that you need to restart your device every time you install a new app.
Overall, I believe all of the problems above can only be fixed with OTA updates, and no amount of cold-boot or factory reset can fix it. I might be wrong, but it is just my opinion.
Anyway, thanks for sharing. Maybe someone will benefit from this discussion.

Since nobody has tried this method, I guess I will give it a shot today. Of course I have major doubts that this will actually work but if Tien said that there is some benefit, I have to at least try it. He is one of the only reps at asus that has ever given us any real help with the TF series.

huy_lonewolf said:
I also don't have the time to try, but I have my own share of doubt regarding these suggestion. Cold-booting my device after loading one or 2 apps is just too much of a hassle and I doubt that it provides any practical benefit. My friend's Nexus 7 haven't been turned off for weeks and I don't see any slow down or problems. The same thing can be said about my phone as well. I know they are different devices, but I don't think Google designs Android in such a way that you need to restart your device every time you install a new app.
Overall, I believe all of the problems above can only be fixed with OTA updates, and no amount of cold-boot or factory reset can fix it. I might be wrong, but it is just my opinion.
Anyway, thanks for sharing. Maybe someone will benefit from this discussion.
Click to expand...
Click to collapse
Seriously? You think cold booting is a hassle? My friend it takes an extra second of hold the power down button when turning your tablet on. Come on stop lazy. Also if the op isn't blowing smoke, then these suggestions are directly from asus, so why would they lie? I personally have seen a huge benefit from cold booting after a couple of app installations. I do it anyways because i do like to keep my cache clear.
Sent from my ASUS Transformer Pad TF700T

pierrekid said:
Seriously? You think cold booting is a hassle? My friend it takes an extra second of hold the power down button when turning your tablet on. Come on stop lazy.
Click to expand...
Click to collapse
If a computer requires regular cold booting to work properly, it is defective. A Linux-based system should be able to reach uptimes measured in years (theoretically, if no updates were required).

pierrekid said:
Seriously? You think cold booting is a hassle? My friend it takes an extra second of hold the power down button when turning your tablet on. Come on stop lazy. Also if the op isn't blowing smoke, then these suggestions are directly from asus, so why would they lie? I personally have seen a huge benefit from cold booting after a couple of app installations. I do it anyways because i do like to keep my cache clear.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
Seriously? If you buy this expensive gadget you shouldn't be doing extra hussle like cold booting after installing an app or two. It should work without. This is the only Android device with this kind of problems. Not sure if this is some kind of memory leak or what is going on. Still its interesting that for example on Galaxy S 3 even beta roms work better than these official ones from Asus.
Asus designs beautiful units, then manufactures them with horrible QC and finally don't seem to know much about software optimizing.

Finally got around to trying this process.... Maybe I installed too many apps at one time since after the first few installs, i was doing more than 2 in some cases. No difference doing this method over factory reset. I am going to contact them again today with feedback from the process and latest update.
Sent from my ASUS Transformer Pad TF700T using xda premium

jordanmw said:
Finally got around to trying this process.... Maybe I installed too many apps at one time since after the first few installs, i was doing more than 2 in some cases. No difference doing this method over factory reset. I am going to contact them again today with feedback from the process and latest update.
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
I can't say that I'm surprised, but I really appreciate your effort. Thanks for sharing.

To be honest the response seemed like a "SYA" response that was so far fetched and so much hassle you wouldn't bother to try it and they could push your issues aside.
I find it funny that they claim "Jellybean is still new..." when it has been out in the wild since around July or earlier. That seems like plenty of time to get the software optimized for your flagship device(s). If you want my honest opinion, the TF700 was placed on the back burner a little bit because of the Nexus 7 that Asus and Google partnered up for. That took priority but I do find it odd that the hardware in the Nexus 7 almost mirrors the TF700, yet the Nexus 7 does not exhibit the same odd behavior or issues we are experiencing (some of us anyway) on the TF700.

I must be one of the blessed ones because I'm not experiencing all the issues that are mentioned here. I had the hardware issue of screen flex and bent adapter port, but other than that and getting a replacement I'm pleased. I actually considered getting a galaxy note 10.1, but just knew I wouldn't be satisfied with the display. The screen is the major aspect of a tablet and you really can't find a replacement at this time for the full HD of the tf 700. I have noticed that my pad is running really well after the last update and I'm really happy I didn't go with the note. I'm totally stock and not rooted. I may root one day if needed and there is a method that doesn't void the warranty by using the bootloader (if there is please let me know...I'd love to use titanium backup with root).
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

I upgraded to JB and I can not connect to my galaxy s2 wifi hotspot. Any idea of solution..?
Thanks for your answers.

KaliS-Pugilist said:
I must be one of the blessed ones because I'm not experiencing all the issues that are mentioned here. I had the hardware issue of screen flex and bent adapter port, but other than that and getting a replacement I'm pleased. I actually considered getting a galaxy note 10.1, but just knew I wouldn't be satisfied with the display. The screen is the major aspect of a tablet and you really can't find a replacement at this time for the full HD of the tf 700. I have noticed that my pad is running really well after the last update and I'm really happy I didn't go with the note. I'm totally stock and not rooted. I may root one day if needed and there is a method that doesn't void the warranty by using the bootloader (if there is please let me know...I'd love to use titanium backup with root).
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Root does not require you to unlock the boot loader.

KaliS-Pugilist said:
I'm totally stock and not rooted. I may root one day if needed and there is a method that doesn't void the warranty by using the bootloader (if there is please let me know...I'd love to use titanium backup with root).
Click to expand...
Click to collapse
ICS can be rooted easily even with the locked bootloader. If you are already on JB, follow the guide to downgrade to ICS 9.x.x.30, root using the debugfs method, use OTA Rootkeeper, and then apply the OTA to JB.

Understanding OTA functionality

Hi all!
Before I phrase my question I should inform that I have an ongoing issue with Asus regarding FOTA not working after Asus replaced my MB, and rear camera functionality. I'm on the TF300T, bought july 2012, completely stock, no root, no unlocked bootloader. I'm pretty much a newbie and do not wan't to lose warranty by doing things I don't understand .
As stated above, I have an ongoing issue with Asus; my MB and rear camera were replaced in connection with the third RMA (rear camera issue). The tablet I handed in had the ww 10.4.2.13 version. All updates from ICS have been performed via OTA and have worked flawlessly. When I got the tablet back, I discovered that it had the ww 10.4.2.9, which I experience as buggy and not very satisfying (in addition - the camera issue had not neen resolved). Fine, I'll just update OTA, I thought, but my tablet states that no update is available. I have tried this over a period of weeks now - no update is available. Actually, the tablet has been handed in to Asus Holland for a fourth RMA and they now claim that no errors exist.
So, what could be the explanation to the fact that I don't see any updates? My internet connection is working, all default settings after numerous factory resets and cold boots, no google account issues, other brand equipment in the household works fine. I know that replacing MB also means different MAC address. Unfortunately, I didn't write down the old MAC address so I can't really compare. Could MAC be the issue; meaning that maybe Asus failed to sync/pair the new MAC with serial# or other certain HW ids, and that there somehow needs to be a match between these?
I'd appreciate any input on the issue as I need to understand certain things before having further discussions with Asus.
Rgds,
sten_amund

It probably not your device since my 3 day old tf can't get ota update either. I am on the same kernel version and getting the same error message as you that no update exist. Which is false. So I went to Asus site and download the latest and manually installed it. Big difference in performance.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

First Time Infinity Owner

Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!

jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
Hi, and welcome to the community!
First things first: check the unit thoroughly for the known issues (screen bleed, loose screen bonding, etc. Several threads in here concerning the most frequent issues.
1) If you happen to get a pre-.30 firmware (which is unlikely at this point in time), install Nvflash first and pull the backups. That might save you form not only severe headaches but a pretty stack of dollars too, if the excrement hits the ventilator.
2) Try and see if the unlock tool works. In a relatively large percentage of 700s, it doesn't. That would solve your problem instantly. (You can then proceed to update to the latest stock ROM, but no custom ROM'in' for you then. That << smiley is actually very mean, because that would be some major suck.)
3) Whatever you do, ONLY use the most recent versions of whatever recovery has your preference. Also update the bootloader to the version your ROM of choice requires!
4) Unless you have extensive experience with flashing and ROMs in general, it might be prudent to pick a stock-based ROM (i.e. CROMI-X). If you comfortable with the odd bug here and there, you might try an AOSP/AOKP/CM-based ROM and see if they fit your bill.
CROMI-X has a great OP with all the updates to bootloader and such you'll need.
5) Don't do anything if you're not sure when starting out. The 700 is not particularly easy to brick, but it is relatively hard to fix in some cases that on other devices (Samsung's comes to mind) would just mean reflashing some stuff (in Odin/Heimdall).
Have fun!
Marty

MartyHulskemper said:
Hi, and welcome to the community!
2) Try and see if the unlock tool works. In a relatively large percentage of 700s, it doesn't. That would solve your problem instantly. (You can then proceed to update to the latest stock ROM, but no custom ROM'in' for you then. That << smiley is actually very mean, because that would be some major suck.)
Marty
Click to expand...
Click to collapse
Hey mate,
Thanks for the info
With the unlock tool, has anyone reported any issues from trying to use it? If it doesnt work, will it just say it didnt work? I cant brick from just using the tool can I?
Cheers!

jonlad1 said:
Hey mate,
Thanks for the info
With the unlock tool, has anyone reported any issues from trying to use it? If it doesnt work, will it just say it didnt work? I cant brick from just using the tool can I?
Cheers!
Click to expand...
Click to collapse
If it doesn't work it just gives some error message. I haven't heard of anyone bricking because the unlock tool failed, so you should be safe there. As far as I'm aware the only issue you'll have from the unlock tool not working is just the fact that you're not going to be unlocked lol.
Sent from my ADR6425LVW using XDA Premium.

jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
I'm with Martin on this:
Until you are sure that your tab is not a lemon with major hardware issues I would not unlock it.
You can root it and start playing around with some more advanced settings in the meantime. Wouldn't it really suck if you unlocked and a day or week later the digitizer would go bad? Asus could say: Sorry, pal - you're unlocked, you're out of warranty.
They have repaired even unlocked devices under warranty, but you can't count on it. And in some cases the repaired tablet came back with a permanently locked bootloader....
So give it a few weeks, in the meantime start reading the relevant thread of your favorite custom ROM(s) to get a feel for them, and familiarize yourself with the process and lingo of flashing.
You could start here:
http://forum.xda-developers.com/showthread.php?t=2204100
I feel a little sheepish since we basically hijacked the original thread, but since the original topic is pretty much outdated and not active anymore, I guess it is ok. I kinda walked a user through the whole process of rooting/flashing a custom rom etc.
Start with post #191. In #193 I wrote a step-by-step guide which HeartWare42 fleshed out even more in post #220.
Note anything you don't understand and Google it.
Read 3 times, ask twice, flash once )

berndblb said:
I'm with Martin on this:
Until you are sure that your tab is not a lemon with major hardware issues I would not unlock it.
You can root it and start playing around with some more advanced settings in the meantime. Wouldn't it really suck if you unlocked and a day or week later the digitizer would go bad? Asus could say: Sorry, pal - you're unlocked, you're out of warranty.
They have repaired even unlocked devices under warranty, but you can't count on it. And in some cases the repaired tablet came back with a permanently locked bootloader....
So give it a few weeks, in the meantime start reading the relevant thread of your favorite custom ROM(s) to get a feel for them, and familiarize yourself with the process and lingo of flashing.
You could start here:
http://forum.xda-developers.com/showthread.php?t=2204100
I feel a little sheepish since we basically hijacked the original thread, but since the original topic is pretty much outdated and not active anymore, I guess it is ok. I kinda walked a user through the whole process of rooting/flashing a custom rom etc.
Start with post #191. In #193 I wrote a step-by-step guide which HeartWare42 fleshed out even more in post #220.
Note anything you don't understand and Google it.
Read 3 times, ask twice, flash once )
Click to expand...
Click to collapse
Thanks for the info guys, I'll check the hardware first!

jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
Hi there,
When I had bought my tf700 I did'nt have a clue what custom rom is.
I was totally naive and ignorant as to Android technology.
I was disappointed with my TF700 performance and lived with it for a couple of months.
Afterwards, I searched the internet until I have found this marvellous forum (which attracts OCDs like the fire attracts moth).
I read and read and read and read, and read more and asked the fine users of this fine forum if I got it all right,
and then one springy night on the end of March 2013, something happened.
A magic...
"I took the red pill" , unlocked my TF700, pushed TWRP and flashed CROMI.
Everything went super.
Ever since then I follow Sbdags CROMI-X thread and keep update my firmware.
Just to remind you - I am not a Computer wizard, my occupation has got almost nothing to do with electronics and I am not a kid (actually I am 37 with many obligations like family and work - so my spare time is scarce).
And here I am - master of my TF700!
So - everything is possible!
And if you follow instructions and restrict yourself to the right method - you can be rest assured you won't brick your device.
Actually It's like cooking: you should find a good recipe and act accordingly.
Cheers

So I finally got it delivered today
It looks good, no damage, screen bleed that i can see. Screen seems fine.
Its running JRO3C.US_epad-10.4.4.25-20121228
JB 4.1.1
I'm not really sure where to go from here - should I wait a few days or just unlock and put CROMI-X on now?
Speed of the system isnt bad, transitions seem a bit slow, havent really installed a bunch of apps yet...

jonlad1 said:
So I finally got it delivered today
It looks good, no damage, screen bleed that i can see. Screen seems fine.
Its running JRO3C.US_epad-10.4.4.25-20121228
JB 4.1.1
I'm not really sure where to go from here - should I wait a few days or just unlock and put CROMI-X on now?
Speed of the system isnt bad, transitions seem a bit slow, havent really installed a bunch of apps yet...
Click to expand...
Click to collapse
You are itching to do it, right?
I can tell, you can hardly wait....
Well, the rational next step would be to wait a week, or two, or however long you can stand it, and then unlock etc.
But where's the fun in rational, right?
Well, while you decide - why not upgrade it to JB 4.2.1? Saves you a bootloader flash and clean install later....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

berndblb said:
You are itching to do it, right?
I can tell, you can hardly wait....
Well, the rational next step would be to wait a week, or two, or however long you can stand it, and then unlock etc.
But where's the fun in rational, right?
Well, while you decide - why not upgrade it to JB 4.2.1? Saves you a bootloader flash and clean install later....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Is 4.2.1 worth the update? I read that 4.2.1 caused a few issues for some people....
I probably will just flash it It feels like it should run quicker, take Maps for example. seems REALLY laggy but on my N7 it was fine?

jonlad1 said:
Is 4.2.1 worth the update? I read that 4.2.1 caused a few issues for some people....
I probably will just flash it It feels like it should run quicker, take Maps for example. seems REALLY laggy but on my N7 it was fine?
Click to expand...
Click to collapse
JB 4.2 was better for most people, others had issues with Bluetooth tethering and some other stuff...
The reason I recommend you upgrade to stock 4.2 is mainly that then you automatically would have the correct bootloader on our tablet.
For Cromi-X you need the 4.2 bootloader. If you are on 4.1 you have to flash it before you flash Cromi-X, if you are already on 4.2 you're good to go. One less thing that could go wrong....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

berndblb said:
JB 4.2 was better for most people, others had issues with Bluetooth tethering and some other stuff...
The reason I recommend you upgrade to stock 4.2 is mainly that then you automatically would have the correct bootloader on our tablet.
For Cromi-X you need the 4.2 bootloader. If you are on 4.1 you have to flash it before you flash Cromi-X, if you are already on 4.2 you're good to go. One less thing that could go wrong....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
That makes sense, I'll get that updated tonight, cheers
Does CROMIx improve the laggy transitions/Maps/Browser?

jonlad1 said:
That makes sense, I'll get that updated tonight, cheers
Does CROMIx improve the laggy transitions/Maps/Browser?
Click to expand...
Click to collapse
It improves e-v-e-r-y-t-h-i-n-g
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

berndblb said:
It improves e-v-e-r-y-t-h-i-n-g
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
SOLD!

jonlad1 said:
SOLD!
Click to expand...
Click to collapse
You will not be disappointed. Welcome to the OCFD corner.
Now that I think of it: http://hope4ocd.com/checklist.php is missing the "Needing the have the latest and greatest x.x.xxxxx version of your ROM", or "Needing to flash at least 5 ROMs a week". Can we petition that?

Hmm, I just tried to update via OTA and it said my system is up to date? I'm on 4.1.1?
EDIT - ok, updated manually. Trying to use the unlock tool but getting "Unkown Error. This may be a connection issue" - is that what'll happen if it's not gonna work for me?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

You could have got the Nook HD+ 32GB for $180 and dead easy to root and put CM 10.1 or Carbon on it and no concern of bricking it. Stock 2.1 on the HD+ is barely ok (very barely), but CM 10.1 rocks.
A little smaller tablet, but same great display resolution. I use this more than my iPad 4 now, which is both a compliment to the HD+ and an insult to how much I paid for the iPad 4.

jonlad1 said:
Hmm, I just tried to update via OTA and it said my system is up to date? I'm on 4.1.1?
EDIT - ok, updated manually. Trying to use the unlock tool but getting "Unkown Error. This may be a connection issue" - is that what'll happen if it's not gonna work for me?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Personally, when I had this problem, I just tried to run the app every day for a week oe so and it eventually works, but others have had to use tricks. Use the search for unlock, you will find several ideas about fixing it.