Related
Guys,
Due to build issues (gaps in glass) i replaced my B5 into B7.
Now NVFLASH attempt closing the APX mode
Any mathod root and install CWM on the B7? Any ETA for this?
Thanks!!!
When Asus released the B70 revision of the Transformer, they changed the Secure Boot Key.
As I can not post outside links, I'll just include this info (obtained from androidroot.mobi):
The inner workings of Secure Boot key and Nvflash
What is Secure Boot Key and how does it work?
I’ve been getting lots of questions about this, so here is some simple background:
The secure boot key is an AES128 encryption key that can used to encrypt various data on the flash memory. It’s a generic nvidia tegra2 thing, that the manufacturer can optionally use to make their device more “secure”.
When the SBK is set, it’s stored in a one-time-programmable “fuse”. This also means that now that the key is out, they can’t change it on already released devices, only new devices.
When the tegra2 starts up, the AES key is available to the hardware AES engine only. E.g. not even the bootloader can read it back! However, the bootloader can *use* the key to encrypt whatever data it wants through the hardware AES engine. And here is the explanation why the blob flashing method actually works! The bootloader checks for the blob in the staging partition and encrypts and flashes it as needed.
Once the bootloader is done, it clear the key from the AES engine which makes it impossible to encrypt or decrypt things from within the OS.
So what happens when it boots into APX/Nvflash mode?
The basic APX mode is stored in the BootROM and hence can never be changed. It appears to accept only a very limited range of commands, and each command needs to be encrypted using the SBK to be accepted. If it receives a command that’s not properly encrypted, it disconnects the USB and appears to be off. This is the dreaded “0×4″ error that people have been getting when attempting to get nvflash working.
It should be noted, that even with the SBK inputted into nvflash, most regular nvflash commands won’t be available. I’m still not entirely sure why (and I can’t rule out it will change).
What *is* available, is the nvflash –create command. What this command does is repartition and format all partitions, set bct and odmdata and send over all needed partitions to the device (and encrypt them as needed). This means a full recovery is possible, but regular ability to flash e.g. just boot.img or read partitions off of the device is not possible at this point.
So what do we need for nvflash?
In order to get a working (e.g. –create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
BCT file (boot device setup, ram configuration and a bit more)
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.
On top of these files, we also need all the partitions, e.g. bootloader.bin, boot.img, recovery.img and system.img. Luckily, these partition files are available in official ASUS updates and can be extracted from the blob file using my blob tools
The first four peices aren’t readily available, but through lots of effort and a good deal of luck, we have managed to recreate the needed files. Secure Boot Key has already been released (note that this was by far the hardest!) and the rest will most likely follow over the weekend. Keep in mind that we want to keep this legal, so don’t expect us to release any ready-made packs for unbricking! We will however make the recreated files available. Since these are recreated and not actual ASUS files, there should be no problems with them.
I hope this helps give a better understanding of how and what secure boot key is and what it gives us.
Click to expand...
Click to collapse
The previous SBK was leaked on the internet, and allowed us to flash a custom recovery and thus custom roms. AES128 is almost impossible to brute force so I would not count on it getting out soon. They might find a weakness on how the key is stored and extract it like that somehow.
Not all B70's have a new SBK. The first batch produced still had the old one and the old root method still works. My Transformer is an example of this.
You don't appear to be so lucky. You'll have to wait on a new method.
Sorry man
Helaas said:
When Asus released the B70 revision of the Transformer, they changed the Secure Boot Key.
As I can not post outside links, I'll just include this info (obtained from androidroot.mobi):
The previous SBK was leaked on the internet, and allowed us to flash a custom recovery and thus custom roms. AES128 is almost impossible to brute force so I would not count on it getting out soon. They might find a weakness on how the key is stored and extract it like that somehow.
Not all B70's have a new SBK. The first batch produced still had the old one and the old root method still works. My Transformer is an example of this.
You don't appear to be so lucky. You'll have to wait on a new method.
Sorry man
Click to expand...
Click to collapse
I guess this might be the first proof of a new SBK. I've been waiting to see if it did actually change.
Rommark: A bit more info would be nice, script output, etc.
Here is my question: will trying to issue nvflash commands under the wrong encryption brick my device? I want to try to root but I don't want to brick my tab!
Sent from my MB860 using XDA App
msticninja said:
I guess this might be the first proof of a new SBK. I've been waiting to see if it did actually change.
Rommark: A bit more info would be nice, script output, etc.
Click to expand...
Click to collapse
For what i know the output of nvflash on the new B70 is:
Nvflash started
[resume mode]
connection failed NvError 0x8
The same error if you try an incorrect sbk with the "old" revision of tablet.
P.S. in my naivety i was thinking on some massive brute force: build a script that will brute force a modest number of keys (i.e. ~1000) and distrubute it among all the owners of the new b70 so any device would try a reasonable number of keys. Soon I discovered that the SBK permutations are 16^32 = 3,4028236692093846346337460743177e+38 = 3402823669209384634633746074317700000000000000000000000000000000000000
CinderWild said:
Here is my question: will trying to issue nvflash commands under the wrong encryption brick my device? I want to try to root but I don't want to brick my tab!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No, it exit with an error and does absolutely nothing on your device.
Ok thanks for the response, I'll try a simple backup tonight and see what happens.
Sent from my MB860 using XDA App
and I thought that ASUS is an "open minded" company :/
rommark said:
and I thought that ASUS is an "open minded" company :/
Click to expand...
Click to collapse
If you have experience with their routers, you'd think that too. This stance really has me confused. Hell, they even flaunt how much they "love the DIY community" here: http://promos.asus.com/US/ASUS_DD-WRT/index.htm
rebound821 said:
For what i know the output of nvflash on the new B70 is:
Nvflash started
[resume mode]
connection failed NvError 0x8
The same error if you try an incorrect sbk with the "old" revision of tablet.
P.S. in my naivety i was thinking on some massive brute force: build a script that will brute force a modest number of keys (i.e. ~1000) and distrubute it among all the owners of the new b70 so any device would try a reasonable number of keys. Soon I discovered that the SBK permutations are 16^32 = 3,4028236692093846346337460743177e+38 = 3402823669209384634633746074317700000000000000000000000000000000000000
No, it exit with an error and does absolutely nothing on your device.
Click to expand...
Click to collapse
Many of the B70s have used NVFlash correctly. Some people that thought it wasn't working were actually using the --resume command before establishing a connection to resume, so they thought it wasn't working.
That's why I'd like to know the OPs script and error output to see if it's a new SBK, or an incorrect script. I already know what the output will be if it's truly a new SBK.
msticninja said:
Many of the B70s have used NVFlash correctly. Some people that thought it wasn't working were actually using the --resume command before establishing a connection to resume, so they thought it wasn't working.
That's why I'd like to know the OPs script and error output to see if it's a new SBK, or an incorrect script. I already know what the output will be if it's truly a new SBK.
Click to expand...
Click to collapse
Well, in my thread in the dev section i have got 2 B70 who can't nvflash :
http://forum.xda-developers.com/showpost.php?p=16297657&postcount=52
http://forum.xda-developers.com/showpost.php?p=16428731&postcount=116
plus one user who PM me saying he owns a chinese (original) model and got the same error (but here i don't know if it's some china-only restriction).
and one who can:
http://forum.xda-developers.com/showpost.php?p=16322484&postcount=67
My script is correct; if the tablet weren't connected or weren't in apx mode the error should be different (i can remember 0x3 or something).
So the new B70s are among us
msticninja said:
Many of the B70s have used NVFlash correctly. Some people that thought it wasn't working were actually using the --resume command before establishing a connection to resume, so they thought it wasn't working.
That's why I'd like to know the OPs script and error output to see if it's a new SBK, or an incorrect script. I already know what the output will be if it's truly a new SBK.
Click to expand...
Click to collapse
This same folder and files worked on tf b5 b4 replacement....
rommark said:
This same folder and files worked on tf b5 b4 replacement....
Click to expand...
Click to collapse
Thank you. That's what I needed to know.
rebound821: I wasn't saying anything about your script. Once again, I was asking the OP, because he didn't say whether he was using a script, using the backup method, etc., and he didn't say whether is was the 0x4 error.
I understand being defensive about your scripts, and I know there are B70s with new SBKs, but I was trying to help the OP make sure his problem was due to the SBK, and not something in his methodology.
I'm not trying to flame, believe me, but if I ask the OP for information about his methodology, please don't reply with guesses about what he's actually doing. From his post, for all we knew, he wasn't necessarily using your script.
just got my replacement b70 through the post, I had a b60 that I had to return because the charger packed up
i an in the UK, so the tablet has the WW firmware tried the Nvflash method and it didn't work for me either
I also got my b60 replaced with a b70 and now I can't nvflash
It's a WW from Portugal...
Brand new TF bought in Norway, ofc a B70 & completely locked...
Which annoys me to no end....
Sent from my GT-I9100 using XDA Premium App
Bought a new TF in Belgium also of the B70 series and it's locked + the SKU starts with TB.
Hi guys and gals.
I'm quite an experienced android users. I owned Galaxy I9000 and now I own Galaxy I9100. I flash ROMs, I root my mobile with various Kernels and stratup scripts. I OC/UV my CPU as well and familiar with CWM mode. Basically, a power-user
I got my eee pad as a present this week and I would like if someone can bring me up to speed about basic kerenl for rooting and advanced feature kernel that is popular among the users here.
How to get into download mode and recovery mode.
I did some searching and came up with many results, however, I would like a pointer or two so I could save me up some reading time.
Much appreciated
Depends on your device serial. If yours statrting with b70(some)/b80/b90, then you can do nothing at this time.
And a little reading in the development sub-forum, will answer most of your questions.
Anything above b70 cant be rooted. I hear some of teh b70 can but not sure..
ROMS.. the 3 top ones I can think of are Prime, Revolution and Revolver. Clemsyn and Blade kernel are popular.
Mine is B70.... so is there anything I can do at all?
Run SBKDetect from the evelopement thread - if it says SBKv1, then you can, if says SBKv2, then you can't
Anyway, you can try BRK's toolkit and if you get a write error, then you can't root it now.
Ok ill try that. Right now im with v3.2.1 is there a date for ICS version?
Sent from my Transformer TF101 using Tapatalk
Asus said "very early" - speculations are that sometime in December.
Do you have an explanation as to why is this device a bit laggy? I only have the email+weather widget and it's quite out of the box homescreen icons but it feels that the scrolling is a bit laggy...
No, I don't have lags at all, so I can not explain your issue.
It says that the SBK detect is for linux (?) how can I run it?
Can you describe the lag? I've no lag with my TF at all. Here's a demo video I made.
No lag at all.
gil80 said:
It says that the SBK detect is for linux (?) how can I run it?
Click to expand...
Click to collapse
There's also a version for Mac.
But I'm on a PC....
And as for laggin I mean that when scrolling it is not as smooth as I would expect or like Ipad2. and I feel that if I will add one more widget... it will simply wont move.. there's this delay from the gesture of scrolling to the actual scroll
If in browser, a fully up to date (or at least Prime ROM) system it isn't so bad any more but for best, use Opera Mobile.
If in home, I've seen mention of it being a HC problem that was later updated away or sth, someone please chime in.
If in every app, something is frakked.
Sent from my Transformer TF101 using Tapatalk
baseballfanz said:
There's also a version for Mac.
Click to expand...
Click to collapse
I need a PC version. Is there any?
No, I don't believe there's a Windows version of the SBK detect script available.
Does anyone know if running the following command using nvflash would fail if he has an SBKv2 tablet?
Code:
nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
I have a B7O tablet that is SBKv1, so it has always worked for me, and I have no way of knowing if it would fail for an SBKv2 tablet.
gil80: One thing you could try to do is download an Ubuntu LiveCD (or any other version of Linux that has a LiveCD available). If you boot your computer from the Ubuntu LiveCD (or it can be installed to a thumbdrive if your computer can boot from USB), you could go to the xda site and download the SBKDetect script and run it. Keep in mind that anything you download using the LiveCD disappears when you shut the computer down (if you use a thumbdrive, it's possible to create a persistent data partition on the thumbdrive so that stuff you download is saved instead of discarded.
This would allow you to use Linux just long enough to run the SBKDetect script to find out if you can root your TF. If you have no Linux experience, then this might be too much for you, but if you have ever used a terminal emulator in Android, you have enough experience to use the SBKDetect script in a temporary Ubuntu Linux environment.
gil80 said:
It says that the SBK detect is for linux (?) how can I run it?
Click to expand...
Click to collapse
you can run install linux in a vmware machine, i use ubuntu
The Asus transformer file system is RFS or EXT4?
gil80 said:
The Asus transformer file system is RFS or EXT4?
Click to expand...
Click to collapse
Depends on where in the filesystem you are/what partition you are talking about. The "/sdcard" partition is vFAT or FAT32, I believe... this makes it so that a Windows computer can use the partition as an external USB hard drive or USB flash drive. The same is generally true for external media, such as MicroSD and SD cards, but you have the option of formatting those as NTFS yourself if you prefer (or any other filesystem that the ROM you are using recognizes).
When you get down into the root partition/root of the filesystem ("/"), you are looking at EXT4 (possibly EXT3... again, depends on the ROM). Other partitions on the internal flash memory may use yaffs/yaffs2 (I have seen this when searching the Googlies, but I have no experience with any partitions that use it... I have only ever messed with the LNX partition, which is 6 on the TF101-A1), and yet others are encrypted.
A ROM developer would be able to tell you exactly what partitions use exactly which filesystems, but I am pretty sure that EXT3 or 4 and vFAT or FAT32 are used.
Hey Guys,
I wanted to prepare my TF101G for being sold. So I deleted all the files on the internal storage. Then I went to the recovery and performed a factory reset.
So far so good.
I then unfortunately thought it might be a good idea to format the /system as well. I know it wasn't a good idea.
I tried now various solutions but nothing worked.
What I tried so far:
-pushing a update.zip via ADB. Doesn't work because ADB doesn't see my TF.
-various scripts like wheelie and others. I installed the drivers successfully but when I want to run one of those scripts the connection brakes up and I have to boot into APX mode again.
My TF101G is a BAO which was running Megatron 1.1.6 before the wipe.
The current bootloader is 9.2.2.4
The recovery which still works is I think the touch version from this thread.
http://forum.xda-developers.com/showthread.php?t=1213723
It can't access the SD card.
I hope someone can help me to get my transformer back to life.
I still have a backup on my SD card which I saved in case that the new owner doesn't wants it after a 1 week trial.
formatting system should have no effect on wheelie/NVFlash. Maybe try it on another computer
I tried on the same computer but under Ubuntu instead of windows.
The output is:
Code:
[email protected]:/home/XXX/android/wheelie# ./wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x428008244002117
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
oops didnt see the G for some reason
Wheelie doesn't work on the Tf101G... i think you should get doom in here he would be of more assistance than i can be
Well you have recovery, so go into that and adb push a working stock-based rom (I recommend arhd) then once that's working again you can try the downgrade again.
Thing O Doom said:
Well you have recovery, so go into that and adb push a working stock-based rom (I recommend arhd) then once that's working again you can try the downgrade again.
Click to expand...
Click to collapse
thought of that but he said
"pushing a update.zip via ADB. Doesn't work because ADB doesn't see my TF."
Hmm that recovery supports it, afaik. ADB is just about the only chance here with no NvFlash
I'm a bit confused ATM.
The TF is showing in the device manager but I don't get any feedback via adb.
adb is working though just tried it with my phone.
It shows as Asus Transformer ADB Interface.
Does it say offline?
Thing O Doom said:
Does it say offline?
Click to expand...
Click to collapse
Where?
adb devices
It doesn't show anything. Just empty space.
That means ADB drivers aren't set up properly, OR the tf isn't sending an adb signal... :/ This is in recovery?
This is a tough one... almost no way to get a .zip on there without NvFlash...
Nebucatnetzer said:
It doesn't show anything. Just empty space.
Click to expand...
Click to collapse
Did you try adb in ubuntu?
sent while running with scissors
gee one said:
Did you try adb in ubuntu?
sent while running with scissors
Click to expand...
Click to collapse
He mentions above that it works with his other android devices I believe, so I don't think it's a windows issue. Never can hurt to fire up linux though
I noticed that ASUS would change the USB device IDs every so often, so the windows drivers could be out of date by the type a new firmware is pushed out.
gee one said:
I noticed that ASUS would change the USB device IDs every so often, so the windows drivers could be out of date by the type a new firmware is pushed out.
Click to expand...
Click to collapse
Why in the world would they do that..? Nevermind, it's ASUS!
OP definitely try a linux box though, not needing drivers is one less kink to work out.
DSL or Puppy linux in a VM box worst fine
I tried to do on Linux yesterday but I had some trouble getting it running. No idea why though it worked before. I'll try again today in the evening.
Sent from my Galaxy Nexus using xda premium
Thing O Doom said:
That means ADB drivers aren't set up properly, OR the tf isn't sending an adb signal... :/ This is in recovery?
This is a tough one... almost no way to get a .zip on there without NvFlash...
Click to expand...
Click to collapse
Yes in the recovery.
Sent from my Galaxy Nexus using xda premium
Nebucatnetzer said:
I tried to do on Linux yesterday but I had some trouble getting it running. No idea why though it worked before. I'll try again today in the evening.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Great I had to fix adb first. The excluded some things with Ubuntu 12.04....
http://www.hackersgarage.com/adb-no-such-file-or-directory.html
And ladies and gentlemen we got contact!
Hey guys,
About two years ago when the Droid X came out, I came out with a one click root app for it that was pretty popular. Since I have the Galaxy S3 now and wanted to root me phone, I decided to make it ridiculously easy for people.
Credit goes to this thread: http://forum.xda-developers.com/showthread.php?t=1875914
I simply packaged it up into a Qt app. I will be releasing it on Linux tomorrow and if I can somehow get a Mac (or someone has one) that wants to compile the Qt app for Mac, we can have it working on all 3 main operating systems.
Here's the download: http://www.mediafire.com/?g4mfv432lzk2pj0
And some screenshots to go along with it: http://imgur.com/a/7Eq48
Enjoy!!! I will update with the Linux version tomorrow
- Sil3ntKi11
Very nice!
Sent from my SCH-I535 using xda premium
Shouldn't this be in the dev section?
jellydroid13 said:
Shouldn't this be in the dev section?
Click to expand...
Click to collapse
It could be but here is the problem i see...
all current root methods that work for ics will no longer work for jellybean. so when the jb ota drops this will be kind of null and void. not saying you couldnt odin back to a ics build then root and upgrade back to jellybeans, but thats alot of extra steps. the best method imo is to odin mr.robinson's pre rooted stock j1 update.
droidstyle said:
It could be but here is the problem i see...
all current root methods that work for ics will no longer work for jellybean. so when the jb ota drops this will be kind of null and void. not saying you couldnt odin back to a ics build then root and upgrade back to jellybeans, but thats alot of extra steps. the best method imo is to odin mr.robinson's pre rooted stock j1 update.
Click to expand...
Click to collapse
Yeah, I know that. But within a few days a new method will be up and I will update it! If someone finds it useful, then great! When the 4.1 root method (non-odin) is out, then I will put that up!
But yeah, most people after updating won't need this
Will this raise the flash counter?
I can compile the qt app on Mac if you get me the source.
Sent from my SCH-I535 using xda app-developers app
alquimista said:
I can compile the qt app on Mac if you get me the source.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Here's the source attached. Also, if you could send me a link to a copy of adb for mac (just the executable) that would be awesome!
ahfu25 said:
Will this raise the flash counter?
Click to expand...
Click to collapse
To be completely honest I am not sure. I have no triangle on my phone. If it does, you can use:
http://forum.xda-developers.com/showthread.php?t=1494114
To reset your counter I believe. Does someone else want to weigh in on this?
sil3ntki11 said:
Here's the source attached. Also, if you could send me a link to a copy of adb for mac (just the executable) that would be awesome!
Click to expand...
Click to collapse
Here are the most useful binaries from the Android SDK for Mac. Included in tarball:
aapt
adb
aidl
dexdump
dx
I'll try and get the Mac qt build up later tonight.
Ta,
ALQI
I'm having problems compiling on my laptop.
I keep getting the error that my version of OS X isn't supported. I'm on 10.7.4, should I be on 10.6 or something?
Anyway, I have an app built, but the bundle doesn't look right. It doesn't contain any of the root tools, and the main executable is way too small.
I don't want to post it here, cause I doubt its functional.
It looks nice though!
alquimista said:
I'm having problems compiling on my laptop.
I keep getting the error that my version of OS X isn't supported. I'm on 10.7.4, should I be on 10.6 or something?
Anyway, I have an app built, but the bundle doesn't look right. It doesn't contain any of the root tools, and the main executable is way too small.
I don't want to post it here, cause I doubt its functional.
It looks nice though!
Click to expand...
Click to collapse
Hey! Thanks for trying! So I used Qt version 4.8.3, the open source SDK. You need three libraries to run the app, QtCore4, QtGui4, and QtWebKit4. They have to be in the same folder as the executable if Qt isn't in your Path. The root tools are in there, "debugfs", "debugfsinput" and "su" and "Superuser.apk". I didn't include the Mac adb tool, as I couldn't get it. That should be named adbmac and be put in the tools/ folder of where the executable lies.
I have changed the source to make this customizable for anyone's root methods, if you look here:
http://forum.xda-developers.com/showthread.php?t=2000988
Here is cleaner source attached, basically the same. So, in order to get this work:
Build the code
Find the folder it was built into (please use release, not debug)
In that folder, find the executable. This is the main folder
Copy the /root, /tools, /html, /device folders that are in the zip into the main directory where the executable is.
Copy your OSX's adb into /tools and rename it adbmac
Make sure Qt is in the PATH variable, if not you need
QtCore4, QtGui4, and QtWebKit4 in the same folder as the executable
For others to use it, they need those libraries in there, or else they will need to have Qt installed
You can statically link the libraries if you so desire but I didn't want to deal with that.
sil3ntki11 said:
Hey! Thanks for trying! So I used Qt version 4.8.3, the open source SDK. You need three libraries to run the app, QtCore4, QtGui4, and QtWebKit4. They have to be in the same folder as the executable if Qt isn't in your Path. The root tools are in there, "debugfs", "debugfsinput" and "su" and "Superuser.apk". I didn't include the Mac adb tool, as I couldn't get it. That should be named adbmac and be put in the tools/ folder of where the executable lies.
I have changed the source to make this customizable for anyone's root methods, if you look here:
http://forum.xda-developers.com/showthread.php?t=2000988
Here is cleaner source attached, basically the same. So, in order to get this work:
[/LIST]
Click to expand...
Click to collapse
Ah, that's my problem. I'm still on Qt 4.7 cause the QtADB tool requires the 4.7 libraries. I can update to 4.8 , but it will take a while cause Macs are dumber than Linux.
Question, can't we roll the libraries into the app itself? I know Avid MediaComposer 6 and up have Qt pretty much rolled into the app to run all of the GUI, they even use some python to run some of the GUI for them (its crap for code but its better than FCP X). I'll look into it while I'm waiting for Qt 4.8 to download and install.
I'll keep you updated.
Ta,
ALQI
tplawi then
alquimista said:
Ah, that's my problem. I'm still on Qt 4.7 cause the QtADB tool requires the 4.7 libraries. I can update to 4.8 , but it will take a while cause Macs are dumber than Linux.
Question, can't we roll the libraries into the app itself? I know Avid MediaComposer 6 and up have Qt pretty much rolled into the app to run all of the GUI, they even use some python to run some of the GUI for them (its crap for code but its better than FCP X). I'll look into it while I'm waiting for Qt 4.8 to download and install.
I'll keep you updated.
Ta,
ALQI
Click to expand...
Click to collapse
Hey! Thanks for the effort. So I actually got a VMWare image of Mac OSX Lion going on my machine and got it to compile. What you are referring to is called static linking and can definitely be done, I just have to compile from source with the -static argument. I'm trying to decide if I should not use WebKit for my GUI as that is the only library that is quite large. I'm going to compile it statically and see how big it is. I might put this up on a private GitHub repo if you want to help work on it.
My idea is that this can be used by anyone to make other root packages. If you noticed in the other thread I sent you, I basically have a very simple custom batch language for them to create for the root method and the rest is taken care by the program. This way it won't discourage people and we can have a one click root truly. Let me know if you want to help me improve it!
Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.
Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.
Install Instructions:
First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.
Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...
Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.
Download ME302C-US-Root.img.gz from MediaFire (see below)
Install the Minimal ADB-Fastboot into a folder (google this you're on your own)
Install the ASUS USB Drivers (google this you're on your own)
Place the image file in the adb/fastboot folder (do not decompress, install as is)
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
SuperSU v1.86 Chainfire (required for all other apps to work)
Root Checker (run it to confirm you have root)
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).
Enjoy your Rooted MemoPad!
Download the image file from here:
http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz
If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.
Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!
gbkelley said:
Yes, folks after two days of trial and error I finally was able to build a system image file from the US OTA update that you install via fastboot. All I need to do now is find a free file upload site to host the file for you to download.
Install Instructions:
Download ME302C-US-Root.img.gz from (wherever)
Install the Minimal ADB-Fastboot into a folder (google this)
Install the ASUS USB Drivers (google this)
Place the image file in the folder
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
Root Checker (run it to confirm you have root)
SuperSU
Some app requiring root and run it - you should get a notification from SuperSU to grant su for app
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to replace that by installing BusyBox from the Market.
Enjoy your Rooted MemoPad!
I'll update this post when I have a download url for you.
Click to expand...
Click to collapse
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Turbojugend said:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Click to expand...
Click to collapse
+1
Why not use Mega? Seems to always work and have great speed.
It is rooted...thank you.
Sent from my ME302C using Tapatalk 4
Turbojugend said:
Why not use Mega? Seems to always work and have great speed.
Click to expand...
Click to collapse
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
notten said:
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
gbkelley said:
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.
Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Thanks a lot for all of this gbkelley. Cheers!!
notten said:
. If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Click to expand...
Click to collapse
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Links if you don't want to google it
Minimal ADB and Fastboot
How to install USB drivers
tdamocles said:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
Hide battery work for you?
Got Root, Thanks so much.
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Turbojugend said:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Click to expand...
Click to collapse
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
notten said:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
Click to expand...
Click to collapse
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Turbojugend said:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Click to expand...
Click to collapse
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
notten said:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
Click to expand...
Click to collapse
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.