Related
Apologies if this is already common knowledge?
It looks as though the B70 Transformers are coming with locked boot loaders, is that the case?
The never-ending battle.
Tuesday, August 2nd, 2011 - 10:21 am - Android, General, Transformer
Been a while since last post, but it appears ASUS’s counter move have finally come.
All signs point to that with the B70 revision of the Transformer, they have changed the Secure Boot Key.
At the same time they appear to have disabled downgrades in the more recent revisions of the firmware (the one B70 comes with!)
This means: At this point it’s not possible to root B70 revision ASUS Transformers. We will of course see what we can do to find a way around it, but keep in mind neither of us have access to a B70 revision model nor do we intend to spend the money needed to get one.
It was a good run, and congrats to all those with pre-B70 revision devices and bummer for everyone who bought newer revision devices hoping to root
Thanks,
RaYmAn & Bumble-Bee
Click to expand...
Click to collapse
http://androidroot.mobi/2011/08/02/the-never-ending-battle/
I'm not remarkably familiar with the different segments, but I'm rooted now (on a device from last month, so B6), but I still have my standard bootloader and recovery. Does this make a difference to rooting, or just to custom ROM's?
This means: At this point it’s not possible to root B70 revision ASUS Transformers.
Click to expand...
Click to collapse
I think it applies to both? (But I'm no expert on these things).
I wonder if any new Asus software updates will also change the secure boot key and prevent other B revisions from being rooted once updated?
Makes me glad mine's B3. Just hope I dont have to return it at any point. Thanks for posting this info though. Interesting stuff.
I'm guessing suddenly lightbleed that nobody notices and creaking that you have to listen out for will all of a sudden be unimportant...
I'm not remarkably familiar with the different segments, but I'm rooted now (on a device from last month, so B6), but I still have my standard bootloader and recovery. Does this make a difference to rooting, or just to custom ROM's?
Click to expand...
Click to collapse
The secure boot key controls access to the tablet in NVFlash mode.
Without it basicallly you can't use NVFlash to update the Firmware on the tablet but it's possible that there might be other rooting methods that don't rely on NVFlash.
Instead these rely on exploiting bugs in the Android OS which can then be used to write data to areas of the tablet that shouldn't and so do things like install custom recovery modes that can then be used to load custom/insecure ROMs etc
(it's how the tablet was rooted before we gained access to the SBK)
I'm sure some bright spark will get it sorted anyways. These things don't remain unchallenged for long.
Now did we get the SBK last time? Someone had to have leaked it; I find it hard to believe it was brute-forced.
Ugh.... Why oh why are they doing this?? Don't they realize that one of their "pros" over Apple devices is becuase they lock them down so much - Why would they go and do that to their products now??? I thought I was finally moving towards freedom by getting away from Apple!!! <sigh>
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
Ugh.... Why oh why are they doing this?? Don't they realize that one of their "pros" over Apple devices is becuase they lock them down so much - Why would they go and do that to their products now??? I thought I was finally moving towards freedom by getting away from Apple!!! <sigh>
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
the thing is wheather we like it or not ..they are their units and they will do what they want. Doesn't mean someone won't crack it like they always do. Just finding some that have been exchanged that have been rooted is enough to tick them off. Just reading here and finding out what s done with them is enough to tick them off. Look at what Motorola is doing. They made a statement that if you want to run a custom rom go somewhere else.
No they are OUR units and WE will do what WE want with them and if they do not like it then they can stick it where the sun does not shine.
There is no need for Asus to do this to the newcomers. It is just plain wrong.
Asus seems to go in the wrong way.
CrazyPeter said:
I'm guessing suddenly lightbleed that nobody notices and creaking that you have to listen out for will all of a sudden be unimportant...
Click to expand...
Click to collapse
ROTFLMAO! Thanks Crazy......very astute!
Do they really think that locking the bootloader will ATTRACT more customers?? If anything, it can only hurt sales...
I can't imagine that a whole lot of transformers get returned rooted - most people who are willing to root them know better than that (I would think)... I just don't get the reasoning behind it. How does it benefit them?
Sent from my Transformer TF101 using Tapatalk
I wonder what Asus will do with the Transformer 2.
Less of an upgrade itch at the moment.
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
I'm guessing its just to hinder people from returning or RMA'ing units for light bleeds or creeking
Sent from Hogwarts
bytetemplar said:
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
Click to expand...
Click to collapse
The serial number is located on the back of the pkg. You will be able to see it before you purchase it.
Is there anyway to safely tell if this is the case? I recently got a B70 and was able to root mine. I just wnat to make sure that I am not affected by this, and if I am want does that mean?
bytetemplar said:
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
Click to expand...
Click to collapse
The serial will start with B70, so you will be able to tell. It's not like the B70 won't be cracked, anyways. There may be benefits to the later revision, as well.
As for Asus' thoughts on locking it down, they have a responsibility to shareholders to protect the IP(intellectual property) on the device. Buying a Transformer does not give you license to their IP. If shareholders feel they are not acting in accordance, they can basically sue Asus for shares/profit.
Personally, I wish the entire bootchain was open-source, but we knew it wasn't right from the beginning, so Asus is within it's rights.
Now, the good news. If we can buy enough stock in Asus, we can vote to open the IP base. If we reallllly buy alot, we might even win.
Once again, let me state, their decision sucks, but it's probably more for the shareholders than the company itself.
Hello folks. I've unlocked my Infinity using the Asus unlock tool. Well, all I really wanted was to root it (which I did) but I got the two mixed up and I also unlocked it first. I will never be loading a custom rom therefore I'd rather keep mine locked. This also voids my warranty and I'm afraid I won't be able to receive OTA's.
Is there ANY way to lock the bootloader back up like it was from the factory? If I should keep the pad unlocked, convince me why.
Thanks for any help!
No, there isn't. Your S/N is already in their database, too. You may use manual firmware updates from their site and they may still respect the warranty (to certain extent?).
There was enough threads on the two for you not to confuse them (as there is about what you can do with being unlocked), so you pretty much rushed into it. Most likely this will not make your life with the Infinity harder, however.
Dammit. I'm an idiot. Now no OTA for me. Well, I can still return it to where I bought it from. I wish I had paid more attention.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
ive looking and i couldnt find one. does anyone have one that i dont need to have an unlocked bootloader?
Not physically possible. If you need customization, use root with the stock rom and be very careful not to brick.
how would it not be possible? just use a stock kernel and you should be good. thats what we did with the atrix 2 since the bootloaders locked.
Don't think you can put a custom recovery on without unlocking the bootloader. No recovery = no flashing ROMs
vegandroid said:
how would it not be possible? just use a stock kernel and you should be good. thats what we did with the atrix 2 since the bootloaders locked.
Click to expand...
Click to collapse
Don't even start on that bootstrap debacle with moto phones. It was absolutely horrid for flashing anything and was not nearly powerful enough for me. The hassle of using a neutered recovery instead of the real thing is just not worth it, even considering the warrantee.
le rustle face
Keion said:
Don't even start on that bootstrap debacle with moto phones. It was absolutely horrid for flashing anything and was not nearly powerful enough for me. The hassle of using a neutered recovery instead of the real thing is just not worth it, even considering the warrantee.
le rustle face
Click to expand...
Click to collapse
.... I fail to see the point of your post. I didn't ask for your opinion on Motorola or what works best for you. Style on topic dude.
Sent from my SAMSUNG-SGH-I747 using xda premium
So there is a way to install custom ROM's without unlocking the bootloader? If so, I'd love to know how!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
The problem is, the methods used on those Motorola phones are very hackish, and not recommended if alternatives are present. And since the TF700 is unlockable, its extremely unlikely those methods will ever be duplicated since those who want to mod can do so without restrictions.
Just look at the OG Atrix community... the instant an unlockable bootloader was leaked, development for those hackish methods immediately halted. Someone ported 2nd init days or weeks before that happened, and nothing was ever written to use it because it simply wasnt needed anymore.
jtrosky said:
So there is a way to install custom ROM's without unlocking the bootloader? If so, I'd love to know how!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
+1. If there was any way to get around Asus's crappy unlocking the bootloader voids the warranty thing I'd jump right on it. I also didn't know that type of thing was possible...
vegandroid said:
ive looking and i couldnt find one. does anyone have one that i dont need to have an unlocked bootloader?
Click to expand...
Click to collapse
Did I read that you were going to try to port paranoidandroid to the TF700 last night or was that one of my weird obsessive Infinity dreams ?? I wish you luck if you are going to try - we need a few more devs around these parts.
I personally wasn't worrying about voiding the warranty considering it rooting voided on all the other devices I've had. I'm more waiting for a reason to unlock the boot loader. It's just a nice bonus that rooting doesn't.
I just say wait till you have a reason, and feel comfortable that the device you got is good.
Did I read that you were going to try to port paranoidandroid to the TF700 last night or was that one of my weird obsessive Infinity dreams ?? I wish you luck if you are going to try - we need a few more devs around these parts.
Click to expand...
Click to collapse
When i can get jellybean then ill work on it. Im super busy with school and work, but i need to set some time aside to port it for tf700. i just cant spare the time to completely port JB too right now.
Jotokun said:
The problem is, the methods used on those Motorola phones are very hackish, and not recommended if alternatives are present. And since the TF700 is unlockable, its extremely unlikely those methods will ever be duplicated since those who want to mod can do so without restrictions.
Just look at the OG Atrix community... the instant an unlockable bootloader was leaked, development for those hackish methods immediately halted. Someone ported 2nd init days or weeks before that happened, and nothing was ever written to use it because it simply wasnt needed anymore.
Click to expand...
Click to collapse
Makes a lot of sense, thanks!
Personally, I'm still interested in a way to flash custom ROM's without unlocking the bootloader, even if it is "hack'ish".
As a good example, I unlocked the bootloader on my original TF700 after I had it for about 3 weeks. I figured that I was good to go - no major flaws... And then about 2 weeks later, the damn thing died on me, so I was stuck with a less-than-45-day-old device that had no warranty!!
I'm just saying - if there is a way to flash ROM's without voiding my warranty, I'd be *very* interested in doing that, even if it was a little hack'ish!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
its rather hard to install custom roms without an unlocked bootloader.
Consider this: You have a computer that boots directly into windows. Now you have administrator access to the computer however you can't change the boot priority, what disks it boots from, or anything having to do with how the thing starts up. Usually when you want to install an operating system, say windows xp, you would put the disk in, boot from the CD, and install it. Well we have no "boot from CD" option, everything pertaining to that is locked down by Asus.
I know other phones have found ways to sidetrack around that but honestly, with how unreliable they are its often not worth it. Asus has this thing locked down pretty well that its damn near impossible to get enough access to load anything custom at startup (even the unlock they gave us is garbage, if that fails your screwed).
If you want to load something custom you are best to get a third party warrenty and use the unlock.
pileot said:
its rather hard to install custom roms without an unlocked bootloader.
Consider this: You have a computer that boots directly into windows. Now you have administrator access to the computer however you can't change the boot priority, what disks it boots from, or anything having to do with how the thing starts up. Usually when you want to install an operating system, say windows xp, you would put the disk in, boot from the CD, and install it. Well we have no "boot from CD" option, everything pertaining to that is locked down by Asus.
I know other phones have found ways to sidetrack around that but honestly, with how unreliable they are its often not worth it. Asus has this thing locked down pretty well that its damn near impossible to get enough access to load anything custom at startup (even the unlock they gave us is garbage, if that fails your screwed).
If you want to load something custom you are best to get a third party warrenty and use the unlock.
Click to expand...
Click to collapse
Even with those methods, you're still restricted. For example, the Motorola phone hacks can run custom roms, but are still stuck with the stock motorola kernels. That means a (somewhat dirty) AOSP rom can be made around the kernel, but a true clean Cyanogenmod or anything requiring kernel level hacks are not possible.
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Completely agree. NVFlash for all.
paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse
+1
+1
There should be no lockdown code in the bootloader for "unlocked" devices.
I agree, they're surprisingly draconian about what "unlocked" means. We're not even covered under their warranty, might as well give us full access to our devices smh
Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
i
urrlyx said:
+1
get
There should be no lockdown code in the bootloader for "unlocked" devices.
Click to expand...
Click to collapse
:good: Yep. All or nothing. Don't void my warranty then partially cripple my ability to get my money's worth
Slammin said:
Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
of course nv flash would have saved all of those bricks from going back to asus.
they should be providing this tool rather then locking it down.
Hearing that the .30 bootloader is signed and won't allow flashing of unsigned bootloaders (downgrades included, since they are not signed) made me incredibly angry with ASUS. It's the wrong way to attack the problem. Even then, it's still possible to flash Jelly Bean to a TF700 in (IMHO) the most crazy of ways, by flashing the TF300 JB ROM. Even on locked devices!
There is this nvflash tool that makes it possible to recover from any brick known to man, and they just don't seem to want us to have access to it. I have unlocked my tablet to do exactly what I want with it, but even after I've voided my warranty, ASUS won't let me do it. Custom ROMs have a higher tendency to brick a device than a stock ROM, and people who've unlocked their devices should be tech-savvy enough to follow a tutorial to nvflash it back from the dead. Instead, ASUS wants them to enjoy their new shiny $500 paper weight/door stop.
ASUS, this was a **** move. The least you could do would be to provide a possibility to downgrade the bootloader (ie. a signed blob of an unsigned bootloader, for example the 9.4.5.26 one). Even better, you could actually unlock unlocked devices, or just give us nvflash for real.
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.
That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Not sure if i understood what you meant with the "wheelie" version but afaik wheelie is used just for "bootstrap" (basically is used to bypass the lock that Asus used in order to prevent us from using NvFlash) in NvFlash mode, after that you will use "native" nvflash commands (wich are different based on the device u are using) , basically what Asus should provide to us from the start.
I'm probably not using the right terms... Using the TF101 as an example, the early TF101s (SBK V1) were able to use NVFlash directly, with no restrictions. Then, Asus being Asus, they modified the SBK (Secure Boot Key?) in the newer TF101's and NVFlash would no longer work on these SBK V2 devices. That's when one of the awesome developers released Wheelie - it allowed NVFlash to be used on the newer SKB V2 TF101's.
So, I think you already answered my question!
If I understand you correctly, Wheelie is just used to get around the SBK at which point NVFlash can be used normally?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
I could be wrong but i think that on the first tf101 batch nvflash was not ready "out of the box" but was possible only after the SBK leak. And that explain why Asus used SBK v2 on the next tf101 batch... Basically they never provided full APX/NvFlash access and i guess they never will.
jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Click to expand...
Click to collapse
Pretoriano80 said:
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.
Click to expand...
Click to collapse
Lets face it, I think everyone was blindsided when .30 was released. Wasn't JB meant to be released next?? I am wondering whether the reason they have actually done this is to prevent flashing TF300 JB on the TF700. Has anyone on .30 actually been able to flash the TF300 firmware? I suspect that there were a few red faces when ASUS saw that the TF300 firmware could be flashed on locked TF700s. Also, that flashing this firmware caused TF700s to be stuck with the TF300 JB bootloader. .30 did repair the damaged TF700 bootloaders but has had the knock-on effect of not allowing us to not use NVFlash. This is not cool...
Hit the "Newsworthy Thread" thing at the top! Lets see if we can get the XDA news people to take a bit of interest in this and cause ASUS a little bit of shame This thread from the Prime forum seemed to get some attention from Tien once XDA made it public (see post 200): http://forum.xda-developers.com/showthread.php?t=1764917&page=20
paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse
+1
one more here.
Another here I was Awesomely Pleased when i have to Unbrick my Prime, but now that NVFlash is out on the Infinity I can't use it? Aww ASUS you Disappoint me..
This is a lost cause as they promised to be looking in to an official nvflash release for the transformer prime but as you can see it never came. The only access we had is when wheelie was released. This is why I cant support them with the way they are treating customers that are buying their tablets. At least with samsung products I have odin. You are just SOL with the asus now. As someone stated above, its like all they want to do is line their pockets. All they are doing is driving the customers away.
Also when yiu unlock your transformer tablet they delete the DRM Keys. Meaning any program relying on it like hulu or play movies will not work (netflix works I think).
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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.