Related
After installing busybox and metamorph from the market, i get an error when running "Start Checks" in Metamorph:
"Some files could not be extracted and set up. Please make sure you have enough free space in /system"
any suggestions
Have the same problem, would love to know the solution!
EDIT: Using xtrROM 3.0.3
Might help others if you guys put which ROM you are using as well.
Open up the apk and find zip and zipalign. If these two binaries are not in /system/bin, MM tries to copy them there. If it is unsuccessful due to insufficient rights, you will get that message. One way around it is to put the files there yourself.
that worked you are a genius i have been working on this for days. Thanks for the help
I got the same message then I ran it again and it ran checks again no problem and I applied Dk's Froyo theme no sweat
Sent from my FroyoEris using XDA App
ihtfp69 said:
Open up the apk and find zip and zipalign. If these two binaries are not in /system/bin, MM tries to copy them there. If it is unsuccessful due to insufficient rights, you will get that message. One way around it is to put the files there yourself.
Click to expand...
Click to collapse
how do you **open up** the apk.
Issue 1: I'm trying to install ClockPackage.apk, Gallery3D.apk, MyFiles.apk in order to have the stock clock. I keep getting the error "Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]" when i try to use the command adb install (any of the 3).apk. I have also tried "adb push" which doesn't seem like a valid command. I tried moving the 3 apk files to my sd card on the phone and using "installer" and "eoeAppinstaller" from the market and these fail as well. Any more suggestions? I really like this di11igaf's ROM, but I cannot stand the new alarm ( i like the gradual volume increase of the stock). I have tried a couple of market clocks, but they just didn't work for me. Thank you very much in advance.
Issue 2: If I use CWM and choose Reboot into Recovery i get the following:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter OK Key, Select : Vol UP / Vol Down
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal sd card
update media, please wait
update media finished
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
-- Applying Multi-CSC...
Installing Multi-CSC
(in red)
Installation aborted
At this point I can use the volume buttons to scroll up and down, but the power button will not select anything. The only thing I can do is remove the battery and boot the phone back up, which then takes me into CWM recovery v2.5.1.0. I was able to install the di11i add on, but I don't think that I'm supposed to be pulling the battery to get to this point.
Thanks again and sorry about the long post.
Im no expert on this type of stuff but I use di11i roms and I just transfer apk's to the root of the phone through the regular mass storage mode and use root explorer for the rest.Havent had any problems yet.
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
From my own personal experience the 3dapp isn't sign so I can't install it too
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
+1 you can simply use root explorer to copy the apk files into \system\app folder. quick and easy.
booty hater said:
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
Click to expand...
Click to collapse
It is a zip file and it installed. What concerned me was the process. Should it have frozen up like that and forced a battery pull? Nothing I've read leads me to believe that was proper behavior of the CWM.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
I just looked into exactly what you were talking about and I got it figured out.It wasnt installing for me either but this is what I did and it works now.
Through mass storage mode I copied the 3 files to the root of the card.
Then I moved the files to the app folder which is inside the system folder.
I use root explorer for the moving.
When you move them into the app folder its gonna ask to overwrite say yes.
After you get everything moved it will work if you go to the app in the drawer.I never actually installed anything but did an overwrite.
booty hater said:
I never actually installed anything but did an overwrite.
Click to expand...
Click to collapse
Right. Apps in the system/app folder are auto-picked up
supervg3 said:
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
Click to expand...
Click to collapse
u cannot see it in my files. u need to have root access, and something like root explorer.
So it looks like I could have just copied and pasted the files from the sdcard/Clock folder I placed them in to the /system/app folder using Super Manager. I swear I tried that and it failed before I went through all the crappy steps below. Oh well.
Ok this is going to sound pretty cheap, but I didn't want to pay the ~$4.02 for an ap that I was going to use three times. I did find another way. I used Super Manager and http://forum.xda-developers.com/showthread.php?t=877316&highlight=installing+apk post #3.
So for any other cheapskates out there.
1. Install Super Manager on phone
2. Install ADB on pc
3. Connect phone to pc and copy the three files ClockPackage.apk, Gallery3D.apk, and MyFiles.apk to the sd card. (I just drag and dropped in windows explorer)
4. Use Super Manager to move to /system/app/ and rename the existing file Gallery3D.apk (I renamed it to Gallery3D.old)
5. Use adb to copy the 3 files from the directory in which you originally placed them on the phone to /system/app/
in adb type:
adb shell
su
(accept the prompt on your screen)
cd /sdcard/whereveryoustuckfile
cp blahblahblah.apk /system/app/ (the red from Pirateghost).
6. Reboot
The clock and alarm work fine, but I cannot get Daily briefing option in alarm to work. I get a FC. I did install the "apk add on pack for 5.6" post 3 of http://forum.xda-developers.com/showthread.php?t=897416 , but I dont think Daily Briefing was included in that. Any suggestions? And one last thing - what is the di11iBrowserfix.zip from post 3 of the thread above for? Thanks again to all who contributed.
I got the daily briefing working. Everything is almost perfect, but I would like two things still.
1. Is there anyway to change the tune that is played when you have smart alarm selected? I have a different tone selected, but I think once you select smart alarm it defaults to that new age tone.
2. My alarm goes off, I stop it, but then I have to unlock it before I see the daily briefing. Can anyone think of a way to have the phone unlock when I turn off the alarm. I know it is so insignificant, but it used to do that when it was stock and it was pretty cool.
Come one guys and gals - don't make me figure this one out by myself j/k but seriously I have surprised myself already by getting this far and I really don't have skill or knowledge for the last two things. I'm learning though....slowly.
Thread etiquette
Did I do something wrong here? I got some really quick responses to my questions before, but nothing on my latest. I ask this next question with all seriousness - should I have started a new thread since it's kind of a new topic? No worries either way, I just want to post in the the most effective way. Thanks. BTW, my phone is working great. I'm getting ready to install 6.0 GPS is a little screwy - often has me west of my location by about 30 meters by I attribute that to the phones hardware. Other than that I have no complaints (except for the lame smart alarm tune)
diablo009 said:
Right. Apps in the system/app folder are auto-picked up
Click to expand...
Click to collapse
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
you should start a topic instead append to other's topic.
you can flash any kernel/modem using CWM, just make sure it is i9000's.
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
diablo009 said:
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
Click to expand...
Click to collapse
Thanks for the info and sorry for appending to this topic!
I found how for the X2 but the instructions dont work for the Revolution.
Anyone know the way to stop it?
Thanks
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
I deleted that file (adding.bak sounds much better) and it has gone away, just like mtmichaelson said.
Sweet thank. Ya on my droid 2 i stopped a bunch of stuff and just did the .bak so if i need it later i can just change it back.
Thanks
Just to double check, this works on revo phone.
When I acess file it has .so file type do I change .so to bak?
I just added .bak after the .so
Sent from my VS910 4G using XDA Premium App
Revolt - LTE
I'm not sure if this is related, but I noticed that after I flashed Revolt 1.3, I never see the "LTE" symbol in my notification bar. I'm in an LTE area, so I know it's available--does that mean my phone isn't running LTE anymore or is the symbol just not showing up on this ROM? I apologize in advance if this is a ridiculously misguided question--I'm new here and learning as I go.
By the way, mtmichaelson--I said this before and I'll say it again--awesome ROM! Thanks again for your hard work.
mtmichaelson said:
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
ally3447 said:
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
Click to expand...
Click to collapse
Yes it does
Sent from my VS910 4G using xda premium
mtmichaelson said:
Yes it does
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
So, right now it is a .so file. Do I just add .bak to it, or change it from .so to .bak?
(Just want to be extra sure.)
Also,I would like to root my phone. I found a way that someone rooted theirs with their 2.2.2. Do you think I should root first, then change the file so it doesn't update? Or does it matter?
by the way, Here is the root I found(sorry it's a bit long):
"How to root your OTA Updated Revo:
This method requires you to downgrade your phone back to the V4 stock version. As of now, there seems to be no root process for the V6 update. This method has worked for me and I am also on a custom ROM that has been said to have some, if not most of the V6 updates included without the bloatware.
Step One:
- Be sure to get the following files:
---- LG VZW_United_WHQL_v1.2.0.exe
---- LGAndroidDriver_Ver_1.0_All.exe
---- LGNPST_Store_Lab-1.zip
---- VS910.dll (required to use LGNPST_Store_Lab-1.zip)
---- VS910ZV4_04.S4_04.P58008.R5.user.tot
---- RevoToolkit-1.0.apk (This is untested by me but supposed to provide an easier method to install CWM mod vs the ADB method)
---- SuperOneClickv2.1.1-ShortFuse (Includes the needed ADB program)
---- rageagainstthecage-arm5.bin (The exploit needed to root revo, not necessarily found with SuperOneCLick)
---- RevoltRom1.3.zip (This is optional, but recommended to speed up your revo and also to comply with the original topic of this thread. It 'seems' to stop the OTA from 'trying' the update since it includes updated features. NOTE that I said 'seems'... Other things I did may be the actual result I haven't seen the OTA try to install...
Ok, so to start, you will want to be sure that you have the drivers on your computer (I'm using windows 7 x64), so that is what this method has proven to work on by me.
Be sure to install:
- LG VZW_United_WHQL_v1.2.0.exe
- LGAndroidDriver_Ver_1.0_All.exe
Both may not be required, but I have both installed and things worked.
Then you will need to install:
- LGNPST_Store_Lab-1.zip
- VS910.dll (This is just copied into the folder LGNPST/Models. My install put the LGNPST program in C:\LG Electronics, not c:\Program Files (x68)... )
- You will run the LGNPST program, select the VS910.dll via Menu: File --> Select DLL.
- Then, in the bottom right of the LGNPST program, select BIN File (folder icon) to load the 'bin'.
--- This will require you to enter *.* in order to find the .tot file. Don't worry, this .tot file is what you need in the LGNPST Program.
- Once loaded and your phone is connected and recognized (Phone must be in 'Internet USB Mode'), hit the Start Button. This will begin the process of restoring your phone back to V4.
After that has completed, which takes a while, you will then need the SuperClick program to root.
- Copy, or verify, the rageagainstthecage-arm5.bin file is located in the Exploits folder where you extraced SuperOneClick.
- Run SuperOneClick, Select the exploit pull down (which defaults to 'auto') and select the rageagainstthecage option.
- Press the Root button and let it do its thing.
--- If it fails, this is what I had to do.. Reboot your phone. While it is rebooting, have the SuperOneClick program ready and waiting for you to hit Root again. As soon as the LG Logo becomes animated, hit Root and let it try again (While it is rebooting). This seemed to get the read/write options to work, where failed. This possibly is part of the update that is sticking around to stop you from rooting. So, try a few times. If/when succeeded, move on to the next steps if you wish to have some of the update 'fixes' without the update and a faster custom ROM...
To install a ROM, you need to have CWM installed.
Two methods to doing so seem to exist:
- The method I used was at this link: [RELEASE][6-14-2011] CWM Ported to the Revolution 4G! - xda-developers
Follow that and you should have a backup original image and the new image to get CWM to work to install custom ROMs
- The OTHER method, which is UNTESTED by me, is to use a simple tool called RevoToolKit, which is and APK file that runs directly on your phone. If it works, which others seem to say it does, this would be the most simple form of installing CWM to your phone. Be aware that this app is small, but uses a downloader to install CWM, so you want to make sure you have a good internet connection or data connection...
After that, you will want to follow the directions for CWM (ClockWorkMod) at this link:
- [Rom][8-17-11]Revolt Rom 1.3 - xda-developers
After all that, you should have a rooted Revo AFTER you managed to do the update.
I included links to some instructions in order to shorten up this post and not 'copy' someone else's methods and be sure that you can give the credit to them. The only credit I deserve for this is a complete step-by-step, in one place procedure to get you back or to root your Revo if you did the update.
In time, I am sure that there will be a simpler way to root the OTA Update, but until then, this is working for me and hope that this helps clear up some issues for others that find it tough to get back to root after the OTA Update."
It then has the file links, but I cannot post them since I am a newb.
Thanks again!
I don't see a way for you to change the file from .so to .so.bak without having root as far a rooting you only have to downgrade if your phone its v6 if out is running v4 all you need to do is root it
Sent from my VS910 4G using xda premium
Is there a way to do this without buying root explorer? I have bloat freezer so is there anything I can just freeze?
Thank You
*EDIT* just bought root explorer for $.99 through Amazon Appstore for those who still need it.
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Sleepykat said:
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Click to expand...
Click to collapse
On the top right of root explorer is a "Mount R/W" button. Click that and it should let you make changes to the system.
Hope it helps
"Home-Less and Iconic"
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Sleepykat said:
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Click to expand...
Click to collapse
Glad to help.
"Home-Less and Iconic"
Hello all,
Noob here. been trying for days not to backup my x8 but keep getting the following error message in xrecovery: E: can't access /tmp/recovery.log If anyone can help I'll be there best friend FOREVER! I've followed all of the tutorials out there but to no avail.
PLEASE HELP!!!
Have you tried using the xrecovery automatic installer you will need es file explorer or root explorer to mount the system folder writable then run the automatic installer. I am asuming you have rooted your device search for the installer on XDA/Google. More instructions is on the official thread. I really hope i helped!
Sent from my E15i using XDA App
hi,thanks so much for the response.ive tried all these avenues but still it nothing works. the tmp/recovery.log is the major issue I'm trying to resolce
I see well good luck i hope everything works out for you
Sent from my X8
creating a /tmp/recovery.log
Well, I hope dasingletoon is enjoying his updated device.
As embarrassed as I am to admit it, here is what I've done:
Created an empty file under /tmp/ named recovery.log, made sure it has all R/W it requires and... upgraded.
Hope it helps.
My Galaxy Tab 7 P1000 was originally running clockwork 3.X... and I just tried to install clockwork 5... and after installation, the device keeps staying at the boot screen. And when I go to recovery mode, the 'HOME' button doesn't work.... :crying::crying:
How can I fixed this brick back to a normal tab?
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
priyana said:
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hey Dude,
Thanks for your reply. I will try it out tomorrow and hope it works on my stupid tab.
By the way, 1 more question. Before reading your reply, I tried to install CWM-based recovery 5.0.2.8 again and tried to install CM9.x on the tab, but not matter which version I used, (P1000, 1000L, 1000N), all of them gave me 'assert failed getprop( ro.product.device ) galaxytab...'. It sounds that the ROM installation file couldn't recognize my P1000 tab.....do you have any idea on how come my device couldn't be recognized.
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Thx X 1000000000000000000000000
ableeker said:
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Click to expand...
Click to collapse