Can I build OmniRom with CWM? - Omni Q&A

Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.

All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.

Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.

PonsAsinorem said:
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
Click to expand...
Click to collapse
Don't mind me...I forgot I was in the Omni boards and not my local device sub-forum

lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.

Entropy512 said:
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Click to expand...
Click to collapse
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.

Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?

Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
I've been flashing OmniROM on my Note II since the very first day only using TWRP. Before that not a single nightly zip of CM 10.1/2, PA or PAC was a problem.
Sent from my GT-N7100 using Tapatalk

lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
Today I installed OMNI ROM 4.4.2 on Galaxy Note with CM 10.1 + CWM (6.0. ...)
- it works Ok.
Generally I followed the "Installing Omni on your device" instruction at docs.omnirom.org
- excluding TWRP installing
- I downloaded Google Apps for Android 4.4 from CyanogenMod site (gapps-kk-20140105-signed.zip)

Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
Only thing I can think of is TWRP is out of date and needs updating for that device, or there are updated TWRP builds and you're not running one.
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
What does that have to do with this thread?
libm compiles just fine as it is in omni - if it didn't, then none of our nightlies would build

lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.

dibblebill said:
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
Click to expand...
Click to collapse
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?

lozohcum said:
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
Click to expand...
Click to collapse
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.

dibblebill said:
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
Click to expand...
Click to collapse
No problem. Thanks for replying, it helped me.
Once the first build is finished I'm going to change recovery.

lozohcum said:
No problem. Thanks for replying, it helped me.
Click to expand...
Click to collapse
If setting up the local_manifest gives issues, let me know- I can try to sort one out for you. I've replaced packages like Calculator, but never the recovery.

Related

Latest nightly kernel 201423110

Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
geowolf1000 said:
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
Click to expand...
Click to collapse
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Just update to 28
geowolf1000 said:
Just update to 28
Click to expand...
Click to collapse
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
bingbinghaha said:
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
Click to expand...
Click to collapse
Let me guess, you were coming back to this kernel from Franco?
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
zaphodbeeb said:
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Click to expand...
Click to collapse
I can flash it or someone has a kernel update to the last nightly?
inscythe said:
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
Click to expand...
Click to collapse
I will try
I am doing this for my self but i want to share with xda friends
Thread update to 31
Amazing improvement to touchscreen
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
reyscott1968 said:
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
Click to expand...
Click to collapse
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
My wifi broke with this as well. Running completely stock 38R.
Can you share Source code please?
CrunchSA said:
My wifi broke with this as well. Running completely stock 38R.
Click to expand...
Click to collapse
Have you backup?
Just restore only system from revovery
Yeah, did that. Just reporting here that it was broken as an FYI.
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
Would this flash over Franco fine? Thanks in advance.
geowolf1000 said:
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
Click to expand...
Click to collapse
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
inscythe said:
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
Click to expand...
Click to collapse
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
geowolf1000 said:
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
Click to expand...
Click to collapse
If you see other custom kernel pages, usually they would have different versions for CM11 and CM11S... So I would assume that there are inherent differences between them. But if it is working fine for you, then great! Maybe I'll try it myself too
runderekrun said:
Would this flash over Franco fine? Thanks in advance.
Click to expand...
Click to collapse
Reflash (dirty) your ROM first to restore WiFi firmware

Galaxy S4 CyanogenMod?

