Database Info

how to fix cm12 modem update and problems thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
TOP TIP "For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed." Thanks go to tobitege for this.

zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
+1. I also flashed the latest official CM nightly, booted it and checked if everything was working and then flashed the latest unofficial Temasek's rom. Everything works fine.
Cheers

@zaphodbeeb: thanks for having created this!
This morning I tested an extended version of the CM-12 flashable zip containing more partitions of the current nightlies.
First test brought me a jackpot in that it flashed without an error message, but soft bricked my phone (black screen, no adb nor fastboot), but power button rebooted in a special mode "HUSB_BULCK" (viewable in device manager). Takin' up the challenge, so after plenty of searching/reading and multiple tries to install the right drivers, I got it going through Color OS installation with special phone flashing tool, then flashing X44 again, unlocking, custom recovery+rooting... that was (deserved) fun!!
Though in the first moments it scared me s***tless!
Long story short, totally agree to just flashing the full nightly and directly clean on top any LP rom you want, if you want to be sure to have it right.

FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.

cam30era said:
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
Click to expand...
Click to collapse
I dirty flashed SlimSaber-bacon-5.0.2-20150110 build on top of SlimSaber-bacon-5.0.2-20150102 and then flashed alpha modem everything works fine.

zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!

That weird baseband version is the correct one, no worries.

radium22 said:
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
Click to expand...
Click to collapse
Good idea. Done. Now this really is the end of my contribution on this subject.

zaphodbeeb said:
Good idea. Done. Now this really is the end of my contribution on this subject.
Click to expand...
Click to collapse
So first flash the 3rd zip (cm12 nightly)
Then dirty flash the main Rom or whats the next step?
Thank you

The full nightly should be flashed first, then wipe clean in recovery and install your actual rom (or restore).

So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..

losthilien said:
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
Click to expand...
Click to collapse
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon

I went for number 3. Did a backup of my temasek ROM. Did a full wipe and installed cm nightly. Had full signal and thought great, this is the right modem. Restored my temasek and signal is gone again.
Any idea why? Did I restore too much of my temasek? Boot, system and data.
Thanks

It might just need another reboot after initial restore to reconnect.

I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.

VQ30DE said:
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
Click to expand...
Click to collapse
Not sure what to tell you. I have no WiFi problems. SlimLP ROM

So I just recovered from a hard brick with a dead battery.... it was brutal. I'm looking to do things more carefully going forward. I'd like to keep CM11S as primary. But obviously I want lollipop asap. If I backup CM11S nandroid... wipe clean, flash CM12 nightly for the modem and such, and then clean wipe and restore CM11S to primary from nandroid... will the modem changes that CM12 nightly made persist? I'd like that.... then I could flash some lollipop roms as secondaries and benefit from the modem changes that cm12 made?

The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.

tobitege said:
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
Click to expand...
Click to collapse
Top Tip man. I like.:good: I'll include in the OP.

timmaaa said:
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
Click to expand...
Click to collapse
You will notice the subtle message added to my sig also, using simple large letters for those with limited reading abilities.

[Discontinued] | CyanogenMod 13.0 | Android 6.0.x Marshmallow | Korean Galaxy S5

