Database Users

Gen1, Gen2, TPT, Root, Recovery, Custom Rom, Cyanogen + Windows Flashing explanation.

Guide(/essay) removed as I don't have this phone anymore, so can't update or change the guide with accurate information, which I haven't tested on my own device first Thanks for all the help from others.

..

..

Restoring tpt functionality
..

These are good explanations, very thorough.
I've picked up on a few things that could be added/edited.
1.) Gen 2 is a newer version of the radio firmware, as well as the different memory map
2.) Add Amon Ra Recovery as an alternative to CWM, I know it's not very popular but I find it good for partitioning.
3.) Add link to Mr Pigfish, https://market.android.com/details?id=com.apedroid.pigfish&feature=search_result
4.) On the Flashing ROM's section, I'd also add 'Go into Mounts and Storage and Select Format System'. Not needed, but recommended for the cleanest installation and hopefully fewer problems down the line.
5.) There's the CM7 Converter thing for people to use CM7 on a Gen 1 phone. It can be flashed via recovery.
6.) Add TPT link for Ginger Stir Fry (Over on MoDaCo) since it's popular.
7.) Remove or clarify 'Gen does not matter' under the TPT section, a few may take this that Gen 1 ROM's can be flashed on a Gen 2 device :/
8.) Put warnings/important things in big scary red writing.
9.) Bold and underline the headings e.g. Gen 1/Gen 2, TPT, Root etc.
10.) Personally, I'd say that the Firmware is more similar to the BIOS than Recovery. Recovery is probably most similar to Windows Recovery Environment.
I'm glad you explained what recovery is since it's a bit annoying when people don't know and don't bother to Google it, hopefully they'll read this and understand. I hope you find my comments constructive.
Partitioning your SD Card.
Why?
To create an EXT Partition for A2SD (Not to be confused with the Froyo Apps2SD).
Why do I want this?
For more space on the phone's internal memory and to allow certain apps like widget's to reside on 'internal' memory which may not be available if they were on the FAT32 Partition used by the Froyo Apps2SD method.
How do I do this?
There are a few ways to do this, I found this method the best. I'd recommend doing this before flashing a ROM with a full wipe to avoid issues.
1.) Create a full Backup in Recovery in case something goes wrong
2.) Mount the SD Card on Windows/Linux/Mac
3.) Copy the contents of the SD card into a folder on Windows/Linux/Mac
4.) Download Amon Ra Recovery - Gen 1 Gen 2 Ensure you download and verify you download the correct version. Flashing the wrong version i.e. Gen 1 on a Gen 2 will cause a lot of problems.
5.) Flash it with your existing recovery e.g. Clockworkmod
6.) Go back to Advanced > Reboot Recovery
7.) Scroll down to Partition SD Card
8.) Select Partition SD
9.) Swap Size 0 MB EXT Partition Size 512 MB/1024 MB - depends on the size of your SD card and the number of apps you have.
10.) Press Home to Confirm. ALL Data on your SD will be erased.
11.) Press back and select EXT2 to EXT3 for the best compatibility with A2SD scripts.
12.) Select USB-MS toggle
13.) Drag and drop the ROM you want to flash on your SD
14.) Disable USB-MS toggle.
15.) Flash .zip from SD Card.
16.) If you intend to use CM7 download S2E from the Market to enable A2SD. Tick the first two boxes in the app. Alternatively, if you want to ensure you have enough space for when the Google Backup & Restore happens I've uploaded the APK of S2E to install BEFORE you flash Gapps.
Enjoy.
BTW are you going to post the guide that you wrote in the first post on MoDaCo? It'll get more views there and subsequently be of more use.
If you have any further questions you can find me on MoDaCo with the same username, I'll do my best to help. I'm not a developer either for that matter.