Guys is there a Official version of CyanogenMode for Galaxy s4 i9505 ? what is it? my phone is very laggy with the stock rom :/
The Cyanogenmod website lists the devices the ROM works on, so why not go there and, oh I don't know, look?
Demitha said:
Guys is there a Official version of CyanogenMode for Galaxy s4 i9505 ? what is it? my phone is very laggy with the stock rom :/
Click to expand...
Click to collapse
Yes, there is. You can fin it in the Original Android Development section. The maintainer is AntaresOne. He has 2 versions. One is the official nighlies and the other is an optimized version.
You can go for either one or, you can choose one of the other roms based on CM12 or CM12.1.
GDReaper said:
Yes, there is. You can fin it in the Original Android Development section. The maintainer is AntaresOne. He has 2 versions. One is the official nighlies and the other is an optimized version.
You can go for either one or, you can choose one of the other roms based on CM12 or CM12.1.
Click to expand...
Click to collapse
Thank you very much fro the helpful answer , are you using any of those ROM's? what the most stable one? . Thanks again.
Strephon Alkhalikoi said:
The Cyanogenmod website lists the devices the ROM works on, so why not go there and, oh I don't know, look?
Click to expand...
Click to collapse
if you cant help just stay away, guess you don't have better things to do.
Demitha said:
if you cant help just stay away, guess you don't have better things to do.
Click to expand...
Click to collapse
He just not prepared to do your work for you. Your op was incredibly lazy. You could have saved time by just looking first, either on cm website or in the development sections in this forum
DSA said:
He just not prepared to do your work for you. Your op was incredibly lazy. You could have saved time by just looking first, either on cm website or in the development sections in this forum
Click to expand...
Click to collapse
AGAIN, If he don't wanna do anything to help just stay the away, No need to waste my time with trash. im very new to this, i wouldn't know to search for a CM forum.
Demitha said:
AGAIN, If he don't wanna do anything to help just stay the away, No need to waste my time with trash. im very new to this, i wouldn't know to search for a CM forum.
Click to expand...
Click to collapse
Just to clarify, you don't know how to type 'CyanogenMod' into a Google search bar but are competent at flashing ROMs?
DSA said:
Just to clarify, you don't know how to type 'CyanogenMod' into a Google search bar but are competent at flashing ROMs?
Click to expand...
Click to collapse
My next thread would be to get help for flashing a ROM.
Why would you create a thread? There's hundreds for that exact thing already..I think some reading may be in order
DSA said:
Why would you create a thread? There's hundreds for that exact thing already..I think some reading may be in order
Click to expand...
Click to collapse
Good point , i will search before make a thread for that.
Demitha said:
if you cant help just stay away, guess you don't have better things to do.
Click to expand...
Click to collapse
It's because this forum is not a helpdesk. It takes 1 second to type "Cyanogenmod I9505" in Google or in the xda searchbar. Most developers don't like these kind of people in their rom threads but it lowers the quality of discussion dramatically.
It's the same for the question you asked in the CM optimized topic. It's not a helpdesk and it has nothing to do with that particularly rom. You can easily test which rom is more stable for you by flashing it.
Lennyz1988 said:
It's because this forum is not a helpdesk. It takes 1 second to type "Cyanogenmod I9505" in Google or in the xda searchbar. Most developers don't like these kind of people in their rom threads but it lowers the quality of discussion dramatically.
It's the same for the question you asked in the CM optimized topic. It's not a helpdesk and it has nothing to do with that particularly rom. You can easily test which rom is more stable for you by flashing it.
Click to expand...
Click to collapse
ok i understand the your point, i will avoid these kind of threads again, thanks for explaining rather than trying to sound like a asshole :good:
Demitha said:
Thank you very much fro the helpful answer , are you using any of those ROM's? what the most stable one? . Thanks again.
Click to expand...
Click to collapse
My first rom was the 5.0.1 GPE rom, then tried CM12 Optimized builds, SaberMod CM12 and 12.1 builds and I am now currently running Resurrection Remix rom.
The most stable from the bunch (for me) was the GPE rom. The fastest and smoothest (for me) seems to be Resurrection Remix.
All of them ran stable for me, with no bugs or serious problems that could not be solved.
CM12 has reached a final version. The developer works on 12.1 now. CM12.1 nighlies is the most updated of the bunch.
Now, for the flashing. Before flashng you might want to backup your stuff. This requires root. You can use CF-Auto-Root to do it. Warning: This will trip knox.
Just google search "root s4 cf auto root" and follow the instructions in the thread. CF-Auto-Root does not work with all s4 variants, so make sure you have the right one.
If you don't want to backup anything, then you can just skip to installing a custom recovery.
There are 3 to choose from: CWM, TWRP or PhilZ Touch recovery.
I use TWRP. You should be able to flash it with Odin. Google on how to flash a custom recovery on the s4. Even if they are for different android versions, it's basically the same process.
GDReaper said:
My first rom was the 5.0.1 GPE rom, then tried CM12 Optimized builds, SaberMod CM12 and 12.1 builds and I am now currently running Resurrection Remix rom.
The most stable from the bunch (for me) was the GPE rom. The fastest and smoothest (for me) seems to be Resurrection Remix.
All of them ran stable for me, with no bugs or serious problems that could not be solved.
CM12 has reached a final version. The developer works on 12.1 now. CM12.1 nighlies is the most updated of the bunch.
Now, for the flashing. Before flashng you might want to backup your stuff. This requires root. You can use CF-Auto-Root to do it. Warning: This will trip knox.
Just google search "root s4 cf auto root" and follow the instructions in the thread. CF-Auto-Root does not work with all s4 variants, so make sure you have the right one.
If you don't want to backup anything, then you can just skip to installing a custom recovery.
There are 3 to choose from: CWM, TWRP or PhilZ Touch recovery.
I use TWRP. You should be able to flash it with Odin. Google on how to flash a custom recovery on the s4. Even if they are for different android versions, it's basically the same process.
Click to expand...
Click to collapse
This is the answer i have been looking for :angel: , i will try the Resurrection Remix , Thanks again.
Demitha said:
This is the answer i have been looking for :angel: , i will try the Resurrection Remix , Thanks again.
Click to expand...
Click to collapse
Use it with KT Kernel. It gives you lots of customizability. You may have a green tinting at first, but this can be easily fixed. Settings > Display > LiveDisplay > Color Calibration and set all values there to 50% and hit Ok. Then just change the brightness so the changes take effect. Otherwise you will have to reboot.
Or you can use it with the default kernel.
GDReaper said:
Use it with KT Kernel. It gives you lots of customizability. You may have a green tinting at first, but this can be easily fixed. Settings > Display > LiveDisplay > Color Calibration and set all values there to 50% and hit Ok. Then just change the brightness so the changes take effect. Otherwise you will have to reboot.
Or you can use it with the default kernel.
Click to expand...
Click to collapse
Awesome, Thanks

