Related
********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?
good job explaining nothing. troll harder
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?
i updated the zip and rebooted used busy box and i dont have that MCR app
Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?
slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there
arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken
slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....
slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.
Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?
Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.
So I received the OTA Update for my Samsung EPIC 4G stock build Eclair DI18.
Unfortunately it did not install due to missing packages.
I was rooted.
I was not running any custom roms,
I did use the SDX Stock App Remover to remove "nascar",
I have seen other people having problems because they are missing the "Asphalt Demo" apk.
Unfortunately if you remove Nascar or Asphalt you will get that error message when you try to install the OTA EC05 update, as well as if you try the manual method of upgrading by copying the update.zip. This happens because the installer is trying to verify packages for the upgrade (which you no longer have).
I went nuts considering all the different methods I could take to apply this update. I wanted the quickest and easiest method, and one that would leave my data intact.
So if this matches your situation, you don't have to reflash back to stock DI18 to recover a couple of missing stock apps and you don't need Odin or the 255 mb tar ROM that's out there (SPH-D700-DI18-8Gb-REL.tar.md5) etc. with this method.
So here is the method I used to restore my Stock Sprint apps so I could get the installer to run.
Before you start, make sure you know which packages you need to restore back to your /system/app folder. (unfortunately, their is no way of knowing which package(s) you're missing if you don't remember what you removed. You could cross reference what you have with someone who has all the stock apps OR the easiest way is to try to apply the update and write down or remember which apk it is complaining about. Chances are you already know which APK you're missing and that's why you're here. If you removed multiple stock apps, then you might have already guessed that you are going to have to restore each apk one by one, and so you may need to go through this process more than once to discover exactly which apk files are missing.)
These instructions also assume that you've already copied the DI18-EC05 update.zip file found in this thread http://forum.xda-developers.com/showthread.php?t=1005593 to your sdcard.
Download the stock Sprint apk packages from:
http://forum.xda-developers.com/showthread.php?t=987777
The file you are looking for that is linked from that thread is:
http://www.nubecoder.com/files/andro...store_EB13.zip (Even though these are EB13 app's it doesn't matter that you're on DI18, we just need the file to be there so we can trick the installer into running.)
Unzip this file and copy the apk's you need to your sdcard by first mounting your android phone in mass storage mode (usb debugging disabled). After you have copied the apk's to your sdcard, you will need to remount your system folder and copy the apks to that /system/apps location for the update installer to recognize it (simply installing the app to your phone won't cut it).
To continue you will need the Samsung drivers ( I am not providing links because this can be found anywhere on the web. My particular Samsung driver archive is called "usb_drivers_GalaxyS_x64.zip" (reboot your system after installing if necessary).
You will also need the "one click root" zip archive (or any other package that can give you access to the adb shell.) I used the adb shell from the "epic aio one click root" file archive "epic.aio.v1.13.zip".
Enable USB Debugging mode in your phone, and then plug your phone into usb.
Follow the instructions below to remount your /system partition as rw so that you can copy back (to /system/app) the missing apk packages that you've already copied to your sdcard.
Navigate to the location where your adb executable is installed:
1. cd C:\android-sdk-windows\tools> adb shell
2. $ su
3. # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
4. # cd /system/app
5. # ls (make sure it is mounted)
6. # cd /sdcard
7. # ls *.apk (show the apk package filenames)
8. # cp "apkfilename" /system/app (copy from current working directory [/sdcard] to /system/apps)
On step 8, replace "apkfilename" with apk's you want to copy. Repeat process as many times as necessary to copy back all the default apk's that you removed.
Taken partially from http://androidforums.com/2079717-post6.html
After you have copied all of your stock apk's back, simply unplug your phone, and reboot. Once you have rebooted press and hold volume down, power and camera buttons until the recovery menu pops back up, then simply select install update.zip
This time the installer will not error out on missing packages.
If you want to root your phone after installing the EC05 Stock Update:
http://forum.androidcentral.com/epi...optional-ext4-new-updated-2-a.html#post760733
For those who only need the stock epic asphalt demo here it is.
(Note to mods, this is a 5 minute demo only, not a full game. As such I believe it is ok to post.)
I was looking inside the run.bat file and I used a run.bat file that did not remove asphalt5.apk and freeHDGamesDemo.apk.
Now I don't know if you need the freeHDGamesDemo.apk or where to find it.
I was going to reinstall the asphalt5.apk, but do I erase the /sdcard/gameloft/ folder and if I do will it be recreated again or should I leave it in?
You can get rid of the gameloft folder on sdcard, thats where it puts the file it downloads when you launch the asphalt demo and it prompts to download. Be careful though, if you have other gameloft games they will also use that folder.
I'm not sure on the free hd demo file, if the ota complains about it we should be able to pull it from the eb13 tar file. If it's not posted by time the ota rolls out I'll add it here for ease.
Sent from my SPH-D700 using XDA App
rocket321 said:
You can get rid of the gameloft folder on sdcard, thats where it puts the file it downloads when you launch the asphalt demo and it prompts to download. Be careful though, if you have other gameloft games they will also use that folder.
I'm not sure on the free hd demo file, if the ota complains about it we should be able to pull it from the eb13 tar file. If it's not posted by time the ota rolls out I'll add it here for ease.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks, I am not a big game player so the little asphalt5 demo is about all I need - I never even opened the freeHDDemo file so I don't know what it does, I was only looking for it incase it stopped you from getting any minor updates via OTA's.
I didn't think the Odin EC05 no data loss upgrade version would remove those two apps on Androidcentral.
i did everything but when i went to the system menu to intall the update.zip i dont have that file...
where do i get it from?
Joph said:
i did everything but when i went to the system menu to intall the update.zip i dont have that file...
where do i get it from?
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1005593
Does anyone know an alternative method to getting CWM or rooting you phone because i updated my android to the official 2.3 update
and now i cant do anything and it says im not rooted when i am so could someone give me a link to get CWM without connecting it to the computer via USB?
Thanks!
You can replace the recovery.img, which is on .cust_backup/image with a file explorer with root access from the device(e.g es file explorer, root explorer...). You also need the "remount" app(you can find it on google play).
You must first run remount app, find the .cust_backup and remount it as rw. Then just copy the cmw recovery.img(from sd card in which you have previously put it) to the .cust_backup/image folder with the help of file explorer app.
need more info, what phone type?, what 2.3.5 upgrade did you use? if it is B526 or below, get hold of super one click 2.3.3(I think) and use it to root the phone, there is a thread on how to do this in the u8800 android development section. Then do as above and copy the recovery.img into the correct folder. Reboot and you will have cwm recovery.
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions
Nice work sub
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list
@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?
slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?
GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command
you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!
No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.
Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
This fixed it! That was a stupid mistake
kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.
I've had several Android devices. That was the easiest root I've ever done.
bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.