Hi i have problem with Kindle Fire,
i changed permissions folder system/app with app Root explorer and then I restart Kindle Fire and now dont want start. I think this is problem permissons for this directory.
Pleas can you send me setting permissions folder APP and how i can change it by ADB SHELL?
I have tried:
adb shell
su
chmod 644 app
Unable to chmod app: Read-only file system
THX very much .-(
Sory my english is very bad.
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
or look here:
http://forum.xda-developers.com/showthread.php?t=1356257
guys please use the search function !
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
pitrsonek said:
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
Click to expand...
Click to collapse
you need root before you can do any of those (i.e. su)
But i think i have root because I install Google market and other app. Or how i can check if i have root?
THX!
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4D1A002600000001 device
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls
ls
config
dropbox
cache
sdcard
acct
mnt
vendor
d
etc
ueventd.rc
ueventd.omap4430.rc
ueventd.goldfish.rc
system
sys
sbin
proc
init.rc
init.omap4430.rc
init.goldfish.rc
init
default.prop
data
root
dev
$
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
krelvinaz said:
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
Click to expand...
Click to collapse
Yes, what he said...you're confusing having root on the command line for "I installed su and superuser to their correct locations"
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
pitrsonek said:
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
Click to expand...
Click to collapse
Something is wrong with your device then.
as a first step look if you have superuser.apk in \system\app\
Ho i dont have Superuser.apk in /system/app/
b63 said:
as a first step look if you have superuser.apk in \system\app\
Click to expand...
Click to collapse
Doesn't really matter if su is not working. Superuser.apk is just a wrapper for su and he's trying to do things on the command line so su is what he's calling to, not SuperUser.apk.
He either didnt root correctly to begin with or he did something after that messed things up. Temp rooting with zergRush and redoing things is most likely what he needs to do.
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
Ther is content dir app:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls /system/app
ls /system/app
-------------------------------------------------------------------------
ATVAndroidClient.apk
AccountAndSyncSettings.apk
AmazonVenezia.apk
ApplicationsProvider.apk
AudibleAndroidApplication-venezia.apk
CSApp-unsigned.apk
CalendarProvider.apk
CertInstaller.apk
Cloud9-unsigned.apk
Cloud9SystemBrowserProvider-unsigned.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
Email.apk
Facebook.apk
Gallery3D.apk
HTMLViewer.apk
IMDb-2.3.apk
KindleForOtter.apk
LatinIME.apk
Launcher.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MarketIntentProxy.apk
MediaProvider.apk
MyAccount-unsigned.apk
OOBE-unsigned.apk
OTASilentInstall.apk
OtterAppManager.apk
OtterTutorial.apk
PackageInstaller.apk
PicoTts.apk
Provision.apk
Pulse-amazon.apk
QuickSearchBox.apk
QuickSettings.apk
Quickoffice_AMAZON_4.1.408_VC.apk
Settings.apk
SettingsProvider.apk
SystemUI.apk
TtsService.apk
UserDictionaryProvider.apk
VisualizationWallpapers.apk
VpnServices.apk
Windowshop.apk
air_runtime.apk
amazonmp3-unsigned.apk
com.amazon.dcp.apk
oem_install_flash_player_signed.apk
Superuser.apk
Vending.apk
$
agree - but it's an indication that his device is not rooted
i would suggest to install superoneclick to the computer and root again
all you need is here : http://forum.xda-developers.com/showpost.php?p=19789892&postcount=35
pitrsonek said:
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
$
Click to expand...
Click to collapse
Maybe on Thursday I can. Busy until then.
I just run SuperOneClick and there is log http://jsfiddle.net/tVnDv/ from this program.
Kindle Fire is Back
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
glad to help ...
pitrsonek said:
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
Click to expand...
Click to collapse
I'm having the same issue, but when I go to change the mount permissions I get permission denied. Anyone care to give me some insight on how to fix it?
you have the $ prompt !!!
type su - the prompt has to change to #
then do the commands ...
Related
First off, I want to say thanks to Kam187 & the Creators of asroot
Okay, Below is the Method I used for getting Root working for my app's.
Even though Shell is running as Root, any Call's made to su trigger's the white List Superuser.apk, So don't think your phone is wide open. G1's & MT3G Setup's are the same regard sh.
I'm not sure is the apk is counted as warez or not, if so I hope a Mod will remove the link to the Apk or let me know to Remove it...
Okay, File's Need to complete the Task is....
Try3 Placed in C:\SDK\tools> found here > File's attached below
SU for /system/bin found here > File's attached below
Superuser app control for our App's found Here > File's attached below
Next, Mount the SDCARD and place the SU file in the root of the sdcard like so ( /sdcard ). This is Important!!!
From here we do the Following.. ( Kam187 script the I edited ).
adb push try3 /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su > /system/bin/su1
cat /sdcard/su > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
Once Done, place the Superuser.apk in your SDK tools Directory.
Mine happens to look like this
C:\SDK\tools>
Click to expand...
Click to collapse
Once you have that Copied over, Open a Command prompt and CD to your sdk\tools directory and type the following.
adb install Superuser.apk
Click to expand...
Click to collapse
Once done, do a reboot of the Phone, Once boot up is complete open a Command Prompt ( or app that needs Root ).
For Command Prompt, type:
adb shell
Click to expand...
Click to collapse
su
Click to expand...
Click to collapse
If done correctly you will now see the deny or allow prompt on the Phone, or just open any app that needs root & you will see the same window.
Here's some Picture of it working
SU working with SU apk on Twitpic & SU working with SU apk on Twitpic
I have upgraded from 309 to 318.......wanting to root it using z4root and universal androot but both apps dont work for this 318 version.....
does anyone have any clues to what i can do? please advise, thanks
Please Do Not Post the Same Question in 2 Forums i will Lock this one as i have answered the other one
Quoted from fards' thread: http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage
Been rooting this way since day 1 -- if you aren't the type in command prompt, you can also just copy and paste the command lines exactly~
GET ECLAIR/FROYO version of Superuser.apk and su
from http://forum.xda-developers.com/showthread.php?t=682828 extract the two files to the directory you're working from..
GET rageagainstthecage from
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
extract the rageagainstthecage-arm5.bin to the same directory you're working from
open a terminal/command line
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 700 /data/local/tmp/rageagainstthecage
adb shell chmod 700 /data/local/tmp/busybox
adb shell
cd /data/local/tmp
./rageagainstthecage
******this will kill adb server but manually kill it anyway and restart it ******
adb kill-server
adb start-server
* daemon not running. starting it now *
* daemon started successfully *
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
**********Follow the following steps to install Superuser.apk, busybox,su ****************
cd /data/local/tmp
./busybox cp busybox /system/bin/
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app/
busybox cp su /system/bin/
chmod 4755 /system/bin/su
exit
exit
then reboot streak
************to remount filesystem as readonly,*************
adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock6 /system
# exit
exit
Click to expand...
Click to collapse
Hi,
a pin of my USB connector is broken so I cannot get a USB data connection to a PC (but charging still works ...).
How can I root the official 318 build of froyo ? More specifically, in the new build, there doesn't seem to be any mounted filesystem on which one can copy RATC to run it.
Any hint welcome.
Have you already tried superoneclick, androot, or z4root? If so, then maybe try the below.
I don't know if this will work but you can try fard's instructions to root manually and use "Terminal Emulator" from Market instead of ADB SHELL, but i don't know what will happen when you run rageinthecage~ You will need to change the instruction a bit for your case.
http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage
Instructions:
1. Copy all the needed files (from fards thread) into the SDCARD.
2. run Terminal Emulator
3. cd /sdcard/
4. busybox cp rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
5. busybox cp Superuser.apk /data/local/tmp/Superuser.apk
6. busybox cp su /data/local/tmp/su
7. busybox cp busybox /data/local/tmp/busybox
8. chmod 700 /data/local/tmp/rageagainstthecage
9. chmod 700 /data/local/tmp/busybox
10. cd /data/local/tmp
11. ./rageagainstthecage
12. Reset Terminal
13. Start Terminal Emulator again
14. mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
15. follow the rest of the instructions below "mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system "
In case you can't find it in the thread, here is the original post by fards:
GET ECLAIR/FROYO version of Superuser.apk and su
from http://forum.xda-developers.com/showthread.php?t=682828 extract the two files to the directory you're working from..
GET rageagainstthecage from
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
extract the rageagainstthecage-arm5.bin to the same directory you're working from
open a terminal/command line
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 700 /data/local/tmp/rageagainstthecage
adb shell chmod 700 /data/local/tmp/busybox
adb shell
cd /data/local/tmp
./rageagainstthecage
******this will kill adb server but manually kill it anyway and restart it ******
adb kill-server
adb start-server
* daemon not running. starting it now *
* daemon started successfully *
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
**********Follow the following steps to install Superuser.apk, busybox,su ****************
cd /data/local/tmp
./busybox cp busybox /system/bin/
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app/
busybox cp su /system/bin/
chmod 4755 /system/bin/su
exit
exit
then reboot streak
************to remount filesystem as readonly,*************
adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock6 /system
# exit
exit
Click to expand...
Click to collapse
Well...
yes, I have tried all that.
The main problem with the last option (i.e. CLI) is that the directory /data/local/tmp/ is not user writable (actually /data permissions are 751). So I was in search of a another directory (in an executable partition) where I can copy rageagainstthecage-arm5.bin.
Finally found it : "find" was my friend. /firstboot/sqlite/jackpal.androidterm/ is owned by my user (ID 10123)! It's the only one I found in all the filesystems!
Note that "find" is available through /system/bin/busybox_1P8P1. Btw /firstboot/sqlite/jackpal.androidterm/ seems to be linked to the terminal process.
Ran rageagainstthecage-arm5.bin various times to no avail ! It didn't give me root!
Im hoping to get some help to get a theme installed on my phone.
It is rooted successfully, busybox is installed successfully also.
Im trying to put the Minimal Matte theme on my phone, but no success. Actually, I managed to make my Contacts disappear...
So, I would greatly appreciate help! I don't know why the adb commands are not working that are given here:
Code:
adb shell mount -o remount,rw /dev/block/stl16 /system
adb push Contacts.apk /system/app/
adb push DialerTabActivity.apk /system/app/
adb push Settings.apk /system/app/
adb push framework-res.apk /system/framework/
adb push twframework-res.apk /system/framework/
If I try it like that, the mounting does not work cuz it says "not permitted". So then I try like this and I get this. So it is not working. How do I fix this and how do I get the theme into my phone? Thank you for help,
Here's what I tried:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# push Contacts.apk /system/app/
push Contacts.apk /system/app/
push: not found
#
Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?
Please note that your phone must be rooted! Your phone is rooted right?
barqers said:
Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?
Click to expand...
Click to collapse
Let me try this...
Im very new to all this, so I'd like to learn the tricks manually so I have a better understanding.
barqers said:
Please note that your phone must be rooted! Your phone is rooted right?
Click to expand...
Click to collapse
As stated in the first post, it is rooted and busybox is installed. Now..let me try your tips. I will report back.
Hmm..still facing the "permission denied" with these commands:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied
Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life
barqers said:
Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life
Click to expand...
Click to collapse
Tried this, but it seems I have to reboot since it did not work.
It does not let me use "adb shell mount -o remount,rw /dev/block/stl9 /system" when I try it. Only when I do the "su" first and then try that...
Now let me try again after reboot.
Still no dice...
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied
Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.
barqers said:
Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.
Click to expand...
Click to collapse
Well, when I go and click the superuser app and all, I can see stuff happening there. Also, it has asked for permission before for adb when I first used it and I gave it. Now it appears on the list there...so it seems to be working correctly, no? And I did it with the superoneclick and it ran through it smoothly as ever. Now let me try if adb is being fussy.
Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...
PolarSoul said:
Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...
Click to expand...
Click to collapse
ADB is being truly fussy! Do you have root explorer? Here is my best guess for you. Move the Contacts.apk to the /system/app/ folder manually with Root Explorer, then follow this guide to give the app root permissions:
http://francoforr.blogspot.com/2010/12/cant-reinstall-apks-easy-fix.html
Have to go find Root Explorer.
PolarSoul said:
Have to go find Root Explorer.
Click to expand...
Click to collapse
Root explorer is a paid app. But maybe ES File Manager or Astro File Manager will give you root capabilities too!
I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.
PolarSoul said:
I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.
Click to expand...
Click to collapse
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/
barqers said:
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/
Click to expand...
Click to collapse
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.
PolarSoul said:
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.
Click to expand...
Click to collapse
No problem~! Haha, yes we do But I think Finland is far from Canada!
I'm hoping it works for you!
It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?
PolarSoul said:
It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?
Click to expand...
Click to collapse
If you check settings -> SD card and storage. How much memory does it say you have? If you have less then 10mb either move some apps to the sd card or uninstall some!
To make this work you must be on stock rooted firmware!!!
I made a quick guide how to root stock 4.3 firmware, and can be found here
I'm not responsible for any damage caused by using this on your phone!!!
Let's start:
1 - you need deodexed app and deodexed framework. download and unzip. will result 2 folders (app & framework) wich must be copied on your phone (int sdcard)
2 - download adb from attach and unzip
3 - enable USB debugging mode (go to settings > about phone > tap on Build Number 7 times, until a message appears saying 'You are now a Developer.') than go to settings > Developer Options and enable USB Debugging Mode
4 - go to adb folder and open a command window (hold shift and right click on mouse button / choose "open command window here")
5 - connect your phone to pc with usb cable
>>> ml6_deodexed_zipaligned_apps_framework
>>> na1_deodexed_zipaligned_apps_framework
Now enter folowing codes:
>>> adb shell
>>> su (if you are using adb shell in su for the first time, keep phone screen on. after entering "su" code, super user request prompt in phone. press allow!!!)
>>> stop (touchscreen will not be active until reboot, don't worry!)
>>> mount -o rw,remount /system/ /system/ (mounting system r/w)
>>> cp /sdcard/app/* /system/app/ (copy deodexed system applications) (this will take 3 - 5 min)
>>> rm /system/app/*.odex (remove odex files)
>>> chmod 0644 /system/app/*.apk (this fix permissions in system/app)
>>> cp /sdcard/framework/* /system/framework/ (copy deodexed framework)
>>> rm /system/framework/*.odex (remove odex files)
>>> mount -o ro,remount /system/ /system/ (mounting system r/o)
>>> reboot (your phone will reboot) (this will take a little)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex
chmod 0644 /system/app/*.apk
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Now you have a deodexed stock rom!!!
do not forget to press thanks
i recommend to remove all knox files from your phone.
to do this you need an application to modify your system files ( i use root explorer )
to remove knox delete this files:
system > app > ContainerAgent.apk / ContainerEventsRelayManager.apk / KLMSAgent.apk / KNOXAgent.apk /
KnoxAttestationAgent.apk / KNOXStore.apk / KNOXStub.apk
system > containers (delete entire folder)
system > etc > secure_storage > com.sec.knox.store (delete entire folder)
reserved...
Well written buddy :good:
I would like to see a "how to zipaligned" the apks also.
robalm said:
Well written buddy :good:
I would like to see a "how to zipaligned" the apks also.
Click to expand...
Click to collapse
attached app are deodexed & zipaligned
Sent from my GT-N7100 using xda app-developers app
Good idea thanks to you
You forgot to add "how to deodex stock 4.3 ML6 firmware"
robalm said:
You forgot to add "how to deodex stock 4.3 ML6 firmware"
Click to expand...
Click to collapse
root the rom and folow instructions.
app & framework are from ML6
Sent from my GT-N7100 using xda app-developers app
cosmyndemeter said:
root the rom and folow instructions.
app & framework are from ML6
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
All worked fine, but i do not like to have old apps and framework on a newer rom version.
robalm said:
All worked fine, but i do not like to have old apps and framework on a newer rom version.
Click to expand...
Click to collapse
explain pls. what rom you have?
cosmyndemeter said:
explain pls. What rom you have?
Click to expand...
Click to collapse
n7100dduena1.
robalm said:
n7100dduena1.
Click to expand...
Click to collapse
uploading na1_deodexed_zipaligned_apps_framework.
download link on #1 post
cosmyndemeter said:
uploading na1_deodexed_zipaligned_apps_framework.
download link on #1 post
Click to expand...
Click to collapse
Thank you for this, I had wondered whether the app & framework were universal. I had not seen it was from the ML6.
Thanks for working on the NA1.
YOSEFE said:
Thank you for this, I had wondered whether the app & framework were universal. I had not seen it was from the ML6.
Click to expand...
Click to collapse
i think app are same, framework can be different
my stock rom flashed is mk9, but is use na1_deodexed_zipaligned_apps_framework without any problem
na1_deodexed_zipaligned_apps_framework uploaded
cosmyndemeter said:
na1_deodexed_zipaligned_apps_framework uploaded
Click to expand...
Click to collapse
Thank you very much.
Going there now.
OP,
can you tell me what is wrong with my phone causing the errors with this?
C:\Users\Me...\Downloads\adb\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o rw,remount /system/ /system/
mount -o rw,remount /system/ /system/
[email protected]:/ # cp /sdcard/app/* /system/app/
cp /sdcard/app/* /system/app/
[email protected]:/ # rm /system/app/*.odex
rm /system/app/*.odex
rm failed for /system/app/*.odex, No such file or directory
255|[email protected]:/ # chmod 0644 /system/app/*
chmod 0644 /system/app/*
Unable to chmod /system/app/mcRegistry: Permission denied
10|[email protected]:/ # cp /sdcard/framework/* /system/framework/
cp /sdcard/framework/* /system/framework/
[email protected]:/ # rm /system/framework/*.odex
rm /system/framework/*.odex
rm failed for /system/framework/*.odex, No such file or directory
255|[email protected]:/ # chmod 0644 /system/framework/*
chmod 0644 /system/framework/*
[email protected]:/ # mount -o ro,remount /system/ /system/
mount -o ro,remount /system/ /system/
[email protected]:/ # reboot
reboot
Thanks.
YOSEFE said:
OP,
can you tell me what is wrong with my phone causing the errors with this?
C:\Users\Me...\Downloads\adb\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o rw,remount /system/ /system/
mount -o rw,remount /system/ /system/
[email protected]:/ # cp /sdcard/app/* /system/app/
cp /sdcard/app/* /system/app/
[email protected]:/ # rm /system/app/*.odex
rm /system/app/*.odex
rm failed for /system/app/*.odex, No such file or directory
255|[email protected]:/ # chmod 0644 /system/app/*
chmod 0644 /system/app/*
Unable to chmod /system/app/mcRegistry: Permission denied
10|[email protected]:/ # cp /sdcard/framework/* /system/framework/
cp /sdcard/framework/* /system/framework/
[email protected]:/ # rm /system/framework/*.odex
rm /system/framework/*.odex
rm failed for /system/framework/*.odex, No such file or directory
255|[email protected]:/ # chmod 0644 /system/framework/*
chmod 0644 /system/framework/*
[email protected]:/ # mount -o ro,remount /system/ /system/
mount -o ro,remount /system/ /system/
[email protected]:/ # reboot
reboot
Thanks.
Click to expand...
Click to collapse
did you this for stock rooted odexed rom
because it seems this is not stock odexed firmware
cosmyndemeter said:
na1_deodexed_zipaligned_apps_framework uploaded
Click to expand...
Click to collapse
Thanks for this.
I have posted you a question here because of the errors I am getting.
YOSEFE said:
Thanks for this.
I have posted you a question here because of the errors I am getting.
Click to expand...
Click to collapse
and i asked if you are in stock odexed firmware with root...