Database Info

Unlock TFI post JB update?

Looks like ASUS needs to update the unlock tool to work on JB?
Clearly states on their site that the unlock is for ICS only.
I of course had to try it for fun (I like punishment?) and surely it failed and luckily didn't leave my tablet any worse for wear.
Are a lot of you guys unlocked? What are the greatest benefits you've found from doing so?
Thanks!

Follow this link, or search others, and downgrade to ICS to unlock: http://forum.xda-developers.com/showthread.php?t=1915598 . If you unlock, you will void your warranty, and can only manually update or use a custom Rom.

amenic said:
Looks like ASUS needs to update the unlock tool to work on JB?
Clearly states on their site that the unlock is for ICS only.
I of course had to try it for fun (I like punishment?) and surely it failed and luckily didn't leave my tablet any worse for wear.
Are a lot of you guys unlocked? What are the greatest benefits you've found from doing so?
Thanks!
Click to expand...
Click to collapse
I'd say the majority of general community users are locked, but they probably just buy a device and would never tinker with it. That's not the inclination of the average XDA gadgeteer so I'd wager that most of us in here are either unlocked, or have tried to unlock but failed.
The main goals of unlocking are threefold:
1) installing a custom recovery (thus enabling Nandroid backups)
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
3) installing custom ROMs
In fact, the general drive to unlock is in point 3, for if you do not plan on installing a custom ROM on your device, there's far less rational incentive to make a Nandroid backup, and you probably would not need the added security of Nvflash -- ASUS will take care of a brick in that case, I guess. So..... the main question is: to customize or not customize?

MartyHulskemper said:
I'd say the majority of general community users are locked, but they probably just buy a device and would never tinker with it. That's not the inclination of the average XDA gadgeteer so I'd wager that most of us in here are either unlocked, or have tried to unlock but failed.
The main goals of unlocking are threefold:
1) installing a custom recovery (thus enabling Nandroid backups)
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
3) installing custom ROMs
In fact, the general drive to unlock is in point 3, for if you do not plan on installing a custom ROM on your device, there's far less rational incentive to make a Nandroid backup, and you probably would not need the added security of Nvflash -- ASUS will take care of a brick in that case, I guess. So..... the main question is: to customize or not customize?
Click to expand...
Click to collapse
I'm just extremely unimpressed and often times frustrated by the stock performance so I'm looking to try anything to make it better. I've purchased a 32 GB micro SD card and I'm going to move /cache and /data over to it to see if that helps. I'd like to get in on CM10 but from what I've read it's not ready on the TFI yet but definitely will do that once it is.

I unlocked my TF700 on Jelly Bean using the unlock tool without any issue.

MartyHulskemper said:
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
Click to expand...
Click to collapse
Sadly I updated to the update right before JB about 10 minutes before the announcement of the Nvflash.
And since you cannot go back down, I am stuck without Nvflash and as such I am staying stock until we get it for JB, then I will unlock and work this old girl.

Didn't work on the 10.4.4.16 firmware 10.4.4.18 seems to work fine - sweet! unlocked!

unable to root/unlock bootloader after repairs?=> Solved (Answer is on page 2)

Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and they've also relocked my bootloader, I think, although I can't get any OTAs.
Original question was:
What can I do to get my root again, because the scripts of sparky's tool don't seem to work anymore...
Sorry for this noobish question, but I swear that this has never happened to me before (and I have unlocked and rooted numerous devices)
What kind of sorcery is going on?!
Click to expand...
Click to collapse
Then I found the answer thanks to these amazing guys answering and trying to help.
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
It might seem complicated, but it really isn't.
Good uck to those who follow(ed) my path

adelancker said:
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and unlocked bootloader.
Click to expand...
Click to collapse
You mean relocked your bootloader?
...or actually unlocked it?

Thats OK said:
You mean relocked your bootloader?
...or actually unlocked it?
Click to expand...
Click to collapse
Sorry for that!
I meant that they relocked my bootloader, but still I can't get any OTAs
Thanks for the answer by the way.
I'd like to get it back to CR asap, since I really like that ROM, but noone has helped be yet
That is, until you arrived!

Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.

I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.

DarkFire1985 said:
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
Click to expand...
Click to collapse
Thanks! I guess I'll downgrade to .30 as well, root it there and maybe attempt to unlock my bootloader.
I really wish to have CR again, so there's no option that this will not work (eventually)

Thats OK said:
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
Click to expand...
Click to collapse
Shouldn't I first have root?
Or directly try to unlock the bootloader.

adelancker said:
Shouldn't I first have root?
Or directly try to unlock the bootloader.
Click to expand...
Click to collapse
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.

