Related
Since I cant post in development section I will ask here if someone can help me. I have U8800 with 2.3 stock rom and I cant remove stock apps (swype in my case).I am rooted with DooMLoRD_v3_ROOT and SU is instaled. I did find apk file (/cust/hw/default/apk) but I am not able to remove it. I tried with titanium backup, root explorer, terminal emulator (cant find target) and with super manager.It seems like I am half rooted as root explorer cant mount rw in cust directory but works in system directory.Any idea is welcome,thank you!
You need to do it manually via adb shell. First to mount the partition as rw and then to remove it. I want to remove this file too, so I' ll try it asap.
EDIT:
I tried but this partition which is on /dev/block/loop0 cannot be mounted rw, I get a permission denied error.
.
In pinkscreen mode delete cust.image file,then delete apps with titanium backup.
We want to delete only some apps.
With your way we loose all huawei' s custom configuration, it' s like we don' t install step3.
This is not a solution.
I hope that we can find solution for this as I want to instal costum swype with my language enabled (slovenian) and can not do it untill I remove stock one. If any of you can post in development section maybe you can ask there if they know the solution for this, thank you!
I fixed it.
I deleted all unneeded apks (stock apps) that stored in cust.img
My method;
1. On Slitaz Linux 3.0
2. Open terminal
3. Copy cust.img from phone to /home folder
4. mkdir tmp
5. mount cust.img /home/tmp
6. cd /home/tmp/hw/default/app
7. Delete apk files what you don't want
8. unmount tmp
9. Copy cust.img from /home folder to phone
Ok, but I dont have linux or terminal on my computer. Is there any way to do this via terminal emulator on the phone? Or is there some step by step guide how to do it as I am not really familiar with terminal or its use.
http://www.multiupload.com/EKPGJ7EUGO
This is "cleared" cust.img. That contains only these apks;
BeyondTheSkyTheme.apk
Calendar.apk
CalendarProvider.apk
DeskClock.apk
ToolBox.apk
1. Download this rar archive and open it.
2. Start your phone in pink screen mode
3. Backup original cust.img to your computer
4. Copy "cleared" cust.img from rar to phone.
Thank you,I managed to install swype in my language and it works great. I was wondering if there is any chance to extract all factory .apk files and post them somewere so people could donload them and install them if they want. I am missing that weather clock widget but swype is far more important to me, so thank you again to make it possible.
This rar archive contains all apks that stored in cust.img -->> http://www.multiupload.com/8DWKNVTXML
Just copy apk file (which ones do you want) to "/system/app" folder and restart.
or
This is only TotemWeather.apk -->> http://www.multiupload.com/IWX7U3G5FU
Just copy to "/system/app" folder and restart.
Thank you, you are the best. Will this cust.img work with 2.3 beta which will be released this thursday according to Huawei? If not I wont update again as I just managed to adjust phone to my needs.
I hope, it will works with the new update. If not, i'll fix it when update released.
could you give us a cleared cust.img for the official 2.3.5???
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.
Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
funkeywoookey said:
Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
Click to expand...
Click to collapse
First off, this is an ownership issue, not a permissions issue
Second, chown 1001 gives ownership to Radio, not System. Chown to 1000 for System ownership
I never did find a solution to this problem. In my attempts to correct the problem, I ran chown on the entire /data partition by accident. The ROM booted, but everything crashed. After this, I just decided to salvage what little I might be able to save and move on with life.
The problem even persisted through wipe/reinstall of the ROM.
Finally, as a last resort, I had flash the stock version through Odin and start over from scratch.
I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....
Ctrl-Freak said:
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
Click to expand...
Click to collapse
About 2 weeks ago I had restored the Motorola 5.0.2 backup posted here on XDA [Link Removed by Mods due to Moto Policies]. I had the SELinux storage access problem. Then I restored the CM12 nandroid i had then.
No problem occurred. All of my data in /data is still intact.
Ctrl-Freak said:
I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....
Click to expand...
Click to collapse
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Edit: I managed to flash a backup of the rom i was running prior to KitKat via OTG cable. TWRP recognized the backup when i made a couple of folders: TWRP/BACKUPS/TA000021JN and i flashed. As soon as the phone booted up I was able to see the TWRP folder on ES Explorer again so i think it 's probably fixed?
Cristian314 said:
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Click to expand...
Click to collapse
Terminal emulator (app), I just tried it, works [emoji2]
Enviado desde mi XT1058 mediante Tapatalk
Hey people!
I just got a nexus 7 2012 and i am wanting to mount it in my car. So i wanted to do a few things before that.
I updated to official 5.1.1 via OTA. Everything is STOCK
First step was rooting which SEEMED to work (DID it via WUGS). It installed SU and busybox. Next step was to create my own bootanimation
This is where the issues have started. I can not change permissions or move any files to the system directory even with W/R option turned on
I can delete the files but can not copy files to the directories. I can no change permissions in ANY directory.
I have tried in root explorer mounting r/w ES file explorer R/W ... i tried to install a new busy box and it installs then immediately says "you installed but it seems there is an older version on the system" i can not uninstall busybox. I tried mounting in terminal and it says all partitions are EXT 4. I have tried rerooting. Root check says everything is fine. SU seems to be working fine (it elevates permissions for all the root apps).
But for the life of me it will not copy anything into / or /system. :crying:
Should i just forget it and install another rom, WIPE everything and start again? If ROM which one is the best at the moment (nexus 2012)
After 2-3 hours of messing about... I just TWRP and flashed a different SU and it starting working.