CyanogenMod is officially dead... so, this project is also discontinued. The web links to ROMs may not be available anymore. Please do not expect any replays from me on this thread. Thanks for all the support. You may try LineageOS, the successor of CyanogenMod, as an alternative.
Here are some useful links
LineageOS
LineageOS kltekor
LineageOS XDA thread for all the klte variants
These are official CyanogenMod-13.0 (Android 6.0.x Marshmallow) builds originally developed for the international S5 (klte) with modified boot.img specially designed for Korean Galaxy S5 variants. Team CyanogenMod deserves all the credits for developing this wonderful ROM.
/* Warning */
Warranty of your device is now void.
I am not responsible for any damage to your device. Everything you are doing on your mobile is on your own risk. Please don’t point your finger at me in case you brick your device or lost SD card.
The boot.img file is specially designed for Korean Galaxy S5 SM-G900S/K/L (klteskt – kltektt - kltelgt). Do not try to flash this file on any other S5 variants (and also other devices).
The ROM alone (without the provided modified boot.img) only supports the international variant SM-G900F (klte).
/* Supported devices */
Samsung Galaxy S5 SM-G900S (klteskt): tested
Samsung Galaxy S5 SM-G900L (kltelgt): tested
Samsung Galaxy S5 SM-G900K (kltektt): tested (thanks to @Cm_RoX)
/* Requirements */
Samsung Galaxy S5 SM-G900S/K/L (klteskt – kltelgt -kltektt) device with more than 80% battery charged.
Windows PC/Laptop
ODIN software (for Rooting and flashing Custom Recovery)
A high quality USB cable
/* Downloads */
CyanogenMod 13.0 for klte
Google apps (GAPPS) for CyanogenMod 13.0 (open GAPPS / A-GAPPS).
cm-13.0 boot.img
Rooting
SM-G900S (klteskt)
SM-G900L (kltelgt)
SM-G900K (kltektt)
TWRP Recovery
/* Recommendations */
Back up your contacts, photos and any other data that you considered as valuable.
Probably you can make a Nandroid backup (if you wish to back up your present operating system along with all the data including apps).
/* Important */
You can use official ROM updates from CyanogenMod. However, it is necessary to re-flash the modified boot.img after each update to avoid boot failure.
The modified boot.img files will be updated and posted in this thread in a regular basis (please see second post).
/* Installation */
1. Root your device
2. Install TWRP recovery
3. Wipe data/factory reset
4. Flash ROM
5. Flash GAPPS
6. Flash cm-13.0 boot.img (important for Korean Galaxy S5)
7. Wipe Cache/Dalvik Cache
8. Reboot
/* Known Issues */
1. No important bug other than some issues related with ‘Media audio’ and ‘Phone call audio’. (Fixed in SM-G900S and L: not conformed in SM-G900K)
2. Please report if you find bugs
I appreciate the suggestions and fixes for bugs.
/* Screenshots */
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/* Acknowledgements */
CyanogenMod (for this wonderful ROM)
Team Win Recovery Project
Our Korean Galaxy S5 Facebook group member’s
Chainfire (for CF-Auto Root)
Ljzyal (for fingerprint lock)
Many other XDA developers
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based on: CyanogenMod
Boot-loader: Lollipop
Created: March 17, 2016

Updates
/* Updates */
----------------------------------- -----------------------------------
Boot.img version ------------------------------------ Date
----------------------------------- -----------------------------------
cm-13.0_boot.img for kltexxx -------------------- 2016-07-17
----------------------------------- -----------------------------------

marvelous its functionnaly my korean s5
After the update its important dont forgoten flash cm-13.0_boot_img_SM_G900S_K_L

Yes... It is important to flash that custom boot.img... Otherwise, it will not boot on Korean S5

sunilpaulmathew, where u find update boot.img?

syapk said:
sunilpaulmathew, where u find update boot.img?
Click to expand...
Click to collapse
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.

unlocked verizon s5, using t-mobile sim card.. need help rooting and updating
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow

ilovemyhoohaw said:
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow
Click to expand...
Click to collapse
Unfortunately, SM-G900V is not ab officially supported device of cm-13.0 (Marshmallow). Rooting guides are however available. If you are really like to try marshmallow, try this unofficial build (select the unified version). Since ur device is very similar to SM-G900F (klte), the recovery (like twrp) and custom ROMs for klte variant might work on ur device. But not guarantied. So, please do everything in your own risk. No one else will take the responsibility of any damage caused to ur device while doing these experiments. I recommend you to back-up every valuable data from mobile and download the stock ROM of your device (from sammobiles) before starting the experiments. Good luck.

sunilpaulmathew said:
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.
Click to expand...
Click to collapse
wwooww, Can you explain how to make this?

syapk said:
wwooww, Can you explain how to make this?
Click to expand...
Click to collapse
It is basically easy in Linux. Download mkbootimg from here. 1) Decompress the stock and cm-13 boot.img (check read me file for the commands). 2) Replace the device tree file of the cm boot.img with the file from stock boot.img. 3) repack and flash into device.

