Hello everyone
I've rooted my tf300t with cwm recovery (installed "root-signed.zip" from boot-menu).
The tablet had stock rom version .17 before i rooted, and still has.
Now, in the lower right corner, there is a notification that says that a firmwareupdate is ready to be installed. Will it be wise to install?
I've read that many loses root if they update, so i don't know what to
do... Is it better to download the update-file from asus.com and install it manually?
Download and install ota rootkeeper from the play store. Make sure you backup your root correctly with this before you proceed with the update. After the update, open up rootkeeper and restore root.
I hope I'm correct but I believe if you installed CWM the update will never work because the stock recovery will find the update and apply it automatically, but CWM won't. So you'll download the update, it'll reboot but never apply. In http://forum.xda-developers.com/showthread.php?t=1714727&page=10 someone seems to have a link to a ZIP you can apply. But you need to re-install CWM and root though.
psjw12 said:
I hope I'm correct but I believe if you installed CWM the update will never work because the stock recovery will find the update and apply it automatically, but CWM won't. So you'll download the update, it'll reboot but never apply. In http://forum.xda-developers.com/showthread.php?t=1714727&page=10 someone seems to have a link to a ZIP you can apply. But you need to re-install CWM and root though.
Click to expand...
Click to collapse
Actually, that is correct. OTA updates will only work with stock recovery. If you have CWM recovery, OTA won't work. You will have to manually install the update.
But I thought that I had to have stock .17 to root?
If I update to a newer version, will I still be able to root?
Not anymore...check out the develpment section to read up on the latest root methods for the latest firmware.
Yup, I side loaded the .30 update with CWM then I no longer had root and I no longer had CM recovery. All is good with my official update installed though, despite being unlocked. So I am happily working to re-install CM recovery and then re-root. It's an orderly procedure, so I will get started on that next.
Done and done.
So follow the ClockworkMod instructions if you are unlocked. You simply repeat the steps to install the CM recovery and then use the CWM just installed to root again. All is well.
Asus may or may not have patched the Sym-linking exploit Wolf first found.
You can attempt running his exploit to root the new firmware, but this is only if you were unwilling to unlock your bootloader, if it's unlocked you can just use CWM.
The 9.2.2.6 patch apparently broke OTA rootkeeper for the TF101G, so take care.
Thank you so much for good support guys!
The tab is unlocked (if not, it had not been possible to install cwm recovery)
I've now downloaded the .30 update zip from asus.com, which brings me to my next question, how do I install it manually?
I've unziped the file once and placed it in the root dir on the sd-card and rebooted.
A triangle appeard in the notification bar. Pressed it, and it rebooted again automatically. But but this time it booted into cwm recovery...(?) From here i pressed "Install zip from sd-card" and then "Choose zip from sdcard" but it seems like my sd-card cannot be found.
I only have the option to choose from internal storage. Should I have placed the firmware update in internal storage instead?
Yes. Neither recovery has support for an external SD card right now. You must use internal storage.
But should I run te update through cwm recovery?
If you make it a CWM flashable .zip you can do that, or if your CWM supports OTA updates, (extract the .zip once, inside should be another .zip, this is what you flash in CWM)
Or you could manually flash through the staging partition using adb or terminal emulator, this would support ext SD.
Code:
su (Grant root Permissions)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
(or /Removable/MicroSD/Blob, wherever you put it)
reboot
mmcblk0p4 is the staging partition for the TF101, if it is the same use that for the TF300t, but I'm not 100% sure till I look at a partition table listing, it's probably 0p4 though.
To install the .30 update you have to have Downloaded it from somewhere - like ASUS.
It needs to be unzipped from it's original to the standard update file name ex: US_epad-user-9.4.3.30.zip This apparently still "zipped" file is the only file contained inside the one that I downloaded. This file must be placed on the root of the sdcard (internal Storage) of the tf300. You reboot into CM recovery and instruct it to update from sdcard where this file is to be found. This is what I meant in a previous post by "sideloading". You are essentially manually installing this update. The tf300 will behave as if you have installed this update normally i.e OTA and reboot to install itself. Once this update is installed it overwrites the ability to use CM recovery and your tf300 is also no longer rooted - so you have to do that all over again. Your tf300 however remains with it's bootloader unlocked so this is the method that we use instead of "Over The Air" updates. The procedure to continue to re-install CM recovery and to root it is in another post:
Transformer tf300t Android Development : [CWM][5.5.0.4] ClockworkMod Recovery for TF300T + ROOT
Hope I have made things more clear,
Cheers!
kjwaugh said:
To install the .30 update you have to have Downloaded it from somewhere - like ASUS.
It needs to be unzipped from it's original to the standard update file name ex: US_epad-user-9.4.3.30.zip This apparently still "zipped" file is the only file contained inside the one that I downloaded. This file must be placed on the root of the sdcard (internal Storage) of the tf300. You reboot into CM recovery and instruct it to update from sdcard where this file is to be found. This is what I meant in a previous post by "sideloading". You are essentially manually installing this update. The tf300 will behave as if you have installed this update normally i.e OTA and reboot to install itself. Once this update is installed it overwrites the ability to use CM recovery and your tf300 is also no longer rooted - so you have to do that all over again. Your tf300 however remains with it's bootloader unlocked so this is the method that we use instead of "Over The Air" updates. The procedure to continue to re-install CM recovery and to root it is in another post:
Transformer tf300t Android Development : [CWM][5.5.0.4] ClockworkMod Recovery for TF300T + ROOT
Hope I have made things more clear,
Cheers!
Click to expand...
Click to collapse
Wow! Thank you sooo much for taking it step by step
I tried it, and it went very well! :victory:
But one last thing; there is still a update-reminder in the notification-bar
This is the same notification that have been there since the first time I connected to the internet, before rooting and all that.
When I press the notification, all I can choose is "postpone" or "install update"...
A re-boot should clear that up.
Nope, I've rebooted several times already, but it's still there...
pogman99 said:
Nope, I've rebooted several times already, but it's still there...
Click to expand...
Click to collapse
Try to clear your cache and reboot.
And don't forget that you have an Index for the TF300 in the Dev Forum for help you or download
philos64 said:
Try to clear your cache and reboot.
And don't forget that you have an Index for the TF300 in the Dev Forum for help you or download
Click to expand...
Click to collapse
Have done that too. Booted the tab by pressing power+volume down and it started a "cold boot". Maybe there's another way also? I have cwm recovery btw...
Related
so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated
You can only install manufacturer ota updates with a stock recovery.
Doing the update can equate to a factory reset, at the very least will lose root - you'll have to re-root it.
Installing a PG59IMG.zip file will wipe your system.
Sent from a digital distance.
steve_77 said:
so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated
Click to expand...
Click to collapse
Id say backup apps with titanium backup and flash the pg5 zip
Sent from my RubiX NonSense using Tapatalk 2
edited
update
UPDATE:
finally got root:
used:
http://forum.xda-developers.com/showthread.php?t=1532809
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip
and flashed it through CMR...
for some reason other root methods just didnt work (i tried about 5 ) and at some point did have superuser.apk on phone but it said bad permissions, and i downloaded a "root checker" and it said i still did not have root..
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...
One thing I'd do is--
I apologize for being late to this thread; I would have listed a more straightforward method with source links had I referenced the conversation earlier. Be that as it may...
steve_77 said:
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip and flashed it through CMR...
Click to expand...
Click to collapse
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
From my experience, it sometimes doesn't want to install unless you follow these steps:
Boot into CWM recovery
Connect your phone to PC via USB
Choose "mounts and storage," then "mount USB storage"
When your phone directory shows up on your PC, copy the Superuser zip to the root of your SD card
Unmount USB storage and go back to the main CWM menu, then choose "install zip from sdcard"
Scroll down to the Superuser zip and select it. Installation should go without problems.
steve_77 said:
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...
Click to expand...
Click to collapse
Erm, no. You most definitely do not want to relock the bootloader. If you have root/s-off, updating Superuser is the only thing I'd recommend. You're golden for everything else.
Hope the above info proves helpful --
--
KingCheetah
KingCheetah said:
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
KingCheetah
Click to expand...
Click to collapse
I tried that the other day, however If i flash that version v3.0.7 (41) -
I no longer have "root" and my "rom manager" and "titanium backup" will not work
- the new su app did look nicer but - defeats the point if it doesn't function, im still trying to find a way to revert my phone and get the old version back in there(have to start all over). Im hoping there is a workaround for this behavior (perhaps there should be a separate thread on getting a working version of superuser 3.0.7 - as it installed fine)?
Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks
Ok. Now after searching some more and trying to manually install the very same zip that was downloaded by the OTA, I see the issue is with the verify/assert/check/md5 for /system/bin/gzip.
And I see the other threads where people discuss the cause and solution for this.
Still interested in how to make the OTA notification come back though
i have the same probleme as you. and don't know how to solve it
scootley said:
Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks
Click to expand...
Click to collapse
I think somehow CWM did stick and so you lost stock.
Use this guide to get back to stock. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
The OTA should come. If not try this trick to force it. http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
It doesn't say but pull your SIM or go into airplane mode first. Turn on wifi and make sure you have a strong signal. Cheers hope this helps.
For the time being, I:
* Tried to force an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Saw it present a checksum error for patching gzip
* Searched the forum for help
* Downloaded the full official 4.0.4 ROM zip for my phone
* Extracted system.img from it
* Converted that image file (not sure what format it is in) into an ext4 image using http://forum.xda-developers.com/showpost.php?p=15333542&postcount=135
* Mounted that ext4 image in linux
* Extracted 3 files from /system/bin in that mount: gzip, ip, ping
* Copied those files to /system/bin on my phone when it was in CWM via adb
* Forced an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Did part of the above steps in a loop, because the OTA update only tells you which files are not matching the checksum one by one
This allowed the OTA update to proceed.
I will check on CWM getting somehow stuck and on reverting it.
Thanks for the tips jayjay3333
I should also mention that I have very little interest in wiping my phone. In other words, to me one of the greatest benefits of Android is it's ability to update the OS successfully.
Luckily I got this to work.
Hopefully I can restore the original recovery without wiping the OS too.
scootley said:
For the time being, I:
* Tried to force an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Saw it present a checksum error for patching gzip
* Searched the forum for help
* Downloaded the full official 4.0.4 ROM zip for my phone
* Extracted system.img from it
* Converted that image file (not sure what format it is in) into an ext4 image using http://forum.xda-developers.com/showpost.php?p=15333542&postcount=135
* Mounted that ext4 image in linux
* Extracted 3 files from /system/bin in that mount: gzip, ip, ping
* Copied those files to /system/bin on my phone when it was in CWM via adb
* Forced an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Did part of the above steps in a loop, because the OTA update only tells you which files are not matching the checksum one by one
This allowed the OTA update to proceed.
I will check on CWM getting somehow stuck and on reverting it.
Thanks for the tips jayjay3333
Click to expand...
Click to collapse
No problem. Glad you got it sorted.
scootley said:
Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks
Click to expand...
Click to collapse
u must accept yes for that it should work.
abhidoT38 said:
u must accept yes for that it should work.
Click to expand...
Click to collapse
what?
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Help with OTA
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
dinothenino said:
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Click to expand...
Click to collapse
droidhaxxor said:
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
Click to expand...
Click to collapse
Thank you very much for your kind reply.I am rooted but still have not unlocked Bootloader. After i've read several threads i was too scared to unlock my bootloader,that's why i was waiting for some answers in order to do it. Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
As for the other thing that you mentioned "nVFlash" i don't know how to do it and although i have read some threads about it i am still very confused how to do it. If you could guide me through it, in simple steps, i would be very grateful. I am on .26 version if that helps.
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery, help is always appreciated !!!
Thank you again in advance,
dinothenino said:
Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
Click to expand...
Click to collapse
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
dinothenino said:
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery,
Click to expand...
Click to collapse
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
_that said:
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
Click to expand...
Click to collapse
You pretty much say it all, with unlocked bootloader, you could flash, custom recovery, kernel, rom, using fastboot, scripts excepted for boot animation for now, cause you need a kernel that supporting it, once we have a custom kernel that support boot animation, you could do that too.
Back to the OP topic, if you have locked bootloader, rooted and running .26 build, you have 2 options to upgrade, but first make sure you read the thread about how to make a backup of your bootloader using NVFLASH before upgrade to .30 or JB. This is extremely important and since you're still at .26, consider yourself a lucky one. Next make sure you have Voodoo OTA installed and make a backup of your root. Also verify that indeed you do have root by download "root checker" from the market. Also use Titinum backup and backup your device. Finally, you have 2 easy options to upgrade.
A. OTA,(incremental upgrade), automatic download and upgrade your device push out by Asus.(No brainer)
B. Manual upgrade, if you prefer to do a full version (fresh install). It is recommended that you do a factory reset before and after the upgrade.
1) Download the correct latest firmware from Asus site, for JB the firmware called US_epad_user_10_4_4_16_UpdateLauncher.zip (this is US version).
2) Extract the .zip file, it will be another .zip file. This zip named EP201_768_SDUPDATE.zip.
3) Copy the file EP201_768_SDUPDATE.zip from your PC to the root of your MicroSD card.
4) Insert the MicroSD card in your tablet and use this button combination to go to recovery --> Start the tablet by pressing Volume Down and POWER together for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire. At this point the device will go in recovery and should start updating your firmware.
5. If you upgrade from .30 to JB, you could skip step 4 and after step 3, just reboot your device and it should find and prompt you to update.
Thats it ..profit!!
There are couple more, but mainly used if you soft brick or issue, like extract the blog file from Asus download and use fastboot to push etc..but I don't think we need that right now.
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
johnlgalt said:
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=1915598
I found that using fastboot from your pc is working bit better.
Actually, quite funny as I was just reading that. I'm attempting to downgrade to 9.4.5.30 now so I can root and then Keep Root and then re-upgrade and see if I can repair root.
I suppose this would be a bad time to think about 'blobbing' the tablet to JB
I would be more worried about the process except for the fact that I checked the binary-script file and all it does it put the blob on the device. No stupid patching like in Motorola devices. Makes like easier to deal with (in terms of applying updates) but a heck of a lot more bandwidth used (in terms of OTAs).
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
johnlgalt said:
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
Click to expand...
Click to collapse
The OTAs contain patches for files in /system, and a blob for kernel, bootloader, recovery (EBT, SOS, LNX).
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.
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
ILowry282 said:
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
Click to expand...
Click to collapse
Since your post was made today, and the update was released yesterday I'm assuming you are thinking that you will be getting the update over the air? You won't. When you have a custom recovery (TWRP) you won't get OTA's.
But don't be disheartened, not in the LEAST. Unless you've removed or altered the default system apps (you would know if you did) all you have to do is download the update to your phone, boot into TWRP, flash the update, and let the phone reboot.
Due to how the OTA updates are rolled out, even if you had not loaded a custom recovery onto your phone, you might not have had it pushed to you for a couple of weeks.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2523217
From what you have described you are "scenario 2". Proceed directly to step B. Like many people, I was also step B. It is easier than making toast.
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
1. If you flash a custom ROM via TWRP it is generally recommended you do a clean wipe beforehand (and before doing that, obviously create a backup). There are cases where you can go straight to flashing without wiping, which is called a dirty flash. Although this is used when you're flashing an updated version of the ROM you're currently running. Following instructions under Section B won't cause you to lose data.
2. You won't lose root because ROMs will generally take this into account. However, if you do happen to lose root, just download and flash SuperSU and you're back on track.
3. Just flash the zip file.
ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
The first part of the reply above is certainly correct, (the rest is also, but I'm just speaking to the first part of it) but I feel it is just going to confuse you.
You did not flash a custom ROM, you flashed a custom RECOVERY. Two different things. When you copy the update onto your phone, in the form that exists in the thread I linked earlier, it is not an entire image. It is an UPDATE to the stock image, which you are already using. As for your concern of losing root, it shouldn't be a concern. As was mentioned in the reply above mentioned, while you are in recovery you can simply just flash SU again.
In fact, I'd be willing to bet the file to flash SU is still on your phone.
As for me personally, I happened to have unlocked the pro version of SU (because why not...it's only $2.50 and I like the app) and just toggled the "survival mode" option. But even if I had not, it would have been a very small thing to loading SU again.
In short, don't worry about losing root. When you first rooted this phone, most of the steps involved were not in rooting the phone, but in unlocking the bootloader. Loading this update has nothing to do with that, so in your case, since you didn't flash a custom ROM (Such as CyanogenMod) and you didn't make any modifications to the system apps...quite literally all you have to do is copy the stuff onto your phone, load into TWRP, fire up the update, and either fire up SU, or have survival mode already enabled, and reboot the phone.
(and no, you don't have to unzip the file pasted in the thread, just copy it directly) The instructions in that thread are really simple, and that's probably giving you a bit of pause, but seriously, it really is that simple in your case, as it was mine.
So I updated but lost root. How do I flash SU?
ILowry282 said:
So I updated but lost root. How do I flash SU?
Click to expand...
Click to collapse
Do you still have custom recovery cwm or twrp? If so download su zip from either of those posts and flash in recovery if not you can flash recovery with adb or flashify and then flash su zip.
Sent from my Nexus 5 using Tapatalk
Worked perfect. Thanks