So i have had this issue for some time now but i have been overlooking it. every time i make a flashable rom for my xperia play and try to install it get a error and cant install from TWERP. If i install on CWM it works, but i did notice that some other zips install on TWRP but not mine. Once i tried something from TWRP website and it worked ON TWRP BUT NOT ON CWM. I need to make a zip that is compatible with both TWRP & CWM
xdarkmario said:
So i have had this issue for some time now but i have been overlooking it. every time i make a flashable rom for my xperia play and try to install it get a error and cant install from TWERP. If i install on CWM it works, but i did notice that some other zips install on TWRP but not mine. Once i tried something from TWRP website and it worked ON TWRP BUT NOT ON CWM. I need to make a zip that is compatible with both TWRP & CWM
Click to expand...
Click to collapse
Maybe your meta inf file in the zip I'd outdated? Try copying one from a newer flashable zip like a rom or one that works. Im not very good with this stuff but it's just a suggestion you could try
Sent from my Xperia Play (r800x)
xdarkmario said:
So i have had this issue for some time now but i have been overlooking it. every time i make a flashable rom for my xperia play and try to install it get a error and cant install from TWERP. If i install on CWM it works, but i did notice that some other zips install on TWRP but not mine. Once i tried something from TWRP website and it worked ON TWRP BUT NOT ON CWM. I need to make a zip that is compatible with both TWRP & CWM
Click to expand...
Click to collapse
I notice that that twrp hates things in updater-script that doesn't exists. For example, setting permissions or symlinking for non-existing files. And better do mounting with busybox command.
If you want just take meta-inf folder from my rom, it work in twrp. Edit to your liking (but delete aroma folder and aroma scrips)
Sent from my R800i using xda app-developers app
abdel12345 said:
Maybe your meta inf file in the zip I'd outdated? Try copying one from a newer flashable zip like a rom or one that works. Im not very good with this stuff but it's just a suggestion you could try
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
if i update it then the zip looses compatibility with CWM
Bakisha said:
I notice that that twrp hates things in updater-script that doesn't exists. For example, setting permissions or symlinking for non-existing files. And better do mounting with busybox command.
If you want just take meta-inf folder from my rom, it work in twrp. Edit to your liking (but delete aroma folder and aroma scrips)
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
i'll take a look for non existing links.
Related
ok im a newbie at this root stuff and i just flashed the fresh evo 3.5.0.1 but i still cant figure out how to change the theme and the one im trying to get says it works with that fresh and when i download it i get two zip files do i need to add both them to my root on my sd im lost someone please help
Take the zip file you want and move it to your root SD folder. Reboot into recovery and choose that file with choose zip from SD option. Then just flash it just like you did for your rom. This is the basic method you use to flash anything to your phone.
Sent from my PC36100 using XDA App
briankurtz79 said:
Take the zip file you want and move it to your root SD folder. Reboot into recovery and choose that file with choose zip from SD option. Then just flash it just like you did for your rom. This is the basic method you use to flash anything to your phone.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
and do a NAND BACKUP FIRST !
Both methods above are correct. And to add the cherry to our ice cream of helpitude, if the theme isn't obviously on when you reboot the rom, check the theme manager app in your app drawer.
What recovery version are you using? If its clockwork 3.0 then you'll need to use something else (either an order version of clockwork or amon_ra). This actually happened to me with cw3.0, I was able to flash a Rom fine but no themes.
Abricr said:
What recovery version are you using? If its clockwork 3.0 then you'll need to use something else (either an order version of clockwork or amon_ra). This actually happened to me with cw3.0, I was able to flash a Rom fine but no themes.
Click to expand...
Click to collapse
You can flash themes, they just have to Edify compatible, which a lot aren't at the moment.
I fixed recovery for the Continuum users so that you have your own button mappings. It isn't integrated into the kernel yet, but I'm going to attempt to get that fully working (I have it partially working atm). Until that is fixed, you get the update.zip method for CWM. So, to accomplish this, you'll need to download two things. First, you need the update.zip file, which is placed on the root of the SDCard (/sdcard/update.zip) and the second item is the recovery kernel, which is flashed via Odin (v1.3). It is now integrated into the kernel and it has been updated to the EC09 kernel. This package will flash both recovery and kernel (so you don't loose CWM when the system boots). Note that if you are still on DL17, you should use the archive packages below. What you will need is this file, and you will want to flash it via Odin (or extract it and use Heimdall).
Open Odin, click the PDA button and browse to and select the continuum_recovery.tar.md5 I400_CWM.tar.md5 file that you downloaded. Remove the battery from your phone, and hold down the volume down button while plugging in the USB cable that is attached to your computer. Make sure you have the drivers installed, if not, you'll need to install them before you continue. Flash the file by clicking start if the phone is detected in Odin. Once it completes successfully, all you need to do is boot to recovery and apply sdcard/update.zip and you'll be in CWM. I decided upon black background with cyan text. This can still be changed if you wish, but I like it
Here are your button mappings:
Camera button/Grip sensor - Select Item (applies to cwm and stock recovery)
Volume Up/Down - Scroll up/down in the list (applies to cwm and stock recovery)
Power Button - Select Item
Menu Button - Does nothing
Home Button - Go Back
Back Button - Go Back
Search Button - Hide Text
I'm still trying to figure out how to get buttons to show up for the touchkeys. For now, they're blank, so just press in the approximate location on the screen for them. We may or may not be able to get buttons there at some point. Also, when you initially boot to recovery, there will be a message about update.zip being gone. Ignore the message as it seems to be a bug. As long as you copied the update.zip from this thread to your SDCard, you should be fine. Enjoy.
If you like my work, feel free to donate to me. Alternatively, sign up for Dropbox via my referral link Also, remember that none of this would really be possible without the generosity of DroidXcon, so you could donate to him as well.
Archive said:
Recovery Kernel
Download - CWM 2.5.x
Download - CWM 3.x
Click to expand...
Click to collapse
Thank you so much imnuts
It works like a charm
and btw, i love the color scheme, lol
This is awesome! Im extremely happy to see great dev work still going on for the continuum!
I'm going to update the update.zip soon then as well to the latest CWM 3.x that we have for the Fascinate as well. Then, maybe look into replacing stock recovery again and hoping it works this time.
im having major problems well maybe not major but i installed cwn but after i rebooted and tried to install a softkey update.zip i lost my cwm and every thing i try to do i cant get cwm back
You have to apply the update.zip every time
Sent from my SCH-I400 using XDA Premium App
I do and I get the discolored screen then it send me to the stock recovery and when I try to install the update.zip it says update.zip not found when I know it's there
Sent from my Rooted Space Time Continuum w/h a 2600mAh battery
Mine says the update isn't found either but it still works for me. I dunno about the discolored screen. I'm sorry :/
Sent from my SCH-I400 using XDA Premium App
i figured out what i was doing wrong i renamed the file to update.zip when i should have left it at just update lol oh well you live and you learn
Ohh lol. The .zip is the type of file it is
Sent from my SCH-I400 using XDA Premium App
Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App
And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App
ntien said:
Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
You need to flash the recovery kernel via Odin, and it is an actual kernel. The update.zip is a fakeflash recovery. It basically kills the currently running recovery and starts up CWM recovery in its place.
ntien said:
And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
The difference is that this recovery has the correct button mapping, where the update.zip that Adrynalyne posted was using the Fascinate's button layout, so things didn't work as expected.
so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?
ntien said:
so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?
Click to expand...
Click to collapse
Yes you can. Recovery is a full kernel, it just boots using a different file and set of commands, and it doesn't start up the android system once booted and provides just a minimal environment. The recovery kernel and standard kernel lie on two separate partitions, and in actuality, this recovery kernel is the standard kernel as well.
New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.
Deleted cause it was a stupid question
imnuts said:
New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.
Click to expand...
Click to collapse
I guess I should read the whole thing before wondering why I can't restore an old backup with the new CWM
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App
ntien said:
Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
...Did you not even see my post right above yours?
I created a flashable zip apk...of xperia semcillumination.apk..
I made all the requirements and settings to flash...
Now when I flash in cwm recovery...it flashed successfully...but does not installed apk...
I checked root...and find .....semcillumination.apk copied in system/Apps....
As well as related libs and frameworks also copied...but still ...its...not getting installed..
Can some one help me to install on custom ROM.
Attaching zip.
Amirphp said:
I created a flashable zip apk...of xperia semcillumination.apk..
I made all the requirements and settings to flash...
Now when I flash in cwm recovery...it flashed successfully...but does not installed apk...
I checked root...and find .....semcillumination.apk copied in system/Apps....
As well as related libs and frameworks also copied...but still ...its...not getting installed..
Can some one help me to install on custom ROM.
Attaching zip.
Click to expand...
Click to collapse
maybe...
any updater script in meta-inf is missing sir?
Hey guys,
is there any working flashable zip for the Pixel Launcher?
I am on 3.5.5 and Stock TWRP Recovery.
I dont want to install it via apk as Google now is not working there.
Thank you so much
Use search
I wouldnt have asked if I hadnt searched and tryed flashing some zips before, Sherlock. So either contribute something or ignore this thread.
Maybe there is someone who has 3.5.5 and a flashed Pixel Launcher with working Google Now running?
i was looking for the same, and also didnt get a clear awnser.
Just simply download the .apk, install it. Reboot in recovery (TWRP), mount the system and with the file manager, move /data/app/com.google.android.apps.nexuslauncher to /system/app
Thanks Elpatii. Tried that, unfortunately when I try to move or copy it I get an "process ended with Error: 1" error Did you get it working with that method? Are you rooted?
It seems like system partition is completely locked in CB 3.5.5
Funny thing is I also flashed the Google Dialer from this thread and it writes itself into system partition:
http://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-install-google-dialer-phone-t3443006
I dont know for sure but the dialer zip mounts and unmounts the system partition by itself during flash. I never found a Pixel Launcher zip that does that. Maybe thats the reason?
Elpatii said:
Just simply download the .apk, install it. Reboot in recovery (TWRP), mount the system and with the file manager, move /data/app/com.google.android.apps.nexuslauncher to /system/app
Click to expand...
Click to collapse
This works fine for me. I downloaded the latest APK from APK Mirror, installed it, then using Root Explorer moved it to /system/app. I rebooted and the Google Now swipe works. I'm on 3.5.5 and it goes without saying I'm also rooted
This must work, modded one with transparent dock on 6.0.1, flash it through TWRP
mhhh I tried flashing SuperSu binaries but it didnt make any changes to my system just like the Pixel Launcher zip. Like the flash itself goes well but nothing changes. Neither I get root nor the pixel launcher. 3.5.5 behaving so strange...
I already tried clean flash the phone and using modified 3.02-22
@Tikerz which TWRP are you using at the moment?
airflyer737 said:
mhhh I tried flashing SuperSu binaries but it didnt make any changes to my system just like the Pixel Launcher zip. Like the flash itself goes well but nothing changes. Neither I get root nor the pixel launcher. 3.5.5 behaving so strange...
I already tried clean flash the phone and using modified 3.02-22
@Tikerz which TWRP are you using at the moment?
Click to expand...
Click to collapse
I'm on the lastest -22 TWRP. I just clean flashed 3.5.5. yesterday with SuperSU SR2. Are you sure SuperSU flashed ok? As long as you have root you should be able to just install the APK and move it to /system/app using Root Explorer or other file manager.
Got it working guys. And here is how:
At first I flashed TWRP 3.0.2-22 like @Tikerz said. I deleted SwiftKey in the system app section (basically I just wanted to try if can do anything in system section). I now can move Pixel launcher folder to system/apps. I think because the deleted SwiftKey app gave me some reserved space in the system section. And, flashing it with TWRP also works now!
Thank you all so much for your ideas and hints, I am very happy now with my Pixel experience
@Darkje Have you also found a solution?
@airflyer737, Yeah m8 flashed the zip and All ok.
Now i need the dpi smaller All is really Big ?
ach3fck said:
This must work, modded one with transparent dock on 6.0.1, flash it through TWRP
Click to expand...
Click to collapse
Tganka
---------- Post added at 11:39 PM ---------- Previous post was at 11:34 PM ----------
ach3fck said:
This must work, modded one with transparent dock on 6.0.1, flash it through TWRP
Click to expand...
Click to collapse
ach3fck said:
This must work, modded one with transparent dock on 6.0.1, flash it through TWRP
Click to expand...
Click to collapse
I've been looking for this launcher for very long time
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Just install Pixel launcher from play store.
panther124 said:
Just install Pixel launcher from play store.
Click to expand...
Click to collapse
Not compatible with my OP3 it says.
bjorg18 said:
Not compatible with my OP3 it says.
Click to expand...
Click to collapse
on every cm13 rom and cm14 rom it is compatible for me. i use this launcher for weeks now.
Does slide to google now work on the play store version??
So just flashing the zip is enough ? No need to install the apk ?
Anyone has the new update?
Hi!
Im trying to figure out how to make a flashable zip to flash after a rom update so apps that I want to install in sytstem/apps can be automatically be flashed from the recovery instead of manually copying them using a file manager. Is there some one that can help me in this?
yakie996 said:
Hi!
Im trying to figure out how to make a flashable zip to flash after a rom update so apps that I want to install in sytstem/apps can be automatically be flashed from the recovery instead of manually copying them using a file manager. Is there some one that can help me in this?
Click to expand...
Click to collapse
I have a script I run after each flash, but I currently only use it to delete apks. Perhaps you can use it as a base, I think you need the function "package_extract_file" (it's commented out in my script, I used it to overwrite a GPS config).
My zip is attached, the file to look into is in meta-inf/com/google/android and is called update_script.
Just play around with it, you can just put it back into the zip and flash it in twrp.
muff99 said:
I have a script I run after each flash, but I currently only use it to delete apks. Perhaps you can use it as a base, I think you need the function "package_extract_file" (it's commented out in my script, I used it to overwrite a GPS config).
My zip is attached, the file to look into is in meta-inf/com/google/android and is called update_script.
Just play around with it, you can just put it back into the zip and flash it in twrp.
Click to expand...
Click to collapse
Great thank you! I'll look at it
yakie996 said:
Great thank you! I'll look at it
Click to expand...
Click to collapse
Look at loads of updater scripts. Learn the commands they use.
Pick some relevant for your needs.
Then use them.
You will get errors. There will be screw ups but eventually it all starts working.
There's no other good way really that's how I learned how to use updater-scripts.