greats !!
thanks ^^

Root and erro for device sm-g900s
hello, xda and chainfire first congratulate you all for great works in molhoramentos developments and to structure our plataforna android! recently bought a galaxy galaxy sm-g900s of a friend who went to korea I am Brazilian and I have residence in Rio de Janeiro and see what by Brazilian forum è not given much value to ess magnifico device what in my opinion is better what Brazilian version sm-g900m and I perdir a big favor '' xda and chainfire family. '' which take a little but sevirços this magnificent galaxy s5 device sm-g900s thank you in advance! now let my problem recetemente did root in my sm-g900s with CF-Auto-Root first time it worked perfectly but after a day just vanished and saying that recently your device has been updated to 5.0 porfavor redo the root and asked also update '' su binary '' but how? I am currently with some financial difficulties and can not contribute donations will not lie I'm paying this amazing handset even with great difficulty! Only then ask for help and support in the galaxy s5 sm-g900s and remember and thank also those involved in progeto cynogenmod for sm-g900s I was very happy to know what is' rom cynogenmod '' want to install but wanted to know whether to take root both 5.0 and 6.0 lollipop good marshmellow now comes I have spoken

Boot loop
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1

BlackMonoch said:
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1
Click to expand...
Click to collapse
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.

sunilpaulmathew said:
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.
Click to expand...
Click to collapse
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160330-NIGHTLY
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
After couple of minutes waiting, still stuck at "Android is starting... Starting apps."
........edit.......
Yay! After taking sometime waiting, I rebooted my device and now starts normally.
Thanks for this tut, now I can finally enjoy CM13 on my phone.
Thanks OP.

Audio Jack Bug
3.5mm audio jack does not work.

BlackMonoch said:
3.5mm audio jack does not work.
Click to expand...
Click to collapse
That is a know bug... and sometimes you may face issues with caller volume. There is no permanent solution at this moment . You can temporarily solve these issues using SoundAbout although it is bit inconvenient. Suggestions are most welcome.

Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,

obosaleh said:
Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,
Click to expand...
Click to collapse
I also face similar issues with the recent nighties... I tested nighties till 20160323 and found no issues. I'm not sure whether this issue exists in klte too. Anyway, thanks for testing and posting your tips.

i have same problem with new update 31-03 01-04 02-04

[ROM] [AOSP] Candy7 -- Final v6.0 [7.1.2][OMS/DUI]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Candy7.1. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web The-Candy-Shop​
Candy 7.1.2 v6.0 Final
Dynamic GApps
FEATURES
Multi-window
OmniSwitch
Immersive mode
Clear all button
Memory bar
Slim Recents option
Advanced power menu:
On The Go Mode
Screen record
Adjustable dialog background shade
Sound panel
Expanded desktop
Lockscreen:
Battery charging current overlay
Adjustable shortcuts
Weather (OmniJaws)
Statusbar settings:
Ticker (disable heads up when in use)
Weather panel
Clock/battery configuration
Traffic indicators
Quick settings tile config
Immersive messages
Force expanded notifications
Carrier label
Tap to sleep
Buttons settings:
Long-press/double-tap actions
Volume rocker
Playback control
Volume key answer
Disable HW keys
Pie control
Navigation bar:
Adjust colors
Smartbar/fling
Pulse
Screenshots:
3 finger
Adjust framing
More to come, we are never done...
Steps:
1) Download ROM zip
2) Download GApps
3) Boot into Recovery
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash Candy7.1.zip
6) Flash GApps
7) Reboot.
BUGS:
1. same as lineage
2. first time registering finger print gives FC
3. flashlight works after 2nd reboot (for me)
Candy Source --
Device Tree
Kernel Source
Vendors
Special thanks to LineageOS, SlimRoms, Omni, TeslaROM, and all the rest who make their source open. We can't do this on our own.
XDA:DevDB Information
Candy7, ROM for the LeEco Le 2
Contributors
saurabh1234, saurabh1234, Candy Team
Source Code: https://github.com/candyroms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Created 2017-12-19
Last Updated 2017-12-19

