Database Info

Post unlocked bootloaded

I began with the thread http://forum.xda-developers.com/showthread.php?t=1833212
I intended to unlock the bootloaded( completely successfully) , root( not attempted) , install nvflash (since I read its a must have) and install a rom, because the stocks lags horribly
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Most important to me is understanding what I am doing. Coming from a galaxy s3, the process here seems different.Now I know samsung and asus are different companies. Its just on the S3, I completely understood, that to root for example....I could flash a rooted stock rom, i could use ODIN for example to flash CWM. Then once I had CWM I could back up, restore, install roms at will
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Thanks for any help

Tjisana said:
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Click to expand...
Click to collapse
The AndroidRoot bootloader is a hacked version of 9.4.5.30 and it can only be installed if your current bootloader is older than 9.4.5.30, e.g. 9.4.5.26. If you didn't upgrade past 9.4.5.26, you can still get nvflash access.
Tjisana said:
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Click to expand...
Click to collapse
Fastboot is part of the Android SDK, which everyone who is into hacking, rooting and installing custom ROMs should have installed on their PC. If you are running Windows, you also need some USB drivers.
Tjisana said:
Most important to me is understanding what I am doing.
Click to expand...
Click to collapse
Right. Don't do anything before you understand what you are doing. Helps tremendously to avoid stupid bricks due to known reasons. One of these is: Never choose "wipe data" from the bootloader menu if your recovery is broken, it's known to cause trouble.
Tjisana said:
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Click to expand...
Click to collapse
Yes, BIOS and bootloader are roughly comparable in their role, at least in their role to initialize hardware and to load the operating system. Fastboot is a tool to install an operating system kernel. You can't insert a CD or USB stick into this device to (re)install Android.
Maybe you already know that an Android device has two such kernels - it can boot either into regular Android, or into a small recovery system that is used to upgrade or maintain the main system. The recovery, as well as the Android boot image, can be flashed using fastboot. The most popular recovery for the TF700 seems to be TWRP, but CWM is also available.
NVFlash is lower level, it can do everything that fastboot can do (in a slightly different way), and it can read or write any partitions or raw blocks on your device. It even works if your bootloader is broken - fastboot in contrast communicates with the bootloader.

Can't mount any partition

Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03

matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD

i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)

matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD

Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change

matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD

i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows

Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.

EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?

http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you

sorry guys today i was very busy, i'll try to solve it tomorrow

matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3

CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem

I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.

pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news

matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD

i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me

matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD

i'll definitely try that method! i'll let you know, thanks guys

matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....

[Q] I have root and I am not sure what to do now

Hello all, yes, this are going to be a very noob questions, but I do not want to end up with bricked device, so lets start.
1. After OTA upgrading TF300T from 4.0.x to 4.2.1, it made my device absolutely useless, well I am gamer and lot of my games just start lagging, extremely lagging, i have made factorial, reinstal, but not helps at all, so I decided to make it hard way.
2.I have never edited Android, so after studying lot of threats I have install adb, asus drivers and made a root via motochopper, which allows you root access but your bootloader will remain lock.
3.But what now??? (next steps is only my theory)
Can i just unlock bootloader via Unlock Device App: Unlock boot loader from ASUS support site (after success it will reboot or something) and then flash ClockworkMod recovery via ROM Manager? And then I just download CleanRom and put it on sd and just flash it and it will be all?
As I said, I have no idea, no idea which rom is the best fo gaming, which ClockworkMod recovery is the best for my device and if that Unlock Device App will working ... or even if my theory is right. Also I have som knowledge about fastboot but every quide was for 4.1 non rooted only. This is my very first post, so please be permissive.
Thank you for answers.
ASUS Transformer TF300T 4.2.1 stock but rooted with locked bootloader, WW sku

