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?
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)?
Hello all,
sorry if this is a repeated question. I tried to read as much as I can in the Q&A and general sections, but could not find it.
I have a NS that was running CNA 1.4 for sometime. I got tired from the performance and I decided to give phone to my better half. Since my wife does not care much about custom roms, I decided to go back to stock so I can give her a care-free phone. She would be capable of doing the OTA updates on her own.
so, these are the steps I did to get to custom:
1. phone came with 2.3.4
2. unlock BL using ADB
3. root and install CWM
4. Nandroid backup
5. OTA update to 2.3.6
6. Nandroid backup
7. Custom ICS rom
when I tried to go back to stock I did a restore to step 6 above, the OTA was pushed automatically to my phone, but when I tried to install, the phone rebooted but did nothing and it seemed stuck at the android with an ! in a triangle.
I removed the battery, restored back to step 4 above and tried again and I got the same results.
I know I am probably forgetting something but I am not sure what is it.
Could someone please offer some direction?
thanks in advance.
Flash official factory images with fasttboot .
You cant get official OTAs when your device is rooted
thanks guys for your reply.
but what is the main cause for not being able to install OTA updates?
1. is it because the BL in unlocked?
2. or because of root?
if because of root, has anyone tried that app from the Market? could it be used to regain root after OTA?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
thanks again.
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
albundy2010 said:
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
Click to expand...
Click to collapse
thanks for the info.
one last question, when I rooted my 2.3.4, it also installed CWM recovery.
Does CWM interfere with the OTA update or just the root?
if it interferes, I'll have to find a way to go back to stock recovery, right?
Yes and no.
For the OTA process to go as "normal' stock recovery needs to be there. Normal as in get the OTA notifcation/auto download reboot and install.
No as in if you manually download or place the ota zip file on your internal storage it will flash in cwm like any other zip.
Also since ICS you currently have to flash the ota zips with aftermarkt recoverys if you do it manually. The pick zip from sd card in stock recovery is broken now.
In the stock rom under /system/etc there is a script that overwrites custom recovery with the stock one on every boot. Rename that file to .bak or something instead of its default .sh If you want to stock recovery back just change the file extenstion back and reboot the phone fully. Next time you boot back into recovery it will be stock again.
Or you don t go to stock recovery and flash the updates by yourself on your phone. Downloaf them and then flash them through CWM. But i think u havent got CWM anymore after grtting an official update. You ll get the original recovery again
thanks again guys.
currently I can go back to either 2.3.4 or 2.3.6 stock roms but both have CWM and root.
ultimately what I want to do is:
1. be able to un-root (probably using this market app)
2. download OTA on phone, do normal "reboot and install"
3. boot up with updated OTA rom.
4. regain root (probably using the same market app)
so, what I understand from prev posts, that I must put back the stock recovery (which I do not mind) for my steps above to work.
can I use ADB and fastboot to push the stock "recovery.img"? and where to find it?
I'll do some searching in the forums, but if someone happens to have link to the thread, it would be fantastic.
thanks again
Why dont you keep the root and flash the official firmware that you downloaded per CWM. So you dont have to unroot and root again later. Or do a factory wipe.
ok guys, so whatever I tried to do I was not able to get the stock recovery back to go with the "normal OTA download on phone, reboot and install thing", so here is what I ended up doing.
1. I had 2.3.6 (GRK39F), rooted stock rom, cwm recovery.
2. Download/install "OTA Rootkeeper" free app from Google Play Market. link below
3. Using "OTA Rootkeeper" app, did a "backup root", then "temp un-root"
4. Download official signed Google ICS update package to upgrade from 2.3.6 (GRK39F) to 4.0.4 (IMM76D) and move it to sd card. link below
5. Reboot into cwm recovery
6. Install update from sd card and choose Zip from #4
7. Go back and reboot system
8. After upgrade to ICS is complete, use "OTA Rootkeeper" app, did a "restore root" and voila
9. So now I have rooted stock ICS rom, and cwm recovery.
notes:
these steps should also work on whatever stock GB rom you have as long as:
a. rooted
b. have cwm
c. download the proper update package in step 4 above.
links:
2. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
4. http://www.randomphantasmagoria.com/firmware/nexus-s/
thanks again guys, couldn't have done without your help
good luck for anyone trying to do the same.
1.Download appropriate rom for your phone
i9020T or i9023
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020t_i9023.zip
and i9020a
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020a.zip
2.Copy it to sdcard
3.Install it through recovery (CWM)
4.Restart system
5.Reboot phone into bootloader
6. Hit recovery and once you get the lil droidy and the !, Push Vol up + Power until you get blue menu
7. Go to wipe data/fact reset
8.Reboot to bootloader
9.then go into adb and type fastboot oem lock
By this time you shouldve completely returned your phone to stock and you are able to get ota updates and everything!!! YAY!!!!
http://www.randomphantasmagoria.com/firmware/nexus-s/
if you wanna go back to 100% stock unrooted, download any rom from that thread and install through cwm then reboot and you will be stock and unrooted with stock recovery and then just lock the boot loader and you will be 101% factory stock and ready to receive ota updates. I would recommend the 2.3.6 because it will give you the 4.0.4 ota right after you reboot.
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM
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...
OK, so the MotoDev team advised me to return my phone to stock before installing JB, which will be pushed to my phone tomorrow morning...
What do I need to insure my system won't crash?
I have an unlocked bootloader, and am rooted. I already did a factory reset on my device. Some system apps are gone though, as I have deleted them (mostly Google stuff though, nothing crucial). Will I be good to go? (And yes, I will save the SBF and post it, no worries, have a Dev Host account and will upload).
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
hagforz said:
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
Click to expand...
Click to collapse
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
If you want to grab the update package and save it you should prevent it from being deleted. I know that twrp could not install asa14 OTA update when I got it so it was just hanging there in /cache along with md5 (or sha1, I can't remeber) checksum file.
I do not know if there are other ways of saving the update package nor if devs actually need it. But ASA14 got to my bootloader unlocked, gsm modded, rooted stock rom and after booting to recovery it just stayed there, no install happend (I installed it manually) because twrp did not pass the command properly or what ever the reason.
This update is coming from motorola directly, not sprint, right?
Anyway, perhaps someone can give you more accurate details. I personally would flash twrp and see if updated arrives. Because /cache is wiped by the update installer after installation. All automated process. After device boots to recovery it installs the package, wipes caches and reboots, if I am not mistaken.
I believe for the past updates we had the best luck by reverting the recovery back to stock as well. You have missing APKs that you removed so those will very likely be looked for by the update and will fail the update process if missing.
So if all goes well this should be the bare minimum I'd say for getting the update to work:
MAKE A BACKUP, don't want to have a bricked phone yeah? I mean you could have Jelly Bean on it finally... but still bricked...
Revert the recovery to stock if you installed TWRP or ClockworkMod, adb reboot bootloader | fastboot flash recovery recovery.img
Restore any and all apps you deleted from the stock image, either by restoring fully to stock or putting them back manually, wouldn't hurt to do another update check in the play store for them as well.
Temp unroot with OTA Rootkeeper
Download the update, reboot it, do a song and dance, ???, profit.
Now, you might try to restore root asap, it may or may not work, we won't know till we try.... I'm using Superuser 3.1.3 and on their website it claims its for arm devices 2.0-4.1 so maybe it'll work. Your bootloader should still be unlocked I'd imagine, so you can reflash your custom recovery and make a new backup.