screenshots

Download My Wallpaper App for More Hipsta Walls and some Nature Wallpapers...
its a free app with no ads...
Play Store Link

This ROM is how different from slimrom.....
Because slimrom doesn't have hardware keys off setting...
I am using from quit past time..

itsvikash said:
This ROM is how different from slimrom.....
Because slimrom doesn't have hardware keys off setting...
I am using from quit past time..
Click to expand...
Click to collapse
this rom has option to disable hardware keys...
and many more features...
slim rom is made to give users a full AOSP experiance.
Candy rom is also AOSP based but with different features

Can u give me
link of dynamic gapps

itsvikash said:
Can u give me
link of dynamic gapps
Click to expand...
Click to collapse
check op its there...bean gapps is called dynamic gapps

I'm facing some issues with dual sim. One of the sims just doesnt show up.
Downloaded and flashed rom just two days ago; so I guess must be the latest version.
Using it with Illusion kernel 3.1b.
Le 2 x522(or whatever the Indian version is)
Was on .19s stock eui before flashing candy rom.
Flashing sequence
Rom
Gapps
Magisk
Kernel(after booting into system, atleast once with stock kernel)

Ronnie_180808 said:
I'm facing some issues with dual sim. One of the sims just doesnt show up.
Downloaded and flashed rom just two days ago; so I guess must be the latest version.
Using it with Illusion kernel 3.1b.
Le 2 x522(or whatever the Indian version is)
Was on .19s stock eui before flashing candy rom.
Flashing sequence
Rom
Gapps
Magisk
Kernel(after booting into system, atleast once with stock kernel)
Click to expand...
Click to collapse
after setup...do a reboot..then a airplane mode turn on and then turn off...
it will work...
if setup is already done...then do reboot and then turn on airplane mode and then turn off...and wait ...
it will work

saurabh1234 said:
after setup...do a reboot..then a airplane mode turn on and then turn off...
it will work...
if setup is already done...then do reboot and then turn on airplane mode and then turn off...and wait ...
it will work
Click to expand...
Click to collapse
Actually I had both the Sims working initially after the whole setup. Even tried calling from both Sims with satisfactory results.
I was on wifi, so then for checking purposes, I tried to switch to mobile data. Didnt work at first. So I turned airplane mode on & off. Got data, but began facing the above mentioned dual sim issue.
I don't have the device with me at present. But I'll surely try your suggestions and report.
On a side note, I also have a Redmi Note 3 and many a times issues related to calls and sim cards in custom roms gets resolved by flashing latest firmwares, so I was wondering if even Le 2 requires flashing firmwares or something?
Also, I had queries about the bootloader unlocking process.
First of all, I'm new to Le 2 development, but I've had about enough experience with rooting and stuff. Not a dev myself, but I can say I've some basic understanding which shall make it easier for you to explain and help me.
I searched about stuff on google and xda, but kinda unable to get proper answers.
Anyways, back to the main topic here;
So for unlocking bl;
I rebooted to fastboot mode after enabling adb debugging and oem unlocking and unlocked bl via fastboot commands, flashed redwolf twrp and formatted the whole device via twrp.
Is that correct? And is that the only method available to unlock bl?
It seems like unofficial unlocking and if it really is so, then is there an "official" way of unlocking?

Ronnie_180808 said:
Actually I had both the Sims working initially after the whole setup. Even tried calling from both Sims with satisfactory results.
I was on wifi, so then for checking purposes, I tried to switch to mobile data. Didnt work at first. So I turned airplane mode on & off. Got data, but began facing the above mentioned dual sim issue.
I don't have the device with me at present. But I'll surely try your suggestions and report.
On a side note, I also have a Redmi Note 3 and many a times issues related to calls and sim cards in custom roms gets resolved by flashing latest firmwares, so I was wondering if even Le 2 requires flashing firmwares or something?
Also, I had queries about the bootloader unlocking process.
First of all, I'm new to Le 2 development, but I've had about enough experience with rooting and stuff. Not a dev myself, but I can say I've some basic understanding which shall make it easier for you to explain and help me.
I searched about stuff on google and xda, but kinda unable to get proper answers.
Anyways, back to the main topic here;
So for unlocking bl;
I rebooted to fastboot mode after enabling adb debugging and oem unlocking and unlocked bl via fastboot commands, flashed redwolf twrp and formatted the whole device via twrp.
Is that correct? And is that the only method available to unlock bl?
It seems like unofficial unlocking and if it really is so, then is there an "official" way of unlocking?
Click to expand...
Click to collapse
you did right..thats the way to unlock le2...
i would recommend you to install official twrp and use 19s bootloader...