You will want to unlock your device with the Asus tool first.
Then you will want to install TWRP, I don't think CWM is working right on 4.2. Twrp works flawlessly. You will want to make sure you get the correct version of TWRP for 4.2, or you may brick your device. It will be called twrp-2.5.0.0-tf300t-4.2.blob . the important part of the filename is the -4.2
This is the link for it. http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
You will want to use that on the Asus 10.6.1.15.3 firmware.
rename the .blob file to twrp.blob
You will need to flash through command prompt while device is in fastboot mode with the command:
fastboot -i 0x0B05 flash recovery twrp.blob
Then put you desired rom on your SD card and flash away. I recommend trying CROMI, very fast, stable, and polished.
There are excellent tutorials in the general section. this one is particularly good: http://forum.xda-developers.com/showthread.php?t=2187982

You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app

Reilly1812 said:
You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
That would be some house. +1 to this sentiment though. It's not hard, but there are risks to consider.

CBank said:
You will want to unlock your device with the Asus tool first.
Then you will want to install TWRP, I don't think CWM is working right on 4.2. Twrp works flawlessly. You will want to make sure you get the correct version of TWRP for 4.2, or you may brick your device. It will be called twrp-2.5.0.0-tf300t-4.2.blob . the important part of the filename is the -4.2
This is the link for it. http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
You will want to use that on the Asus 10.6.1.15.3 firmware.
rename the .blob file to twrp.blob
You will need to flash through command prompt while device is in fastboot mode with the command:
fastboot -i 0x0B05 flash recovery twrp.blob
Then put you desired rom on your SD card and flash away. I recommend trying CROMI, very fast, stable, and polished.
There are excellent tutorials in the general section. this one is particularly good: http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
thank you very much for the guide, of course, I will asking about every step I do not understand well. I will start next week (because school) but now I can safety unlock bootloader via Asus App. thx

Reilly1812 said:
You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I couldn't have said it better myself.
Read, read, and read some more. If you have questions, ask.
Sent from my C525c using Xparent SkyBlue Tapatalk 2

Success
I just did all of this on my TF300T today and can confirm that it works without issues. I just did them in a slightly different order... I'll explain the entire process. First, I downloaded the newest official firmware listed on Asus's website, put that shizzy on my MicroSD, plugged it into my device, booted, and waited. If you do not automatically receive an update notification, head to your settings and press, "Check for Updates" (that is what I had to do). Once you finally get the message to update to the firmware on your SD Card, accept and wait for the process to finish. Next, I rooted my tablet with motochopper. Then, I downloaded the correct version of twrp from the site. If you update your TF300T to the latest official firmware on Asus's website, you will need to downloaded the .blob ending in -4.2 (and place it in the root of your, "sdcard," directory). Finally, I installed the custom recovery through terminal. SUCCESS! Best of luck, man!

[Q] something like CMInstaller for my TF700?

Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.

I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.

CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.

madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html

Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP

Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!

madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.

What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:

LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?

berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:

LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend

berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...

berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.

Upgrading from 4.1 to 4.2

I have looked everywhere for help on this subject.
I have rooted my tf300t with unlocked boot loader 4.1, but what are the steps to upgrade to 4.2? I want the latest roms but im stuck with the old 4.1
Do I need to update my TWRP first? I have an old version
If there is a link to show me how please post if not let me know please...im desperate and im going away to Dubai for the xmas period

Found the solution. Please close this thread

olster said:
Found the solution. Please close this thread
Click to expand...
Click to collapse
Could you provide solution please?

Tunameltsalad said:
Could you provide solution please?
Click to expand...
Click to collapse
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.

cmendonc2 said:
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.
Click to expand...
Click to collapse
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.

majorpay said:
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.
Click to expand...
Click to collapse
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/

cmendonc2 said:
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/
Click to expand...
Click to collapse
OK, so with this 4.1 modded tablet, if I take the latest version of 4.2, grab the blob, and do the following:
Code:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Is that going to work, or am I going to end up with a brick?
I know that there has been some warnings on upgrading to 4.1 with 4.2 files, so I want to double check before I make a bookend out of this thing.
EDIT: Pulled the trigger - worked out fine. Now I will install a recovery and we'll be good to go!