Thats OK said:
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Click to expand...
Click to collapse
Thanks for all the help!
It's not the first time I root (and/or) unlock a bootloader. It's just that now, those super easy root command methods don't work anymore. I have done completely manual rooting in the past, but I am not sure that will work either.
Besides, I got adb running before on my Infinity, but I'll make sure to downgrade to ICS first before doing anything else.
Here's what I am going to do:
1) downgrade to .30
2) try to root (with or without sparky's tool )
3) unlock bootloader (although I'm not sure if that'll work, judging from the comment of the Dutchman above)

I'll let you know in this thread if it worked or not.
My prediction: root will work, unlocking bootloader won't, since it's already been unlocked one and therefore my serial number is already in their database!

So i got my infinity like 2 weeks ago. The first thing i tried to do was to root it. I plugged in my device, installed drivers and checked unknown sources and usb debugging. I opened debugfs and tried to root my device but it suddenly closes. Whats likely to be the problem. And no i dont have asus sync installed.
P.S i returned my infinity on amazon as there was a hardware problem. Ill get the new one in a couple of days.
Thanks in advance.

Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).

MartyHulskemper said:
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
Click to expand...
Click to collapse
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!

Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Hmm... No idea what that could be.
I managed to unlock it, but that was after I reverted to ICS .30 (not obligatory, from what I understood ) I didn't use the Unlock Tool from the Asus website itself but an older (ex-official) Unlock Tool. (v7) I think it was.
I'll have a look and see if I can find it.

That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.

adelancker said:
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Click to expand...
Click to collapse
So glad to read that you have been successful.
...and do have fun flashing\updating\customizing!

DarkFire1985 said:
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
Click to expand...
Click to collapse
The unlock tools provided by ASUS to unlock the TF201, TF300 and TF700 have been proven to be identical files (by checksum verification) --- no need to reinvent the wheel there.
The unlock step indeed is crucial -- and it depends on ASUS' database. If you can't get past that, there'll no flashing available in terms of recoveries (and therefore no custom ROMs either). Have you tried dropping Gary a line yet?

No not yet. Will do that.
Sent from my ASUS Transformer Pad TF700T using xda premium

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Maybe you should have a look here. Seems like there were a couple of guys capable of unlocking it after all, and they were in the same situation as you.
I checked and the bootloader unlock tool was indeed an offial asus one. I downgraded before unlocking, but I saw you did too...
No idea what else I can do to help.

[Q] JB back to ICS, still possible to use NvFlash?

I recently purchased my TF700- I wasn't aware of the fact that unlocking the boot loader would void your warranty, and that there was a slightly more complicated process for prepping the TF700 for flashing roms and kernels compared to previous android devices. (This is my first tablet, so I don't know if this is normal for tablets though!) Plus the fact that I need to be on ICS to do everything initially.
And just a BTW, this is comparing it to my experiences w/ the G1, Epic 4G, GS2, and the GS3- where I never actually had to deal with unlocking the boot-loader directly/or having the risk of ruining my warranty.
So basically what happened was that I read through the forums and learned that unlocking the bootloader would void your warranty- and being that it is always risky business + the fact this tablet is a lot more expensive than a phone- I decided I wasn't going to be rooting/flashing roms and kernels and etc, on my TF700. I didn't want the risk of bricking something I just paid $600 bucks for. So I took the OTA update to Jellybean.
With further research though, I found out about NvFlash, and then it would make my tablet brickproof. And that immediately sparked my interest! I read though, that it does not work with the .30 firmware though.
This is where I got a bit confused- I know I can downgrade to ICS (the .30 v tho) and then unlock/root/then flash stuff.
BUT, by me taking the OTA update to 4.1.1 JB, did I **** up my ability to use NvFlash? Cause I really want too unlock my phone and flash roms, but I'm just really scared of bricking my device.
If anyone could help with what my plan of action should be, it would be much appreciated, thanks!

Can't be done unfortunately, you need .26 firmware for nvflash. At the moment you're out of luck :/

****! Well just my luck :/.
I was going to send in my TF700 back in anyways for a replacement since the screen was popping out in the corner, so I guess I'll wait till then!
Thanks for the response!

Just out of curiosity, why doesn't downgrading back to an ICS rom do the trick? Is there something that gets left behind by Asus's JB rom that doesn't get downgraded when you go back to Asus's ICS rom?
Sorry to revive an old thread but I couldn't find a pertinent new thread about this.
Thanks!

pgratz said:
Just out of curiosity, why doesn't downgrading back to an ICS rom do the trick?
Click to expand...
Click to collapse
You need a bootloader that does not check signatures to install the hacked bootloader. You cannot downgrade to such a bootloader, because all later ones do check signatures, and the unsigned ones are rejected.