saurabh1234 said:
you did right..thats the way to unlock le2...
i would recommend you to install official twrp and use 19s bootloader...
Click to expand...
Click to collapse
Okay, will shift to official twrp and since (luckily) i never updated my stock rom after 19s version, my bootloader shud still be 19s, right?

Ronnie_180808 said:
Okay, will shift to official twrp and since (luckily) i never updated my stock rom after 19s version, my bootloader shud still be 19s, right?
Click to expand...
Click to collapse
yes

Change Logs:
Latest Device Tree
Latest Kernel Source
Flash Magisk for Root
Link - https://drive.google.com/open?id=130nPA5sMlmv_moqGe1d5eF9oCx_ialTk

[ROM][OFFICIAL] Omnirom for Oneplus7pro [10]

CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
DOWNLOAD Official
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS
MAJOR BUGS:
huh ?
Minor bugs:
flash on your own risk.
FLASHING
First Time:
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
reboot
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS 10
Version Information
Status: Stable
Created 2019-10-02
Last Updated 2019-11-19

amazing , thanks

The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?

Gordietm said:
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Click to expand...
Click to collapse
That should be ob obvious, but i will add it

[ROM][BETA] Omnirom for Oneplus7pro [10]
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Click to expand...
Click to collapse
Always nano

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Read OP : flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED

[ROM][BETA] Omnirom for Oneplus7pro [10]
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Sent from my iPad using Tapatalk Pro

paatha13 said:
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Click to expand...
Click to collapse
Yes

Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Good luck

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Probably you missed something, skipped one step etc.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.

gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
No, oos camera also works fine

I have no idea what it is. Had to boot a fastboot rom just to get back up and running after that last crashdump. going to go back to OOS for a little I think. I have never had a rom do this but this one has done it every time I have tried. Thing is I love Omni so I hope one day i can get it running properly.
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
Don't worry i didn't forget lol. That's why i'm going to keep trying after every release. It will work for me one day.

[ROM][BETA] Omnirom for Oneplus7pro [10]
Everything fine with installations no had any issue with first attempt.
Installing nano gapps not had any issue too this time at opposite with weekend build.
Seems this build more stable and I'm now charging the phone,download my usual staff from play store,will setup my device and will start to work on it later when phone full charge.
Thanks @darkobas.
darkobas said:
No, oos camera also works fine
Click to expand...
Click to collapse
Yes I can confirm OOS camera working fine.
Sent from my iPad using Tapatalk Pro

Does anyone know of an app or mod that allows the navigation buttons to be inverted? The custom navbar app doesn't work on 10 yet and that isn't integrated into the rom yet. I'll live but it is tough to try to retrain the brain, ha!

First impressions using couple of hours is solid.
Battery life look promising and satisfactory.
Very smooth experience so far.
Speaker loudness and quality is on par with oxygen just like with Pie version.
Brightness level seems on par with high oxygen levels although I haven't test it in sunlight, will do tomorrow [emoji14]
Stock(android 10) gesture navigation works great but prefer oxygen one and since using nova launcher I'm with vivid gesture navigation app since when using third-party launcher automatically stock gesture navigation are disabled.
There's dark mode but I'm not fan of it since it's dark gray and not black that prefer (will use substratum to apply truly black theme almost everywhere)
Vast majority Omni features working fine so far.
Wi-Fi, mobile data, so far all excellent, BT will test tomorrow intensively.
Almost all oxygen features are present and worked fine, except vibration need some tuning but that also appy to stable OOS 10 version.
On Pie vibration was better both Omni and OOS.
High brightness level is still present
I found some bugs though like dt2w not such reliable almost half of the attempts needed 2 and rare 3 times to wake up screen or even press the power button at end because not responding at all.
Aldo digital wellbeing to me every time try to open I'm getting fc.
Safety net not passing through magisk also.
I assume will improve in future build don't forget it's still beta.
More observations and safe conclusions will have after couple of days of using the new rom.
But so far general impressions after few hours is at good and satisfactory level and the build is safe to be daily driver for sure.
Sent from my GM1913 using Tapatalk

