Update File for new firmware - Asus Transformer TF700

here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile

DroidEris1981 said:
here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile
Click to expand...
Click to collapse
I suggest that you rename it to the file name that recovery will accept and it should flash as normally done with the full firmware (in theory).
Is this for us version?
did you adb pull off the cache?
thanks!

FYI - after renaming this to "US_epad-user-9.4.5.26.zip" and putting it in on the root of my MicroSD. The system detects the update right away, but also fails right away (android guy on his side - red exclamation). After I boot back into .22, I have a message waiting saying the the update failed becuase the update file was older the the current version (which simlply isn't true - I'm on .22 for sure).
The OTA file looks fine to me (manifest inside says it's .26)...
Anyone have any ideas?
EDIT: Here is the update portion of the error log from /cache/recovery (it simply believe's it's the wrong version!):
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /data/media/US_epad-user-9.4.5.26.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
E:check version fail
Installation version error.
I:result_code: 80000013
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
Thanks!

All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)

Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
Trying this right now.

E:check version fail
Click to expand...
Click to collapse
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
eoh7678 said:
Trying this right now.
Click to expand...
Click to collapse
Do let us know if it works or not!

Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace, OTA insists that there is no update available. Any ideas for a fix there?

Redefined301 said:
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
Do let us know if it works or not!
Click to expand...
Click to collapse
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!

eoh7678 said:
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Click to expand...
Click to collapse
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...

Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
Have already tried that- correct firmware installed, dlpkgfile for correct region placed in /cache, still no love.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace missing and altered apk's and build.prop, OTA insists that there is no update available. Any ideas for a fix there?

Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...

jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
jtrosky said:
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...
Click to expand...
Click to collapse
The same file name as it was originally came from.

Redefined301 said:
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
The same file name as it was originally came from.
Click to expand...
Click to collapse
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?

jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.

jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.

eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...

eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Did you messed with your /system too? If not then version should be correct ?

Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.

jtrosky said:
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...
Click to expand...
Click to collapse
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
eoh7678 said:
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.
Click to expand...
Click to collapse
Don't bother because here I've got another tablet and it's not up to date yet checked for update and there's none available, the update was just available ota for few hours.
So let's put it this way, this is a BETA version and not supported.

Redefined301 said:
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
Click to expand...
Click to collapse
I'm not following. As far as I know, people are still receiving the update - it's not "pulled" or anything - just not working for a select few as far as I can tell.. I've also heard a lot of users saying that it makes a noticeble performance difference.
I give up - I guess we'll just have to wait for Asus to post the full version (it seems to take a week or so before they post the full firmware)...

Related

[UPDATE] CWM - Stock + Root - 9.2.1.27 US Updated 8/20/2012

I'm back, baby!
Sorry for letting you all down insofar as you've relied on me for porting the stock updates to CWM-friendly versions. So to catch up, here's the 3 OTAs US users need to get current. On the off chance Asus updates our transformer tf101 any more, I'll mod those as well.
It's been a while since my previous update, so I assume that most of you are on the latest stock ROM by now, or have jumped ship to a custom ROM. If you'd like a cwm-friendlified version of a stock ROM for a non-US device, let me know and provide your dlpkgfile.
These are stock updates repackaged for Clockwork mod.
This update DOES NOT:
* Root your device if it's not already rooted
* Install clockworkmod
* Install at all if you aren't rooted
* Install at all if you don't already have clockworkmod.
* Install at all if you are on a custom ROM.
This update has:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.1.3)
* No longer contains Busybox. Use Jrummy's Busybox installer.
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW or TW firmware, whichever the file requires.
4. The appropriate prerequisite firmware (e.g. the latest firmware before this update)
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
Your firmware/locale not listed? Send me your dlpkgfile and I'll add it.
CWM package for ASUS TF101 FOTA 9.2.1.27 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-9.2.1.27-US.zip
Tested by me
Prerequisite: 9.2.1.24 US
CWM package for ASUS TF101 FOTA 9.2.1.24 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-9.2.1.24-US.zip
Tested by me
Prerequisite: 9.2.1.21 US
CWM package for ASUS TF101 FOTA 9.2.1.21 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-9.2.1.21-US.zip
Tested by me
Prerequisite: 9.2.1.17 US
Older / Other packages
http://bellybuttonporn.com/android/transformer/
I have gobs of web hosting space, so I don't plan on removing my old releases any time soon. Find them all here.
FAQ
Q. Will my non-stock/custom/tweaked ROM work?
A. Probably not!
Q. I get an assert error about a file ending in .ko, what's wrong?
A. You replaced your kernel, didn't you? Put the original kernel and kernel modules back and try again. Put all the .ko files back, it will error out on the other ones too.
Q. I get an assert error about a file ending in apk or odex, what's wrong?
A. You replaced a bundled app, didn't you? Netflix is a big culprit here. You need the original apk and odex back.
Q. After I updated to this firmware, X doesn't work! Help!
A. Hold on there, friend. If the update works and you see the new version number after reboot, then my involvement is all done. Your problem is either imaginary or with the stock rom. Search for an existing thread with your question. If you don't find one, search again. If you still don't, then post a thread in the appropriate forum.
Q. Why haven't you been updating?
A. I don't know! But thanks for all the PMs. It's nice to feel loved.
Is it possible to have WW version too? Thx
+1 for WW version....
Thanks daoist,
Has anyone have a copy of the last version of Music2.odex? I've long since for some reason done away with it.
Also, what is the proper way to blow away the patch check and apply for a single thing like music.odex, and then rezip it so that it is recognized as valid?
Thanks,
---------- Post added at 08:20 AM ---------- Previous post was at 08:00 AM ----------
hachamacha said:
Thanks daoist,
Has anyone have a copy of the last version of Music2.odex? I've long since for some reason done away with it.
Also, what is the proper way to blow away the patch check and apply for a single thing like music.odex, and then rezip it so that it is recognized as valid?
Thanks,
Click to expand...
Click to collapse
Never Mind:: I didn't realize I was a level off (1 too high) on rezipping, so it works fine now.
Note: Just in case anyone else needs to remove lines from updater-script and repackage, don't make my mistake. At first I had repackaged from a level above so that I wound up with the first thing visible in the .zip file being kwt-cwm-*18, rather than all the stuff inside of it. That causes an update error immediately, so I just moved down and only rezipped the files inside the first folder.
Thanks much -
Why is this file smaller than the one that Asus pushed?
jadesse said:
Why is this file smaller than the one that Asus pushed?
Click to expand...
Click to collapse
The one asus pushed has a blob file which will overwrite the recovery partition (e.g. it will remove clockworkmod). In order to keep cwm, the SOS recovery partition is removed from this update.
If you have a WW transformer and wouldn't mind being a guinea pig, try this update:
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.18-WW.zip
Let me know how it goes.
Thanks, the upadte is installing now!
Installing, but si it working ?
Caramel said:
Installing, but si it working ?
Click to expand...
Click to collapse
It works just fine on my TF running ADW EX launcher.
It might just be my imagination, but the scrolling widgets
even seem to be more responsive.
Thank you daoist!
Eric
daoist said:
If you have a WW transformer and wouldn't mind being a guinea pig, try this update:
Let me know how it goes.
Click to expand...
Click to collapse
I've installed it without issues.. Now i'll test how it works. Thx about ur link
Anyone else confirm that the WW package I posted works?
daoist said:
Anyone else confirm that the WW package I posted works?
Click to expand...
Click to collapse
I have a WW TF and your WW package worked perfectly.
Many thanks!
how did you get Backup app working? easy fix? thanks
Sent from my Transformer TF101 using Tapatalk
Can you update the main post with the WW CMW version ? (since others comfirmed it working..)
Hi
Just being a bit of a noob here; How do I apply the update?
I'm on a Transformer WW-version
Just copy the file to /sdcard/update.zip??
Root Access Is Denied
I installed the update without issue and double checked root which was working. Now, after a few hours later my root access is denied. I haven't changed anything. Any ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
TomTcom said:
I installed the update without issue and double checked root which was working. Now, after a few hours later my root access is denied. I haven't changed anything. Any ideas?
Click to expand...
Click to collapse
Thought it was an update that I did to Superuser, I uninstalled the update, rebooted and no luck. I'm going to attempt to reflash the update from this post.
---------- Post added at 09:54 AM ---------- Previous post was at 09:37 AM ----------
Well that didn't work at all. I attempted then to update superuser through superuser but it was denied. Not sure how this all happened, maybe it was the market update to superuser.
Unless there are any ideas I may go back and re-root using the Toolkit.
---------- Post added at 10:17 AM ---------- Previous post was at 09:54 AM ----------
So I redid the root toolkit. Everything installed exactly as it should but root anything is still denied. I'm not going to blame this update but I'll try and get to the bottom of this and report back just in case it happens to anyone else.
---------- Post added at 10:37 AM ---------- Previous post was at 10:17 AM ----------
Ok, got my root back. I redid everything then redid the Asus firmware update. Wow, odd. Well anyways if anyone loses it you may have to go back and re-root with Toolkit (if that is what you used) and reinstall the update from this thread.
So not sure if this is the correct method but I changed the way I installed it. I did Toggle Script Assert on and then installed as opposed to just a standard install zip from SD card. So if I've missed instructions anywhere and this post was a big waste I'm sorry.
Rejh said:
Hi
Just being a bit of a noob here; How do I apply the update?
I'm on a Transformer WW-version
Just copy the file to /sdcard/update.zip??
Click to expand...
Click to collapse
Hmm well that doesn't work.
(Copied zip to update.zip, rebooted in [stock] recovery and pressed volume_up when prompted)
Do I need Clockwork Recovery?
UPDATE: nevermind, just read it in the first post
baseballfanz said:
how did you get Backup app working? easy fix? thanks
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Assuming you have root, you have to remount /system rw, and then chmod 4755 /system/xbin/asus-backup
Sorry if this has been covered but I cannot figure it out.
I'm trying to install this update but I'm getting an assert error I cannot get past.
error message
assert failed: apply_patch_check("/system/app/AWS.apk".
I did uninstall Asus webstorage before so I went to the app store and installed it from there but I'm still getting the same error. I have searched the web but cannot find AWS.apk to download and install or drop in that folder.
Any idea how to get past this other than restoring my system?
Thanks

[Q] Difficulting Rooting

So I just got my TF101 and I am also relatively new to Android. I am on version 3.2.1, Kernel 2.6.36.3 ([email protected] #1), Build number HTK75.US_epad-8.6.5.13, and my Serial number starts with B80KA.
Since I am on 8.6.5.13, I can't use Razorclaw, which is unfortunate.
I have tried using the Transformer Root Toolkit v7.1, but I can not get it to recognize the device when it is in APX mode so I am stuck there.
I also looked at this thread and followed those steps to no avail. Should I grab the OTA update and try those steps again? Or is there an easier way?
Thanks!
Edit: Fixed Serial.
First of wrong serial number.
Use the serial number on the bottom of your tablet or the back of your box.
Any how try this
http://forum.xda-developers.com/showthread.php?p=20809986
The link you posted is almost identical to the one I did. So that suggests that I should just grab the OTA update and then root it?
SimonSaysBleed said:
The link you posted is almost identical to the one I did. So that suggests that I should just grab the OTA update and then root it?
Click to expand...
Click to collapse
if you grab the OTA you'll get 8.6.5.21 which definitely is NOT rootable with Razorclaw.
seems like the two methods is almost similar but slight different, i would at least try both to see which one work if any.
Sent from my Transformer TF101 using Tapatalk
You should search for OTA .19, I think it was posted around here somewhere or maybe via google, so you can update to .19 and use Razorclaw's tool.
Well I have 8.6.6.19 (in the form of UpdateLauncher_WW_epaduser8_6_6_19.zip), so does it matter that it is the one for the TF101G and not the TF101?
Also, what exactly do I do with that zip file to install the update? I tried booting into recovery but that didn't do much.
SimonSaysBleed said:
Well I have 8.6.6.19 (in the form of UpdateLauncher_WW_epaduser8_6_6_19.zip), so does it matter that it is the one for the TF101G and not the TF101?
Also, what exactly do I do with that zip file to install the update? I tried booting into recovery but that didn't do much.
Click to expand...
Click to collapse
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1
baseballfanz said:
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1
Click to expand...
Click to collapse
But now I can't get into recovery mode. I could get into it yesterday but it didn't work, but now I can't get in at all...
baseballfanz said:
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1
Click to expand...
Click to collapse
I try this and not works
I have a TF101G serial BAO... with firmware 8.6.6.23. When I enter in recovery mode, after a few seconds appears a yellow triangle (yellow warning) inside android body and don't install nothing...
Any sugestion?
dinotav said:
I try this and not works
I have a TF101G serial BAO... with firmware 8.6.6.23. When I enter in recovery mode, paste a few seconds appears a yellow triangle (yellow warning) inside android body and don't install nothing...
Any sugestion?
Click to expand...
Click to collapse
Did you extract the content of the zip file or did you just use the file you download?
baseballfanz said:
Did you extract the content of the zip file or did you just use the file you download?
Click to expand...
Click to collapse
1) Extract and copy "WW_epad-user-8.6.6.19.zip" to my microSd card
2) copy the same file with the name "EP101_SDUPATED.zip"
3) copy this 2 files for internal sdcard of my TF101G
4) Enter in recovery mode. Power On + Vol Down, then Vol Up
I think that i make the things right....
Hey I finally got it to boot into recovery...and it worked! And I'm rooted! Woohoo, thanks everyone.
Now my last question is hopefully more simple. What do I do since my TF downloaded the OTA update? Is there a way to permanently postpone the update install? Will it go away if I install a custom ROM?
SimonSaysBleed said:
Hey I finally got it to boot into recovery...and it worked! And I'm rooted! Woohoo, thanks everyone.
Now my last question is hopefully more simple. What do I do since my TF downloaded the OTA update? Is there a way to permanently postpone the update install? Will it go away if I install a custom ROM?
Click to expand...
Click to collapse
If you install a custom ROM it will go away. Alternatively you can install the latest stock ROM with root by installing this "custom" stock+root ROM. The system will be left exactly like you had somehow rooted the latest stock ROM.
You could flash a rooted stock rom or you can go into
Settings>Applications>Manage application>All>DMClient>Clear data.
Could also use Titanium Backup to freeze DMClient
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
dinotav said:
1) Extract and copy "WW_epad-user-8.6.6.19.zip" to my microSd card
2) copy the same file with the name "EP101_SDUPATED.zip"
3) copy this 2 files for internal sdcard of my TF101G
4) Enter in recovery mode. Power On + Vol Down, then Vol Up
I think that i make the things right....
Click to expand...
Click to collapse
Double check you files and make sure it's not filename.zip.zip
baseballfanz said:
You could flash a rooted stock rom or you can go into
Settings>Applications>Manage application>All>DMClient>Clear data.
Could also use Titanium Backup to freeze DMClient
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
Double check you files and make sure it's not filename.zip.zip
Click to expand...
Click to collapse
Confirmed that the filename have only one ".zip"
My microSD card is FAT32 format... Have to be in NTFS?
dinotav said:
Confirmed that the filename have only one ".zip"
My microSD card is FAT32 format... Have to be in NTFS?
Click to expand...
Click to collapse
FAT32 is correct format.
Make sure it's on the root of the sd card and not in any folder
File name:
Code:
WW_epad-user-8.6.6.19.zip
EP101_SDUPATED.zip
Maybe try a different sd card if you have one.
Also just double checking but when entering recovery,
are you waiting to see the words at the top left of the screen prompting
you before pushing Vol up.
baseballfanz said:
FAT32 is correct format.
Make sure it's on the root of the sd card and not in any folder
File name:
Code:
WW_epad-user-8.6.6.19.zip
EP101_SDUPATED.zip
Maybe try a different sd card if you have one.
Also just double checking but when entering recovery,
are you waiting to see the words at the top left of the screen prompting
you before pushing Vol up.
Click to expand...
Click to collapse
Ok, i gona try with a different sd card. Yes i know, i see the words, then I push Vol up to load boot.
Remember that I have a TF101G and not TF101.
dinotav said:
Ok, i gona try with a different sd card. Yes i know, i see the words, then I push Vol up to load boot.
Remember that I have a TF101G and not TF101.
Click to expand...
Click to collapse
Yes the files that everyone is using is actually made for the TF101G
but it's also working on the TF101.
baseballfanz said:
Yes the files that everyone is using is actually made for the TF101G
but it's also working on the TF101.
Click to expand...
Click to collapse
I tried a different sd card but give me the same error. I saw the Android guy with some gears turning but 10/15 seconds later appears a yellow triangle
Hi dinotav,
I don't think we (those with TF101G/8.6.6.23) have any options at this point.
dinotav said:
I tried a different sd card but give me the same error. I saw the Android guy with some gears turning but 10/15 seconds later appears a yellow triangle
Click to expand...
Click to collapse

Rolling back

I know this is going to sound silly but is there any way to roll back to previous firmware after an update?
yes you can, after the update, if you have not deleted the backup, simply go to settings->phone->update. In there you will see a restore button with a date on it. Hopefully that should work.
japmeet said:
yes you can, after the update, if you have not deleted the backup, simply go to settings->phone->update. In there you will see a restore button with a date on it. Hopefully that should work.
Click to expand...
Click to collapse
The restore button is not there as I expected, the same thing happen to me before where Zune back ups disappear from the default folder you just mention. I know this as fact because the last back up did show up and the restore button was there then one day while checking for updates it just vanished, I was like WTF? So I actually copied a back up from like 5-11 but I don't know how to make Zune see the pks file I tried to use the Windows Support tool app but it tells me "a prior backup does not exist in the proper location to restore to your device". Please help, I don't want to go to Android or iPhone. Thanks.
I'm assuming you're trying to make zune see the pks file, but aren't backups made in .dat and .hash file formats? this is pretty annoying
japmeet said:
I'm assuming you're trying to make zune see the pks file, but aren't backups made in .dat and .hash file formats? this is pretty annoying
Click to expand...
Click to collapse
Yea I know it's anoying; when I went to the default folder where Zune saves the back upfiels all I saw was this pks file, I'm thinking that if there were were a dat or hash file, I might have missed them; in that case I'm out of luck.
sinister1 said:
The restore button is not there as I expected, the same thing happen to me before where Zune back ups disappear from the default folder you just mention. I know this as fact because the last back up did show up and the restore button was there then one day while checking for updates it just vanished, I was like WTF? So I actually copied a back up from like 5-11 but I don't know how to make Zune see the pks file I tried to use the Windows Support tool app but it tells me "a prior backup does not exist in the proper location to restore to your device". Please help, I don't want to go to Android or iPhone. Thanks.
Click to expand...
Click to collapse
Do you still have the backup?
---------- Post added at 11:34 PM ---------- Previous post was at 11:30 PM ----------
You can try this steps see if it works : http://forum.xda-developers.com/showthread.php?t=1448950
Ttblondey said:
Do you still have the backup?
---------- Post added at 11:34 PM ---------- Previous post was at 11:30 PM ----------
You can try this steps see if it works : http://forum.xda-developers.com/showthread.php?t=1448950
Click to expand...
Click to collapse
Yes Sir, I still have the back up; I'll try your link. Thank you so much.

