I am new to rooting so I dont know how to install mods on a Rom . I have ARHD 6.3.1 . Already downloaded required mods just wanna know how to install them . Thanks in advance.
Most mods are designed to be flashed in Recovery, just like the ROM itself.
It's a good idea to backup the ROM in recovery first, as there's no "uninstall" option for these mods. So if you decide you don't want the mod, you can restore your backup to get everything back to the way it was before you flashed it.
Depending on what mods you've downloaded, most of them are usually just flashable .zips, just like the ROM itself. So you simply install them by rebooting to recovery and flashing the .zip files you've downloaded and then rebooting afterwards.
I have downloaded CRT mod , advanced power manager mod , honeycomb icons + % battery mod , beats audio(music box) mod . should i just flash them from recovery just like i flashed rom . Thanks
There's a fairly easy way to check for yourself if a ZIP file is meant to be flashed in Recovery, like a ROM.
Just open the zip file (don't extract it, just open it in your favourite ZIP program). Have a look inside and if you can see a folder called "META-INF" then you know it's a flashable ZIP file.
See the attached screenshot for an example. There might be lots of other folders inside the zip (system, data), but as long as there is one called "META-INF" then you know you can flash it in Recovery.
Can anyone link me to a guide for putting together a zip file of apk's I like to install after flashing a ROM? Thanks.
U can download a gapps zip and replace the apps with whatever apks u would want but I think most gapps zips will install them in system but I'm not sure, you could try the inverted gapps as I'm pretty sure those install in data to make them more easily removeable later
Just add them to the ROM before you flash it in the System/App folder
bdK14 said:
Can anyone link me to a guide for putting together a zip file of apk's I like to install after flashing a ROM? Thanks.
Click to expand...
Click to collapse
Can you clarify the question? Do you mean a zip of apps that you just don't want to forget to install or do you mean actually mean a flashable zip like some of the other guys mentioned?
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.
For CM11 Nightlies:
Find nightlies here:
http://download.cyanogenmod.com/?device=n1
If you're already on CM 10.2, just wipe cache and dalvik. Flash over your current build.
If you're coming from anything else, wipe cache, dalvik, data, and system. Then flash normally.
If you want gapps, you'll have to flash gapps as well.
No need for any modified files on nightlies. I assume that official stable builds will still be defaulted to flash on stock recovery though.
————————————————————————————————
CM 10.2 Information. Please do not use the following to flash CM11!
This is the method that I used to install CyanogenMod on TWRP.
I have tested this, and it is working perfectly on CM builds:
cm-10.2-WPPH47N-n1
cm-10.2-WPPH50O-n1
I will continue to test and update as new CM builds come out until CM flashes normally on TWRP
————————————————
First - Have TWRP as your recovery (2.6.3.1). Don't ask me how to do that.
Second - Backup your ROM! Just in-case something breaks, it's not my fault, and I'm not responsible.
————————————————
Now, we begin:
Download the newest CM build for the Oppo N1 from http://www.cyanogenmod.org/hardware/oppo-n1/#images
————————————————
After downloading your CM build from the above link, you'll need to follow these instructions to get setup for flashing in TWRP.
To modify your downloaded CM file, you can use either of the two methods below:
1: You can modify it yourself. It's actually very simple, just one line change.
2: I have attached an already modified updater-script to my post. You can use that and drop it into place (the file inside the zip, not the whole zip).[/b]
YOU ONLY NEED TO USE ONE OF THESE METHODS!
Method 1: To modify the file yourself:
First, open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Open the updater-script
Remove the first line only! You will remove:
Code:
assert(getprop("ro.product.device") == "N1" || getprop("ro.build.product") == "N1");
Do not remove anything else unless you know exactly what you're doing!
If you modified the file within the .zip, just save the file and it should save to the CM zip.
If you extracted the .zip, save the file and then go back and rebuild the zip.
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
——————————
Method 2: To download my pre-modified updater-script
Download my attached file (updater-script.zip)
Extract the file inside the zip (there's only one file)
Open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Simply copy your extracted updater-script from where you extracted it and drop it into the CM zip (It should save after)
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
————————————————
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
:victory:
I hope this all makes sense...
Basically you download the CM rom
Modify or copy the updater-script into the zip
Then you move the ROM to you phone
Then you go through the above area with wiping and flashing
* Pictures are attached
* Please let me know if there are any problems with this.
* Both versions of CM released so far have identical updater-script files. The .zip that I have attached will work on both builds.
* I will keep updating as needed
• Last updated: January 1, 2014
We're working on fixing TWRP so the asserts work properly.
https://github.com/omnirom/android_bionic/commit/4482d8513920d614e3799a214c5bad07b72580d2#diff-1 broke a lot of things.
https://github.com/omnirom/android_bionic/commit/ad76c85b9ca587084089d086f954158bc0eae905 allows flashing newer firmwares on older recoveries - but not the other way around.
The short-term fix is a TWRP build made from a 4.3 tree - this is 90% done.
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Entropy512 said:
We're working on fixing TWRP so the asserts work properly.
Click to expand...
Click to collapse
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
rayfin said:
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Click to expand...
Click to collapse
BTW, I'd prefer that my personal dropbox not be directly linked. The same file is now an attachment to my post in the TWRP thread.
Harfainx said:
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
Click to expand...
Click to collapse
i have some question can u help me :3
1. this download link is the file you already fix it right ?
https://www.4shared.com/download/UPP...N-N1_FIXED.zip - No wait - Direct download link - Full flashable ROM
Click to expand...
Click to collapse
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
kenjilolip0p said:
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
Click to expand...
Click to collapse
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Harfainx said:
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Click to expand...
Click to collapse
Camera orientation is handled by the camera HAL blobs.
CM does have back touchpad support but it's wonky (which is why omni hasn't merged it yet, we're still discussing whether to completely rearchitect it or just fix it.)
good work
Sent from my M045 using XDA Premium 4 mobile app
Except root it works
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
fesar said:
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
Click to expand...
Click to collapse
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
nowy57 said:
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
Click to expand...
Click to collapse
Go into SuperSU and remove it in the settings (unroot). That will get rid of all of the current SuperSU stuff.
Then flash SuperSU in TWRP.
To flash the unmodified CM, you can try the TWRP in post #3 of this thread HERE.
Or you'll have to remove the same line in the updater-script. The same method posted in the OP. Don't use the uploaded updater-script that I have there though. You'll need to change your own. It's a really simple fix. You don't have to extract all the files out. You can just modify the one file (I use Notepad++).
Sometime tomorrow I'll update the whole OP to include the newest CM version. I'm about to head out to our New Year's event, so I won't be available for the evening.
Enjoy the evening everyone. I wish you all the best! :good: :victory:
i have installed TWRP from #3 - not succes install CM newest version after this
i have unthick superSU and then install again via TWRP superSU.zip after that thick superSU on system android and no succes - root acces didnt come
happy new year
-------
I am a little dissapointed couse I downloaded CM ROM from OFFICIAL SITE http://www.cyanogenmod.org/hardware/oppo-n1/#images and I cannot install it SIMPLE on my device
OP updated! The newest release of CM has been added. I'll keep on top of it from now on, sorry about the delay.
I'm not going to host the CM builds anymore, since the modification is so small from the original CM build. Everyone flashing this should be capable of making the small change that's outlined in the OP.
:highfive:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
nowy57 said:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
Click to expand...
Click to collapse
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
okay , I will try it and confirm
I v got mac osx
under mac I unzip ROM , deleted first line from script then zip it , it doesent work .
but under windows - working good
Harfainx said:
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
Click to expand...
Click to collapse
What's wrong with wiping system?
You don't even wipe system if you go from ColorOS to CyanogenMod?
- Frank
cm11 nightlies are out and downloadable from cyanogenmod
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
Cm11 nightlies are out..
Do you think we can flash on twrp
If so what would you wipe...
I was thinking about using banks minimal.. 19 MB..
Please give the community tour thoughts and a step by step tutorial..
I would download the nightly from cyanogenmod and banks gapps.. Check md5 alla onmy phone
Reboot recovery and wipe all maybe even system except sdcard
Flash cyanogen then gapps then
Rewipe cache and dalvik
Reboot
I am on omni nightlies now.. Thanks in advance
where do you see nightlies for oppo n1 ?
edit:
ohhh I see
http://download.cyanogenmod.org/?device=n1
better later than never
I just lost hope for good support and sold my oppo n1
I didnt belive for good support having it from one month and non of help from CM team
When I try to flash a new Zip file, it disappears from the directory, both on SD internal and EXTsd card.......Goo manager FC and Rom manager says it's not there?
Any ideas to check for?
Re-installed Goo.im, Rom manager, still no luck.
Is there a way to manually Unzip and install without rebooting in recovery?
Tried to fix permissions, got "an error occurred while attempting to run privileged commands."?
What are you trying to flash?
Also, if you constantly moved from TW to AOSP, you were supposed to flash the zip to restore your SD card AFTER you flash the TW rom. This may be your issue as starting with android 4.2 Google added multi user and moved your files to a folder named /0 (or legacy).
Most of the time I had issues with not locating the zip it was due to this error. My recommendation, download and move the file to the root of your extSD before going in to recovery.
Also, remember Goo.im downloads are saved on the gooim folder in your internal SD card, not the downloads folder.
jibust said:
What are you trying to flash?
Also, if you constantly moved from TW to AOSP, you were supposed to flash the zip to restore your SD card AFTER you flash the TW rom. This may be your issue as starting with android 4.2 Google added multi user and moved your files to a folder named /0 (or legacy).
Most of the time I had issues with not locating the zip it was due to this error. My recommendation, download and move the file to the root of your extSD before going in to recovery.
Also, remember Goo.im downloads are saved on the gooim folder in your internal SD card, not the downloads folder.
Click to expand...
Click to collapse
Thanks. Haven't run any roms on this one. Running stock and rooted with Aviate. I've tried dloading directly to extsd, transfering from my laptop to extsd and SD.
I was trying to flash the Dark Ink lockscreen v2 and 16 ink lockscreen. I'm stumped.....I was able to flash Bravia Engine, Exposed Framework, Multi-Window Mod......it's just the Lockscreen zips. And the only reason I was doing it was because I wanted the ink to work without the S-Pen.....Not that big of a deal I guess. It has to be something simple I am overlooking...
EDIT: Fixed....sort of.... It wouldn't install from any other folder than the CWM Backup folder?? If anyone has an idea as to why, I would love to know?
dmxinc said:
Thanks. Haven't run any roms on this one. Running stock and rooted with Aviate. I've tried dloading directly to extsd, transfering from my laptop to extsd and SD.
I was trying to flash the Dark Ink lockscreen v2 and 16 ink lockscreen. I'm stumped.....I was able to flash Bravia Engine, Exposed Framework, Multi-Window Mod......it's just the Lockscreen zips. And the only reason I was doing it was because I wanted the ink to work without the S-Pen.....Not that big of a deal I guess. It has to be something simple I am overlooking...
EDIT: Fixed....sort of.... It wouldn't install from any other folder than the CWM Backup folder?? If anyone has an idea as to why, I would love to know?
Click to expand...
Click to collapse
Alot of your problems are because you're trying to flash mods on a stock odexed system. If you want to flash rom mods you need to flash a rom that is deodexed. Basically a stock just rooted system breaks up the app in your system. This allows faster boot times. An deodexed system compiles the split up apps together. This will allow you to flash mods and easily modify your system. When you flash a mod you replace the original app. If it's odexed you don't replace the whole app.
Sent from my phone
210euser said:
Alot of your problems are because you're trying to flash mods on a stock odexed system. If you want to flash rom mods you need to flash a rom that is deodexed. Basically a stock just rooted system breaks up the app in your system. This allows faster boot times. An deodexed system compiles the split up apps together. This will allow you to flash mods and easily modify your system. When you flash a mod you replace the original app. If it's odexed you don't replace the whole app.
Sent from my phone
Click to expand...
Click to collapse
Thank You. :good: I thought I flashed the "Stock_rooted_deodexed CALK7," But I used the "back to stock thread" which includes the Odexed version, and what you're saying makes sense.
I live, I learn.....:fingers-crossed:
dmxinc said:
Thank You. :good: I thought I flashed the "Stock_rooted_deodexed CALK7," But I used the "back to stock thread" which includes the Odexed version, and what you're saying makes sense.
I live, I learn.....:fingers-crossed:
Click to expand...
Click to collapse
I've flashed the wrong zip before and it sucks trying to fix mistakes. But after awhile you just backup once a week lol.
Sent from my phone