Has ASUS accidently blocked NVFlash through the JB update or was it purposely blocked in the JB 4.1.1 update?
Any word from ASUS about unblocking NVFlash in the future updates?
What are the odds of an explot in future updates?
Sign this if you havent already :good:https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
ronniereiff said:
Has ASUS accidently blocked NVFlash through the JB update or was it purposely blocked in the JB 4.1.1 update?
Click to expand...
Click to collapse
It was never officially supported - we always had to use a hacked bootloader to get the blob, and a special tool to enable nvflash. With the JB update they added signature verification for bootloader updates - I don't know if they did it to block nvflash, but I doubt that it was the main reason.
I doubt it too.
Having said that, if I was Asus I wouldn't want users messing with NVflash either so it's no loss to them that you don't have it. If you use the device as they intended it you wouldn't need nvflash.
sbdags said:
If you use the device as they intended it you wouldn't need nvflash.
Click to expand...
Click to collapse
...or CROMI.
IMHO, they should give users who unlock their tablet their unique SBK. Since unlocking voids the warranty anyway, it would be only fair to give users full control over their device.
_that said:
...or CROMI.
IMHO, they should give users who unlock their tablet their unique SBK. Since unlocking voids the warranty anyway, it would be only fair to give users full control over their device.
Click to expand...
Click to collapse
Agreed but they have never done this. I had the original TF101 which on the first few revisions had a working NVFlash. Thesame thing happened. The version I bought had a updated bootloader and the NVFlash was a thing of the past.
The same has happened on the prime and on the TF300 as well as the infinity.....
Asus have no reason to give it to us really. In fact they make money by us not having it from people who have to send in bricked devices. Which by all accounts they replace the mainboard on and don't use any flashing tools to recover although I suspect they could do it that way. Unless they reflash with a new serial???
sbdags said:
Asus have no reason to give it to us really.
Click to expand...
Click to collapse
Yes, unfortunately - as long as nobody offers a more open device with similar capabilities.
Related
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it works for you too, and which version of FW and S/N you have.
Thanks,
milo
miloj said:
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it work for you too, and which version of FW and S/N you have.
Thanks,
milo
Click to expand...
Click to collapse
With nvflash being available for all TF101 devices, we will always have root, no matter what.
whitekidney said:
With nvflash being available for all TF101 devices, we will always have root, no matter what.
Click to expand...
Click to collapse
Doesn't the nvflash method unlock the device and void the warranty ?
No it doesn't, since the bootloader was cracked and not officially unlocked by ASUS, there's no real way for them to tell. It does no permanent change to your bootloader or APX mode. Nvflash for sbkv2 is in my signature, however, the Tf101G and slider have different bootkeys which have yet to be cracked. Those will have to continue to use exploits. My PERI tool currently works on all devices and firmware (and supposedly the next update) and is a one click root option. You can check it out in my signature.
miloj said:
Doesn't the nvflash method unlock the device and void the warranty ?
Click to expand...
Click to collapse
No.
Rooting voids your warranty too, by the way.
miloj said:
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it work for you too, and which version of FW and S/N you have.
Thanks,
milo
Click to expand...
Click to collapse
the link is not working
Is there any way to root or unlock the Infinity after updating to Jellybean. The current methods do not work. Will i have to wait for someone to come up with a new tool or what
Downgrade back to .30
http://forum.xda-developers.com/showthread.php?t=1915598
Install SuperSU and OTARootKeeper
Use OTARootKeeper to protect root
Update to JB
Use OTARootKeeper to restore root
macaumen said:
Downgrade back to .30
http://forum.xda-developers.com/showthread.php?t=1915598
Install SuperSU and OTARootKeeper
Use OTARootKeeper to protect root
Update to JB
Use OTARootKeeper to restore root
Click to expand...
Click to collapse
It looks like there is different versions of .30 does it matter what one. Thank you so much
Just follow the SKU of your infinity and download the file from ASUS.
macaumen said:
Just follow the SKU of your infinity and download the file from ASUS.
Click to expand...
Click to collapse
Man i am so confused right now. I have hacked many phones including my S3 and flashed many times. I am just confused coming to Asus. I have never had a asus device before and down want to screw anything up. Any extra help would be greatly liked thanks man
aldude345 said:
Man i am so confused right now. I have hacked many phones including my S3 and flashed many times. I am just confused coming to Asus. I have never had a asus device before and down want to screw anything up. Any extra help would be greatly liked thanks man
Click to expand...
Click to collapse
Settings --> About tablet --> Build number
There you will find something like "XX_epad" in the middle of that very long string. In which XX = your tablet's SKU. It can be US, WW, TW, etc.
Sorry, I don't have my tablet in my hands. Cannot get you a screenshot. I am sure there's some around the forum.
Let me know if you can find it
macaumen said:
Settings --> About tablet --> Build number
There you will find something like "XX_epad" in the middle of that very long string. In which XX = your tablet's SKU. It can be US, WW, TW, etc.
Sorry, I don't have my tablet in my hands. Cannot get you a screenshot. I am sure there's some around the forum.
Let me know if you can find it
Click to expand...
Click to collapse
Awesome i see its the US version. I have found it on Asus website. Now one more thing and this may sound stupid. I see it says put it in adb/fastboot. where is that exactly haha thanks again
Oh wait, I guess you haven't unlocked the infinity yet. Fastboot is available only after unlocking. I haven't unlocked mine, so I am not very familiar with that.
Using adb connecting to your tablet through command prompt is essentially the same as running terminal emulator on the tablet. I guess you should be familiar with adb as you hacked many phones already.
You know what. I heard that the unlock tool also works in JB for TF300T. I guess it should be working on TF700T with JB also. You can try it first before downgrading.
You can try this guide to downgrade to .30. Just download the .30 file instead of .22 stated in the post.
http://forum.xda-developers.com/showthread.php?t=1803343
Hi fellow modders,
Been flashing lots of devices, very seasoned at this.
SO many threads warn users to have "The lastest JB bootloader".
I upgraded to 4.1 with the stock ASUS firmware using TWRP. Now I'm running CleanRom 2.4.
I don't know where and how to check which bootloader I have.
If I do have the old bootloader, is there a guide to upgrade my bootloader?
Thanks!
Miguel:victory:
My bootloader version shows up when I hold volume down when booting. It's displayed in the top left corner when the 4 boot options appear...
solar_burn said:
Hi fellow modders,
Been flashing lots of devices, very seasoned at this.
SO many threads warn users to have "The lastest JB bootloader".
I upgraded to 4.1 with the stock ASUS firmware using TWRP. Now I'm running CleanRom 2.4.
I don't know where and how to check which bootloader I have.
If I do have the old bootloader, is there a guide to upgrade my bootloader?
Thanks!
Miguel:victory:
Click to expand...
Click to collapse
Well, if you're so experienced, sir, you could've (and probably should've) come to an answer all by yourself, just by reading. In the CleanROM thread, Scott put forth that you NEED a JB bootloader (which is "the" latest version) to boot it at all. And if in doubt, I'd say flash the latest ASUS stock ROM. You have plenty of experience, right?
By the way: in my gut feling, there's a relatively high percentage of "experienced users" (or at least people regarding themselves that way) bricking their TF700. Wonder why that is. Humble down a bit.
It's not quite that simple...
Not every firmware update has an updated bootloader, because not every update needs a different bootloader. Yes, you can flash the latest firmware, but there's no guarantee that it will contain the latest bootloader...
So I pressed the button combo to see my boot loader, I got 2.10e. I'm sure I can find out which version number I need on my own. Which version do you have?
I didn't even notice that tiny text! Thanks form the tip! Danger_rat. Although I did flash the latest Asus firmware before using clean ROM as I was concerned about the need for the latest boot loader. Just didn't know if I upgraded it or how to tell.
Thanks Danger_rat! Knew you guys would come through
I know you don't have to help but you took the time, so thank you.
Sent from my Nexus 7 using xda app-developers app
Mine shows:
Android cardhu-user bootloader <1.00e> released by "US_epad-10.4.4.18-20121012" A03
danger-rat said:
Mine shows:
Android cardhu-user bootloader <1.00e> released by "US_epad-10.4.4.18-20121012" A03
Click to expand...
Click to collapse
I got the WW version since I'm in Canada, maybe that's why mine says 2.0e?
Either way, I'll look up the version numbers later.
Thanks Danger_rat!
danger-rat said:
It's not quite that simple...
Not every firmware update has an updated bootloader, because not every update needs a different bootloader. Yes, you can flash the latest firmware, but there's no guarantee that it will contain the latest bootloader...
Click to expand...
Click to collapse
The complete firmware always includes the bootloader.
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
solar_burn said:
I got the WW version since I'm in Canada, maybe that's why mine says 2.0e?
Click to expand...
Click to collapse
I checked all my WW bootloaders:
ICS bootloaders say "2.10 e" at least for versions starting with 9.4.5.26 - don't have older ones.
JB bootloaders say "1.00 e" (yes, funny, isn't it?)
Why the hell does ASUS keep breaking chronology with the ICS/JB naming scheme? Ugh, this is making things even more complicated, as it provides even more numbers to reckon with. Thanks for pointing the numbers out, though, that might come in handy later on.
MartyHulskemper said:
Why the hell does ASUS keep breaking chronology with the ICS/JB naming scheme? Ugh, this is making things even more complicated, as it provides even more numbers to reckon with. Thanks for pointing the numbers out, though, that might come in handy later on.
Click to expand...
Click to collapse
Maybe that was actually Nvidia's idea - or for some reason Asus decided to use an older bootloader for the newer OS. But it's easier to use the text after "released by" anyway.
_that said:
The complete firmware always includes the bootloader.
Click to expand...
Click to collapse
Yes, I know, but some people got to JB via OTA updates which may not contain the bootloader.
I basically thought the other response was overly aggressive, unpleasant, and unhelpful, so I was trying be a bit more helpful - after all, isn't that the whole point?
danger-rat said:
Yes, I know, but some people got to JB via OTA updates which may not contain the bootloader.
Click to expand...
Click to collapse
OTA updates also contain the bootloader (when it changes). And since the dlpkgfiles are strictly incremental (they check for the exact version to upgrade from), you can't skip or miss the update with the bootloader.
_that said:
OTA updates also contain the bootloader (when it changes). And since the dlpkgfiles are strictly incremental (they check for the exact version to upgrade from), you can't skip or miss the update with the bootloader.
Click to expand...
Click to collapse
I'll take your word for this device, but historically that hasn't been the case for all Android devices, but that's not really the point -- the OP wanted to know what bootloader version he had, and I was simply trying to help...
danger-rat said:
I'll take your word for this device, but historically that hasn't been the case for all Android devices, but that's not really the point -- the OP wanted to know what bootloader version he had, and I was simply trying to help...
Click to expand...
Click to collapse
Appreciated. My point was that a stock ROM *downloaded* from ASUS will contain the then-current bootloader. It' d be a pain to flash and then have to reflash the desired custom ROM, but it is not exactly the end of the world either. (Although it did feel that way when my update from .22 resulted in the recovery being reset to the useless stock recovery version.
As far as your opinion of my style or phrasing is concerned: not every meal is to everyone's taste. You'll have to deal with it.
everyday new user with new bricked device....!
I'm sure this is Asus s trap ... for still our money
How can wipe data erase bootloader....!
Where is our dev.... To break asus SBK
I don't understand a word you just said.
Do you work for Asus?
mine is working just fine now after the latest update
there is a issue i see with your post
if u choose to unlock it
and install a rom then bricked it. its not asu's fault and has nothing to do with them
or the quality of the item.. you always run the risk of brick if u choose to install anything other than the stock rom..
zWarHawkz said:
mine is working just fine now after the latest update
there is a issue i see with your post
if u choose to unlock it
and install a rom then bricked it. its not asu's fault and has nothing to do with them
or the quality of the item.. you always run the risk of brick if u choose to install anything other than the stock rom..
Click to expand...
Click to collapse
I couldn't have said it better myself. :good:
+1
Sent from my ASUS Transformer Pad TF300T
smokarz said:
I don't understand a word you just said.
Do you work for Asus?
Click to expand...
Click to collapse
I laughed at this because Asus does have a track record for misspellings and strange grammar.
The TF300 is a good device.
I had one TF101 before, which was very good device, I can say that the little error from Asus is about the TF201 "Prime".
But the TF pad are always very functional, without problems for the most of time
My Asus TF are always unlocked, always rooted, no bricked.
The problem that you want always more. More what ?
Functionalities, Overcloked, undervolt...etc
Don't forget that these devices have some limits.
And then certain users don't respect, or don't give attention to the instructions given by devs.
That's why that they have a brick instead of a TF pad:crying:
:good:
Hi, Im lost in these topics about this problem. I got Asus TF700T and I want to root. But when I tried to Unlock this tablet I got this message:
An unknown error occurred, the cause may be connected to the network. Wait and try again.
Can anyone tell me why? Or what I can do with this problem...
LucikMucik said:
Hi, Im lost in these topics about this problem. I got Asus TF700T and I want to root. But when I tried to Unlock this tablet I got this message:
An unknown error occurred, the cause may be connected to the network. Wait and try again.
Can anyone tell me why? Or what I can do with this problem...
Click to expand...
Click to collapse
The error indicated that your device is not registered with Asus server or there's problem with Asus server. Many ppl have this issue and the only way is to wait and try again on another day. Sometimes it takes days, weeks, some...never!! Asus is no longer support this and they transfered this process to third party, so we're at the end of the rope.
buhohitr said:
The error indicated that your device is not registered with Asus server or there's problem with Asus server. Many ppl have this issue and the only way is to wait and try again on another day. Sometimes it takes days, weeks, some...never!! Asus is no longer support this and they transfered this process to third party, so we're at the end of the rope.
Click to expand...
Click to collapse
So there is no chance to root??
LucikMucik said:
So there is no chance to root??
Click to expand...
Click to collapse
Rooting has nothing to do with unlocking. You still can root your device, but without unlocking you will not able to flash recovery in order to flash custom rom/kernel.
buhohitr said:
support this and they transfered this process to third party, so we're at the end of the rope.
Click to expand...
Click to collapse
source?
mrjayviper said:
source?
Click to expand...
Click to collapse
ASUS CASEID=RPTM20121129101715-271
Hi David,
Thank you for reaching out. Last I heard, the unlocking problem was due to an issue with the servers over at HQ. Since then, I was informed that they (HQ) would take over handling it. I'm sad to say, that I have not heard anything from them since and I am probably in the same situation as you guys. The best I can recommend is to send it in for RMA since it is believed to be an issues with the MB not being able to communicate with the servers.
Tien
Is that answer your question?
buhohitr said:
ASUS CASEID=RPTM20121129101715-271
Click to expand...
Click to collapse
Where does this mention a third party? I would read HQ as Asus HQ in Taiwan.
Ihave the exact same problem. imgonna sell this if it cant be unlocked!
buhohitr said:
Rooting has nothing to do with unlocking. You still can root your device, but without unlocking you will not able to flash recovery in order to flash custom rom/kernel.
Click to expand...
Click to collapse
Can you root it on JB without unlocking first ? I missed something...
Envoyé depuis mon ASUS Transformer Pad TF700T avec Tapatalk
Astegal said:
Can you root it on JB without unlocking first ? I missed something...
Click to expand...
Click to collapse
No, but you can downgrade to ICS, root it with debugfs, use OTA RootKeeper, and upgrade to JB again using dlkpkgfiles saved from OTA upgrades (downloads are available in some thread on this forum). This procedure does not require unlocking and results in a rooted JB.