Hello, hedgepigdaniel from modaco here.
Nice guide, I have a couple of suggestions/comments
I don't know if you are aware, but Gen2 blades do have TPT, they just use a different file format (image.bin rather than the .img and .mbn files). There are not as many custom layourts and such around, but I have just put one up for the purposes of unbricking. For that reason, I don't think its a good idea to recommend flashing via windows as protection from a brick anymore (especially because windows flashing goes horribly wrong every so often).
In the rooting section, why don't you link to kalt kaffes modified z4root instead - since it can root Gen2 blades aswell. For Gen2 blades, ROM manager from market is the the easiest way to install recovery.
I've written an unbricking guide in the last few days (that's where the Gen2 TPT is). You are welcome to make use of that if you like.
Glad I finally got enough posts to post in the development section...

..

TPT is not able to change the lowest level firmware file - partition.mbn. If you try to flash a TPT with a different partition.mbn then it just wont flash. You need windows to change the entire firmware. What wbaw has done (and I just repackaged his work as "custom") is create a mixture of files from Gen1 and Gen2, partition.mbn and the few files that have to match from Gen1, and the rest from Gen2. This makes it possible to TPT a Gen1 phone to a mixture that for all intents and purposes is Gen2. wbaw's TPTs can't be flashed to a real Gen2 phone because they have a Gen1 partition.mbn, but It would be equally possible for someone to make the opposite of what wbaw has made - a image.bin TPT with a Gen2 partition.mbn and co and Gen1 everything else (or just with a different partition layout), but no one has yet done so (and I haven't taken the time to work out how). So right now windows is the only way to go back to Gen1 from Gen2, but it doesn't have to be. More to the point, it isn't the only way to re-flash real Gen2 firmware, because I've now put a Gen2 image.bin in my unbricking guide. That's why I wouldn't recommend that people flash anything via windows with the aim of avoiding a brick.
You can use this tool by fonix232 to convert between multi-image TPTs and image.bin TPTs. If you start out with the multi image files from stock Gen2 firmware then you can create a image.bin that will flash on stock Gen2 phones as I have done.
EDIT: jsut to clarify, It's still fine to flash via windows as per my guide if you want to be able to flash all the TPTs that are out there on forums now, or to repartition or enable fastboot, its just not necessary as a safety measure.

Not sure if this is the best idea for 'n00bs' but there's an excellent partition tool for custom partitions.
http://android.modaco.com/topic/337...ol-windows-only/page__p__1672185#entry1672185
By Ricardopvz
It works with the Windows Flasher and the TPT's.
Instructions for use:
1.) Open the program
2.) Drag the sliders or enter values for the partition layout you want
3.) Press Create files
4.) Open the TPT .zip
5.) Navigate to the directory with "partition_zte.mbn" and "appsboot.mbn"
6.) Replace the existing "partition_zte.mbn" and "appsboot.mbn" with the new ones.
Done.
Also, add How to flash the Gapps package/Where's my Market gone and difference between Stable, Nightlies etc. under the CM section since some people can't be bothered to Google it.
1.) Place the gapps file that you downloaded on the root of your SD Card
2.) Reboot into recovery
3.) Select Flash .zip from SD Card
4.) Confirm
5.) Reboot
6.) Done
What's the difference between Stable, Nightlies, Experimental and Alpha?
Stable versions are those where all known issues have been addressed and resolved. This version is for everyday use.
Test / RC versions are similar to the experimental versions, but are in the final stages of testing before being "stable". There may be a few bugs left, but this version is usually stable enough for everyday use.
Experimental / Alpha versions are those where new features are being added, modified, and tweaked, and there are known bugs that are being worked on. This version is for beta / alpha testers.
Nightly builds are daily compiled builds from source. This version therefore has the latest bleeding edge features & tweaks, but it is also the mostly likely to have bugs and issues.
Click to expand...
Click to collapse

