hello, i am trying to use this mod:
http://forum.xda-developers.com/showthread.php?t=1107041
and what i get when i execute it is this:
http://gyazo.com/79dee96c40968ebb54d6e2531f886b0b
Using Atrix 4.5.9 2.3.4 rooted bootloader unlocked stock ROM
please any help would be appreciated.
Can anyone help please?
The rom you are running must be deodexed for the script to work
jhotmann said:
The rom you are running must be deodexed for the script to work
Click to expand...
Click to collapse
Some people in the thread are saying it doesn't have to be deodexed? Also can I deodex my stock rom? I dont want to flash another rom
Prerequisite 3 says you must be deodexed. If you are comfortable with the command line there is a way to decompile the odex, modify it, and then copy the signature from the original odex file and get it to work...
jhotmann said:
Prerequisite 3 says you must be deodexed. If you are comfortable with the command line there is a way to decompile the odex, modify it, and then copy the signature from the original odex file and get it to work...
Click to expand...
Click to collapse
I am not too comfortable with the command line, can you paste me the needed commands to manually deodex? Or is there an app to do this?
Also are there any cons to deodexing?
I heard deodexing will speed device up, is this true?
The pros and cons are heavily debated of deodexing...it will make the first boot after a change slower but is easier to mod.
They will be very similar to this procedure I wrote a blog post about changing the default orientation, only skip my step 4 and replace it with:
java -jar patch.jar androidpolicy\com\android\internal\policy\impl\KeyguardViewMediator.smali
(with the patch.jar being the one from the bin folder included with the wakeonvolume mod...place it in the same folder as adb.exe)
If you decide to go through with the steps backup you phone first...but in the end it may be easier to just flash a different rom that's already deodexed.
If the deodex process messes up can I use cwm to restore to a previously backed up odexed state?
Yeah, it will be like nothing ever went wrong.
dk00 said:
I am not too comfortable with the command line, can you paste me the needed commands to manually deodex? Or is there an app to do this?
Also are there any cons to deodexing?
I heard deodexing will speed device up, is this true?
Click to expand...
Click to collapse
just nandroid your current ROM and flash a deodexed ROM. problem solved and in half the time.
dk00 said:
I am not too comfortable with the command line, can you paste me the needed commands to manually deodex? Or is there an app to do this?
Also are there any cons to deodexing?
I heard deodexing will speed device up, is this true?
Click to expand...
Click to collapse
Couple more options:
1. Flash a deodexed stock system.img from here. This is what I did, and it was really easy.
2. Manually deodex the stock ROM yourself using instructions found here.
alright so i fully deodexed my device using this guide
http://forum.xda-developers.com/showthread.php?t=1162764
and now i am getting this error message when i run the wakeonvolume.bat script:
http://gyazo.com/79dee96c40968ebb54d6e2531f886b0b
can anyone help me please?
Bump
Sent from my MB860 using XDA App
Related
Someone who has done the whole DI01 update, please dump their system for me, or just the framework folder, apparently the one given to me had the stock android lockscreen patch applied to it lol.
Aside from that, the DI01 deodex works perfect, I opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
I will also need someone who knows how to sign updater-scripts to open the one attached, and just save it again properly and upload it for me. I am trying to get a flashable CW zip but the darn thing always gives me a status 6 error, which means the CW cannot read the updater script.
Sorry for the n00b question, but what benifit does deodexing provide? Also if there is another software update will I have to readd any .apk's to my /system folder?
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Is there anything involved in a dump besides just copying the files in /system?
namebrandon said:
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Click to expand...
Click to collapse
Because I am too lazy to go through all that.
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
s44 said:
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
Click to expand...
Click to collapse
That is all I need. The only things I deodex are the contents of system/app and system/framework.
frostman89 said:
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
Click to expand...
Click to collapse
Try a real editor, like bluefish or something.. Those scripts look like sh#! in notepad.
If no one has done it by tonight, just grab me on IRC and I'll do it under Linux for you.
Make sure you've got the file/directory structure right too.. You can't just throw a script in a zip file, but I'm sure you knew that. Myself and and a few others had the wrong directory structure at first, don't remember what error number that gave us though.. I think it just froze.
OK, how can I get it to you? I can't post links or (I think) files yet.
s44 said:
OK, how can I get it to you? I can't post links or (I think) files yet.
Click to expand...
Click to collapse
You can just zip it up and upload it to mediafire.com
Just splice up the link like WWW. Website. Com and I will just delete the spaces.
Mediafire upload just not working for some reason. Hm.
s44 said:
Mediafire upload just not working for some reason. Hm.
Click to expand...
Click to collapse
http://multiupload.com/
J1HDKEGYAR at multiupload
Would anyone be willing to upload the stock camera apk. Thank you !
If no one gets you one by around 10:30 I'll boot into ubuntu and upload the file I pulled. I have some homework to get done first
thanks bro!
Sent from ma mothalovin! MOPHO!
Here ya go. It's the .apk with the .odex file packaged in a .zip archive. Extract them and then "adb push BlurCamera.apk /system/app" and "adb push BlurCamera.odex /system/app".
excuse me if I sound like a noob but so flash I have to deodex my phone and do I need root?
Sent from ma mothalovin! MOPHO!
oh and thanks a million man!
Sent from ma mothalovin! MOPHO!
You do not need to being using a custom ROM or a deodexed ROM to use this. You don't flash it, either. Extract the .zip archive and then follow the instructions I put in the upload post.
Canot get it going
Hello guys
I did try to swap the camera app from the Droid to Photon but no succes, couldn't get the shortcut to show up. Now I'm trying to restore the stock one, same thing, can't get shortcut to show up, help please. BTW, did all the process with root explorer and I have the right permitions. No deodexed.
Elendil_23 said:
Hello guys
I did try to swap the camera app from the Droid to Photon but no succes, couldn't get the shortcut to show up. Now I'm trying to restore the stock one, same thing, can't get shortcut to show up, help please. BTW, did all the process with root explorer and I have the right permitions. No deodexed.
Click to expand...
Click to collapse
If you have an deodexed version of the apk, then do "adb install namehere.apk".
Still no go
mrinehart93 said:
If you have an deodexed version of the apk, then do "adb install namehere.apk".
Click to expand...
Click to collapse
Hi, thank you for your answer, I don't have adb installed, is it possible any other way?
There are other ways, but I recommend using adb. If you do any type of android modding you should learn how to use adb and be familiar with it.
My email is [email protected]
Be rooted. Have a computer with adb working, or do this from an android terminal emulator. The instructions are for adb.
The applypatch commands are going to have [] around them to show you what to put, but we not used in the actualy script.
-----------------------------------------------------------------
Code:
adb shell
su
cd sdcard-ext
applypatch [Original Boot.img] [Desired Name of new Boot.img] [A] [B] [C]:[boot.img.p]
-----------------------------------------------------------------
A = Desired Boot.img's Sha-1 sum
B = Size (in bytes) of the desired boot.img
C = Original Boot.img's Sha-1sum
Looking at the updater-script you can see this line of code or something similar for applying the boot.img.p to the phone's boot.img.
You need this as a reference for the SHA-1 sums of the patch and boot.img and desired final boot.img.
//Reference script\\
Code:
assert(apply_patch("MTD:boot:[B]:[C]:[B]:[A]",
"-", [A], [B],
[C], package_extract_file("patch/boot.img.p")));
//Actual script\\
Code:
assert(apply_patch("MTD:boot:8388608:fe086e1f547082c3cf2a5f65dacb81fd232ecd89:8388608:4a7070c32d0312aa48e52e207c7932434bc46cb1",
"-", 4a7070c32d0312aa48e52e207c7932434bc46cb1, 8388608,
fe086e1f547082c3cf2a5f65dacb81fd232ecd89, package_extract_file("patch/boot.img.p")));
Actual commands used to patch D4 .219 fastboot file boot.img with D4 6.16.208 boot.img.p:
------------------------------------------------------------------------------------------
Code:
adb shell
su
cd sdcard-ext
applypatch boot219.img boot208.img 4a7070c32d0312aa48e52e207c7932434bc46cb1 8388608 fe086e1f547082c3cf2a5f65dacb81fd232ecd89:boot208.img.p
------------------------------------------------------------------------------------------
mattlgroff said:
My email is [email protected]
Be rooted. Have a computer with adb working, or do this from an android terminal emulator. The instructions are for adb.
The applypatch commands are going to have [] around them to show you what to put, but we not used in the actualy script.
Click to expand...
Click to collapse
Thank you very much mattlgroff. Our Razr Dev section really need more tutorials as this one.
Excellent !
-- Edit --
Do you mind bringing us a Tutorial to port an ICS system app to make it work in another ICS?
Here's an example: SoundRecorder.app from a Motola GSM ICS leak to Retail.BR GSM ICS 4.0.4
This really worth a really cold beer.
BTW. I can provide you all the files you may need or follow a guide to make it work to upcoming Razr's ICS. I've tools to extract .img, DD's even an app compiler. But I get stuck in signing. framework-res.apk etc.
Reason: Some features are built in some ICS versions but not in others. There's more apps, like SIP native support wich are not present in most ICS 4.0.4. I've tried a few Tutorials, but they aren't that much noob Engineering friendly. lol
Thanks man
pedrotorresfilho said:
Do you mind bringing us a Tutorial to port an ICS system app to make it work in another ICS?
Here's an example: SoundRecorder.app from a Motola GSM ICS leak to Retail.BR GSM ICS 4.0.4
This really worth a really cold beer.
BTW. I can provide you all the files you may need or follow a guide to make it work to upcoming Razr's ICS. I've tools to extract .img, DD's even an app compiler. But I get stuck in signing. framework-res.apk etc.
Reason: Some features are built in some ICS versions but not in others. There's more apps, like SIP native support wich are not present in most ICS 4.0.4. I've tried a few Tutorials, but they aren't that much noob Engineering friendly. lol
Thanks man
Click to expand...
Click to collapse
I've never done any modifications of apk's like this, I'm more into leaks and utilities
I agree that someone should make tutorials on this though. Sharing our knowledge is the best way to not have to repeat trying things that don't work over and over.
mattlgroff said:
I've never done any modifications of apk's like this, I'm more into leaks and utilities
I agree that someone should make tutorials on this though. Sharing our knowledge is the best way to not have to repeat trying things that don't work over and over.
Click to expand...
Click to collapse
Hi mattlgroff!
Do you know a Dev that may help us?
Thanks
pedrotorresfilho said:
Hi mattlgroff!
Do you know a Dev that may help us?
Thanks
Click to expand...
Click to collapse
I don't sorry.
apktool
I thought it was possible to make changes to an apk with apktool and then repack those changes back into original apk so you don't lose signing.
X
xlightwaverx said:
I thought it was possible to make changes to an apk with apktool and then repack those changes back into original apk so you don't lose signing.
X
Click to expand...
Click to collapse
We need to figure out how to check for dependencies on these disassembled APK files.
Also, these applypatch instructions have been posted by whirleyes before: http://forum.xda-developers.com/showpost.php?p=26363001&postcount=2
trying to figure out why manually patching would be necessary, why not just dd the boot.img partition after updating?
Q9Nap said:
trying to figure out why manually patching would be necessary, why not just dd the boot.img partition after updating?
Click to expand...
Click to collapse
If no one who knows how can upgrade to that version. Here on the XT912 Verizon front, barely anyone is left on GB who can help us with this. This way I can pull a leak and flash it within minutes with no external help.
What I am doing wrong? It doesnt work. I get always an error:
"bootxxx.img" is already target; no patch needed.
I did everything like described in the OP.
Edit: My fault. Want to update an older boot.img to the newer one using the boot.img.p, but it doesn't work.
EDIT: It worked. As you said, it shows an error but done it already. Thx!
Hi guys, is there any way to let the patch install with any SHA for the currently installed boot.img ? Magisk messes it up so OTA updates cannot work
Wanted to share this with fellow amaze users. It's a collection of scripts/binaries that will seamlessly reodex your /system/app and /system/framework folders. This will give you a noticeable increased in overall speed/fluidity, boot times, ram usage... I generally prefer to re-odex anything I use. Major downside to re-odexing is that you can't easily modify the APK. But honestly, it's not that difficult to simply deodex the APK in question, mod/theme it, then reodex it. I find the benefits are well worth it.
The original script was created by tommytomatoe. All credit goes to him for the actual creation of this script. I simply made a windows batch file to ease the setup and execution of said script.
Please PLEASE PLEASE make a NANDROID backup before you run this. I've never had it mess anything up, but who knows... just back up and be safe!..
ZIP is attached below. Unzip into any directory (make sure the files stay together) and run Dexo.bat - You MUST HAVE BUSYBOX, WORKING ADB (Wireless ADB support is built into the batch file), and ROOT!
I originally had a quick batch file made for just myself.. but I changed things around and made it a bit more user friendly and other things.... I've only tested it ONCE on my own device once (the modified one).. so just be warned.. and make a backup first!
The batch file will not close on its own, when it's done the device will reboot on its own. You can simply just close the window.
Hope this helps some people! Good luck.
--------------------
[What is Odex?]
During the build process, Android can be built with the flag “WITH_DEXPREOPT=true”. This means that the dex files are preoptimized in the build environment using a dalvikVM on the host, as opposed to optimized during boot on the device. The dex-preopt process results in two files per apk or jar – the jar/apk file and its accompanying .odex file.
----------------------
[What is so tricky about reodexing?]
Due to the nature of the dalvik VM (according to documentation in AOSP), the VM expects the optimization process to follow the strict BOOTCLASSPATH.
/* There are some fragile aspects around bootclasspath entries, owing
* largely to the VM's history of working on whenever it thought it needed
* instead of strictly doing what it was told. If optimizing bootclasspath
* entries, always do them in the order in which they appear in the path.
*/
So that is the dex-preopt during the build time. All the vendors ship devices with Odex, ie, stock ROMs are odex. What about ROMs that have been deodexed? Or how do you go about editing the smali code from the odex files? Thank goodness for JesusFreke, we have baksmali and smali. Using the two in sequence, one can successfully convert the optimized dalvik executable (odex) and dissemble it into a human readable (sorta) language called “smali”, created by JesusFreke and resembles the Jasmin language. Anyways, carrying on. Using the dexopt-wrapper binary, you can re-odex your ROM after it has been deodexed. This sounds pretty simple but as stated above, the VM expects the optimization to follow the BOOTCLASSPATH. You cannot silly nilly deodex android.policy.jar and then re-odex it. Your device will not boot. You must transfer the original “signature” from the original odex file to the newly created (Hint, dd if=original.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc). This can be done on a Linux machine or with the busybox binary.
OK. So what is this tool? I just wanted to give a brief (or not so brief) overview of the process. This tool doesn’t deal with partially odexed ROMs. This tool is for odexing a ROM that is completely DEODEX.
The benefits? Faster boot, smaller imprint on /data/ partition, overall faster feeling. The phone will generally just run a little bit faster, system apps will launch quicker..
The myths? I can’t theme ODEX! WRONG! You can theme odex just fine! Just use baksmali and smali.
This requires BUSYBOX.
This requires ADB.
Again HUGE THANKS to tommytomatoe for the original script and his original efforts.
THIS ZIP FILE IS NOT FLASHED IN RECOVERY! You simply extract it to a folder on your hard drive. Then run Dexo.bat, follow on screen instructions. Make sure to nandroid as well as having phone plugged in VIA USB with debugging enabled, or have wireless ADB ready to go.. batch file supports wireless. Just have to follow prompts and enter IP.
ericdjobs said:
Wanted to share this with fellow amaze users. It's a collection of scripts/binaries that will seamlessly reodex your /system/app and /system/framework folders. This will give you a noticeable increased in overall speed/fluidity, boot times, ram usage... I generally prefer to re-odex anything I use. [/B][/SIZE]
Click to expand...
Click to collapse
Tried this on my ICS ROM and it works fine.
Thanks!
Doesn't work for me :/
Sent from my HTC Ruby using xda app-developers app
avenged_sevenfold27 said:
Doesn't work for me :/
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Oh! It's not supposed to be flashed in recovery!
Sorry if I wasn't clear on that.
It's a script and a batch file. The batch file will make uploading the script, changing permissions, etc etc etc, a lot more intuitive and easier.
You simply need to extract the ZIP anywhere on your harddrive (Have to be using windows for the batch file to work.. if you're running Linux i'm sure you can figure out how to do it manually anyways) Make sure to keep all the files in the same folder.
Then simply execure dexo.bat and follow the prompts. Make sure you have the phone plugged in via USB and USB debugging enabled.. or have Wireless ADB running (batch has built in support for wireless ADB)
You can run it while the phone is on. The phone will reboot itself when the script is finished.
ericdjobs said:
Oh! It's not supposed to be flashed in recovery!
Sorry if I wasn't clear on that.
It's a script and a batch file. The batch file will make uploading the script, changing permissions, etc etc etc, a lot more intuitive and easier.
You simply need to extract the ZIP anywhere on your harddrive (Have to be using windows for the batch file to work.. if you're running Linux i'm sure you can figure out how to do it manually anyways) Make sure to keep all the files in the same folder.
Then simply execure dexo.bat and follow the prompts. Make sure you have the phone plugged in via USB and USB debugging enabled.. or have Wireless ADB running (batch has built in support for wireless ADB)
You can run it while the phone is on. The phone will reboot itself when the script is finished.
Click to expand...
Click to collapse
It goes through all the prompts for me, but then on the final "Press any key to continue" when I press any key, the batch file just closes with nothing being done to my phone.
Guess I should add, I'm using windows xp, and yes, usb debugging is enabled
masondoctorjt said:
It goes through all the prompts for me, but then on the final "Press any key to continue" when I press any key, the batch file just closes with nothing being done to my phone.
Guess I should add, I'm using windows xp, and yes, usb debugging is enabled
Click to expand...
Click to collapse
Hmm strange. I guess I should add instructions to do it manually, just in case something like this happens
Basically just open a command prompt, navigate to wherever you unzipped everything...
adb root
adb remount
(adb connect again here if using wireless)
adb push dexo /system/bin
adb push dexopt-wrapper /system/bin
adb push zip /system/xbin
adb push zipalign /system/xbin
adb shell chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign
then the final command
adb shell dexo
let me know where at in this process it's getting snagged if that doesn't work.
ericdjobs said:
Hmm strange. I guess I should add instructions to do it manually, just in case something like this happens
Basically just open a command prompt, navigate to wherever you unzipped everything...
adb root
adb remount
(adb connect again here if using wireless)
adb push dexo /system/bin
adb push dexopt-wrapper /system/bin
adb push zip /system/xbin
adb push zipalign /system/xbin
adb shell chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign
then the final command
adb shell dexo
let me know where at in this process it's getting snagged if that doesn't work.
Click to expand...
Click to collapse
Thanks... It might be a couple of days before I have a chance to try this again, but I'll let you know if this way works.
Sent from my HTC_Amaze_4G using xda app-developers app
Just ran the manual instructions since I had the same error noted above and all goes well until after the last adb shell dexo command; I get a message saying everything is installed but I also see this: Please install these binaries to continue: sed cp unzip. What does that mean?
Edit: I went ahead and rebooted anyway and nothing happened, still deodexed.
How can you tell if the custom rom you're on is dedoxed or redoxed? I'm on the ViperA
Sent from my HTC_Amaze_4G using xda app-developers app
kevinrubio1 said:
How can you tell if the custom rom you're on is dedoxed or redoxed? I'm on the ViperA
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Use root explorer or some similar app and go into system/apps and if you see any files right next to the app files that say .odex then you are not deodexed.
Also most custom ROM's state right in the OP if the are deodexed or not.
Sent from my HTC_Amaze_4G using Tapatalk 2
I don't have access to computer so can I run commands through terminal emulator?
Sent from my gt-1900 using xda premium
Doesn't work as of yet...
Followed the instructions
BusyBox Rooted S-off on ViperAmaze 1.7.1 ran the script as Admin and phone restarted after completion of script and stuck on bootscreen.
running fix permission and wiping dalvik+cache just in case if it works will report back EDIT: doesn't work had to recover nandroid
Can anyone dumb this thread down to what deodex/odex means to a person with no dev skills or
What can I do with deodex apks?
Is this a significant boost in speed etc?
Dumb and Dumber (remember the movie?)
blindskater39 said:
Can anyone dumb this thread down to what deodex/odex means to a person with no dev skills or
What can I do with deodex apks?
Is this a significant boost in speed etc?
Click to expand...
Click to collapse
When a Carrier releases a version of software it is ODEXED meaning you have an app like camera.apk, and you have a camera.odex
It's a file that contains the libraries and other things to support the apk.
When you DE-ODEX you build all of the stuff into the apk file so you don't need the .odex files.
it reduces the nuber of files in the rom. Meaning you now only have a camera.apk with no .odex file.
RE-ODEXING the apps and files makes it run faster.
That is taking the files back out of the apk file so you have two files again.
It seems easier to take DE-ODEXED files from one rom and use them in another rom, but you cannot just copy an apk that hasn't been DE-ODEXED into another rom without its' associated odex file.
How's that?! Hope it helps!
Looks like.... IT WORKS on Super Sense 3.2 (coming very soon)! This will speed it up big time!
chevycowboyusa said:
When a Carrier releases a version of software it is ODEXED meaning you have an app like camera.apk, and you have a camera.odex
It's a file that contains the libraries and other things to support the apk.
When you DE-ODEX you build all of the stuff into the apk file so you don't need the .odex files.
it reduces the nuber of files in the rom. Meaning you now only have a camera.apk with no .odex file.
RE-ODEXING the apps and files makes it run faster.
That is taking the files back out of the apk file so you have two files again.
It seems easier to take DE-ODEXED files from one rom and use them in another rom, but you cannot just copy an apk that hasn't been DE-ODEXED into another rom without its' associated odex file.
How's that?! Hope it helps!
Click to expand...
Click to collapse
For the most part its much easier to comprehend, thanks! But why can't you copy a de-odexed apk to another rom if it doesnt which doesnt need the .odex files anymore?
blindskater39 said:
For the most part its much easier to comprehend, thanks! But why can't you copy a de-odexed apk to another rom if it doesnt which doesnt need the .odex files anymore?
Click to expand...
Click to collapse
You can. I'm sorry if I complicated that part..
Sent from my HTC_Amaze_4G using xda app-developers app
this may be a stupid question but will this work on cm11?
dtr145r said:
this may be a stupid question but will this work on cm11?
Click to expand...
Click to collapse
No, CM11 is already deodexed.
SuperAfnan said:
No, CM11 is already deodexed.
Click to expand...
Click to collapse
well yea,
i know that.
thats the point, to 'RE-Odex' it....
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Vaibhav Chauhan said:
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
Click to expand...
Click to collapse
can i use another rom's updater script in my rom which has same base??
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
es0tericcha0s said:
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
Click to expand...
Click to collapse
i tried to replace updater script but not working
i also have tried to compare set perms but i am unable to find fault in it
@es0tericcha0s
please tell me what to do??
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
es0tericcha0s said:
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
Click to expand...
Click to collapse
actually i am using android kitchen to make the rom
and when i use the cosmic rom's updater script in it the status 1 error was solved
but it stuck on boot animation
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Vaibhav Chauhan said:
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Click to expand...
Click to collapse
Not all phones have adb access while in a bootloop. But to do so you would need adb set up on your computer, change directories to the adb folder (or if it's enabled globally, then where ever), and type:
adb logcat
You'll want to save it somewhere like:
http://pastebin.com/
and upload the link.
I am not skilled at reading logcats, so not sure if I can be of any more help after that.
If you don't have adb set up already, then just use this one: http://forum.xda-developers.com/showthread.php?t=2317790