pgratz said:
Just out of curiosity, why doesn't downgrading back to an ICS rom do the trick? Is there something that gets left behind by Asus's JB rom that doesn't get downgraded when you go back to Asus's ICS rom?
Sorry to revive an old thread but I couldn't find a pertinent new thread about this.
Thanks!
Click to expand...
Click to collapse
Well, Asus had patched the security hole with .26 ICS firmware. They updated the next version of ICS which is .30 and this blocked the exploide. The signature (key) from the ICS .30 is no longer the same as ICS .26. So if you tried to downgrade to .26, you're going to see signature mismatch and it will failed. The signature on ICS .30 and all of the JB are the same, so you can upgrade or downgrade from 30 and up....Here is where the story ended!!

Ah, OK that makes sense. Thanks for the explanation!
Paul

Downgrade from JellyBean to ICS
Hi,
I am very new hear and not sure how to start a new thread. I just purchased the Asus TF700t because it was supposed to have ICS, but I found it has JellyBean. Is there a way to downgrade it to ICS?
Thank you.

etoliway said:
Hi,
I am very new hear and not sure how to start a new thread. I just purchased the Asus TF700t because it was supposed to have ICS, but I found it has JellyBean. Is there a way to downgrade it to ICS?
Thank you.
Click to expand...
Click to collapse
You need to look around a bit.
I attempted an answer for you in another thread that you had replied in.
Please look here >>>> http://forum.xda-developers.com/showpost.php?p=38530719&postcount=5

[Q] JB Stock Needs Help

Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?

NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too

[Q] Is it possible to downgrade to pre 9.4.5.30 firmware ?

I've been searching on Google and these forums, but I want to get a final answer. Is it possible to downgrade to the less secure firmwares that are pre-9.4.5.30?
Also, does this unlock the bootloader, or am I misunderstanding what I'm reading?
I got my tablet yesterday and couldn't resist upgrading it despite knowing that often-times this causes a problem for customization. I now know I won't be able to get nvflash working on it, even if I unlock in the official way, but am I losing anything else ? I'm thinking about just returning this one and getting a new one that isn't upgraded, but I think I may just be stubborn and doing this on principle.

NegativeOne said:
I've been searching on Google and these forums, but I want to get a final answer. Is it possible to downgrade to the less secure firmwares that are pre-9.4.5.30?
Also, does this unlock the bootloader, or am I misunderstanding what I'm reading?
I got my tablet yesterday and couldn't resist upgrading it despite knowing that often-times this causes a problem for customization. I now know I won't be able to get nvflash working on it, even if I unlock in the official way, but am I losing anything else ? I'm thinking about just returning this one and getting a new one that isn't upgraded, but I think I may just be stubborn and doing this on principle.
Click to expand...
Click to collapse
As far as I know, it is not possible to go under .30.
Hell, I 've even tried going back to .30 but my tablet for some reason even refuses that (which is not normal, I know )
Why would you like to do that anyway? For the NVFlash Tool? The tf700 is pretty brick proof so you're not really in danger

To be fully unlocked? To not worry about warranty claims? I dunno. I haven't tried going back to .30 yet, but if what you say is true and it doesn't always work to do that, then I can't get it unlocked at all, which I absolutely want to do as I like playing with different roms.

Note
Unlocking is still possible with JB firmwares, even though the Asus unlock tool download page says it's ICS only.
What the .30 firmware is required for, is rooting without unlocking, because it's the last firmware on which the debugfs exploit is available.
I myself downgraded for root last week-end, since I am unable to unlock for a different reason.

Oh, I'm rooted. I guess it just boils down to the feeling of freedom associated with a device unencumbered by arbitrary locks.

NegativeOne said:
To be fully unlocked? To not worry about warranty claims? I dunno. I haven't tried going back to .30 yet, but if what you say is true and it doesn't always work to do that, then I can't get it unlocked at all, which I absolutely want to do as I like playing with different roms.
Click to expand...
Click to collapse
You can always unlock. Therefore, if you are planning to unlock+root, you can stay on JB.
As far as only rooting goes, you can usually always go back to ICS (I think may have a corrupt download, which prohibits me to downgrade)
I'll need to have a look into that, but you shouldn't worry about that.
As for the warranty: yes, I believe it contains full coverage. You should then be free to do whatever you want

adelancker said:
You can always unlock. Therefore, if you are planning to unlock+root, you can stay on JB.
As far as only rooting goes, you can usually always go back to ICS (I think may have a corrupt download, which prohibits me to downgrade)
I'll need to have a look into that, but you shouldn't worry about that.
As for the warranty: yes, I believe it contains full coverage. You should then be free to do whatever you want
Click to expand...
Click to collapse
Well - they technically void your warranty when you unlock. So no, not free to do whatever you want.

I believe SquareTrade will still cover physical damage, however if it is a software problem it will not be covered. Anything software related is not recovered, because before flashing I was gonna get one and anything software related will not be covered. So I turned down the getting the warranty because I take good care of my stuff. Usually .
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.7 Odex AND That's UltraCleanRom(7 sec boot )
Kernal: _That's Stock V6 Kernal
Theme: Timberwolf's Blues & Jazz Theme V2.1
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/showthread.php?t=2204100