Hi there!
I'm a owner of a TF101 (B50) for month now, and recently I had the need to switch between multiple version of Android (as I'm an Android dev) : back and forth to/from Honeycomb from/to ICS for example, multiple time a day!
So, as I'm used to do with all my "Google's Experience" devices (Nexus S, Galaxy Nexus), I installed CWM on my TF101 to be able to generate nandroid. So far, so good.
I then downgraded my tablet to stock 3.2 using nvflash, installed CWM, and did a nandroid. Great, I now have an Honeycomb backup. Of course, at this point, I'm no more able to upgrade using OTA, so here's my first question :
1- Once CWM installed, how do you upgrade to the latest build ? Asus blobs are not compatible with CWM!
Then, since I needed an ICS nandroid, I reverted to stock 3.2 (using NVFLASH), and I let the OTA did the job for me - before installing CWM. Ok, now, I have both Honeycomb and ICS as backup : let's test that.
I rebooted in recovery, and then restored my 3.2 nandroid (from ICS, remember?). All I had once the job was done, was the android logo with an exclamation mark
After some Googling, I understood why : unlike my Google's devices, on the TF101, it seems CWM can't restore the boot partition. So, the bootloader used was the one for ICS, and the tablet failed to boot.... Here's my 2nd question :
2- Am I right? What guys are you suggesting to be able to switch easily between different nandroid versions ? Should I nvflash the boot partition by hand? If so, where to find a documentation on NVFLASH ? (I'm regretting fastboot )
Thanks for reading.
You can repackage the blobs so that they can be flashed from cwm. I think one roach's 3201 recovery is packaged this way, so you can take it apart to see how it all works. Essentially blobs are flashed through the staging partition. There is a blob tools thread in the dev section that has all the details.
If you want to go back and forth between roms, I think that nvflash will be your best bet. Rayman and bubble bee have the most info. Check out therenwebsite. It's something like androidroot.mobi? There is also a full backup and restore thread in the dev section that explains a lot of the details of nvflash.
sent from my transformer
I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?
nono240 said:
I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?
Click to expand...
Click to collapse
yes but you will loose root and cwm recovery. It's the easy unroot method.
Not a big concern. I can easily recover both root and CWM using the universal root method since I have a B50!
Thanks
Will you lose root/cwm even if you have OTA Rootkeeper installed?
You Shouldn't but no guarentees x)
Related
I believe this is my first post on these forums. I just did the nachoroot mod today per
[ROOT] NachoRoot - supporting all firmware jan 3rd 2-118
and
[Update: Works On The OG Transformer, Too!] Exclusive: 'NachoRoot' Brings Root Access To The Transformer Prime, Even With The Newest Firmware:
on my TF101 B80 32 gb.
I did the procedure per the second link above. I've been able to verify root with Root Check Basic from the Android Market.
I've never rooted an Android device before and am quite concerned about unrooting, in case I ever need to return my unit to Asus.
I've heard I need cwm, the clockwork recovery mod, in order to unroot. I hope it is ok to do this after the initial rooting procedure.
Please pardon me if this has been asked before, as it my first time, and I find a lot of the documentation a bit cryptic.
Thanks in advance...
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
skallal said:
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
Click to expand...
Click to collapse
Are you sure you have flashed CWM recovery? You should have a lot more options.
After installing RecoveryInstaller, did you open the app and click on "flash CWM recovery" tab?
I didn't click on the flash tab because I don't intend do recovery at this time. To be clear I understand what recovery is, I think it means to return my TF101 back to an unrooted state with the current ota release, which is .23, and also wipe out all my data. If this is incorrect, please let me know.
You said I should see more options than just the flash tab. What else should I see? And when should I see it?
Now that I've successfully rooted, my main objective is to learn how to return my device back to its unrooted state in order be ready for the ICS ota update when it arrives. If that means I'll also wipe out my data in the process, then I'll need to learn how to backup and restore.
Please do let me know if I understand the process or not. I still have have a reading and learning ahead.
Recovery lets you flash packages, ROM patches, and complete ROMs that require very deep (i.e. low level) system access.
If you don't intend to flash any custom ROMs (e.g. Revolver) or install things that need low level system access (e.g. a USB to Ethernet adapter) you won't need to flash CWM.
One of the admins on Transformer Forums gave me the impression I need cwm to unroot my TF101. That is the only reason I downloaded it.
If I don't need cwm to unroot, then I'll focus my reading on unrooting link listed earlier in this thread.
I don't have any interest in other roms, at least not for now. My concern, for now, is unrooting when it comes time for the ICS update...
baseballfanz said:
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Click to expand...
Click to collapse
The second link above (theunlockr.com) refers to old firmware (repacked-8.2.3.13_US_without_SU_app.zip).
Is that file already outdated?
Perhaps a newer version for .21?
Well it all depends on your serial number. Early builds (B60 and earlier plus some B70) you can use NVFlash to get back to totally stock.
If you have B80(and some B70) and above you'll need cwm recovery to get back to stock following the link i posted above.
I finally watched the video from your earlier post and it answered a quite a few questions.
Bottom line: when it comes time to update to ICS, do I need to unroot first?
The ICS update is my main reason for unrooting. I read for some users lost root after the last ota update to .21. I don't have any immediate need to unroot other than to prepare for the ICS update when yet comes.
And there's also a long term need unroot when and if I ever send the unit back to Asus for service.
I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!
theremix said:
I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!
Click to expand...
Click to collapse
Technically you'll still receive the OTA update you just can't apply it if you have CWM or a custom ROM installed.
You can't install custom ROM without CWM (if you have an older SBK tablet you can use NVFlash with a compatible ROM).
So I shouldn't install cwm until the ICS drops right?
Sent from my Transformer TF101 using Tapatalk
If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.
CalvinH said:
If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.
Click to expand...
Click to collapse
Thanks, I think I'll just wait for the OTA as I want to update as soon as ICS drops in.
Sent from my PC36100 using Tapatalk
I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).
Woodrube said:
I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).
Click to expand...
Click to collapse
1- The RecoveryInstaller app only help to flash the recovery image so no you can just delete it.
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot
baseballfanz said:
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot
Click to expand...
Click to collapse
I figured that would be the case with the executable part of the apk.
I read that thread but wasn't sure if only the stock recovery by itself could be flashed w/o the prepacked ROM.
ok so ive searched everywhere and tried reading everything but im very confused. i see that it is going to be very hard to root my tf101 since i have the latest asus ota update (build #9.2.1.24) but i cant quite wrap my head around how to do it.
i tried using the backup exploit and sparkyroot but those dont work on the latest ota. i already have Rom Manager installed and tried the recoveryinstaller.apk from Gnufabio but those didnt do anything either.
iv read the thread about downgrading (Wolf's guide) but im hesitant to do that since i dont understand it and i have no experience using the shell command (is that the same as using a terminal emulator?) can anyone please explain the terminology and how to downgrade? what program do i need on my computer (running windows vista)? please be gentle and dumb it down for me and include any links to programs or files i may need
thanks so much
p.s. is a "Blob" the same thing as an SBF? and if i did a factory data wipe, would that downgrade from ics 9.2.1.24 or keep it the same?
Adb shell is the same as running a terminal emulator, just google android sdk download and click the first link. Follow wolf's instructions carefully using your favorite recoveryblob from the development and you should be perfectly fine. Never use Rom manager, please just uninstall it now. If you factory reset, the recovery will still be there, as a reset only deletes user data, to return to stock you would need to flash stock recovery over cwm (not recommended) or flash a whole ASUS ota package from their website (better, removes any root and rom you have, cross that bridge when you get to it) What are the first 4 digits of your serial number? (for ex: mine are B70K) If they start with B60 or lower (B50,B40,etc..) you can just use NvFlash instead of having to use wolf's guide to root. Don't be too scared, it isn't that bad, just follow instructions carefully.
Thanks for the reply. My serial is b60. After more searching I was able to find an adb dummies guide and was able to downgrade to .17 but I didn't read one extra post to see that sparkyroot doesn't work with .17
So I had to do it all over again and go down to .11 and that worked and then I used sparkyroot and voodoo ota rootkeeper. Will rootkeeper work/stay if I do a factory reset? Cuz some apps and services aren't working. Or should I just do the ota to .17 and then .24? And now I can use nvflash in order to flash a new rom? Is that in the market or just google it?
Thanks again
You didn't need to go through all that since you have NvFlash, but good learning process I suppose
At this point, since you're rooted, use recoveryinstaller again to install CWM recovery, download a kernel.zip (I recommend Guevor's kernel) your favorite ROM .zip, and a new recovery.zip (as 3.2.0.1 works but is pretty outdated) [OR you can go to team rouge's thread in dev for an NvFlash version of recovery and NvFlash instead of recovery installer and update, then apply rom and kernel .zips in new recovery]
Make sure to place the .zips on external SD card if you're using 3.2.0.1. Any other Qs?
Edit: links
NvFlash: http://forum.xda-developers.com/showthread.php?t=1123429&highlight=nvflash
Rouge Recovery: http://forum.xda-developers.com/showthread.php?t=1446019
when you say that recovery.zip 3.2.0.1 is outdated do you mean the CWM version?
is flashing a new kernel safe? this is obviously my first time with a tablet with so much "freedom" compared to my droid2global lol
personal opinion, what do you think of android revolution rom? any other recommendations?
Yes the CWM version, I did use 3.2.0.1 for awhile though, it works, it's just old.
Yes, flash away, just always remember to wipe cache and dalvik-cache before flashing anything.
Android revolution is a great stock based rom, if you like the tab the way ASUS sends it too you, I personally prefer AOSP based roms, so my other recommendation if you want to go that route is Megatron or AOKP Build 37
Guevor's v20 kernel is the best out atm, imo.
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
mikaole said:
just fastboot TWRP for ICS and then flash the 1st JB StockRom(dl from Asus and unzip once) in TWRP.
Then fastboot TWRP for JB, then flash the latest JB StockRom(dl from Asus and unzip once) .
Then fastboot TWRP for JB and then the Rom you like
Click to expand...
Click to collapse
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
bsaman said:
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Thanks! So you were going from another set of instructions but ended up just flashed twrp-jb and installed the unzipped zip of Asus JB release via TWRP (I left out the revert to ICS part since I'm already there)? And do you have nvflash installed? No issue running the JB version of TWRP prior to upgrading to JB (had thought bootloader or ... would have an issue with it)? Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
wha2do said:
Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
Click to expand...
Click to collapse
I think you're right... I was on BB6 w/ICS bootloader (NVflashed, though I don't think it matters) and had to roll back to ASUS ICS ROM first, then rooted, then upgraded to ASUS JB ROM, and then it goes blurry. Not sure if I upgraded TWRP or rooted stock JB at this point.
In any case, I followed the "update to JB" thread to a tee, and all went well except for the step regarding the actual JB update.
Sent from my Transformer Pad TF300T using Tapatalk HD
wha2do said:
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
Click to expand...
Click to collapse
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
tobdaryl said:
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
Click to expand...
Click to collapse
Thanks for the info. To add to your one comment (for others that may come across this looking for add'l info), flashing a full stock rom will overwrite any custom recovery previously in place. TWRP (using the appropriate version for your firmware) or CWM will need to be reflashed again...
Checking, it does appear v10.4.2.9 is the first version of JB on the TF300T.
I've come across at least one or more posts/guides that mention ICS v9.4.3.30 should be installed before updating to JB - one being: [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]. I'm wondering if it's because that method updates to JB using the dlpkgfile (not sure what format it is)?
My take is doing the additional flash to v9.4.3.30 first can't hurt anything, but quite possibly unnecessary here? Any other thoughts or words of warnings from anyone? Thanks!
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.