Related
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)
This is my first post, so here goes. I have been reading all day after following the guide on the developers forum on unlocking, rooting. Everything went well, it is unlocked, cwm flashed, and rooted. However, rootcheck comes back with "this device does not have proper root access." I did some reading and found out i would have to do more to get a "full root." Superuser is installed and i can use a root browser so I am guessing i have a limited root....
Does anyone have suggestions? Really want to get this done before flashing any custom roms. If it helps, i had 4.1.1 JB before all of this. Suggestions on roms to flash would help, i read i should only flash a rom based on JB. I dont know if its related but i have been unable to do a backup with CWM...results in error.
I hope provided pertinent info. Thanks in advance.
bobrebn3 said:
This is my first post, so here goes. I have been reading all day after following the guide on the developers forum on unlocking, rooting. Everything went well, it is unlocked, cwm flashed, and rooted. However, rootcheck comes back with "this device does not have proper root access." I did some reading and found out i would have to do more to get a "full root." Superuser is installed and i can use a root browser so I am guessing i have a limited root....
Does anyone have suggestions? Really want to get this done before flashing any custom roms. If it helps, i had 4.1.1 JB before all of this. Suggestions on roms to flash would help, i read i should only flash a rom based on JB. I dont know if its related but i have been unable to do a backup with CWM...results in error.
I hope provided pertinent info. Thanks in advance.
Click to expand...
Click to collapse
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
== Part 4 - Remove the Bloatware ==
Check second post
== credits ==
- eyeballer for TWRP recovery
- untermensch for CWM recovery
- sparkym3 for his automated rooting toolkit
- Redefined301 for his guide
Click to expand...
Click to collapse
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
cool
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
CyberDyne
Thanks. I just flashed the TWRP recovery...I really like the gui. I have a question though...the superuser3.2 file you said to flash...where do i find that? I'm up to that point. Thanks again, for your help. Also, another question...is it correct that I have to only install roms based on official ASUS JB 4.1.1 ? I'm really unclear on that stuff. If i flash another rom will it undo what I just did in flashing TWRP? I'm getting a little confused between flashing these recoveries and flashing roms...help
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
Awesome...it worked! I found the .zip file you mentioned and flashed it with TWRP, installed supersu and it all worked. If someone could answer the remainder of my question about which roms to flash, I would appreciate it. Thanks again CyberDyne!
bobrebn3 said:
Awesome...it worked! I found the .zip file you mentioned and flashed it with TWRP, installed supersu and it all worked. If someone could answer the remainder of my question about which roms to flash, I would appreciate it. Thanks again CyberDyne!
Click to expand...
Click to collapse
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
thanks
CyberdyneSystems said:
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
Click to expand...
Click to collapse
Thanks again for your help. I completed my backup in a couple minutes, then used titanium backup for the apps. I will research the roms you mentioned and others. You solved all my problems...transformer related problems that is....have a good day.
TF700?
Hey guys, I have the same problem as OP and the subsequent poster only that my device is a TF700, can you guys tell me if this method works for the infinity?
CyberdyneSystems said:
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
Click to expand...
Click to collapse
As far as I know, you can only flash custom JB ROMS that are based off the JB bootloader. Once you did the OTA upgrade to JB, the bootloader was updated as well. If you try to flash any ROMS that are based off the ICS bootloader, you're going to brick your tablet. That's what I keep reading. I'm still on a locked tablet, but I read everything on the forums.
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
Hey I have a similar problem for k3 note (k50a40) can you help me with that
Thanks
Update : Problem Solved
Ok so I've had this phone forever, mainly use it to play games and stuff on bc im not with sprint any more im using a bionic as main device. But I have always loved to hack this phone with new ROMs and mods etc. bout four months ago Idr why but mine and my gf's were unrooted and I had to re-root them. So I got hers hooked up first to the comp, rooted, adb and everything worked fine I've had custom ROM on hers since. For some reason, I plugged mine in RIGHT after hers, adb wouldn't pick it up as a device for some reason. Now I finally am able to pick it up on ubuntu through adb and i've tested it I can push/pull/sideload etc, fastboot flash recoveries etc. I have flashed several recoveries today to try to flash su binary to root the phone and one recovery worked, IDR which it was because I renamed it to recovery.img but its some kind of touch recovery thats not cwm. that one worked for me to actually load after I flashed it, so I sideload flashed the su zip and on the log it went through chains' little messages and said the root successfully worked. i booted the phone and had superuser, but none of my superuser apps are working. i updated the app. still not working. I tried to boot to recovery, didn't work i get stock recovery. every other recovery i flash will NOT work when trying to boot to recovery. it only takes me to the error page where i can get to stock recovery. can ANYONE help me here. i need to get su working and get the device to where I can really load a custom recovery. any help from anyone will really be appreciated. i've been trying to get this phone flashable for a while. im getting frustrated, once again, like every other time i've tried to do it in past months.:crying:
ok so my problem is fixed. I guess what was going on is I didn't get a successful root by having to sideload & flash the zip through the only recovery that would work. When I flashed TWRP, thankfully to the gods of hacking and Android that worked. So in TWRP I was able to successfully flash the su binary and that allowed me to successfully root/maintain root. Through that my recovery stayed in place and did not go away. Through this I was able to flash a ROM, that being an old (not too old, back in the 2.12 era) and did not work efficiently, everything closed as soon as I opened it. So I found an old GB CM7 ROM on my sdcard and successfully flashed it and since it didn't have GApps I had to go through the browser to download rasbean and flash that. That worked well, although the OP had stated GApps was included and was not, so I had to get him to send me the rb version of the jb 12-12-12 gapps, and flashing that worked and fixed all my issues in that rom so...long story short(after a long story) I got everything working. So basically, for future reference, find a recovery that will stick long enough for you to get the su binary onto storagge and flash it.
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.
Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!
ACaton said:
Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!
Click to expand...
Click to collapse
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.
graphdarnell said:
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.
Click to expand...
Click to collapse
Ok, so to clarify, if I want to flash the official rom from Asus to upgrade from Android 4.1 to 4.2 then I should use fastboot instead of trying via the SD Card. In the process however, it will overwrite CWM (the custom recovery) correct?
Where would I find the instructions on how to use fastboot to install the official rom? I know it would be from the command line, but what exactly would the command be?
Once I've installed the official Asus 4.2 rom, then I can install TWRP correct?
Thanks
There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.
Graiden05 said:
There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.
Click to expand...
Click to collapse
Thanks!!
For my own edification, the command from what I can interpret is:
fastboot - the program
-i 0x0b05 - the USB identification
flash - command to flash (as opposed to say reboot)
staging - this I'm not sure of ... staging because it's a new rom that's going to be installed. Curious why it wouldn't be system, as aren't I installing a new system rom?
blog - the blob file I want flashed.
Correct?
Yes. As I understand this, staging - partition used to store something that going to be flashed. Blob from stock firmware contain data for bootloader, recovery, boot, system partitions. Here full description of fastboot command.
I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?
nbranquinho said:
I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?
Click to expand...
Click to collapse
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.
ACaton said:
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.
Click to expand...
Click to collapse
Thx for the alert, I already have the correct blob for my tablet.
The process work fine and now I have the JB installed on my Tablet!
Thx.