Just wondering why I can't download the Samsung wearable app in the Google Play Store on this. When I get it from the APK it tells me that this software which is on my phone is not compatible with the watch is there a way to fix this so I can connect my Galaxy watch to this amazing ROM this happens to me on every single ROM except CR Droid 9.0 don't know why:crying:

This is a pic of what the Samsung wearable app said

[ROM][UNOFFICIAL] AOSP Extended (AEX) 5.8 for Nvidia Shield Tablet OMX Fixed

**** Work in progess ****
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AOSP Extended is an AOSP based rom which provides stock UI/UX with various customisations features along with the Substratum theme engine. The project has been made by cherry-picking various commits from various other projects. Being based on AOSP it provides a smooth and lag-free experience out of the box. We will constantly try to add more features and make it even better in future updates. A ROM by a user, for a user. #StayAOSP #ExtendYourDevice #BeExtended
Features
Silky smooth Android experience
Tons of customisation
Pixel-like UI (Launcher, settings, Google Now swipe...)
Full Substratum/OMS support
And much more (check official AEX website)
HW Accleration working !!!
Camera working
Kernel Features
Added IO Schedulers:Zen,Sio,Maple,Tripndroid
Added Governours:ElementalX,SmartMax,Tripndroid
Added Filesystem:SDCardFS,F2fs
Removed:EXFat causes random Bootloops and compatibility problems
Modified Dtb for faster charging (Tested around 2.4A at 5 Volt Chargepower with Anker 20W Wallcharger and 2A at 9V with Anker Power Port+1) experimental QC2.0 enabled Tests needed
Optimized for Battery:SmartmaX Cququiet:runnable Maple IO Sheduler as default
If you need performance change to Interactive and Cpuquiet:Balanced
Download
Latest release here.
https://androidfilehost.com/?w=files&flid=305454 no Zram
https://androidfilehost.com/?w=files&flid=305455 with Zram
https://androidfilehost.com/?w=files&flid=305556 DTB with QC2.0
Installation
Be on the latest firmware - if you are not, or aren't sure just flash latest stock recovery image for your device (you will lose data and TWRP so back data up and prepare to reflash TWRP)
From TWRP3.3.1 wipe Cache, Dalvik, System, Data and Internal Storage
Flash ROM
Flash ARM (not arm64!) 8.1 mini gapps
Flash DTB after all with : fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Netflix with SD:
Install latest Magisk
Download Libeoemcrypto patch and Props Fingerprint Mod
after reboot run in Terminal with Root rights Props choose 1 Edit device fingerprint
f Pick a certified fingerprint
16 Nvidia after that choose your device
Reboot and download Netflix from Store
Fixed: HW Accleration OMX works now
Camera full functional now
Kernel Bootloops/Random reboots
LTE Fix no Sim Card detected
Bugs
Netflix HD still not working
Nvidia Games crashes
As Workaround you could use Moonlight Gamestream to stream PC Games
Report bugs if you find any, every opinion is welcome, try to describe problems with as much detail as possible
Thanks
AEX team, LineageOS team, and all people around this project and this device
Special thanks to Steel01 and Artemka2008 for there help with the OMX Fix
XDAevDB Information
AOSP Extended for Shield Tablet, ROM for the Nvidia Shield Tablet
Contributors
Triodexe, Steel01, Artemka2008
Source Code: https://github.com/aospextended
Kernel Source: https://github.com/Triodex/TrioX-V04-Kernel
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.x
Based On: AOSP+LineageOS
PLATFORM_SECURITY_PATCH := 2020-02-05
Version Information
Status: Testing
Current Stable Version: 5.8
Stable Release Date: 2020-02-20
Created 2020-02-20
Last Updated 2020-02-29​

