Database Info

[Q] My Asus TF300T is on stock Android 4.0.3, what to do next?

The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!

What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app

This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...

Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD

Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.

It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app

Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596

pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?

Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89

Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.

opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.

Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:

pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...

[Q] SOLVED: Help - KitKat upgrade from stock... ish.

So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.

Just a little bump, not too big... no love for Tim?

Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2

zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!

The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.

I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol

Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.

Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck

b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!

Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!

It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol

Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh

No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!

[Q] Stuck booting

Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag

You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!

Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)

shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.

berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington

When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.

shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.

Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true

I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.

Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again

[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!

So where does one get the latest OTA?
cheers

Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.

Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!

bootloop - question on how to proceed

I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:

monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....

berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.

Nobody has any more expertise to proffer?

monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary

berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!

Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.

New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.

Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience

berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.

Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again

berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?

No, you cannot relocate the bootloader. Flash away

berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.

Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.

I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks

Not enough information. What can you get to?
What's your ROM, bootloader, recovery?

berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks