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
Related
I tried to update my rooted TF using a repacked 8.4.4.11 update.zip file (the one with all the patch files in it), but it kept failing on checking of the existing APK hashes. Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file.
You should be able to apply this to any US version TF (rooted or stock as long as you have CWR) and bring everything up-to-date without losing root or any of your other install modules, system APKs, etc.
Make sure you back up first, as this is something I quickly threw together and has not been properly vetted. If you find a problem, let me know and I'll try to get it fixed and updated ASAP.
You can also download this ZIP and just take out any APKs you are interested in (the google video apk seems to be popular for example).
Link: http://blog.ryantadams.com/2011/07/...4-5-to-8-4-4-11-changed-files-rom-update-zip/
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
nicknowsky said:
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
Click to expand...
Click to collapse
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Edit: Thanks this is a great idea, and I was just ready to try this when I saw Prime 1.6 out. Keep it up, I wonder if something like this would work when the 3.2 update comes out.
ToyTank said:
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Click to expand...
Click to collapse
...Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file....
Click to expand...
Click to collapse
Looks like so; zip should be run on-top of 8.4.4.5.
thank you worked for me
This does not have SU in it (or anyhtign else "custom"), but when applied to a ROM that already has SU/busybox/anyhting else in it, those files will be retained.
This is an "update" in the sense that it only contains files changed between 8.4.4.5 and 8.4.4.11, so you will need to be coming from 8.4.4.5 (or perhaps anyhtign 3.1, not sure). It is nto really an "update" though, as all of the patch files (blahblahblah.apk.p) and the patch script have been replaced with full 8.4.4.11 version of the files and the script has been udpated to simply copy these over into the appropriate folders on yoru TF.
I see this being most useful for people who have modified their 8.4.4.5 install such that in will no longer be patachable using a script that pataches the existing files.
I just used this to update from 8.4.4.5_US and it seems to have worked just fine! I kept my superuser app, and nothing was touched. My apps, widgets, and settings are all in the right places. I've now got 8.4.4.11! Thank you very much rtadams89!
Thank you for this!! I've been racking my brain trying to get to a rooted 8.4.4.11 with a good CWM recovery and this did it!
thanks.
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
rpavich said:
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
Click to expand...
Click to collapse
My bluetooth works fine, using it right now. Did you tweak anyhting else on your TF?
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Does this also give you the Nvidia boot animation?
Is it possible to get a .zip for the WW version?
down8 said:
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Click to expand...
Click to collapse
Try clearing data for the "dmclient" app.
AllTheWay said:
Does this also give you the Nvidia boot animation?
Click to expand...
Click to collapse
Yes. Anything new or updated is included.
rtadams89 said:
Try clearing data for the "dmclient" app.
Click to expand...
Click to collapse
Thanks!
rtadams89 said:
Yes. Anything new or updated is included.
Click to expand...
Click to collapse
My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
+1, also interested on this
down8 said:
Thanks!My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
Click to expand...
Click to collapse
That is the boot animation I use, and I may have accidentally included this in the zip. If you want the real 8.4.4.11 animation, you can download the "update" 8.4.4.11 zip file that has been posted on xda and inside you will find that boot animation.
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
Since I don't have a WW version myself, I don't have a need to do this and quite frankly because I don't have much free time, I don't want to say I'll do something and then not follow through. Further, I'm not sure I can install the WW versions on my US transformer. That said, I will see if I can whip one together. If you get impatient waiting, you can follow the same process I did and make one yourself:
Backup your current ROM/setup
Wipe your device (leaving CWR in place)
Install the stock 8.4.4.5 WW with the ZIP found on XDA
"Update" to 8.4.4.11 using the update zip found on XDA
Backup this new 8.4.4.11 ROM
Restore to your first backup
Take the backup of the 8.4.4.11 ROM you made last, and use your computer to "unyaffs" it
You will now have 8.4.4.11 versions of all the system files; Look at the updater-script file in the 8.4.4.11 update zip and remove any files you just "unyaffs"ed that aren't mentioned in there
Put all of the remaining files (in their folder structure) into a zip file
Copy the updater-script (and it's folder structure) from my download to your zip file
Verify that your final zip looks like the one I posted
You should then have a ZIP file that will bring all the files on your device up to 8.4.4.11 WW without touching any of your other files (like su).
My BT doesn't turn on either.
I went to this as a stepping stone while recovering from a failed root. Went to an older stock than this update. I notice a few slow downs here and there and BT not working, but that's about it.
What I would really love is an image of 8.4.4.11 stock/rooted. I like having it rooted for things like Titanium, but I still like having the stock image. I can't seem to get back to that now.
Link is down, Dropbox says too much traffic. Rapidshare/MUpload?
This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
Has this been tested yet??
Thanks
*Offtopic*
delete ffs
same here, stock but with xoom system UI and bloatware deleted.
Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.
Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip
cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
The issue is I have it back on my device, I found it, and the update is still hanging on that.
daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...
Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?
Worked fine on mine, Thx.
daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.
Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market
Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?
The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.
Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.
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)...
Ok, From now on if i see people asking how to update / how to keep root im going to link you to this thread, im tired of answering it.
This works if you are on STOCK RECOVERY. If you are unlocked there are lots of other options for you (such as flashing a rooted kernel) so go to development and find that. Since im not unlocked i had to do it the hard way. This method works if your OTA updates are screwed up. If you HAVE OTA updates you can just use OTA rootkeeper to backup and disable root, make sure all stock apps are restored, and proceed with root.
Note for the updater: The OTA updater is a DIFFERENCE updater, if files are missing or different versions the update will fail. Best practices say to update sequentially, never skip an update. It might not cause problems now but could cause problems in the future.
If your OTA updates have failed or for whatever reason you can not get OTA's, you have a LOCKED bootloader, or for whatever reason want to manually update and keep root then this guide is for you. Also please note the process for going from .16 to .18 is the same as going from .30 to .16.
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
To reset the tablet if you dont have stock apps:
Determine which version you are running. For me it was .30WW
Go to www.asus.com and download the firmware for your version
plug your tablet into the usb on your computer, unzip the firmware and put it in the root of your tablet (Dont use USB memory sticks or SD cards, just transfer it directly)
restart your tablet, it SHOULD load the file and go about resetting the tablet to stock.
If that does not work, try starting the tablet holding power and volume down, on the splash screen press volume up and reset the tablet that way.
Once your tablet is returned to stock you can proceed.
Click to expand...
Click to collapse
Make sure you are ROOTED. Use whatever method works for you.
Now would be a good time to make sure superuser is updated, mine was old so a quick update on the market and its all good.
Use OTA Rootkeeper to backup root
Download the DLPKG file apropriate for your version.
If you want to update to JB you must have .30 installed and download the .16 file, WW or US, depending on your region. Other packages are provided for convenience (This method can be used to spoof the OTA update to any version as long as you have the file)
DLPKG for .26 WW HERE
DLPKG for .30 WW HERE
DLPKG for .16 WW HERE or HERE or HERE
DLPKG for .16 US HERE or HERE
DLPKG for .18 WW HERE or HERE
DLPKG for .18 US HERE or HERE
(Make sure you only take the file for the version you want to update to, only one step at a time, so if you are on .30 WW you need .16WW before you can do .18WW)
DLPKG for US .20 HERE
DLPKG for WW .20 HERE
DLPKG for US .23 HERE or HERE or HERE or HERE
DLPKG for WW .23 HERE
DLPKG for .25 WW HERE
You will also need the command file HERE or HERE
Transfer the files to your tablet using the USB cable.
If you use a USB memory stick or SD card make sure its formatted FAT32.
Please note there have been reported problems with people using USB memory sticks or SD cards, often the files fail. I have had best success using the USB cable provided with my tablet and directly transferring the file. YMMV.
Click to expand...
Click to collapse
Once the files are on the tablet use Root Explorer or your favorite root file browser to move the two files
(NOT THE STOCK FILE BROWSER IT CANT SEE THE ROOT DIRECTORY)
"command" goes to /cache/recovery
"dlpkgfile" goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-R-R for both.
Note: There has been a little confusion about "root directory" so i will explain a little further. The root directory is generally protected. You will have to be rooted (by definition, having root access, kind of like administrator access in windows) and use a file browser like root explorer. The stock file browser only lets you see a few specific areas and will not let you access the root directory of the tablet. Root explorer will also let you modify permissions which the stock browser will not let you do. Im sure there are other browser applications that work equally well as root explorer, thats just the one i have had success with. As always, Your Milage May Vary.
Click to expand...
Click to collapse
Go into OTA Rootkeeper and TEMP UNROOT.
Shut down the tablet. Remove the USB cord. Remove any USB memory sticks. Eject your Micro SD card. UNdock the tablet. Lets not let anything go to chance.
Press and hold both the power and volume down buttons (volume down is closest to the power button in case you forgot like me)
Soon as the splash screen comes up you should see some text on the left side, release the power and volume down buttons and press volume up.
Now just sit back and wait, this can take a while. I got myself a snack and took this time to stretch a little.
Once your all booted up you should be running JellyBean. Open OTA Rootkeeper and restore root.
Please note i did not come up with the steps in this guide. I did not originate the files. I am nowhere near smart enough to do all this on my own. I meerly collected the information and links to files and pieced it all together. I wrote this so even my father could follow these instructions so hopefully you all succeed! If something needs clarification please let me know.
- Edit -
Added notes on restoring tablet to stock.
- Edit -
Added .18 links. Thanks to xcal321 for providing them.
- Edit -
Cleaned up the guide a little. Hopefully its less wordy and easier to follow.
- Edit -
Added links to my personal google drive for nearly all the files, should have no problem for overseas users with limited access to mediafire
- Edit -
Sorry it took so long, added files for .20 US and WW. Will copy them to my personal Gdrive when i have more time.
- Edit -
Still alive, added .25 WW. Nearly all the files are uploaded to my personal google docs account so if something goes screwy let me know via PM
That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco
doncieslacco said:
That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco
Click to expand...
Click to collapse
If OTA works for you after that then use OTA. For a large portion of us OTA did not want to work so these are the steps i used. Essentially its the same thing, OTA downloads the same files and puts them in the directories mentioned. Just make sure you do the temp unroot before updating as forgetting to do that step has lost some people root.
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
are you unlock or locked? did you try to upgrade from .30 to JB?
buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
are you unlock or locked? did you try to upgrade from .30 to JB?
Click to expand...
Click to collapse
I'm unlocked and started the process on. 30 rooted. I did downgrade from JB though and wanted to be rooted again. Should I try to upgrade to JB manually? How should it update to JB, OTA download?
buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
Click to expand...
Click to collapse
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.
Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium
Jimmah555 said:
Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
TWRP implies unlocked, this method is for locked bootloaders.
If you are still getting the dead android try restoring the tablet to factory condition before proceeding. If you have any frozen apps, if you removed any stock apps, if you have a modified build.prop, etc. it can cause the update to fail.
i will update OP with instructions to return to stock.
Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
Windows security and linux permissions are two VERY different things.
Use something like root explorer to modify the permissions of the files once they are on the tablet. Once you transfer the files to your SD card or even via USB to the tablet the permissions get changed to RW-RW-RW or similar. As far as i know you can not do this in windows.
Syn010 said:
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.
Click to expand...
Click to collapse
Use an application like root explorer. Regular file explorers can not usually see the root directory of the tablet. If you are just using the stock file browser it will not work.
pileot said:
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
Click to expand...
Click to collapse
Thanks for the OP. I am having trouble getting the JB OTA.
I am running rooted and locked at .30 with some minor tweaks using Titanium backup. Those tweaks are removing ASUS and Google bloat app. In order to get JB OTA, do I have to reinstall the bloat apps or reflash .30? Does all the stupid bloat have to be there for OTA to occur? If so, I hate that.
john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.
quartercirclebak said:
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.
Click to expand...
Click to collapse
What did you use to gain root again? As far as I know, rebuffs does not work with JB. Or are you unlocked?
everytime i do, i get back to .30 and when i check /cache
dlpkgfile still there with rw-r-r
but command in /cache/recovery/ disappear
what i mistaken?
-lukin- said:
Does all the stupid bloat have to be there for OTA to occur?
Click to expand...
Click to collapse
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.
HeartWare42 said:
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.
Click to expand...
Click to collapse
Makes sense, thanks for the the concise explanation.
Thank you so very much. kept trying to root jelly bean before, and ended up bricking tab somehow. thankfully best buy exchanged under factory defect cause after bricking, it got super HOT. I'll donate some adult beverage money when i get paid.
thank you again.
Hello !
First of all, thank you for your post.
I have a question "Yes or No". I translated your method (thank you again) in french for the french users, and I told them that they could unlock the bootloader once the firmware is back to ICS (.30). I am not sure about it, I would like you to confirm this ?
Then the method would be :
Downgrade to ICS (v9.4.5.30 WW)
Root with RootDebugfs.bat
Unlock Bootloader
Temp unroot with OTARootKeeper
Upgrade to JB (v10.4.4.16 WW) with OTA
Restore root with OTARootKeeper
This guide will teach you the easiest method to root and install CWM on your HP Slate 7 2800! These instructions are for Linux, but you should be able to do this on Windows with the correct drivers instead of the android.rules files.
HP Slate 4600: I need someone to test this with the 4600!
DISCLAIMER: This was successfully tested on my HP Slate 7 2800 on Linux Mint 17. THIS COULD POTENTIALLY BRICK YOUR TAB IF SOMETHING GOES WRONG!!! Proceed at your own risk!
How to Root:
1. Download Cydia Impactor from http://www.cydiaimpactor.com/ and install it.
2. Download and install adb. There are multiple ways to do this. One way is to install the Android SDK from http://developer.android.com/sdk/index.html and install adb through the SDK manager.
3. Download the android.rules.zip from https://sites.google.com/site/jrc2swebsite/downloads/hp-slate-7-2800 and extract the .zip file.
4. Move the two **-android.rules files to /etc/udev/rules.d and mark as executable. Restart your computer.
5. Enable USB Debugging in Developer Options on the tablet. Connect it to the computer.
6. Open the Terminal Emulator on your computer and change the directory to the path where adb is located like this: cd insert/path/for/adb/ (hit enter)
7. Start adb and scan for devices by running sudo ./adb devices (hit enter.) You should see a serial number with the word device next to it.
8. Minimize adb and start Cydia Impactor. Make sure it says "# drop SuperSU su to /system/xbin/su." Click "Start." If you get a no device found error, click "Bridge" > "Connect" and then click start again.
9. Reboot your tablet. Download Root Checker from the Play Store to make sure you are rooted. Follow the tutorial in the next post for installing CWM Recovery and the SuperSU app to control which apps are granted root access.
DISCLAIMER: This was successfully tested on my HP Slate 7 2800 on Linux Mint 17. THIS COULD POTENTIALLY BRICK YOUR TAB IF SOMETHING GOES WRONG!!! Proceed at your own risk!
How to Install CWM Recovery and SuperSU:
Download CWM Recovery for the Slate 7 2800 from http://forum.xda-developers.com/showpost.php?p=49165523&postcount=1 and install following the instructions in the post.
Install SuperSU:
Download the latest SuperSU from http://download.chainfire.eu/supersu and flash in CWM Recovery.
Credits:
@Chainfire (SuperSU)
@rjwil1086 (CWM Recovery)
www.cydiaimpactor.com (Cydia Impactor)
Android/Google (Android SDK)
@jrc2 [me] (android.rules files)
Whoever taught me how to make the android.rules
If I left you out (I promise it was an accident,) please send me a PM and I will add you to this list.
Useful links:
CWM Recovery
SuperSU Thread
JB-SlateROM
Source Code for this tab (Thanks @tommyboy76!)
Restore Image (How-to install is on the same page as the image)
CWM Flashable Stock ROM
My Website
reserved
Bump
Bumping this so more will see this thread
Cydia is not working anymore with fw version 1.05.17, has anyone found a way to root the new fw? or to mount /system as rw? please let me know if you guys have anything
math_green20 said:
Cydia is not working anymore with fw version 1.05.17, has anyone found a way to root the new fw? or to mount /system as rw? please let me know if you guys have anything
Click to expand...
Click to collapse
Did the slate 7 have a software update? I will have to check that out. Just to make sure, what is your model number?
it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day
math_green20 said:
it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day
Click to expand...
Click to collapse
I'll post the link if I have it. Do you know what Android version this update is?
jrc2
math_green20 said:
it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day
Click to expand...
Click to collapse
HP has updated their website and only has the new update.zip there. The only thing I know of is a CWM flashable version of the old update.zip. You can find that at http://forum.xda-developers.com/showthread.php?t=2608181
Looking at other threads, the OTA does make rooting no longer possible.
jrc2
jrc2 said:
I'll post the link if I have it. Do you know what Android version this update is?
jrc2
Click to expand...
Click to collapse
It is still 4.1.1, I'm back on 1.05.6(The stock CWM flashable one), Idk how I did this but i've been able to get CWM back on my device without rooting, I tried to modify boot.img to disable the install-recovery.sh script, this got me stuck in a bootloop but allowed me to flash CWM and the old firmware back in, I guess I got lucky
I got the stock kernel and the Rk30_sdk one to compile but I don't understand how to repack it in boot.img, bootloop everytime.
Thanks for the help anyway buddy.
We should make an all-in-one post for this device with firmwares, CWM, rooting options and stuff
math_green20 said:
It is still 4.1.1, I'm back on 1.05.6(The stock CWM flashable one), Idk how I did this but i've been able to get CWM back on my device without rooting, I tried to modify boot.img to disable the install-recovery.sh script, this got me stuck in a bootloop but allowed me to flash CWM and the old firmware back in, I guess I got lucky
I got the stock kernel and the Rk30_sdk one to compile but I don't understand how to repack it in boot.img, bootloop everytime.
Thanks for the help anyway buddy.
We should make an all-in-one post for this device with firmwares, CWM, rooting options and stuff
Click to expand...
Click to collapse
I sort of started that in the 2nd or 3rd post here, titled "Useful Links".
I simply can't root this device.
Cydia Impactor responds with "signature bugs unavailable" and all this Chinese 1-click root stuff doesn't work at all.
Tried on Linux Mint and Windows 7 (both x64).
The problem might be my firmware, which is v1.05.18_user.
This is the stock firmware that was preinstalled on my tablet.
How can i downgrade the firmware?
Oddy94 said:
I simply can't root this device.
Cydia Impactor responds with "signature bugs unavailable" and all this Chinese 1-click root stuff doesn't work at all.
Tried on Linux Mint and Windows 7 (both x64).
The problem might be my firmware, which is v1.05.18_user.
This is the stock firmware that was preinstalled on my tablet.
How can i downgrade the firmware?
Click to expand...
Click to collapse
Sorry I didn't see your post until now! I do not have the latest firmware on my tablet, so I haven't experienced this problem (I decided not to update after seeing the reports of people being unable to update. @math_green20 somehow managed to get it downgraded, but I do not know exactly how he did it. You might be able to figure out something from the previous posts in this thread.
Have a great day!
jrc2
hi Any new Rom is available for HP slate 7 voice TAB ,Please provide the isntructions
vinaymysore777 said:
hi Any new Rom is available for HP slate 7 voice TAB ,Please provide the isntructions
Click to expand...
Click to collapse
If you are talking about the 2800, then no,, I do not believe so.
jrc2 said:
If you are talking about the 2800, then no,, I do not believe so.
Click to expand...
Click to collapse
hi JRC2,
Im having HP slate 7Voice tab 6102 RA whether this is 2800 or other version
What is the Rom available for this tab