Frank's Tools
This is a compilation of methods used to modify, install and recover your system on the TF101. This is a one click root, ubuntu installer and dianostic/custom set of tools. I did not make any of the ROM's, NVFlash, ADB, aBootimg or any other tools inside of this installer. I just make the user friendly interface and easy to use process for modify your TF101.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*****THIS METHOD IS DESTRUCTIVE TO DATA***** THIS WILL ERASE ALL OF YOUR DATA AND INSTALL A FRESH COPY *****
YOUR ARE RESPONSIBLE FOR ANY DAMAGE THAT MAY OCCUR WHILE USING THIS PROGRAM. MYSELF NOR ANY OTHER PERSON OTHER THAN YOURSELF IS LIABLE FOR ANYTHING THAT MAY OCCUR DURING ITS USE.
What you need:
Nvflashable ROM
Ubuntu Filesystem
SBK1 system
Instructions:
1.) Extract archive to a location of your choice.
2.) Put Ubuntu.img and ROM into main folder ( Ubuntu, system, boot and recovery IMG ).
3.) Run the tool.
4.) Do whatever you like
*note: Ubuntu may have to resize the partition. Let it do its thing it may take a couple of minute to do it.
To use Ubuntu you have to press power and volume down when booting. And then press volume up.
Error Reporting Format
1.) Operating System (PC):
2.) SBK Version:
3.) Model:
4.) Transformer Storage Size:
5.) Install Option chosen:
6.) Problem:
7.)Command Output:
- Provide as much information as possible, also if possible pictures are always good.
################################################## ##############
NVFLASH AND ABOOTIMG IS PROPERTY OF THEIR RESPECTFUL OWNERS.
Release notes:
Version 1.1.3
-Dualboot - Android as Default, Ubuntu as Secondary. *Fixed Bootloop
[Carried over from previous version]
Version 1.1.1
-Basic Install with Android as default and ubuntu as secondary.
- Android only install
- Detailed install process
- GUI for aBootIMG and NVFlash* Simple, but still a GUI
- Added Keyboard button for starting the virtual keyboard inside ubuntu.
##DOWNLOADS##
*Due to recent events i will no longer develop this tool. I am releasing the source so everyone can benefit from it. Please if you use my source give me some credit. Part of the reason i am stoping the development of this tool is because to much of my time is being spent on it and causing problems. So here you go guys, merry Christmas...
Frank's Tools SOURCE - VB
Frank's Tools Version 1.1.3
Lilstevie's Thread - Ubuntu Filesystem(Ubuntu.img)
oh my god!you released this,the same vday that i try to put ubuntu on transwformer....i have windows and this,is a big news!hi have a question--ubuntu.img that is HERE...is ok?i put it in main folder?and system.img,you mean the system.img of a nvflashable rom like prime or revolver and i should put it also in main folder?
Hi there,
Sounds like a great tool and im very interested. Can you dual boot with ubuntu and the current rom?
Does it replace CWM ?
Is thereanything to prepare, before installing etc?
I was also wondering if this just completely wipes the tablet and puts only ubuntu or whether it can dual boot. Dual boot would be awesome.
Sorry should of been clearer it uses prime and it is dualboot. Ubuntu is primary. The ubuntu img is from lilstevies thread. Ill update the original post with links.
Can you make an option so that prime is the default and android is secondary?
Where do I get the .imgs? Could've at least linked to them.
The system.img file is a nvflashable rom like prime. The ubuntu img is from lilstevie's thread "Ubuntu on the Transformer". As for the Dual-boot with android as default it will be on my next release. Its a long story on this release. I had alot of options for this release, but it would take alot longer to get it all finished. So i released this mini-version just to let people play around with a little bit. My next version with have a bunch of options along with a GUI interface for ADB and NVFlash.
So will this only work on devices with SBK1?
Correct. As of right now it is on SBK1
frankc123 said:
Correct. As of right now it is on SBK1
Click to expand...
Click to collapse
So it probably won't be possible on an SBK2 device until it is cracked?
This is exactly what i been waiting on gonna try this asap, thanks boss!
Edit: I just hook the transformer up to computer in nvflash mode and click intall?
Sent from my Revolver Powered Asus Transformer
As of right now sbk2 devices does not work with this install method.
Anyone that has used the tool i would like some input if its working for you or if you are having any problems with it.
I need SBK2 cracked lol
Hmm looks like mine is an sbk3
What would have happened if i had tried to flash this ?
hmm maybe i've been out of the loop for the past few month but what is SBK1/2/3 ?
also, i'm already running revolver, would rather keep this intead of prime... is there anyway of installing this without loosing all the data on my revolver install and keeping revolver?
i wait your next release,with android how primary OS.....
So, what if we did a nandroid on our current rom and pulled the system.img from the backup, would that work?
Danny-B- said:
Hmm looks like mine is an sbk3
What would have happened if i had tried to flash this ?
Click to expand...
Click to collapse
where does this SBKv3 come from? I have not heard of devices with yet another SBK, unless of course you are referring to the SL101 or TF101G, but those devices wouldn't be SBKv3, they would be SBKv1 for those devices, the nonclementure for the SBKs are TF101 SBKv1 (The currently known key) and SBKv2, the definition of them is relative to the device itself, as that is key v1 and key v2 for the TF101
sorry i might be wrong. I did a search and found a thread that said it could be sbk3 ...
My serial number is B70KAS309901
Related
Since msullivan's guide is generalized for all devices I thought I would tailor one specific for our Evo's.
I take no credit for any of this except for what is my own personal experience. 99% of the following has been taken from the original thread HERE
I have not tested this on an AOSP rom nor gingerbread for that matter. If anyone has confirmed it working I will add to the list. Supposedly CM7 cannot find the image file, if that's the case the resolve should be: In Android the "real" location is often /mnt/sdcard, and then the /sdcard mountpoint is added for simplicity. So yeah, my guess would be that Cyanogen doesn't have the /sdcard mount. You can fix your issue by opening the file "bt" in a Unix-compatible text editor (such as Notepad++, or an editor on the phone itself), and replace all instances of "/sdcard" with "/mnt/sdcard".
Working so far:
Froyo Sense (MynsWarmTPTRls5)
Evo Deck (gingerbread) 1.2f
CM7 (gingerbread) Thanks DoManOfFuture
WARNING: THIS IS NOT FOR THE FAINT OF HEART
UPDATE: My goal was to create a version of BackTrack 5 for ARM that was easy to use and install. As of this time, that IS NOT the case! The versions posted here are **probably not** going to work straight out of the box. If you know what you are doing in a Linux environment, you'll probably be able to get it working.
Because of this, the project is currently completely unsupported. You are free to dive in, but you are doing so with no support for me, and I'm not liable for any damage that might be done to your device's ROM.
I encourage you to pass this up unless you know what you are getting yourself into!
If you were referred here from the XDA-Developers.com article...
Hi there! Let's get one thing on the record here... this is *not* a native client! This is the chroot + VNC method that we'd been using to get Ubuntu running with Android for a while. The article makes it sound like that's the case, but sadly it's not. However, with the chroot + VNC method we can really run BackTrack 5 on an Android device, and it really does work. This takes some technical skills, and isn't for the non-Linux experienced user.
Requires a rooted device!
BackTrack 5 installation guides are making their way around this forum. I've tried to synthesize it all, but I've also added my own touches to help with usability and features, along with a workaround for the "ioctl LOOP_SET_FD failed" error message some people have been getting.
In theory this build is nearly universal, so if you have an Android device it should work. I've put it all in one zip file that you can download directly from my website, no hassles or wait timers.
If you are interested have a look, feel free to re-post. Credit goes to the BackTrack team and xda member anantshri (he's got skills, give him props guys), who built the base image file.
If you like what you see help me out, hosting is expensive!
http://www.mattslifebytes.com/donate
(alternatively, you can show interest in the products and services featured on my website, if you know what I mean )
Click to expand...
Click to collapse
Instructions:
BusyBox-
First things first you'll want some of the prerequisites one being Busybox. I'm currently running Myn's Rls5 Rom. All I had to do was go to the market and install "BusyBox Installer." Open that and install the latest version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Terminal Emulator-
If you do not have one go to the market and install "Android Terminal Emulator"
VNC-
You'll also need a VNC client. Go to the market and find a suitable VNC Client. "android-vnc-viewer" is a good one.
Starting Backtrack5-
After you have the zip downloaded you'll want to unzip it and place the "bt5" folder on the root of your SD Card.
-Next open your terminal emulator and type “su” <enter>, “cd /sdcard/bt5″ <enter>
-Now enter “sh bt” <enter> (in the future to start BT5 skip the line above and come straight to this command)
-enter "y" when it asks you if you want to start with VNCserver.
Note: I had already ran this before which is why your screen may look different
-Now all you need to do is open your VNC client and connect with the following info:
127.0.0.1:5901 pw: root
When you are finished go back to terminal emulator and type "exit"
Click to expand...
Click to collapse
DOWNLOAD:
Direct HTTP Links:
http://brilldoctor.co.cc/Files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
http://www.shenye.co.uk/files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
Mirrors:
http://www.megaupload.com/?d=M6YCKZLR
[/LIST]
Thanks
I'm running CM7, and am a very competent linux user so I'll give this a shot. I'll post back with the results. Doesn't seem complicated, well getting it running at least, maybe the build process was, but I'll get back with the results none the less.
Update: Works like a charm.
Updated compatibility list. If anyone is running a different rom and these instructions worked for you let me know so I can add it in. Thanks!
Just thought I'd mention, using your guide, this is running perfectly on my Nexus S running 2.3.4 (rooted, deodexed and zipaligned). I have the UI up in the VNC viewer and also can SSH in from my mac too.
Running BT5 on a Nexus S (9023i) with CM7 nightly 88 no problem. It is not very quick, but hey, it works.
Install was not to difficult at all, just download, unzip, run "sh bt", and connect with VNC
so i got it to work on ava-z3 but when in backtrack i tried to run console commands and it didn't work maybe i did something wrong or its just not supported for the phone may be someone can help if they can i was trying to crack my own wep and i have done it many times on my computer but when i tried it on the phone it didn't even recognized basic commands i get it you can run backtrack 5 but what are you able to do with your phone can annyone explain and advice me ?
*rubbing hands together* downloading now. Hope it works on the n1
Sent from my Nexus One using XDA Premium App
Just so you guys know you cannot crack WEP with this. This method CANNOT have direct access to your wifi card therefore it cannot support a lot of the methods used to crack, etc..
This is backtrack5 running on top of your android rom.
Just thought I'd make that clear to those thinking they have a mobile cracking OS That's what netbooks are for lol!
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
i dont know about the mac version but there should be a readme in there for installation. also i think the mac needs codeless kext installed. should be outlined in the readme but couldnt tell you for sure.
I followed the instructions as best as I could understand. The UI pops up but refuses to flash or even recognize my phone.
re: flashing rom
tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
Since you have a mac it would be a lot easier for you to flash a
clockworkmod type custom rom.
You must have clockworkmod recovery to be able to do this.
If you are running stock rom and already have clockworkmod
recovery in your phone then then you can BACKUP your stock
rom with clockworkmod and then flash a new custom rom
as long as its a clockworkmod rom zipfile.
Most all of these custom roms you see here on xda are all
clockworkmod types (zipfiles) which do NOT need ODIN
or Heimdall at all.
But you do need to have a usb card reader if your your
computer is not reconizing your samsung phone as an external
USB drive.
If your Mac computer does reconize your phone as a external
USB device then you do not need to remove the microSD card
and you do not need a card reader.
I am sure you know how to use a usb card reader so I will not
go into that now.
Here is the link to the most popular custom rom for Infuse
which is the type you need. (clockworkmod flash)
http://forum.xda-developers.com/showthread.php?t=1195571
Follow the easy step by step instructions to a "T" if you
don't want to start all over and have to do it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good Luck,
Enjoy!
Please don't forget to give me a big THANKS if this post was worthwhile reading!
----------
Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.
tight686 said:
Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.
Click to expand...
Click to collapse
You are already on a rooted rom. Just get sgs lernel flasher and flash a "rainbow fix kernel." But id try to get heimdall working. it is super easy on linux. I love the debian package system.
If it doesnt see the device it sounds like an issue with that "codeless kext" which is described as being like a driver. that is unless samsung dropped the ball on the boot loaders again. the bootloaders in the odin oneclick packages for the galaxy s would prevent the device from being visable on a mac in download mode. later versions had this fixed. if i had a mac id help. i think the mac is a great system but i just dont know enough about your problem.
there is always the bootcamp or virtual machine options. if you need windows maybe i can help out if you pm me. or yu can do a quick install of mint or ubuntu which is not only more similar to mac than windows but with no need for drivers and the debian packages is easier to install heimdall on than odin is in windows.
or maybe you can contact the developers of heimdall.
tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
what version of heimdall did you download? i ask because it seems 1.3 wants a firmware.xml file that specifies compatible devices, could be an issue of it looking for that file. i still use v1.1.1, i just updated to 1.3 but dislike it and am going back, will see if 1.2 is compatable with the 1.1.1 frontend because it doesnt appear to have a frontend package.
edit:
yes v1.2.0 comandline seems to work with 1.1.1 frontend, install 1.1.1 and then you may upgrade to 1.2 (atleast that's how it works under linux)
Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.
tight686 said:
Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.
Click to expand...
Click to collapse
most use ubuntu. debian packages but there own repositories that are less likely to provide unstable updates to break your system.
Hi
Here are the nvflash versions for the .17 update. For those that wanna go back to stock for warrenty or have a dualboot this can come in handy.
I've tested the WW version on my on transformer and it worked (got a B70 with SBK1) created the US and TW version the sameway with the same config files so it should work! LET ME KNOW IF IT WORKS FOR YOU
But remember i'm not responsible for any bricks flashing my causes and you do this on your own riks.
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
I'm hosting them on my own server:
http://www.xdafileserver.nl/
*Added US version, and TW version
Thanks
.
Worked great on a B60 and a B70.
Thank you.
Sent from my Transformer TF101 using Tapatalk
not for TF101G - B90 ?
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Korumera said:
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Click to expand...
Click to collapse
oow.. thanks for the reply..
mine still in stock, but HC 3.2.1.. i thought ICS for TF101G already available for certain countries..
thanks a lot anyway..
@Korumera
I want to create JP version.
Can you tell me how to create ?
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
rdosti said:
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
Click to expand...
Click to collapse
Yes
NVFLASH'ing removes every partition and restores the orignal one.
Windows won't allow me to install the driver. It says the third-party INF does not contain digital signature information, and it doesn't give me an ignore and proceed anyway option. Any ideas? I'm doing this from device manager.
Edit: if anyone else has this happen, rebooting to boot options (the screen that lets you boot into safe mode and such) there is a setting to disable signed drivers. That worked for me.
This is so useful. Thanks.
Really good job! Thanks man!
nicely done! I was thinking about creating one for this version but I got tied up with work.
No problem
Hope it comes in handy!
and chadster214 work comes first at least they say so haha
Hi!
ROM: NVFLASH_ICS_9.2.1.21_WW_NOROOT
CWM Recovery ICS - Stock?
Edit: When i press power+volume down for 7 seconds (aprox) show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Thanks a lot. Fixed a issue for me. No matter what I flashed I couldn't get the wifi to work again. Just stayed in a state of trying to turn on.
Tried and tested the WW version; no problem at all.
Korumera said:
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Click to expand...
Click to collapse
I install the new NVFLASH_ICS_9.2.1.24_WW_NOROOT
My recovery it's the same, how is the recovery stock? you have screens?
I read that is normal in stock (android with admiration sign)
Thanks in advance, sorry for my english
This process works fine. A few things to keep in mind:
1) Unzip the .7z file in a folder in a folder at the root of your hard drive: I typically open my Windows boot drive, create a new folder, name it "nvflash" and dump the archive's contents into it. This avoids getting errors as a result of the Windows folder/file path being too long.
2) Timing is important when connecting the tablet to the computer: on Windows 7, I simply press the power on+volume up buttons for 2-3 seconds (up until the "new hardware found" bubble appears in the tray area), I then let go and make sure the screen remains off (*VERY IMPORTANT*).
3) To install the Windows driver for my TF101, I go to Device Manager, right-click on the APX icon (it should show a yellow exclamation point), update the driver by pointing Windows to the /usbpcdriver folder (e.g. c:\nvflash\usbpcdriver, for example), let Windows finish the install and ONLY then start the flashing process by running download.bat in Administrator mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there, this is a beta version of a tool that I made.
It's designed to be used by people that are unfamiliar with Wheelie or Nvflash.
This is a tool designed to automate the process of unbricking your device, flashing a new firmware, or flashing recovery.
This tool uses Wheelie and Nvflash.
Credits to Androidroot.mobi for Wheelie and Nvidia for Nvflash!
Thank you AndroidRoot crew for reviving my tablet.
WARNING: ONLY USE THIS ON TF101 DEVICES - IF USED ON OTHER DEVICES YOU WILL BRICK IT
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Does NOT work for:
TF101G (TF101 3G)
SL101 (TF101 Slider)
Requirements:
APX Drivers ( I recommend using these )
Flashing recovery:
Start EasyFlasher.
Follow the simple instructions (click the buttons)
???
Profit! If you want Root, download latest Superuser, put on sdcard/internal storage and flash from CWM.
Instructions for unbricking/flashing ASUS stock firmware.
Download the latest ASUS WORLDWIDE Firmware [yarr.fjolstad.no - direct https]
Mirror [MEGA]
Put the .zip inside the "asusupdate" folder (inside EasyFlasher folder)
Do _NOT_ UNZIP it. Else this won't work.
Click the "Flash Asus stock zip" button in EasyFlasher and it'll do the rest of the job.
Screenshot:
Download:
Latest version always available on my site: https://yarr.fjolstad.no/pub/EasyFlasher-0.8.3b-STABLE.zip
NOTES:
Even though I test every release before I release it, please note that some things could be broken.
I am not responsible if your device is bricked, (although that should be impossible unless you can't get into APX mode for some reason)
Changelog:
Code:
[B]Version 0.8.3*[/B]
Fixed progressbar
Rewrote some code to fix XP issues
Fixed some minor issues
[B]Version 0.8.2*[/B]
Removed some unused code
Added official TWRP 2.2.1 & Roach CWM recovery
New GUI again
Removed Ubuntu button (separate app. coming)
[B]Version 0.7.1[/B]
Added TWRP 2.2 recovery
Removed backup/restore - Use recovery instead guys, it's much faster and nvflash is.. buggy when reading large partitions. Might still add a flash function.
Added most of the code for ubuntu dualboot, however the function is not yet implemented, I need to test it some more, PM me if you want to betatest.
Rewrote some code
[B]Version 0.6[/B]
Code for backup/restore added, needs further testing.
Cleaned up the GUI, again. still ugly.
[B]Version 0.5[/B]
Did some work on the GUI, still ugly
Added OneFlash - unbrick/restore to stock in 1 click.
Wrote code for superuser autoflash, needs more testing.
Want to be a beta tester for future features? PM me :)
[B]Version 0.4[/B]
Released first public beta, everything should work.
Recovery Flashing Added.
[B]Version 0.3[/B]
Added SBK Selection
[B]Version 0.2[/B]
Rewrote how I use wheelie/nvflash
new GUI
[B]Version 0.1[/B]
Test GUI
Wheelie added.
nice!......wont try it but i can appreciate how much easier it will make things
Good alternative to my tool Nice work. Works well
Yeeha!
After days of frustration and a marathon 6-hour run today, I finally got a working recovery. You are so my hero!
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Never donated to anyone before but thought I'd throw you a beer or so. No donate button though.
Emandab1 said:
After days of frustration and a marathon 6-hour run today, I finally got a working recovery. You are so my hero!
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Never donated to anyone before but thought I'd throw you a beer or so. No donate button though.
Click to expand...
Click to collapse
Thanks But I'd appreciate it if you donated to AndroidRoot instead, they are the reason why all of this is possible, they worked hard on Wheelie.
You can donate to them here if you wish:
http://androidroot.mobi/donations/
Am I understanding this right? This will make NVflash usable on my B8O?
Works on any Tf101, not the Tf101G or slider. Any tf B20-C14912409214012949 though
THANK YOU SOOOOOO MUCH. I am not going to stress about flashing nearly as much now. I was always scared of a bricking chance since NVflash wasn't an option.
Now that I have done this can I use the standard NVflash tool for flashing ROMs also?
Looking forward to trying this. I was wondering, how hard would it be to make an "idiot-proof unbrick" option on this?
Basically I was thinking make it so the user downloads the latest ASUS blob files or whatever it needs, and then have a button that automatically runs the scripts to unpack it and then flash it.
Would it be easily doable? May save a lot of people new to this a lot of headaches
jtc42 said:
Looking forward to trying this. I was wondering, how hard would it be to make an "idiot-proof unbrick" option on this?
Basically I was thinking make it so the user downloads the latest ASUS blob files or whatever it needs, and then have a button that automatically runs the scripts to unpack it and then flash it.
Would it be easily doable? May save a lot of people new to this a lot of headaches
Click to expand...
Click to collapse
This is coming in the next version which will be out later today.
Later today! What's the hold up?
I'm curious. Why do you want the ASUS updates now that we've gotten some good ICS ROMs for the Infuse? To me that sounds like a step backward.
Emandab1 said:
Later today! What's the hold up?
I'm curious. Why do you want the ASUS updates now that we've gotten some good ICS ROMs for the Infuse? To me that sounds like a step backward.
Click to expand...
Click to collapse
Oh it's already out (ver 0.5), I just forgot to tell you guys.
Are there any features that people want added? I love suggestions
whitekidney said:
Are there any features that people want added? I love suggestions
Click to expand...
Click to collapse
I would love to be able to flash ROMs with this tool. Is that possible to add?
Sorry for the noob question but can this be used to downgrade to honeycomb by putting one of the zipped blob files from Wolfs thread in the asusupdate folder?
joefloater said:
Sorry for the noob question but can this be used to downgrade to honeycomb by putting one of the zipped blob files from Wolfs thread in the asusupdate folder?
Click to expand...
Click to collapse
Yep, should work, tell me if you have any error and I'll reprogram it for you.
Putting just the "blob" file in the temp folder should also work.
This works awesome! Thank you so much.
Bah, stupid Android with red exclamation point!
EDIT: Nevermind, I am an idiot. At least now I know my Transformer is SBK2, all is working fine, thanks!
whitekidney said:
Yep, should work, tell me if you have any error and I'll reprogram it for you.
Putting just the "blob" file in the temp folder should also work.
Click to expand...
Click to collapse
I have tried it both ways, with the zip file in the asusupdate folder and with the blob in the temp folder and either way it just hangs and does nothing.
Any help would be greatly appreciated.
joefloater said:
I have tried it both ways, with the zip file in the asusupdate folder and with the blob in the temp folder and either way it just hangs and does nothing.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try running it as admin.
Welcome to bigwheelie for Asus TF101.
Here you will find a utility in both a bash version and a python2 version which will repartition your TF101, giving you much more space where needed for future growth of the software base. The python2 version has prettier output, but functionality is the same for both. To use the python2 version, your environment will need to point any calls to python to whatever the python2 binary is on your particular distro. It currently won't work under python3, only python2. It calls whatever python is set as the default when you type 'python'. You can check with 'python --version'. You may need to, at least temporarily, create a soft link to your python2 to python in your ~/bin directory as root. Check with your distro for instructions. Otherwise, use the bash version which should work on about any modern Linux system.
These are Linux utilities that will handle both SBK1 and SBK2 devices. I have tested both with an SBK1 device. To use, download either zip to a folder on your Linux system. Assuming you named the folder "bigwheelie", then do the following from a terminal:
Code:
cd ~/bigwheelie
unzip bigwheelie.zip
Now plug your device in and place it in APX mode. Easiest way is to power off the device with it plugged into pc and then press volume up and power for about 5-6 seconds. The screen will remain blank. Otherwise, just press volume up and power until the screen goes black then continue to hold for about 5-6 seconds more. Then do this:
Code:
./bigwheelie
You will see this:
Code:
THIS PROCESS WILL WIPE ALL DATA FROM
YOUR DEVICE AND REPARTITION IT WITH
A NON-STOCK PARTITION STRUCTURE.
##### ALL RISKS ARE YOUR OWN!!! #####
##### ENSURE DEVICE IN APX MODE #####
******* REFLASH MENU *******
1) Choose 1 for SBK1 device
2) Choose 2 for SBK2 device
0) Quit
Choice: 1
Choose accordingly to the type of tf101 device you have. If you were actually in APX mode and chose the SBK option correctly, then you should see the process begin and some files moving and then partitioning happening and, finally, the blobs getting written to the device, with an indication of success or failure at the end. If it was successful, then you will see the tablet automatically reboot to Asus ICS stock Android and TWRP_2.8.1.4 will reside in your recovery partition. You will now have the following:
/system 1GB
/cache 1GB
/boot 12MB
/recovery 12MB
You can now reboot into TWRP to flash the ROM or other software of your choice, including larger gapps packages than we were previously able to. The growth of gapps packages sizes and the challenge of keeping TWRP small enough to fit into the stock recovery partition are the main drivers for this.
Enjoy!
Download links:
Filename: bigwheelie-bash.zip
bigwheelie-bash.zip
Filename: bigwheelie-bash.zip.md5
bigwheelie-bash.zip.md5
++++++++++++++++++++++++++++++
Filename: bigwheelie-python2.zip
bigwheelie-python2.zip
Filename: bigwheelie-python2.zip.md5
bigwheelie-python2.zip.md5
Special thanks to bumblebee and rayman for wheelie and other scripts, to nvidia for nvflash, and to Asus for stock firmware blobs.
XDA:DevDB Information
bigwheelie, Tool/Utility for the Asus Eee Pad Transformer
Contributors
sidneyk
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-12-04
Created 2014-12-04
Last Updated 2014-12-04
Reserved
Reserved
Then you did it I'll try
Excellent, new script works perfect! Great Job!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downlaod links added to OP
Download links are now added to the OP.
For Windows how can I do? (PS: it's for curiosity, because I have Ubuntu virtualized...)
And how can I return to old partition table? With restoring Asus Stock blob with nvflash?
Thanks for your work
prendomiao said:
For Windows how can I do? (PS: it's for curiosity, because I have Ubuntu virtualized...)
And how can I return to old partition table? With restoring Asus Stock blob with nvflash?
Thanks for your work
Click to expand...
Click to collapse
I'll post something for Windows later, after a little more testing. Why would you want to return to smaller partitions? Yes, you could use one of the tools available to nvflash an Asus stock rom package back, repartitioning to stock partitions, assuming the tool includes the stock flash.cfg file.
Sent from my SM-N900T using XDA Premium HD app
Thanks (know if it is a reversible process was for curiosity your partitioning method is very useful )
Any news on a Windows version for this? I don't have a spare box to put Linux onto to and use this
Taomyn said:
Any news on a Windows version for this? I don't have a spare box to put Linux onto to and use this
Click to expand...
Click to collapse
Been busy working on kernel. I'll try to get the windows version up in the next couple days.
Sent from my SM-N900T using XDA Premium HD app
Is 12 megabytes enough to be future proof?
Regards
Magissia said:
Is 12 megabytes enough to be future proof?
Regards
Click to expand...
Click to collapse
It's enough to buy us some time. I'm currently building recovery images with kernel and initrd gzipped at around 8.5 mb. That's with Timduru's kernel source. The goal I'm reaching for is to use one kernel source for both rom and recovery. And, also we needed a bigger system partition. The beauty is it can now be changed if we run out again.
Sent from my SM-N900T using XDA Premium HD app
Can't we just throw LVM and ignore the physical partitions? Or would that be too complicated?
Regards
Magissia said:
Can't we just throw LVM and ignore the physical partitions? Or would that be too complicated?
Regards
Click to expand...
Click to collapse
Yeah, was my first thought too. The problem is that the recovery has to reside in a special partition. it is too small to solve the chicken and the egg problem.
doppelhelix said:
Yeah, was my first thought too. The problem is that the recovery has to reside in a special partition. it is too small to solve the chicken and the egg problem.
Click to expand...
Click to collapse
I don't know much about lvm, although I did run across an lvm mod for another device that I considered but I'm not too good with the kernel yet. This works and is simple.
Sent from my SM-N900T using XDA Premium HD app
sidneyk said:
This works and is simple.
Click to expand...
Click to collapse
And elegant. Even if the main development for this device is down to you and tim, a lvm approach has to be integrated into the kernel, either directly compiled or as a module. The forum would be reduced to a "doesn't work" nightmare if people mix lvm-recovery and non-lvm ROM. Your approach ensures backward compatibility. I like that.
doppelhelix said:
And elegant. Even if the main development for this device is down to you and tim, a lvm approach has to be integrated into the kernel, either directly compiled or as a module. The forum would be reduced to a "doesn't work" nightmare if people mix lvm-recovery and non-lvm ROM. Your approach ensures backward compatibility. I like that.
Click to expand...
Click to collapse
Yeah, I've been pulling my hair out trying to get a newer kernel to build and drivers migrated over with not much luck in order to fix seemingly broken selinux support in current kernel, or more specifically proper handling of xattrs and selinux labels.
Sent from my SM-N900T using XDA Premium HD app
@sidneyk - 1st of all, thanks for bigwheelie! Can you tell me why you used 1 GB of space for Cache? Cache was always barely used on my android systems (~50-100mb). Did this change with Lollipop?
GoodSoul said:
@sidneyk - 1st of all, thanks for bigwheelie! Can you tell me why you used 1 GB of space for Cache? Cache was always barely used on my android systems (~50-100mb). Did this change with Lollipop?
Click to expand...
Click to collapse
I read somewhere that cache should be at least 2/3 the size of system for OTA style updates, so I just matched it with system. I don't know if it gets used more with lots of games or not, it always seems to be mostly empty. But, just in case...
Sent from my SM-N900T using XDA Premium HD app