CyanogenMod Tips/Solutions, some from the CyanogenMod Wiki here.
It's slow!
Remove stock launcher "ADW". It slows down the homescreen badly.
Recommended: "Launcher Pro" or "Gingerbread Launcher" from Market.
Omg I flashed CM7 and now I don't have Market!
You need to install the Gapps zip. Sign into your account on the First Time Setup screen and Market will activate
My Wi-Fi doesn't turn off/it's draining my battery!
The workaround for Wi-Fi sleep policy that doesn't seem work is download Green Power from the Market if you want your Wi-Fi off when your screen turns off.
Help, Nightly 1xx doesn't work properly/There's a bug!
They're nightlies, sometimes they don't work properly. Use the recommended Nightly from the Wiki Page or another ROM. Also, refer to the CM7 thread on MoDaCo linked below for possible fixes/workarounds.
I don't know what nightly to choose!
First check the CyanogenMod Wiki listed above the CM7 thread on MoDaCo here.
Read the last five pages on that thread for up to date info and feedback on the latest nightlies.
If you still don't know then post in the CM7 thread. Don't create an entire new thread to ask that question please.

Hi im trying to root my friend's blade. I cant find the file to root. Could you be kind to show the link please?
Guide to Rooting:
Enable USB Debugging:
Settings-->Applications-->Development-->USB Debugging (tick)
Install this Apk:
Install Astro File Browser from the market. https://market.android.com/details?id=com.metago.astro
Download the file on your computer, then copy it across to somewhere on your phone
Browse to that somewhere and click on the file. Open app manager and click install.
After installation, click open.
Tell it to do Permanent Root
Wait for it to reboot
Done.
Sent from my X10i using XDA App

teddymild said:
Hi im trying to root my friend's blade. I cant find the file to root. Could you be kind to show the link please?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'd suggest you use the TPT method here since the process would be quicker than rooting it manually etc.: http://android.modaco.com/topic/337798-gen1-to-gen2-tpt-upgrade/
This will root the phone, install Clockworkmod recovery and put on a new 2.3 ROM as well. I'd suggest you use the Ginger Stir Fry one on that page.
I think z4root would work as well if you don't want to carry out the TPT method.

How's the guide going?

Thank you. I'll try it.
k0zmic said:
I'd suggest you use the TPT method here since the process would be quicker than rooting it manually etc.: http://android.modaco.com/topic/337798-gen1-to-gen2-tpt-upgrade/
This will root the phone, install Clockworkmod recovery and put on a new 2.3 ROM as well. I'd suggest you use the Ginger Stir Fry one on that page.
I think z4root would work as well if you don't want to carry out the TPT method.
Click to expand...
Click to collapse
Sent from my X10i using XDA App

This thread dead?

..

It would be nice to take this thread further.

[TOOL]PERI-0.42 One click root+recovery/fix-bootloops+soft-bricks ALL Devices+.27! :D