[ROM] [DISCUSSION] Official Mokee Rom Releases [6.0.1] [GT-I9100]

First I want to say I didn't build this rom, or have anything to do with Mokee Open Source. Any bug reports or feature requests should be directed to Mokee developers.
I only started this thread to provide a link to the roms, as they are not available on xda until now, and a lot of users may not be aware they are still around.
Personally I have found this rom to be very stable, with some nice features.
Links:
Mokee Official Site
Mokee on Google+
Changelog
Bug Tracker
Official Rom Releases
http://download.mokeedev.com/?device=i9100
Recommended Gapps
Open Gapps
Warning(particularly for MM builds): If you try to flash gapps, you will probably find it won't fit on the stock /system partition. In this case you will need to repatition - Repartitioning guide.
Make sure you choose a pit file that increases /system and not just /data(eg, I91001GB_4GB.pit)
Alternatively use Lanchon's re-pitting tool if you want to avoid losing your data
If you want to donate to Mokee and make their life a bit easier(donations will go towards bandwidth etc),
you can donate HERE
Instructions
1. Wipe data/factory reset(from KK compatible recovery)
2. Format /system
3. Flash rom
4. Flash gapps(optional)
5. Flash isorec recovery(for MM, see below), you only need to do this once
6. Reboot
Credits
- Mokee Developers
- CyanogenMod
- AOSP
- SlimRoms
- OmniRoms
Note: Now that Marshmallow(6.x.x) has been released, a warning for anyone flashing these latest nightlies. The kernel(isorec CM kernel) comes bundled with CM recovery, which is more or less useless. If you want a working recovery, you will need to flash the rom, followed by gapps(if you want play store), followed by an isorec recovery from HERE
Be sure to flash either CWM or TWRP for i9100. It is obvious from the name of the file.
And read about Isorec if you are not sure.
Thank you to @Troubadour666 for the Youtube review
Thank you @noppy22 for starting this thread. I had been downloading the ROM from G+ but the added benefit of a thread here on xda means that you have fellow S2 users to discuss problems etc with. Thank you again mate.
downloading....
thx for share
Thank you for the rom....downloading :good:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
Mokee has already got my twrp recovery as I supplied it to them back in june 2015
@arnab Thank you.
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Edit: I tried the last trim/twrp kernel and got bootloop on 160102 build....
noppy22 said:
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Click to expand...
Click to collapse
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Drhedphuk said:
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Click to expand...
Click to collapse
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Troubadour666 said:
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Click to expand...
Click to collapse
Xpose will not flash for me.
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
noppy22 said:
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
Click to expand...
Click to collapse
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
souler456 said:
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
Click to expand...
Click to collapse
Well, no. The reports of freezing with his last release stopped me from trying that. BTW the GeneSys kernel(.tar) that was released is the same as the kernel in DU 9.8, but for me the DragonKernel I tried is the last "AOSP" kernel I found to be stable
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
It's basically Cyanogen 12.1 with a couple of extra features like wakelock blocker. My own opinion, I think it is a lot smoother than stock Cyanogen.
To correct my earlier post. I reflashed the Rom and flashed xposed during the flash process and it flashed without any problems.
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
I added some screenshots in the OP. Hope this gives you an idea of features....
noppy22 said:
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Click to expand...
Click to collapse
Great ROM! I repartitioned my phone using 1/4G pit and this ROM works very nice. Thanks devs!
Xposed may not be installed in MoKee RELEASE version cuz they said they odexed the ROM.
Sent from my GT-I9100 using XDA Free mobile app

