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
Related
Dear Community,
this is my first post on XDA-devloppers.
I ask you for help as y have a serious promlem with CM 9.1 on my xperia arc.
I flashed CM on my phone using the latest stable rom downloaded from the official cyanogenmod website (cm-9.1.0-anzu.zip)
Everything worked perfectly and i was delightet.
Unfortunately, after two days my phone crashed.
By crashed i mean that it first reacted very slow then froze. After this, the screen went black (backlight on) an then dark.
no button could get me back to lockscreen.
then suddenly the phone rebootet.
this happened every time about one minute after booting my phone.
As the problem didn't seem to get away i decided to reflash it:
wipe SD
delete davlik cache
reseting to factory
and then istalling the same rom and gapps from zip
everything worked fine again, but after one day i got the same problem again.
what can I do to fix this?
I would appreciate any kind of help
and excuse me if this isn't the right forum (search also, didn't help)
sincerly,
PraetorAce
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
popthosegaskets said:
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
Click to expand...
Click to collapse
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
PraetorAce said:
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
Click to expand...
Click to collapse
You can try the nightly versions if the stable doesn't work for you.
Take out the boot.img inside the ROM zip and flash with fastboot. Then put ROM zip onto SD card and flash with CWM.
僕のLT18iから送られてきた
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
PraetorAce said:
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
Click to expand...
Click to collapse
Odin is for Samsung devices only. If CM9.1 doesn't work for you then you might want to try CM10.
僕のLT18iから送られてきた
By far the best forum is 4pda. A big thanks to forum member acbka aka asyan4ik
1. Eloquent
2. Phandroid
3. HTC Mania
4. Droid Sans
5. Android Hilfe
6. Frandroid
7. 4pda.ru MATE
Shendu and also for the P6
MIUI
LEWA OS
News
Unlock Codes
uppon2 said:
By far the best forum is Eloquent. Keep an eye on these 2 users 'fte9k' and 'kangvip' - I did try one of the roms out but it was all Chinese. I kept getting a constant system force close at the startup procedure sent in to bootloop. Be very careful when trying the non english roms! I do not want to hear anybody blaming me for a bricked phone.
1. Eloquent
2. Phandroid
3. HTC Mania
4. Droid Sans
5. Android Hilfe
6. Frandroid
7. MIUI
8. Unlock Codes
9. News
Click to expand...
Click to collapse
You can add a Russian forum 4pda.ru MATE
acbka said:
You can add a Russian forum 4pda.ru MATE
Click to expand...
Click to collapse
Added
I am about to try LEWA OS. I have always wanted to give this a shot but it was never available on any of my devices. I will report back
*EDIT* Look below for details
uppon2 said:
I am about to try LEWA OS. I have always wanted to give this a shot but it was never available on any of my devices. I will report back
*EDIT* I have changed my mind. I have taken a long time to setup my phone to be the way it is now and don't want to risk having to flash stock firmware again in order to fix a soft bricked phone, not that it usually worries me, it's just annoying trying to get everything perfect again (I don't rely on nandroid backups as even they aren't perfect_
Click to expand...
Click to collapse
you are wrong, backup through twrp 2.6.3.3 works perfectly! Before Recover to do
wipe - advanced wipe
-Wipe dalvik cache
-System
-Cache
-Custom Storage
-Date
restore you buckup -
reboot -
i restore stock b907 / pac man rom / my port fly ui (cm 10.1 joe.stone)
:good:
acbka said:
you are wrong, backup through twrp 2.6.3.3 works perfectly! Before Recover to do
wipe - advanced wipe
-Wipe dalvik cache
-System
-Cache
-Custom Storage
-Date
restore you buckup -
reboot -
i restore stock b907 / pac man rom / my port fly ui (cm 10.1 joe.stone)
:good:
Click to expand...
Click to collapse
I have been doing this for many years. I have goten to points of soft bricking where recovery is impossible to get in to and where I needed to enter download/bootloader modes. The only way to restore a nandroid is if I have backed it up to my computer beforehand, flashed a firmware in download/bootloader mode then re-root/unlock and flash a recovery again, transfer the nandroid to my device and hope the data has not been corrupted during the process between phone and computer. I have actually needed to do this several times and more than once the nandroid was not restorable.
MIUI V5
http://rom.miui.com/en/download/view/id/359370#top
I ended up flashing LEWA OS. Very fast and everything seems to be working fine for me. GPS is working better for me now than on stock, camera and HDR mode are great, speed is good. Wifi and Data is working flawlessly. Beautiful lockscreen and UI. All of the theming options seem to be working as well (for those familiar with MIUI etc.) The rom has a lot of visual tweaking and you can even kill the current running app by long pressing the back button *note* it does work, you just need to hold it for longer. You can also swipe in between the notifications and the switches tabs anywhere on the screen
The first time I flashed this it would not pass the boot animation. I ended up flashing B907 again and then running the bootloader unlock again (regardless of if I needed to or not) and then flashed the rom again. Step 1. Copy the LEWA rom zip and Gapps to your phone, then reboot in to recovery. 2. In TWRP; do an advanced wipe "cache, dalv, system, data" and then go to install and find the rom and install it. 3. reboot and make sure the rom loads all the way (do not bother setting up google account yet), once this happens reboot in to recovery again by holding power button and selecting reboot>recovery (inside of the rom this option is available), once you are there please install Gapps with TWRP, then reboot and enjoy.
Screenshots
Lockscreen Screenshots
Video showing off the rom (all of these features work on HAM)
uppon2 said:
I ended up flashing LEWA OS. Very fast and everything seems to be working fine for me, the only issue so far is I can not scroll left or right to select lockscreen shortcuts, I can only slide it down to unlock. Camera and HDR mode are great, speed is good. Wifi and Data is working flawlessly. Beautiful lockscreen and UI. All of the theming options seem to be working as well (for those familiar with MIUI etc.)
The first time I flashed this it would not pass the boot animation. I ended up flashing B907 again and then running the bootloader unlock again (regardless of if I needed to or not) and then flashed LEWA rom by extracted the files to a new folder and then running the Flash_All.bat from inside the folder. After the files have finished all I did was reboot and it worked this time.
Click to expand...
Click to collapse
Hi, You can put some screenshots of the ROM??
thanks.
elroysk said:
http://rom.miui.com/en/download/view/id/359370#top
Click to expand...
Click to collapse
Because of P6?
This ROM is 100% compatible with Mate?
I have not tried.
ErSergi said:
Hi, You can put some screenshots of the ROM??
thanks.
Click to expand...
Click to collapse
Here are some screen shots. (The navigation keys are like that by choice, remember I am using the Australian model so I only have 1gb of ram )
Some of the lockscreen which is actually live (I am using the BigBang theme)
elroysk said:
http://rom.miui.com/en/download/view/id/359370#top
Click to expand...
Click to collapse
hasbrone said:
Because of P6?
This ROM is 100% compatible with Mate?
Click to expand...
Click to collapse
If you look in the first post of my thread, you will see that MIUI is already listed but from a different download area and from a different author. If you scroll down you will actually find the file for Ascend Mate. I will tell you now though, the file name is the same as the P6 so I am assuming it is the same or they have used the P6 file and tweaked it. I am going to look at both files and give it a shot at running them today.
This is the file provided under the Huawei Ascend Mate
uppon2 said:
If you look in the first post of my thread, you will see that MIUI is already listed but from a different download area and from a different author. If you scroll down you will actually find the file for Ascend Mate. I will tell you now though, the file name is the same as the P6 so I am assuming it is the same or they have used the P6 file and tweaked it. I am going to look at both files and give it a shot at running them today.
This is the file provided under the Huawei Ascend Mate
Click to expand...
Click to collapse
I already installed this rom and it looks neat..
before you install make sure u replace the boot.img with ascend mates boot.img file. the one in the zip file is for P6.
Hi uppon2 , Hd video playback youtube in this ROM? works?
You can put the link in the forum, where you downloaded this ROM Lewa Os.
thanks!
I downloaded d zip...how to flash it
Sent from my HUAWEI MT1-U06
ErSergi said:
Hi uppon2 , Hd video playback youtube in this ROM? works?
You can put the link in the forum, where you downloaded this ROM Lewa Os.
thanks!
Click to expand...
Click to collapse
HD Playback is working fine for me with Youtube. You can get the file from the first post or follow my instructions below
shaun100689 said:
I downloaded d zip...how to flash it
Sent from my HUAWEI MT1-U06
Click to expand...
Click to collapse
I have already given instructions on how to flash the file and I will post them again.
The first time I flashed this it would not pass the boot animation. I ended up flashing B907 again and then running the bootloader unlock again (regardless of if I needed to or not) and then flashed LEWA rom by extracting the files to a new folder and then running the Flash_All.bat from inside the folder. After the files have finished all I did was reboot and it worked this time. I then installed Gapps after being certain that the rom would load
So is it necessity to unlock boot loader...?
Sent from my HUAWEI MT1-U06
Uppon2 , https://disk.yandex.com/public/?hash=UG0GbIYB6yTozqYOQtxz5U5g0Bf7ymAIfTr3ZqQyjg8=
I downloaded this ROM and no. bat file in order to install ...
as installed?
this link is correct, because I see this. bat file to install??
I think these instructions are not in this rom?????
The first time I flashed this it would not pass the boot animation. I ended up flashing B907 again and then running the bootloader unlock again (regardless of if I needed to or not) and then flashed LEWA rom by extracting the files to a new folder and then running the Flash_All.bat from inside the folder. After the files have finished all I did was reboot and it worked this time. I then installed Gapps after being certain that the rom would load
Q&A for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
axelander1 said:
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
Click to expand...
Click to collapse
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Deltadroid said:
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Click to expand...
Click to collapse
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
axelander1 said:
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
Click to expand...
Click to collapse
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Deltadroid said:
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Click to expand...
Click to collapse
this file takes a parameter, I suppose awifi070u-perf_defconfig is used (see the other make script make_awifi070u_defconfig.sh).
However this has CONFIG_IP_MULTICAST=y.
I somehow doubt that this is the config which is actually used for the official builds. If I understand http://wiki.cyanogenmod.org/w/Build_for_v500 correctly, the command "breakfast v500" would pull the kernel repo and triggers make for the kernel's .config file?
Yes. You can also create a local manifest to pull a specific repo without having to pull everything.
Example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cmhub" fetch="git://github.com/CyanogenMod/" review="review.cyanogenmod.com" />
<project path="device/lge/v500" name="android_device_lge_v500" remote="cmhub" />
</manifest>
Example Procedure:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
repo sync device/lge/v500
repo start my_fixed_branch device/lge/v500
cd device/lge/v500
<edit files>
git commit -a
repo upload device/lge/v500
---------- Post added at 12:23 AM ---------- Previous post was at 12:11 AM ----------
Just substitute "device" for "kernel" in the project path and name.
How do I know if I'm using hardware or software decoding for Netflix? No idea if I need your patch.
Also, I installed cm-12-20150226-NIGHTLY-v500.zip yesterday. Updated to cm-12-20150227-NIGHTLY-v500.zip with CyanDelta today, works like a charm. Thank you!
If you make a backup of /system/etc/media_codecs_google_video.xml then you can revert the patch. It only removes one line in that xml file so that adaptive playback is not an option for h264 decoding. The only difference is that hardware decoding should save on the battery. This patch was taken from slimRom and I need it for other devices, so I thought it would be worth testing for this device also.
Hi everyone, I am on 28\02 nightly and Google Now doesn t work, showing "Network error. Check your network connections".
Does anyone knows how to solve it?
It's working here. Either the Google services is temporarily down in your area or you need to install the correct version of gapps. The "Delta" gapps that I have posted in the development section are up to date and working.
cm12 crashes after flashing
Everytime I flash cm12 it fails. I get into the setup process, login to wifi' cyanogenmod, and google. I never get passed this. During setup I get messages that say "unfortunately there is a problem with music", then the same for camera. Then the screen stars flashing and eventually goes dark. The back key shows at the bottom, but the other two do not show. The back key is nonresponsive. I have to power down and get back to recovery and restore my cm11 backup.
When I got the gpad, it came with 20D, andI had to use the lgflashtool to get back to 4.2.2. (20A0. Then I rooted with stump and installed twrp using flashify. Then I was able to flash cm11 (m10, 11 and 12). Cm11 ran like a champ.
A couple of weeks ago I decided to flash a cm12 nightly and had the problem described above.
I have tried multiple combinations of steps to solve this problem: going back to 4.2.2, rooting and flashing cm12 from 4.2.2, I have tried 4.4.2. I have tried multiple versions of twrp and philz. I have wiped with and without wiping system. I have tried different versions of gapps-lp. I have tried different versions of the nightlies.
Every time I get the same result (which I think is the definition of insanity).
What is most frustrating is that I have another gpad that went from cm11 to cm12 with no problems. Worked the first time using the 0217 nightly,
So what am I doing wrong? Why am I having problems with cm12 after I flash it?
Thanks in advance. Xda has been a life saver since I got my first tablet, a viewsonic, a few years ago.
John
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Still can't set up CM12
Deltadroid said:
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Click to expand...
Click to collapse
Thanks for the suggestions. I first checked the camera.
While in CM11 I turned on the camera and took a picture. I also opened a terminal window and grepped both the OV and the S5K cameras. Nothing came back for OV. I did get stuff from S5k. So I assume the camera is the right one.
Then I did went into recovery, carefully wiped and formatted, and flashed CM12 and Gapps.
I am still getting the camera and music errors. Then the screen flashes to black and the it locks.
The bad news is that I cannot get back to recovery. It looks like I'm back to the lgflashtool.
I will try again from stock. But right now I think it is miller time.
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Are you sure you did wipe SYSTEM before flashing?
Still can't set up CM12
Deltadroid said:
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Click to expand...
Click to collapse
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
johnseidel said:
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
Click to expand...
Click to collapse
The reason your recovery failed is because your 20D firmware has an aboot.img that is not loki exploitable. After rooting, you will need to replace your aboot.img with the aboot.img from 10A firmware. This means you are keeping the 20D bootloader but only downgrading the 10A aboot.img so that you can use the loki tool to install a custom recovery. Flashify also needs a loki exploitable aboot.img (10A) to be installed before it can work and install a lokified recovery. The trick is to keep your new bootloader from 20D but only downgrade the aboot.img. There is a batch file in the development section that does this with a script using the dd command.
Okay.
20D is flashed and rooted.
V50020_aboot_twrp_v2 has been executed.
Flashify flashed TWRP 8.0.0.0 and rebooted.
I am assuming the next step is to flash CM12, but wanted to make sure. I've shot myself in the foot so many times I'm running out of toes.
Next, factory reset, and format /system. You could also format your internal sdcard, but it's not often necessary.
Finally, install latest nightly build of cm12. You can install gapps later.
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
Note, make sure you copy the files to your sdcard first if you plan on formatting the internal sdcard.
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.
include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? ( Subject to OEM's)
*
*We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
/
Palladium OS is not yet another ubiquitous os but a trendsetter of its own level. The Prime focus here
are on speed, stability and above all, its a community driven os where everyone can experience their ideas
without any limitations. All these is complemented by the Meteor Fall programme which are a series of OTA updates
which adds in new features and suggestions. So, now you know why its christened The Palladium OS.
Source
Palladium: PalladiumOS
Install Instructions
Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM
- Flash Gapps Zip file (Only for Vanilla variant)
- Reboot your device.
Downloads
ROM: sourceforge
GApps: NikGapps
Credits
- Google for AOSP
- LineageOS
- Project Fluid
- ShapeShift OS
- Pixel experience
- Project Streak
- Dot OS
- Octavi OS
- Bliss ROM
- AICP & POSP & Pixys Team for thread template idea
- Also many pro devlopers who all help us to bring this rom to you..
- Please let us know if we forgot to mention your name in credits..
AND TO THE PALLADIUM TEAM FOR THIS ROM
Build Author/Maintainer - Arokz Dpk
Device Name - Oneplus 5 and 5T
Device Codename -dumpling and cheeseburger
Kernel Source - https://github.com/ArokzDP/kernel_oneplus_msm8998
ROM Status - Unofficial
Android Version - 11.0
ROM Version - v1.3
thanksssssss
Wow! Thank you, is it my birthday? I will flash over the next couple of days. Thank you once again.
I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.
Drhedphuk said:
I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.
Click to expand...
Click to collapse
Am on the same gapps version and it booted jus fine for me. If the zip is corrupted u wont be getting successful flash message. Maybe try again afterwards when free. Also happy that u tried it.
Arokia said:
Am on the same gapps version and it booted jus fine for me. If the zip is corrupted u wont be getting successful flash message. Maybe try again afterwards when free. Also happy that u tried it.
Click to expand...
Click to collapse
I also guess the boot loop could be due to encrypted or decrypted thing. Try with f2fs instead...
Arokia said:
I also guess the boot loop could be due to encrypted or decrypted thing. Try with f2fs instead...
Click to expand...
Click to collapse
Okay, thank you for the advice. I will let you know.
Added to the OnePlus 5 Index Thread here.
Drhedphuk said:
I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.
Click to expand...
Click to collapse
Happened to me as well but i got it fixed by flashing the vanilla rom first and then let it boot, after that i rebooted back to the recovery and flashed gapps. Worked just fine. Hope this will help anyone having a similar issue
Any way to get rid of the home buttons and have a home bar instead ? Couldn't find any option like Derpfest has. Props for the great rom, I'm loving it and the battery life is just incredible.
Jalef said:
Happened to me as well but i got it fixed by flashing the vanilla rom first and then let it boot, after that i rebooted back to the recovery and flashed gapps. Worked just fine. Hope this will help anyone having a similar issue
Click to expand...
Click to collapse
Thank you very much. Which gapps package did you flash?
No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.
Drhedphuk said:
No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.
Click to expand...
Click to collapse
Make sure you have the zip files anywhere in your internal storage. But not inside a folder within the internal storage. Because whenever you wipe data,system,cache and dalvik it will also wipe the downloaded files inside the download folder.
Jalef said:
Make sure you have the zip files anywhere in your internal storage. But not inside a folder within the internal storage. Because whenever you wipe data,system,cache and dalvik it will also wipe the downloaded files inside the download folder.
Click to expand...
Click to collapse
I kept them in the same place that I kept Pixel ROM and was able to flash that afterwards. Plus the APK's that I had within that folder and the Majisk zip were fine too. Weird issue.
Drhedphuk said:
I kept them in the same place that I kept Pixel ROM and was able to flash that afterwards. Plus the APK's that I had within that folder and the Majisk zip were fine too. Weird issue.
Click to expand...
Click to collapse
That's actually weird because when i flashed on my end everything got deleted from there
Drhedphuk said:
No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.
Click to expand...
Click to collapse
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package.
KeinePanik said:
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package
Click to expand...
Click to collapse
KeinePanik said:
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package.
Click to expand...
Click to collapse
I was wondering whether my codeworx Twrp was maybe outdated. Can I flash Orange fox over the top of codeworx with a zip file?
Edit: Flashed Orange Fox, I'll try again.
Yesss!! Flashed it! It was obviously the recovery version that I was running. On the suggestion of @KeinePanik I flashed Orange Fox recovery and voila! (Thank you my friend)
My apologies to the developer and everyone else for flooding this thread with my issues.
I have been running the app for about 5 hours now and can report that it is really smooth, great battery life and some nice UI extras. Many thanks to the dev, will it go official?
Current release has june sec. patch or shall I wait for the upcoming update if it around the corner ???
m.omdaa said:
Current release has june sec. patch or shall I wait for the upcoming update if it around the corner ???
Click to expand...
Click to collapse
Security patch is May 5.