Sprint OTA

Just got notification of OTA update to patch stagefright on LS996.
Im rooted so I guess I'll wait for mods to update and patch root new system.img
Anyone know where I can pull the update.zip never done it in lollipop...
Pretty sure its in your /cache folder. Almost positive that is where I pulled my last OTA from. Good luck!
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
If you do manage to pull the update, post a link so I can add it to my collection please =)
Didnt find it in /cache using root browser and Im rooted ZV7. Any ideas where it might be. I can do a pull and upload it so you can save it.
Ha! I found it...
/data/data/com.google.android.gms/app_download/
In case anyone is interested, you can download it here!
https://drive.google.com/file/d/0B2ihvr_1hzAnX0I2ZXV5Q3E0Zlk/view?usp=sharing
Thanks man, I actually wanted to delete it... I thought I had disabled updates thru disableservice app. But it downloaded the update anyway...
Try freezing the Update Center app. I unfroze it last night and the update hit this morning.

Testers needed for Samsung Galaxy M, A and few more series..

Hi All,
I am planning on providing Samsung Galaxy stock debloated ROMs for M series FLOSS or GFS version.
Please contact me here for testing purposes and if anyone is interested.
Few added stuffs maybe given as well, depending on the kind of framework changes, as I will avoid any changes, as the FW breaks a lot.
I do not have any phone, hence all testing will be on the testers, so be sure to keep backups in case you agree to test.
Moreover, OTA is not possible and most probably it will be a decrypted OS. You will need good bandwidth and patience to do it.
Everything that you people do on TG can be done here, needs patience, which is all one should always have.
Share this with others, who wants to join. I will try any other series too, but only android 9 and 10 at the moment. Android 11 is not in my list.
Glad to hear that
TWRP
Nazim navas said:
Glad to hear that
Click to expand...
Click to collapse
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
vdbhb59 said:
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
Click to expand...
Click to collapse
I am not sure about the twrp it has some bugs
M21_Testing_20200929.tar
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built, and uploading. It is a heavy file, around 4.2 GB (hopefully only one time). Flash with ODIN (in AP). Uncheck auto reboot.
Reboot to stock recovery, format data, mount /system, format data once again, and reboot to DOWNLOAD mode.
Then try each of the following boot methods:
01. Reboot normally (you can keep auto-reboot" checked for this trial) - If fails, try 02..
02. After flashing, reboot to recovery, format data, dalvik/cache, reboot - If fails, try 03..
03. Extract the 3 files, and zip to a .zip extension via 7zip and not WinRAR. Add the META-INF (full folder) folder from the attached zip, to the ROM zip and flash via TWRP (the one available).
-- Unzip the META-INF zip, and unzip the tar file ROM. Copy them all to say desktop and add all 3 files and the META-INF folder to .zip via 7Zip. Resultant file should be a zip file consisting of META-INF folder, boot, system and recovery image (.img) files.
-- The tar file consists of boot.img, recovery.img, system.img. - If fails, try 04..
04. If for any reason you are not able to boot, just replace the boot and recovery with the original/stock boot.img and recovery.img, do not change the system.img I gave. Add all to a tar file (via 7Zip) and flash via ODIN. Please note, do not use any other file. Chances are you will boot.
Please note, booting may take a minimum of 10-15 minutes, so please be patient. Once SAMSUNG logo comes it should ideally boot. I am yet to get a way to make DM-Verity work with ODIN. I will post link of ROM soon.
ROM uploaded. N. B. Testing only. https://cloud.operationtulip.com/s/nb7TjDAskmL47tn/download
Ohh, and in between each try, or failures, you may have to format data (may). At times I have seen for any reason if it fails, clearing or formatting data is needed which is odd on M series, but not always. Probably, trial error mode, but I do recall.
Also, in the 4th option, if you boot with stock boot and recovery, you will not be rooted. I will try and add root to the system, but cannot guarantee as of yet.
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built few testing TWRP's. Try them out and let me know what works, what not please.
1. TWRP+Mod - This is a modified version of what I wanted to build out of TWRP. This consists of that old TWRP, but modified to suit the latest builds. - Link
2. TWRP+Stock - This has stock features enabled. Should be good to go anyways. - Link
3. TWRP+vdbhb59 - This I have modified in many many ways, so should be good to go as well. - Link
4. TWRP_20201001_Test - Image/Tar - This I have made from scratch. If you say this one works, then I will load this as Unofficial (until TWRP accepts it) as Android 10 working.
In each let me know, what is working, and what is not.
You should be able to flash DM-Verity through these, post you install the OS I gave. File attached (do not rename the file).
All M21
If you face any issues try flashing twrp+boot via .tar in AP in one file. Then check.
There are telegram groups check thier forums !
prashantp01 said:
There are telegram groups check thier forums !
Click to expand...
Click to collapse
Is anyone working on TWRP? For M21 yet? Android 10
Twrp odin fail
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
ahmad_subqi said:
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
Click to expand...
Click to collapse
Yeah I know. As I mentioned, trial error run and testing to understand what can be done.
Can you post logs?
Nazim navas said:
The twrp not working
---------- Post added at 07:14 AM ---------- Previous post was at 07:10 AM ----------
I rooted m21 through odin
Click to expand...
Click to collapse
Okay, can you try what I mentioned about the ROM through ODIN? I need to know that first. TWRP is not the necessity as of now, but to boot up modified system binary is. Please flash the rom via ODIN, as mentioned in the earlier post. Not with TWRP.
Edit: Also give what ever error you face. Snapshot, in writing, and the stage at which you get the error, etc.,
Check if any of these TWRP work: https://www.androidfilehost.com/?w=files&flid=318632
Nazim navas said:
A51 ported twrp working but internal storage not working not sure about first one
---------- Post added at 02:54 AM ---------- Previous post was at 02:53 AM ----------
The bugs in ported twrp from a51
I checked the twrp last 2 days it is not working perfectly as expected
*unable to backup or restore showing error like key is absent /twrp folder is not found
*error in internal storage may be due to encryption
*error flashing dm verity zip/multi disabler zip (/odm not found )
*unable to flash gsi images as it is not showing system image during flashing it only shows boot,recovery,optics,spectrum and super
*unable to repair /change format in wipe section
*all others like sd card /usb is mounting no issue with that
All this are my personal experience when i tested the twrp hope any developers will fix this soon
Click to expand...
Click to collapse
Okay, these bugs would have been there, as whoever ported they could not get a working one having /superimage and since /odm is not there as separate. ODM is a supra path, rather than individual path. This will take time, else will have to gather latest stock and make it as Pie would be like. Will take time though.
Thanks for testing out mate.
i got m31, ill be happy to test if any m31 develeoping avilible
anilkuruhan said:
i got m31, ill be happy to test if any m31 develeoping avilible
Click to expand...
Click to collapse
Thanks mate. Can you share the latest version and country code details? Also your system details (about) page. It will help me find more information.
Nazim navas said:
Model no SM-M215F/DS
Click to expand...
Click to collapse
The trouble with latest updates is it has superimage. The super unpacker/packer does not work properly. You tested earlier. M21 has that. M31, I have not checked yet. If it has superimage too, then I will have to wait till I get a working one. Will check.
Thanks again.
Nope, superimage. I am having serious trouble with my W10 to run these even with VMUbuntu. Will only be able to work if that acts properly.

Categories

Resources