temp - Nexus 7 - unofficial - lineage 14.1

Lineage 14.1 UNOFFICIAL for Nexus 7 WiFi (flo) and LTE (deb) by @hazzer.
NEW thread by the rom developer hazzer.
[ROM][DEB|FLO][7.1.1][UNOFFICIAL] LineageOS/CyanogenMod 14.1 Nightlies
https://forum.xda-developers.com/ne...lineageos-cyanogenmod-14-1-nightlies-t3534440
Download links and more can be found in the new thread.
Newest builds by @hazzer
LTE (deb)
WiFi (flo)
- Available in the developer's thread.
https://forum.xda-developers.com/ne...lineageos-cyanogenmod-14-1-nightlies-t3534440
Edit : Updated to the developers current thread.
Running a OK on my device since yesterday. Thanks for this.
Sent from my Nexus 7 using Tapatalk
Are we going to see more builds soon? Any word on a fix for Google Voice SMS in Hangouts crashing?
----- other links -----
Nexus 7 [2013] (Wi-Fi) "razor/flo"
Factory Stock rom MOB30X - 6.0.1 (Google AOSP)
https://dl.google.com/dl/android/aosp/razor-mob30x-factory-52684dff.zip
TWRP (TeamWin Recovery Project)
https://twrp.me/devices/asusnexus72013wifi.html
CM device info - Thanks to web archive -
http://web.archive.org/web/20161224193325/https://wiki.cyanogenmod.org/w/Flo_Info
Nexus 7 [2013] (Mobile - LTE) "razorg/deb"
Factory Stock rom MOB30X - 6.0.1 (Google AOSP)
https://dl.google.com/dl/android/aosp/razorg-mob30x-factory-10b7ca08.zip
TWRP (TeamWin Recovery Project)
https://twrp.me/devices/asusnexus72013lte.html
CM device info - Thank you to web archive -
http://web.archive.org/web/20161224193412/https://wiki.cyanogenmod.org/w/Deb_Info
I'm gonna try and get a thread up in the Original Dev area this afternoon. Life has been quite busy lately (Uni interviews are dominating my life ). Has anyone got any problems they want to report?
Sorry for the lack of builds; my autobuild script has been a little buggy as of late. Think they're fixed now
Thanks to @ipdev for making this thread also
There's mention on the download site that "At the moment, this is all completely stock LineageOS code, so will encrypt your device". Is this true for the Nexus 7? Thanks.
ninja_rancher said:
There's mention on the download site that "At the moment, this is all completely stock LineageOS code, so will encrypt your device". Is this true for the Nexus 7? Thanks.
Click to expand...
Click to collapse
No. It doesn't encrypt by default
Trying to get it flashed again now. First attempt said the file was corrupt. Getting the MD5 this time to make sure it works out
hazzer said:
No. It does encrypt by default
Click to expand...
Click to collapse
Wait...you said "no" and then "it does encrypt". I'm slightly confused. Will my tablet be encrypted if I install LineageOS? I'm currently running CM 14.1 and it did not require any encryption.
ninja_rancher said:
Wait...you said "no" and then "it does encrypt". I'm slightly confused. Will my tablet be encrypted if I install LineageOS? I'm currently running CM 14.1 and it did not require any encryption.
Click to expand...
Click to collapse
I apologise, I mistyped my post. It does not encrypt by defauly
Deleted
@hazzer do you know anything about the bug I asked about above?
Link_of_Hyrule said:
Are we going to see more builds soon? Any word on a fix for Google Voice SMS in Hangouts crashing?
Click to expand...
Click to collapse
This sounds like an OpenGapps issue. I don't actually have Google Voice, so I can't replicate the issue. Sorry :-/
hazzer said:
This sounds like an OpenGapps issue. I don't actually have Google Voice, so I can't replicate the issue. Sorry :-/
Click to expand...
Click to collapse
It works on my OnePlus One and on my Nexus 7 in aosp builds so it's hard to say.
Hey @hazzer, thanks for doing this. Quick question. installing thus unofficial version, Will it receive future updates from the official version when it comes out? Will the latest CyanogenMod be automatically updated to Lineage OS?
Beat regards and thanks again.
Can't wait to flash this rom! If I have the latest nightly available for CM, is it OK if I just flash this rom without wiping data?
Sent from my Nexus 7 using XDA-Developers Legacy app
xXLosstarotXx said:
Can't wait to flash this rom! If I have the latest nightly available for CM, is it OK if I just flash this rom without wiping data?
Click to expand...
Click to collapse
Not sure if I would recommend it but, it did work. (Dirty flash.)
I would recommend making a backup before you try. (Just in case.)
Sent from my Nexus 7 using XDA Labs
Note :
My primary one (clean install) seems to run smoother that my secondary (dirty flashed over cm.)
https://download.lineageos.org well isn't that just lovely. Almost everything is back up https://status.lineageos.org
fbrubbo said:
Hey @hazzer, thanks for doing this. Quick question. installing thus unofficial version, Will it receive future updates from the official version when it comes out? Will the latest CyanogenMod be automatically updated to Lineage OS?
Beat regards and thanks again.
Click to expand...
Click to collapse
Yes, you can just dirty flash to the LineageOS official nightlies. The latest CM won't be automatically updated, you will have to flash the first LineageOS build, and then you'll get updates.

