Database Info

unroot my tf300

I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help

jflynn0 said:
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
Click to expand...
Click to collapse
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173

dxwilliams40 said:
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?

cjohnsonthe2nd said:
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
Click to expand...
Click to collapse
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?

dxwilliams40 said:
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
Click to expand...
Click to collapse
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.

cjohnsonthe2nd said:
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
Click to expand...
Click to collapse
Remember to full wipe before installation including /system and after clear dalvik and cache then fix permissions.
By not wiping /system can cause some data to be left and corrupt stock installation had this happen on my g2x and have seen it on some other threads.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wiped the cache before I started the install and now when I boot into the usb fastboot my comp flashed a bootloader notification but then nothing else happens. I tried it a second time and I dont even get the notification. Also if I let it boot regular the Asus screen shows when i first boot but then nothing ever comes up just black screen

Can't load recovery

Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.

It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)

ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.

buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.

ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.

okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.

ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.

buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.

ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T

did you unzip the file? should be a zip within a zip. you flash the zip inside

lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm

[Q] New (virgin/stock) TF700 to CROMI 3.2 - is this right?

Hi there, been loitering on the sidelines for a while, reading many many threads and now ready to leap in. I have bought a TF700 Infinity and want to get it fully modded, enhanced, streamlined and dripping in XDA goodness. I want to know if the things I have planned are a) in the correct order, b) are the correct/most suitable methods and c) are inadvisable or unecessary for any reason.
Root the device
- Using the DebugFS method (details HERE and HERE).
Unlock Bootloader
- Using the ADB tool from blackmambazzz
- If the ADB tool doesn't work then I'll use the download from the Asus website
Install recovery (TWRP)
- I will try using GooManager first (hence the reason to root)
- If GooManager doesn't work then I will try the ADB tool again (option 1)
- If I get problems with the latest version I will try TWRP v2.3.1.0 (as some people have reported that this could be better)
Flash JB bootloader
- Boot into recovery (as per the instructions in the All-In-One Guide For Asus Infinity post)
- Flash the 10.4.4.25 JB bootloader found in this post
Flash ROM (CROMi 3.2)
- Using the downloads from the CleanROM Inheritance 3.2 post, flash CleanROM Inheritance and choose my options through the Aroma installer
Flash stock kernel (by _that)
- Use TWRP to flash the stock kernel through the CROMi installer v1.6 found in the CleanROM Inheritance 3.2 post
Hopefully that will get me from out of the box virgin TF700 to a fully charged awesome tablet/laptop that is smooth and powerful. Hopefully I've done my research and got it right but please let me know if there is anything incorrect. Thanks!

The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.

hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!

marci4na said:
hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!
Click to expand...
Click to collapse
Try power off your device, wait a few seconds, then boot back into cwm see if that helped!

If all else fails I would switch over to TWRP I prefer it way more then cwm.

_that said:
The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.
Click to expand...
Click to collapse
Thanks _that, your work on the stock kernel is most appreciated and I can't wait to experience the fruits of your hard work. My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu. Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.

mrlee1980 said:
My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
Click to expand...
Click to collapse
3.2 already contained "my" kernel, 3.2.1 contains the nodpi variant.
mrlee1980 said:
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu.
Click to expand...
Click to collapse
Correct.
mrlee1980 said:
Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.
Click to expand...
Click to collapse
Looks good. Note that the ADB tool has no error handling. If it does not work, it makes sense to invest some time to get adb and fastboot working on your PC, it is always helpful.
If you don't have any apps installed yet, you don't even need to let it settle - just don't expect absolute smoothness in the first minute, while it's still doing some background stuff.

OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.

mrlee1980 said:
OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.
Click to expand...
Click to collapse
Have you tried to flash .25 JB bootloader and reflash cromi ODEX 3.2.1 with _that stock no dpi kernel? make sure wipe cache and dalvik cache first before flashing.

mrlee1980 said:
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
Click to expand...
Click to collapse
The settings screen does not show the bootloader version. The bootloader version is only displayed when you hold down Volume-down while powering on - tiny text in the upper left corner while the bootloader menu is shown.

Please Help - Updated JB bootloader - can't boot

I just bought a new Infinity today to replace my Prime. I never bothered unlocking/rooting/etc the Prime but given I'm starting from scratch thought I'd go that route out of the box on the Infinity.
I've been carefully reading all of the guides, etc and have used the unlock tool, then created the nvflash backup files (which involves a custom bootloader first).
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next? I'm not new to flashing but w/ my Galaxy Nexus things have always gone pretty smoothly.
Thanks in advance.
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
ALSO,
I had not accepted the software update from Asus yet so I was still on ICS. Does that have anything to do w/ my problem? What should I do?

Kidd_Funkadelic said:
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next?
Click to expand...
Click to collapse
Simply boot to recovery and install CROMI.

Kidd_Funkadelic said:
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
Click to expand...
Click to collapse
Are you on Windows? The "$" sign is not used under Windows -- have you tried typing "fastboot -I.... " ?

_that said:
Simply boot to recovery and install CROMI.
Click to expand...
Click to collapse
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Either way I'm stuck at the moment w/out adb and no SD card. I'm running out on my lunch break to pick one up, which should be all I need to get working again. To be safe I'm going to go back to the .30 ICS stock image first. Once I know that worked, I'll take another stab at CROMI.

Kidd_Funkadelic said:
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Click to expand...
Click to collapse
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.

_that said:
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.
Click to expand...
Click to collapse
Gotcha. I didn't realize TWRP supported adb. Anyway I was able to get back up and running w/ my nvflash backups, though I have to say finding info on actually using the backup files took a ton of digging and some trial and error... Now to try again at CROMI!

I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.

SilentOrchestra said:
Flashing cromi or reflashing the same bootloader yields an error message.
Click to expand...
Click to collapse
And now we are supposed to guess what error message you saw?
The next step is to set up an adb connection from a computer to your TWRP. This way you can get more detailed info what went wrong.

SilentOrchestra said:
I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.
Click to expand...
Click to collapse
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?

FordPrefect said:
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?
Click to expand...
Click to collapse
I agree, it seems you never updated to a JB rom. A JB boot loader needs a JB Rom, It seems the JB boot loader wont boot ICS. Just flash Cromi and you should be good.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.4 Odex
Kernal: Hundsbuah V2.0 OC 1.75 GHz
Theme: Timberwolf's Blues & Jazz Theme V1.9

[Q] Help understanding my current rom/recovery situation

Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:

Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?

Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.