So, the one thing left not working is the camera? Any hope of fixing that?

Thanks for releasing this. Can't wait to give it a try. Curious about the zram vs no zram. What is that? Also, what is dtb? Thanks again.

Hi
For the Camera bug i still try to get this fixed.
@bigcletus
Rom with Zram have 510MB Compressed RamSwap that you can increase with Kernel Managers like the StockRoms
Rom without Zram didnt have this
The Dtb is needed for the correct Charging Amps and Voltage Regulation so if you notice after flash the Rom that Quickcharge isnt working flash the Dtb again with Fastboot.
Greats Triodexe

I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.

bigcletus said:
I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.
Click to expand...
Click to collapse
Hi
Did u use the Latest Twrp 3.3.1 to flash the Rom ?
For the Bootloop i dont know yet why it happens sometimes have the same problems again after a few restarts device stucks at Nvidia Logo but after manualy Poweroff/On its boots most af the time .
Guess there is a problem with one of the Governours/Shedulers i added or the Exfat Kernel Support.
But curios is the same stuff works in the Aosp4.6 Roms.
Could be that the Old Nvidia Vendor Blobs arent so good for Oreo based Roms but the newer ones from Shield Tv have no Hardware Accleration yet
But Dmesg didnt help me for this when i boot into recovery device always boots
You could try flash another Kernel the K1 Nougat from bleeblob or Bitos Kernel Version 10 should work better
So i reflashed the nozram over my Rom again and got no bootloop only wiped cache and dalvik
Could you look Into your Internal storage if there is some stuft left Form the Old Rom Apps and Magisk
Stores the Data there.
Greats Triodexe

I am using TWRP 3.2.3. I have flashed LOS 14.1 and 15.1 with this version of TWRP but maybe this rom needs the newer version?
I will try again when I have more time and I'll wipe the internal storage as well. Thanks.

Install and boots OK. I can't get Netflix to work.

Darkside281 said:
Install and boots OK. I can't get Netflix to work.
Click to expand...
Click to collapse
Hi yep Netflix is a beast cause it didnt accept the Widewine Version we got
Solution i used is Downloaded Netflix over ApkPure and use the Netflix Magisk OemCrypto patch.
Only in SD Quality then but for me its ok
Maybe with other Widewine Files we got Netflix in HD
Greats Triodexe

First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?

xconwayx said:
First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?
Click to expand...
Click to collapse
Hi
No normaly the Dtb is inside the Kernel you only need to reflash it when Qc2.0 not working you can see it when dmesg kernel and look at the Bq2419-st8 message if it shows Qc2.0 Charger.
Or easier use ampere App when your charge mA goes around 2500 then QC works.
Qc2.0 charge takes then around 45 Minutes from 15% to 90% the last percents from 90-100% charges a liitle bit slower i wouldnt stress our Batterys to much
Greats Triodexe

So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.

I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?

Kf_Umbra said:
So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.
Click to expand...
Click to collapse
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe

Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?

bigcletus said:
I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?
Click to expand...
Click to collapse
Hi
Nvidia Games didnt work for me too i can open it and register but when i start to stream a game it crashes
With the newer Vendor Files it works but then the HW Accleration is broken.
Try to get this fixed together with the no working Camera but this crappy Logs in Logcat from Nvidia didnt show the reason why it crashes.
Only for the Camera i know that it happens after Jpeg creation that it crashes
Greats Triodexe

Triodexe said:
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe
Click to expand...
Click to collapse
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.

Kf_Umbra said:
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.
Click to expand...
Click to collapse
I tryed the Dtb again flashed with Fastboot and no bootloop dont know why it didnt work for you.
Did Quickcharge works when you only flash the Rom ?
Greats Triodexe

bigcletus said:
Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?
Click to expand...
Click to collapse
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe

Triodexe said:
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe
Click to expand...
Click to collapse
I have the original LTE model.