Lineage OS 13 for *KKBL*

There's an unofficial build of Lineage OS 13 for KKBL available in the Razr HD section. As far as I know, this is the first build of Android 6.x or above that has been released on KKBL (which means 3.4.x kernel). So, two questions.
How many and what changes are required to get this working on XT907?
Has anyone already attempted this (and would like to provide feedback)?
@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...
rahimali said:
@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...
Click to expand...
Click to collapse
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907
DiamondJohn said:
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907
Click to expand...
Click to collapse
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
although i wouldn't know what to do with it since i'm no dev. you think you could somehow port the xt92x build to xt90x / msm_moto8960 devices?
rahimali said:
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
Click to expand...
Click to collapse
I have assumed that the source and the dest are both msm8960 devices, bo9th on the same level/ver of bootloader, and therefore this reads as a shared code path traversed by both devices, so its already taken care of (in both). You are looking for DIFFERENCES in the code path.
PS: the other thing you will need to modify is the "updater-script" (in particular the first line) and the build.props (it doesn't normally flash from the zip without extra instructions, even though "its there"). I have personally changed the first line of the updater script and then copied the firmware files and an updated build.prop within TWRP before my first boot for quick checks. Just use the set permissions to 755 for safety on each file as well (for testing)
I have been trying to build crDroid for xt907_JBBL, but have been having issues. Today I thought of upgrading to the KKBL, which made me then search and not find, a suitable TWRP (ie >= v3.x)
is there a xt907_KKBL TWRP >=3.x? or would I have to build one?
DiamondJohn said:
is there a xt907_KKBL TWRP >=3.x?
Click to expand...
Click to collapse
No. The last is 2.8.6
Shmaks said:
No. The last is 2.8.6
Click to expand...
Click to collapse
Can that flash Nougat ROM's?
DiamondJohn said:
Can that flash Nougat ROM's?
Click to expand...
Click to collapse
Who knows. The last custom rom for kkbl is cm12 and 2.8.6 flash it, so there is no way to check
Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716
DiamondJohn said:
Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716
Click to expand...
Click to collapse
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?
Shmaks said:
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?
Click to expand...
Click to collapse
I am trying to build crDroid v3.6 (ie 7.1.2), however for my JBBL its having numerous FC's I do have a zip file which would enable me to upgrade to KKBL which would make it interesting to see if a KKBL version is more stable. IF I could also SAFELY go back to JBBL I had a Moto X and accidently (by accepting an OTA) downgraded my bootloader and that caused a hard brick on the device, so I am a little cautious to say the least, as it is my daily.
I am also just downloading the device tree for an xt907 KKBL on my build machine and see if it can build a LineageOS 13. I'll let you know how it goes, and probably paste up a link for others to test if it succeeds to build since my device is JBBL
=============== edit =============
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL
DiamondJohn said:
IF I could also SAFELY go back to JBBL
Click to expand...
Click to collapse
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
DiamondJohn said:
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL
Click to expand...
Click to collapse
Cool, hope for a successful experience
Shmaks said:
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
Click to expand...
Click to collapse
Thanks, the links I found for these zips were all dead or required registration.
Shmaks said:
Cool, hope for a successful experience
Click to expand...
Click to collapse
Its at 4 % .., step 1512 of 34456 ... 5% and I'm off to bed, its late here. The big problem is uploading it to a host, its normally an over night job or at least a a few hours. So it may be two nights before its up somewhere to download IF it succeeds in da build.
9%....
11%...
DiamondJohn said:
Thanks, the links I found for these zips were all dead or required registration.
Click to expand...
Click to collapse
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a
@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...
DiamondJohn said:
11%...
Click to expand...
Click to collapse
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Shmaks said:
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a
Click to expand...
Click to collapse
rahimali said:
@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Click to expand...
Click to collapse
No need, because I have a an xt905, it has Australian frequencies, which means Australian specific modem. These zips were only for me to confirm the steps I plan to take when flashing manually using fastboot, from an Australian specific (ie xt905) Image file. so, one example is enough. Thanks anyway.
rahimali said:
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Click to expand...
Click to collapse
I don't know. I know on previous version of Android, new versions of ROM zip files took advantages of features not in older TWRP images, and TWRP 2.8.x is getting old.
There is little drive in me building, uploading and posting a KKBL ROM post, if no-one else is testing it for me ie save me the hassle of flashing KKBL only to find TWRP &/OR ROM does not work. Yes, its all about me
rahimali said:
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...
Click to expand...
Click to collapse
More than enough. I have built a nougat ResurectionRemix and a crDroid (available HERE for testing; JBBL only) and it felt just as snappy as Marshmallow. Also, on my daily, I am running LOS13.0 with the Nougat Kernel, overclocked to 1.98GHz. ie we can also get a small/tiny boost easily with OC; the feature is built into the kernel but simply switched off in the LOS official builds.
DiamondJohn said:
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Click to expand...
Click to collapse
Can't wait
Shmaks said:
Can't wait
Click to expand...
Click to collapse
have you tried TWRP for KKBL? And you may be waiting for a dud however upload is at 53%
DiamondJohn said:
have you tried TWRP for KKBL?
Click to expand...
Click to collapse
Yes, it works!

Categories

Resources