TF101, SL101 and TF101G on ICS firmwares anything else is untested.
Also should work on TF201 and TF300T on ICS ONLY!
For Windows, tested on windows 7 x64 bit, xp 32 bit and windows 7 32 bit.
Your data will be retained, unless you wipe in TWRP or something
UPDATE:
Added V0.41 which includes TWRP
Also V0.42 which is even newer TWRP!
apk not working sofar :[
If you have a TF201, or TF300T, this will work still, but you need to replace the included file 'recoveryblob' with a recoveryblob from a recovery from your device (download the .zip file for the recovery you want, and extract the 'blob' or 'recoveryblob' file from it and place in PERI folder, naming it recoveryblob and overwriting the otherone!)
Initiate project-PERI:
Since there's no one-clicks that I've stumbled across, and many people are asking if this-that etc.. works with .24, I've made an easy one-click (ish) that guides you through it and runs the necessary commands.
Thanks to:
Team Rouge (I used their touch recovery version)
Wolf (For his method to flash recovery!)
Roach (Bootloop fix)
Members here for testing help :] (I'm bad about typos...)
Download here (feel free to mirror):
V0.1- Platypus - 13.42MB
Version 0.1
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
V0.2- Elephant - 13.39MB
Version 0.2
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.3- Raptor - 13.39MB
Version 0.3
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.4- Indri - 13.39MB
Version 0.4
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.41- TwrpyIndri - 14.29MB
Version 0.41 (TWRP 2.3.2.3)
V0.42- TwrpyIndri Cutting Edge - 14.15MB
Version 0.42 -- Recommended (TWRP 2.5.0.0)
Just unzip it to a folder anywhere and run the .bat file!
Works with or without MicroSD, just let the device totally reboot (E.G. don't let any commands run at the splash screen or in recovery.)
Fixed reboot confusion in V0.2 -Didn't fix in v0.2, Did fix in v0.3 though
If I did anything wrong, or offended any devs, killed someone's cat, or something else, Please let me know!
Post here with any questions or problems, I tested this and everything worked fine, but still consider it as final? release candidate 4.
Did it work?
This should do everything needed, and all is included in zip!
If you want to skip any steps that you've already done if you mess up, just unplug the USB and pretend that it isn't throwing 'device not found' errors, then get back to where you were.
If superuser isn't installing but you have recovery, try 'fix permissions' in recovery. -- Fixed (hopefully) in V0.2
Read the readme and run as administrator! Video-tut is here!
**Also attached to thread.**
PERI - Changelog --
Code:
[*][B]V0.42[/B]
-- Added [I]cutting edge[/I] TWRP 2.5.0.0
-- Thanks jazzruby
[B]V0.41[/B]
-- Added TWRP 2.3.2.3 recovery, finally c:
-- Fixed a couple typos.
-- Fed a llama candy.
[B]V0.4[/B]
-- Added option for ROOT users to just flash recovery.
-- Added unbrick/bootloop fix option for those that can access adb (hopefully works)
-- Bug fix, minor layout change.
-- Second-Last windows release! :D 'Last is auto APX unbrick..' Then the app.
-- Indri
[B]V0.3[/B]
-- Fixed reboot typo that causes failed reboot
-- Other layout issues and typos
-- [I]Added a Readme, read it[/I]
-- Got angry at video recorder for not working.
-- Raptor
[B]V0.2[/B]
-- Fixed a few layout issues and typos.
-- Added driver autoinstaller for Windows 7. (XP Can still use manual)
-- Updated the SU zip I was using, hopefully fixes fake error messages.
-- Fixed reboot confusion (Reordered command layout)
-- Elephant
[B]V0.1[/B]
[I]-- Initial Release[/I]
-- Helps you root and install recovery.
-- Simple mostly automated batch script.
-- Driver install guide too!
-- Reboot bug included!
-- Platypus
[/CENTER]
Tl;DR: This installs recovery and walks you through rooting your device from total stock. It includes everything you need, download is above.
It also functions as a unbrick for soft-bricks where you can access ADB or if your recovery is bootlooping and won't flash anything.
If you already have root: This tool will work on an already rooted tf to install Rouge's latest Touch Recovery (Reads from internal and external)
--if you're in a bootloop and can boot into android via-cold-boot, this will fix it! --
So if anyone who's already rooted doesn't mind doing further testing on it that would be great, the more reports the better!
If the superuser.zip isn't giving you root (For whatever reason ) try flashing the attached SuperSU I packed.
Video:
How to use PERI to root your Transformer!
**coming soon**
Unbricking/fix recovery bootloop:
I added an unbricking help/feature in V0.4 that'll help with bootloops or softbricks. PERI will help you through it.
**If you want to use the 'I'm already rooted just flash recovery' feature, you need to have given adb su access already!!!**
I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know.
It might have bugs though and not work, in which case 'Don't taze me bro!'
I pretty much copy-pasted roach's bootloop fix.
--
If I helped, click thanks!
Thing O Doom isn't responsible for bricks, dead cats, or thermonuclear war. (Although I will help you with the first two. Seek a bomb shelter if you experience the third problem.)
The .bat is open-source, download the .zip and take a look at the .bat with notepad++, if you like.
If you're having driver issues, give USBdeview a looksee.​

What does it do, exactly ? You are downgrading and then rooting with it ?

No, it doesn't need to downgrade, it just runs wolf's exploit and directly flashes recovery on your tf. All user data is safe.
If it was a downgrade, the filesize would be alot bigger as I'd have to include a stock ROM.

tried it on my transformer with the latest .24 update but it could not flash the recovery at first time, got error ..... lemme check again
Edit: got error --- "cannot stat 'recoveryblob': No such file or directory" ---
I am sure that I am using the same transformer as yours as mine was imported from USA.

About Guide
Hi all,
I think ıt should be a more detailed guide.
"Just unzip it to a folder anywhere and run the .bat file!" it seems very easy.
I do not want to offend the developers and Thing O Doom
tigerfire25;
you can try that move the blob file internal memory of asus and try again. I an now at work so I can not try the method. I am just suggesting you, do not hope too much

I tried to make with simplicity in mind, so that really is all you need to do:
1. Make folder and extract contents of .zip into it.
2. Run the .bat file, which then holds your hand through the whole process.
3. ???
4. Profit.
EDIT5: Tigerfire, please try with a MicroSD inserted. This may fix it, thanks for reporting back.

Done
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks

Yeah, the reboot to recovery scripts don't work, it's actually just a simple 'adb reboot' command. I couldn't get 'adb reboot recovery' to work, sorry about that, that's why I detailed the manual instructions in there.
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD

worked for me o/
I now have revolution HD Rom on my .24 TF101
thanks for your help ^^

Hi Thing O Doom,
Nice work and thanks
Thing O Doom said:
I tried to make with simplicity in mind
Click to expand...
Click to collapse
You might be able to automate the process a little better by running the PnP Utility ('PnPutil.exe').
e.g.
Code:
pnputil -i -a %~dp0\adb-drivers\android_winusb.inf
-a - add package
-i - install package
You can skip the install command (-i) if you like (drivers will now be in the 'driver store' (-a) and installed when device is connected).
PnPUtil - TechNet
Thing O Doom said:
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
Click to expand...
Click to collapse
You might want to try/use the su pkg from HERE
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
It uses a newer 'update-binary' and cleaner/updated 'updater-script' & pkg.
-JR-

Thanks for the pointers, I'll be uploading V0.2 a bit later to fix some of those bugs and automate the process a bit better.

Added V0.2 and Changelog in OP.
Thanks jazzruby for pointers!

@ Thing of Doom
Quarkko,
1. You use the same recoveryblob (Tf101 and Tf101G are very similar, so 3rd method works on both.)
2. You don't need to do anything, as you won't get OTA updates anymore if you install CWM. You can manually flash rooted updates in CWM later if you want to update.
3. Following to the letter, almost 0. You'd have to unplug your tf DURING the flashing of the recoveryblob. (The dd if command)
4. You still can't use NvFlash, since you have a Tf101G, sorry it hasn't been cracked yet.
Clear guide- Use my PERI: one click root and recovery installer (in my sig), it walks you through it and runs the commands for you. Works on the tf101G
Click to expand...
Click to collapse
Thanks for the reply.
I tried your PERI method! But unfortunately I use XP for these jobs. Should I wait for the xp drivers. Thanks anyway.

You can still use PERI with xp, just not the Autoinstall of drivers portion of it. Hit no when it asks to install drivers, then when it gets to the section that asks if a device shows up, hit no and then it will redirect you to a manual install of the ADB drivers.
All it needs are ADB drivers, which are easy enough to install.

TF101/G ONLY! anything else is untested.
does it mean onnly the g version or only the tf101?
kind regards
gandalf

I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.

Worked for me.
Asus Transformer TF101 | ICS 4.0.3 | Compilation IML74K.WW_epad-9.2.1.24-20120503
Thank You!

xxanthor said:
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Click to expand...
Click to collapse
I have a TF101 serial number starting with 0 and US version. I also have to face with reboot problem twice.
Command Screen say that;
Reboot: Operation not permitted. (both Revovery and Flashing screens)
I used a laptop with operating windows 7 32 bit. After reboot problem, this time I try to exectue the batch file as an administrator but, the laptop can not see the device.
Finally, I reboot my device twice manually. Then, I waited for the final reboot. The final reboot completed. There is no Superuser apk. I get into the recovery menu and I installed by manually.

Thing O Doom said:
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Click to expand...
Click to collapse
-thanks.. it did it,but no root.-and the recovery- if i trie to go to recovery after pressing vol up i only see the android layinf with a red triangel and exclamation mark.
May i try once more?
Kind regards and sorry for my englisch
By the way :funny comments

Try V0.2, it fixes reboot problems mostly. If it can't see it, then drivers need to be re/installed. Is USB debugging enabled?
So did you manage to get Rouge recovery on there and root?

Root for ICS TPT! This time the REAL thing!

Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!

emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:

God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!

Great news! Who might have thought that a working exploit is already out there?

This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.

FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!

Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.

22 hours and 5 badly needed factory resets were worth it ^^

Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.

emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!

after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks

Amazing how much of a difference having root on this tablet makes.:good:

Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?

Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?

First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.

i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...

Somebody buy that man a beer.!!!!!!

Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.

pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?

Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these

[Q] Thinkpad Tablet from China without PlayStore: Root, CWM, ROM?

Hi all,
After countless checks on forums and other threads on XDA, I've decided to post this thread as I couldn't find a similar case anywhere.
Situation is I have a TPT from China. Long story short, it was from my company, and when I moved back to Europe I got to keep it.
Anyway, the problem is that it comes with a blocked Lenovo Store, meaning I can't access any of European/US/international apps. Going to Google Play store online doesn't work ("you haven't used any device with this account") - tried from tablet or from computer.
So I thought I would root and install a custom ROM that could enable me to get to the store and personalization/optimization of the device.
I managed to root my TPT thru this thread: http://forum.xda-developers.com/showthread.php?t=1925025
Everything went OK but then I am stuck at the next stage.
If I understand well from this thread http://forum.xda-developers.com/showthread.php?t=1846044, I need to install CWM and then install the custom ROM.
The thread about installing CWM, http://forum.xda-developers.com/showthread.php?t=1831161, just doesn't work, maybe I'm doing something wrong.
If anyone can help it would be very helpful, right now my TPT is just useless...
Thanks all, any help will be very much appreciated.
M0t3l
Here are the specs:
Thinkpad Tablet 32GB
Android version 4.0.3
Kernel: 2.6.39.4-g9b8008b-dirty
Build number: A400_03_0070_0132_SC
Machine Type/model: 183825C
I am on Windows 7 and Mac OSX

Needing a few more details than "just doesn't work"... Are you getting an error message?

Thinkpad Tablet from China
da_reeseboy said:
Needing a few more details than "just doesn't work"... Are you getting an error message?
Click to expand...
Click to collapse
Hi Da Reeseboy, thanks for answering first.
ADB drivers have already been installed on my windows machine in order to root the TPT.
Then at step 3 of the tutorial ("backup your old recovery"), I tried to input the commands into the TPT but nothing happens.
I have installed an application from the chinese lenovo store called SuShell in order to do that (I do speak some chinese). SuShell just tells me "command executed", that's it.
Actually I am not clear if I have an "old recovery" or if it's only for people already with CWM.
So I went on to step 4.
I did copy the file "recovery.img" to an SD card, stick it into the TPT and tried to proceed on the TPT via SuShell again, but when I type in the commands, SuShell tells me "command executed", but nothing happens again.
So I am a little confused if I am doing something the wrong way or typing the commands not thru the right channel or something else.
That's where any help will be very useful.
Thanks again!

Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).

TPT from China
da_reeseboy said:
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
Click to expand...
Click to collapse
Thanks da_reeseboy, that made it!
I had a few gliches on the way but nothing major that I couldn't overcome.
I did follow the steps on the tutorials and now CM seems to be working fine on the tablet. It seems that a couple of functions on the TPT are either crashing or not working correctly, will try to look into it, but mainly I am now able to access the Play Store and said goodbye to the Chinese Lenovo Store.
Cheers again!
M0t3l

exFAT and NTFS drivers for Lenovo Yoga Tablet 2 - a solution!

I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!

Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix

I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.

I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!

I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.

I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.

I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.

Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though

Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.

Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.

Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !

You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.

Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!

Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.

Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!

I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.

zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks

Same way you did it when rooted. It is launched one time only.

mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.

Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it