i have flash motoblur 1.071, and it seems i have problem with file/dir permission, i can't install app from market, logcat said "couldn't create temp file for download package file"..
How do i run permission fix of this?
Finally i got it working,
chmod 7777 system/app
and now i can install app from market
lesjaw said:
Finally i got it working,
chmod 7777 system/app
and now i can install app from market
Click to expand...
Click to collapse
Sorry was tied up with stuff, good to hear you fixed it.
Hey guys,
I have updated this thread with a script and files for those who are unsure of how to make this work. Its a quick script so don't expect much, reverse engineered to simply de-odex your phone fully.
You must have ADB added to your "Allow" list in Superuser.apk.
WARNING:
This can brick your phone if you do not do things properly. I have tested it on my phone and it worked flawlessly. Once again though, I was on a fresh install of 1.4.2.
INSTRUCTIONS:
-Download files here <-- Updated link
-Extract files to C:\
-Execute SevensDeodex1.1.bat
-Wait a few minutes
-Phone will reboot and take a while to start up
-Done
MANUAL INSTALL:
Navigate to extracted files through CMD or Shell
Type the following commands
adb.exe push 142system.tar.gz /data/local/tmp/
adb push bin/install_script.sh /data/local/tmp/install_script.sh
adb shell
Once in adb type:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
Known issues:
-Photoeditor.apk deleted as de-odexing this was a problem. So what
Updates:
1.1 Updated to fix some issues with the bat file.
1.0 Original release
Special Thanks to: NFHimself for showing me the way
i know that ken was looking for a dump of /system and /data, did you or will you toss one at him seven?
i would, but i was working on some frameworks on 0.37 that i don't really want to leave unfinished
raybond25 said:
i know that ken was looking for a dump of /system and /data, did you or will you toss one at him seven?
i would, but i was working on some frameworks on 0.37 that i don't really want to leave unfinished
Click to expand...
Click to collapse
You want me to upload a framework dump?
Will that help, let me know exactly what you need and I'll try to help.
I found aout about that method too last night, I just deleted the photoeditor apk and odex file and it ran through the app deodex fine. When I tried to copy my framework files though adb shell refused to replace the files, even using the -f force command.
Yes... could someone throw me:
/system/
/data/
I know that's a lot... but that's what I'll need. Thanks guys. PM me if you need a private FTP server to upload it. If not, you can use Dropbox or Hotfile.com (I have a premium account).
http://db.tt/kdUycD1 just dumped that last night..might be a slow downlad though...raybond25 gave me the script for it since I've never done it hope its what you need
Sent from my MB860 using XDA Premium App
that was something that was needed, but after that it needed to be deodexed. I sent snake's dump to NFHimself and he deodexed it.
Deodexed system
raybond25 said:
that was something that was needed, but after that it needed to be deodexed. I sent snake's dump to NFHimself and he deodexed it.
Deodexed system
Click to expand...
Click to collapse
so with a deodex script we can deodex our system and framework?
Sent from my MB860 using XDA Premium App
SN4K3B1T3 said:
so with a deodex script we can deodex our system and framework?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
i'm not sure how NFH did it, you'd have to ask him about his method but that system has deodexed /app and /framework
i'm not sure if he plans on writing a script that will do this and releasing it or not, that deodex was mainly because kennpenn was looking for it.
but, yes it can be done.
Will upload deodex files now
any special tricks ive tried deodexing at least 4 times and it stops at 91 out of 134...pissed
yeah i got an error at core.odex
I agree there is no sense reinventing the wheel, I used dsixda's htc kitchen to do it, had a working folder for something else, simply replaced app and framework with the files from telstra and ran his script and selected deodex. He has bits in there specific to the Atrix, I noticed that when looking at the scripts to do my own version, didn't bother after since it was already done. No errors, and haven't had a problem in over a month so it's all good, it only needs to be done once per firmware.
My rule of thumb, don't run anything for your $$$ phone if you don't have source or can read the scripts yourself, especially if it hasn't been tested specifically on your phone. Don't be in a rush to execute some file or script unless it's from a family member you really like with lots of money.
Cheers!
NFHimself said:
I agree there is no sense reinventing the wheel, I used dsixda's htc kitchen to do it, had a working folder for something else, simply replaced app and framework with the files from telstra and ran his script and selected deodex. He has bits in there specific to the Atrix, I noticed that when looking at the scripts to do my own version, didn't bother after since it was already done. No errors, and haven't had a problem in over a month so it's all good, it only needs to be done once per firmware.
My rule of thumb, don't run anything for your $$$ phone if you don't have source or can read the scripts yourself, especially if it hasn't been tested specifically on your phone. Don't be in a rush to execute some file or script unless it's from a family member you really like with lots of money.
Cheers!
Click to expand...
Click to collapse
I've updated the OP and thread title.
Now includes a working script to deodex. Very simple and straight forward, no need to use any other tools and this should make it easier for all other users who are new at this.
Thanks for your help sir, you are a king amongst men!
Not a problem.
One thing about the script, Superuser.apk needs to know about the shell having root access, so once you root the phone, do an adb shell su command, accept the prompt from Superuser.apk, and you are good to go. I tossed some stuff into my root.bat (.sh) scripts to launch Superuser.apk and update it's database automatically, bit of a hack but worked the last 20 times I tried it.
NFHimself said:
Not a problem.
One thing about the script, Superuser.apk needs to know about the shell having root access, so once you root the phone, do an adb shell su command, accept the prompt from Superuser.apk, and you are good to go. I tossed some stuff into my root.bat (.sh) scripts to launch Superuser.apk and update it's database automatically, bit of a hack but worked the last 20 times I tried it.
Click to expand...
Click to collapse
ooooooooh you absolutely right.
Since I'm new at making scripts i'm going to simply just update the script so that the user has to put ACCEPT on the phone before running the rest of the commands you know, new vers coming now
I keep getting this error.. I took a screen shot of it.. Any ideas?
nate_benji said:
I keep getting this error.. I took a screen shot of it.. Any ideas?
Click to expand...
Click to collapse
easy. It means you do not have root access allowed with ADB.
If you're phone is not rooted, go to the link in my signature that shows you how to root.
If you have root and you know its working then you must do the following first:
Open up your command prompt - make sure to keep your phone's screen active and unlocked.
Type "adb shell"
Once you have $
type "su"
check your phone's screen, as you will be prompted to allow, or deny access.
Select "Allow"
Now you are set to go, execute the script again.
Let me know of your results
I just tried it on a fresh SBF flash and root, root confirmed working though adb shell. It pushes everything fine, but when it goes to execute the script the cmd window just closes.
EDIT: Managed to get a screen right before it closes. Not sure of the problem because root works in adb and titanium backup.
Open up CMD manually
then navigate to where the bat file is and run it.
Tell me what the output is please.
Also, you said Root is working through ADB.
Then try to do everything manually as such:
adb.exe push 142system.tar.gz /data/local/tmp/
adb push bin/install_script.sh /data/local/tmp/install_script.sh
adb shell
Once in adb type:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
And there you go.
Hello guys,
Today I will show you a simple method to change Superuser Client - From ChainsDD's/Koush's SuperUser to chainsfire's SuperSU.
I personally prefer the SuperSU over SuperUser.
If you are unsure, you might want to read up on it.
For a basic idea, look here - http://getandroidstuff.com/superuser-vs-supersu-android-root-management-at-its-best/
So, if you're a ROM dev/porter, and would like to replace, this is what you need to do!
What you need
Latest SuperSU and binary - can be found here
The ROM you're working on!
WinRAR (or similiar)
5 minutes of time!
Instructions
Download the SuperSU.zip
Extract it!
From the common-folder copy the superuser.apk
Open your ROM's flashable .zip via WinRAR
Navigate to /system/app
Replace the superuser.apk from the .zip we extracted
Go to our extracted SuperSU folder
From the arm-folder copy su
Navigate through ROM.zip to /system/xbin
Replace the su
WinRAR will update the archive!
Profit!
In case the above doesn't work out for you, then also copy chattr and chattr.pie from arm-folder to /system/xbin of your ROM.zip
(Thanks to @F4uzan and @-CALIBAN666- for the tip!)
Thats it!
Enjoy!!
Nice tutorial.
Seems easy!
Sent from my IdeaTab A2107A-F using xda app-developers app
One suggestion :
On some ROM it's needed to copy chattr and chattr.pie from arm folder
Great guide, btw
F4uzan said:
One suggestion :
On some ROM it's needed to copy chattr and chattr.pie from arm folder
Great guide, btw
Click to expand...
Click to collapse
Thanks, where should the chattr and chattr.pie be copied too?
I shall update OP!
system/xbin
Does anyone know what files to replace/permissions to set in the system image when updating SuperSU and busybox, and where to get these files?
Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/
arohrmann said:
Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/
Click to expand...
Click to collapse
Thank you! I had to place the busybox file into both bin and xbin in order for busybox installer to recognize the updated version, but other than that, I followed your instructions exactly. So now my question is if I just updated the supersu binary to the latest version, why is supersu still telling me that I need to update the binary? Did you extract these from 2.46?
Two more questions: how did you extract them, and where did you get the version of busybox that you included in your previous post?
busybox is just in priv-app not in app - it works.
I don't know, why that update message comes up. It's the latests SU
You can open apk's like ZIP to extract. But you can find Update-ZIP to flash with recovery, to extract
That's the latest busybox I installed on an other android. Just moved to the System-Images.