Database Info

[ROM][09/05/12] CyanogenMod-7.2 RC2 for Desire GSM

CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (how-to).
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. WIPE (wipe data/factor reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Latest version: 7.2.0-bravo - 09/05/2012
Download: CyanogenMod Mirror Network
Google Addon: Get gapps-gb-*latest*.zip
Download: http://goo-inside.me/google-apps/
CM7 HBOOT r2 by Alpharev | xda thread
Change partition table size 145/5/287 (system/cache/size)
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7r2.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD:
Simple2Ext (Easy with a GUI)
CM7 Legacy App2SD Addon Script (For Advanced user, Command Line)
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
*Note: I'm not part of the CM Development team, however after waiting for ages for someone who was to post a thread for RC2 it didnt happen, due to this ive taken it upon myself to start one so people dont mistakenly think RC1 was the latest release, I hope no one minds me kicking a thread off.

Reserved for future use

More CyanogenMod ?
Sorry Bro...
what is "new" or "future" or....2 outer CyanogenMod-7.2 RC2 ?
See Kali
NIGHTLY
and more...?!

There is no point in creating another CM thread..

I don't see why this thread is necessary, there are several CM7r2 threads already... please PM with an explanation me if you'd like it reopened.

[TF700T][ROM][5.0][OFFICIAL] CyanogenMod 12.0

*** DON'T FLASH THIS IF YOU ARE NOT COMFORTABLE WITH DATA LOSS, INSTABILITY, RABID DOGS EATING YOUR CAT, OR SPACE ALIENS STARING AT YOU IN THE MIDDLE OF THE NIGHT! ***
*** If you like this post and can't donate to the cause, then hit thanks! ***
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits:
Steve Kondik and the amazing CM team
See here for more contributors
And the many testers and contributors not listed above, including: chrmhoffmann, thunderger, jaybob413, Everett Coleman, Pretoriano80, untermensch, Richard Huynh and others I probably forgot
*** This is a development thread.
For questions and troubleshooting refer to this thread ***
*** Backup your data before continuing! ***
What works:
Audio
Hardware Acceleration
WiFi
GPS
Bluetooth
Touchscreen
HDMI
Microphone
USB host
Dock
Cameras
Encryption
Accelerometer
Gyroscope
Compass
Known issues:
Performance quicksetting tile isn't implemented yet (but is available through sys.cpu.mode property)
Dock battery indicator tile isn't implemented yet (but hardware works)
cm-recovery doesn't work (even boots)
lock key button in keyboard doesn't wake up the device
Netflix has issues after pausing, rewinding or fast forwarding. (libomxplayer.so) It's an ASUS issue at this point. (FIXED? Please confirm, I'm not seeing these issues anymore)
Screenrecording is broken, codecs issue (OMX doesn't support virtual displays, we only have 4.2 blobs, will not be fixed, unless Asus releases KitKat for our devices)
You tell us...
*** Backup your data before continuing! ***
Instructions (README, A LOT!!!!!!):
Make sure your device is unlocked. Grab the unlock utility here, under Others -> Utilities
(If you're on stock 4.2.x, skip this step) Install the 10.6.1.14.4 or greater bootloader for your variant, see here for more information.
Download Clockwork Recovery 6.5.0.1 here
Download GAPPS
Place the cm-12-YYYYMMDD-EXPERIMENTAL-JRUESGA-tf700t.zip (you can grab it from downloads section) and gapps-lp-YYYYMMDD-signed.zip (search in internet for a valid package) on your sdcard of your slate
Reboot to the bootloader: Power off slate, then: Power + Volume -. Hit Volume - until you hit the USB symbol, then hit Volume +.
Flash Clockwork Recovery
^^ BACKUP YOUR DATA!
Next, Wipe Data Factory Reset (ONLY NECESSARY IF COMING FROM ASUS stock ROM or something other than CM11.0!!!)
Then 'install zip from sdcard', 'choose zip from internal sdcard', then install the cm-12-YYYYMMDD-NIGHTLY-tf700t.zip.
Then install gapps-lp-YYYYMMDD-signed.zip.
Go back to the main menu and Reboot Now.
Upgrading builds:
Reboot to recovery
Install cm-12-YYYYMMDD-EXPERIMENTAL-JRUESGA-tf700t.zip
Reboot
or use built in cmupdater
If you run into issues outside the 'Known issues', please post a logcat.
You will need the adb binary on your computer (Windows, Mac or Linux):
Code:
adb logcat > logcat.txt
If are get a hard lock and have to reset, please pull the /proc/last_kmsg and post it after you are booted again.
Code:
adb pull /proc/last_kmsg
Please do not report on ANY known issues!!!
Help? Click here...
Donate to the devs:
dasunsrule32 - (Google Wallet - [email protected] or PayPal)
jruesga
Source(s), Gerrit and Changelog:
Source(s):
https://github.com/CyanogenMod/android_device_asus_tf700t/tree/cm-12.0
https://github.com/CyanogenMod/android_kernel_asus_tf700t/tree/cm-12.0
Gerrit ( Submitting patches/fixes ):
http://wiki.cyanogenmod.org/w/Doc:_using_gerrit ( When submitting a patch, please use this group vs adding myself and individual devs: Transformer Team )
Changelog:
http://www.cmxlog.com/12/tf700t/
XDA:DevDB Information
CyanogenMod TF700T CM-12.0, ROM for the Asus Transformer TF700
Contributors
jruesga, dasunsrule32
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Bootloader 10.6.1.14.4 or above
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-01-19
Last Updated 2015-01-28

Reserved

Reserved

cm-12-20150118-EXPERIMENTAL-JRUESGA-tf700t.zip
This is the first experimental image for TF700T CM12.0 (Lollipop) cm-12-20150118-EXPERIMENTAL-JRUESGA-tf700t.zip.
Please, be sure you backup your data before flash it. This are the MUST HAVE requirements (Downloads):
* 10.6.1.14.4 or greater bootloader
* Clockwork Recovery 6.5.0.1 (I didn't test TWRP)
* GAPPS 5.0 (Lollipop) - Search in internet for the proper ones
This is an experimental versión, so expect things not working.

Will test with TWRP 2.8.0.1.

Installed it successfully (dirty flashed over CM11)! No FC 'til now. Thank you for your hard work! :good:

Process.com.google.process.gapps has stopped error.
I use basketbuild gapps everything ran well before I installed gapps.

dracinn said:
Process.com.google.process.gapps has stopped error.
I use basketbuild gapps everything ran well before I installed gapps.
Click to expand...
Click to collapse
Please, try to post a logcat when reporting an error
Code:
adb logcat > logcat.txt
I'm using 20141109 from http://d-h.st/users/dhacker29/?fld_id=27426

jruesga said:
Please, try to post a logcat when reporting an error
Code:
adb logcat > logcat.txt
I'm using 20141109 from http://d-h.st/users/dhacker29/?fld_id=27426
Click to expand...
Click to collapse
My logcat.

dracinn said:
My logcat.
Click to expand...
Click to collapse
The basketbuild gapps are 20141109 (5.0) but the current version of android is 5.0.2 and the GoogleContactsSyncAdapter is crashing because doesn't find a resource. Try to upgradte to the latest published version of the dhackers99 gapps (http://d-h.st/users/dhacker29/?fld_id=27426)

jruesga said:
The basketbuild gapps are 20141109 (5.0) but the current version of android is 5.0.2 and the GoogleContactsSyncAdapter is crashing because doesn't find a resource. Try to upgradte to the latest published version of the dhackers99 gapps (http://d-h.st/users/dhacker29/?fld_id=27426)
Click to expand...
Click to collapse
Appears to be the same problem as far as I can tell. Will try clean install.

Lollipop using data=F2FS
Does anyone know if this can be used if data is formatted to F2FS?
Also does the kernel support it?

norm883 said:
Does anyone know if this can be used if data is formatted to F2FS?
Also does the kernel support it?
Click to expand...
Click to collapse
Not yet. I will consider to add it to in my TODO list.

F2FS
jruesga said:
Not yet. I will consider to add it to in my TODO list.
Click to expand...
Click to collapse
Thank you sounds great!

I use this version as my daily driver. The only big thing that i miss is the not working auto rotation. When can we expect a new (experimental) firmware?
Thank you!

My Public said:
I use this version as my daily driver. The only big thing that i miss is the not working auto rotation. When can we expect a new (experimental) firmware?
Thank you!
Click to expand...
Click to collapse
We have a fix for the rotation problem. I will leak a new flashable zip this weekend with some other fixes

Wrong thread... Sorry' 'bout that.
Added on edit:
FYI, the Q&A / Troubleshooting links to the CM11 thread rather than the CM12 specific thread.
This is the correct link:
http://forum.xda-developers.com/transformer-tf700/help/tf700t-cyanogenmod-12-t3006630

John Kotches said:
Wrong thread... Sorry' 'bout that.
Added on edit:
FYI, the Q&A / Troubleshooting links to the CM11 thread rather than the CM12 specific thread.
This is the correct link:
http://forum.xda-developers.com/transformer-tf700/help/tf700t-cyanogenmod-12-t3006630
Click to expand...
Click to collapse
I updated the link to Q&A thread. Thx

I find this helps a lot with the chrome problem. Try this !
http://www.techrepublic.com/article/pro-tip-speed-up-chrome-on-android-with-this-handy-hack/

cm-12-20150126-EXPERIMENTAL-JRUESGA-tf700t.zip
New experimental version is up in the downloads section http://forum.xda-developers.com/devdb/project/dl/?id=10822
Changelog:
* Fix auto-rotation
* Update wifi/bluetooth rfkill driver to bcm4330
* Added bluesleep support
* Updated media codecs (should improve netflix playback)
* Updated selinux policies
* Removed camera wrapper and forced camera api 1 (this should prevent errors with third party camera apps)
* Set "High Performance" mode during boot
* CyanogenMod CM12 2015-01-16 upstream changes
Thx to chrmhoffmann and lj50036 for some of this patches
Please, read the OP before flash it if you came from other rom or cm11.

[ROM][7.1][LineageOS(CM)14.1 and CM13 ][UnOfficial] (Nougat) [tate]

CM13.0 (Marshmallow) unofficial builds for the TATE
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
download:
new: https://www.mediafire.com/folder/u7sb7p10ik7v0/tate
old:https://www.mediafire.com/folder/5a97vbv93k24n/tate
old:https://www.mediafire.com/folder/w9nh7oyabwvww/tate
backup before flash, gapps need for upgrade, don`t flash SuperSU
deep sleep fixed
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
bluetooth lte-version fix: https://forum.xda-developers.com/ki...elp/kindle-fire-hd-8-9-bluetooth-rom-t3315904

Great, now it's time to bring TWRP 3.0.0.0 for better results.

alexander_32 said:
Great, now it's time to bring TWRP 3.0.0.0 for better results.
Click to expand...
Click to collapse
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.

build 20160215 (backup before flash, gaaps need for upgrade): http://www.mediafire.com/download/pj2994j9p358tit/cm-13.0-20160214-UNOFFICIAL-tate.zip

xWolf13 said:
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
Click to expand...
Click to collapse
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).

alexander_32 said:
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
Click to expand...
Click to collapse
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs

monster1612 said:
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you very much :good::good::good:

@transi1 Great rom! Very fluid. Only issue is the lack of deepsleep. Do you have an idea what might be causing it?
Also I flashed the ROM with Twerp 2.7.x.x so Twerp 3.0 is not required (but if you guys build it,i'll still take it )

Thanks for bringing CM13!

hope this rom to be official

build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed

Screenshots please??

transi1 said:
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Click to expand...
Click to collapse
My battery thanks you. From what I can tell, everything that was working in cm12.1 also works in cm13. Along with very aggressive memory killer recommended from OP, I'm also using max cpu freq 1500MHz with performance governor and deadline scheduler with 512kB read-ahead in kernel adiutor and the performance is good. In cm12 I remember several crashes with the same cpu oc but for now it seems stable.

How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk

Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
LOL! Definitely don't flash supersu! Just got my kindle back up from soft bricking it that way.

Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Click to expand...
Click to collapse
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).

r3t3ch said:
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
Click to expand...
Click to collapse
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Sent from my Amazon Tate using Tapatalk

Jrhoop said:
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Click to expand...
Click to collapse
If you can enter fastboot you have nothing to fear. TWRP is the only recovery that is consistently updated and is highly recommended over philz/cwm. Download TWRP 2.8.7.0 and extract the img from the zip.
I've never been a fan of flashing tools from within android. It's much simpler to just go into fastboot and use:
Code:
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img

You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting

Maromi said:
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Click to expand...
Click to collapse
Hey what rom are you running on the KFHD?

[RECOVERY][mido][k4.9] KudProject's Unofficial TWRP 3.5.2_9-1 [21-05-2021]

Notice: This is a dedicated thread for unofficial TWRP builds with msm-4.9 kernel. If you don't know why you're here, you probably want to just stick with whatever recovery you're using right now.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Disclaimer​
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements​
Redmi Note 4(X) (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing Instructions​I assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-mido.img
Where x and y are version of TWRP you're going to flash.
(???) You know the rest.
Downloads
Webserver | MEGA
Known Issues​
You tell me?
Special Thanks​
Dees_Troy and everyone behind TWRP
Acknowledgements for msm-4.9 kernel port: https://kudnet.id/~raw/mido-4.9
Everyone on Redmi Note 4(X) community
Device Sources​
TWRP repository fork
Device tree
Kernel source

Changelogs​twrp-3.5.2_9-1-KudProject-mido
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated MoeSyndrome kernel in recovery
Added back Cust partition entry in fstab (umounting it also umounts Vendor partition)
twrp-3.3.1-3-KudProject-mido
Synced with TeamWin's changes up to 25 May 2020 (UTC+8)
Switched f2fs-tools to latest AOSP master
Updated prebuilt kernel to include all fixes and workarounds done in kernel
twrp-3.3.1-2-KudProject-mido
Initial TWRP build with msm-4.9 kernel in preparation for custom ROMs that ship 4.9 kernel
All other builds older than 3.3.1-2 are with msm-3.18 kernel instead.

Notes​
This specific TWRP build is mandatory for flashing ROMs that ship msm-4.9 kernel and target FCM level 3. Any other recoveries (official and a number of TWRP forks) aren't supported nor will be guaranteed a successful flash.
Technical advice (although unrelated to TWRP): Never flash 3.18 kernel on 4.9 ROM or vice versa and hope everything will work. Just... don't.
Verifying released builds​This was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.

And... I'm officially back!

We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??

ShreyYy said:
We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??
Click to expand...
Click to collapse
You can flash TWRP from TWRP itself just fine, just target right partition. And, you probably want to use 3.3.1-1 instead if you don't plan to flash any 4.9 ROM.
[Spot the device version]
Sent from my MI 9 SE using XDA Labs

It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.

Yes, look at los 16 official from Aryan Kedare, post 1167 with links.

Official TWRP 3.4.0 got released for mido.
Can we use that? Or you have to do your magic first?

speter2 said:
It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.
Click to expand...
Click to collapse
Evolution x support 4.9

Hi community,
Please, correct me if i'm wrong. If i already have installed a custom recovery, i just have to flash this and reboot to recovery and thats all? Regards.

Any update on 3.4?

lintah_darat said:
Any update on 3.4?
Click to expand...
Click to collapse
Under testing for all 3 devices so far
PS: You'll probably need updated ROMs more than recovery.
Sent from my Redmi Note 4 using XDA Labs

Hello guys, first post here I have installed the last Pixel Experience 11 Stable with the official lastest TWRP 3.4, but in the PE11 official page, they have a link to use this TWRP Custom version.
What should I do now ? Flash the custom and reinstall the PE11 ? Sorry if its a newbie question, but Im still learning about rooting and Custom ROMS. Cheers

Version 3.5.2_9-1 is now available. Release is currently available only via download server due to storage constraints on MEGA mirror. Enjoy!

does it need lazy flasher?

So no one has bothered to point out kudnet.id isn't working and the latest build is not posted on Mega.nz ?
Is this project abandoned?

[ROM] [11.0] [OFFICIAL] AICP 16.1 [instantnoodle]

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
Pixel Experience Team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)​
On Clean Flash: mandatory for first install !!!​At the beginning, if you are on Stock OOS 11 ROM with locked bootloader, please follow the instructions for unlocking bootloader here: https://wiki.lineageos.org/devices/instantnoodle/install
1. Download the ROM and GApps to your PC with proper adb & fastboot setup.
Also download to your PC instantnoodle-recovery.img from HERE
2. Boot to bootloader and run in cmd (windows) / terminal (linux)
fastboot flash recovery instantnoodle-recovery.img
4. Boot to recovery. Tap on Factory Reset (this will erase everything on your device) then return to main menu
3. Connect your device to your PC and tap on Apply Update -> Apply from ADB and
4. Flash the ROM zip file using
adb sideload aicp_instantnoodle_r-16.1-WEEKLY-{date}.zip
5. Once its finished, reboot to recovery to flash the GApps (optional, needed for e.g. Google Playstore to work). This is mandatory becoz will switch automatically current slot and will flash GAPPS.
Once it boots to recovery, tap on Apply Update -> Apply from ADB then run
adb sideload GAPPS.zip
6. Reboot and set up your device.
7. Reboot back into recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The main workflow for flashing via recovery:
reboot to recovery -> adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip -> reboot to system
Click to expand...
Click to collapse
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 21.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
Go to Aicp Extras -> Update Centre then install new Weekly Build.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: We are building Neutrino Kernel adopted to our sources with permission by Kernel Dev
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
Common device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Join us on our Discord Channel
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:[/U[
ROM OS Version: 11.1
Kernel: Linux 4.19.176
ROM {Firmware|Vendor} OnePlus8Oxygen_15.E.35_OTA_0350.
Status: {STABLE}
Release Date: 04-03-2021
You want to see a "normal" night at the "DEV office", click here!!​

AICP recovery: link HERE
---------------------------------------------------------------------------------------------------------------
New build guys
10.04.2021 UPDATE​
Download aicp_instantnoodle_r-16.1-WEEKLY-20210410.zip from HERE
Changelog: link HERE
No GAPPS in the ROM.zip.
** İf you are comming from older version - no need to flash clean.
-- if you are rooted: Just go to Updater in AicpExtras choose the downloaded zip from your storage and install the update.
-- if you aren't rooted:
**** Download the zip. Connect your phone to your PC. and run adb root in terminal (or cmd windows for Win). Then run adb shell setenforce 0 and install downloaded zip as local upgrade from Updater in AicpExtras. You'll be on enforcing selinux mode after reboot
-- You can flash in recovery via adb sideload. İf you choose this way, don't forget to reboot to recovery and flash your GAPPS.zip via adb sideload again.
-- if you want to clean flash:
**** reboot to recovery. Format data then follow the procedure given below:
flash rom.zip via adb sideload -> reboot recovery -> flash gapps.zip via adb sideload -> reboot to system
What's new:
1. April '21 ASB merged
2. Added ALipay fingerprint payment support
3. Screenbrightness fixes for all 3 devices
4. Many fixes including SafetyNet (fixed again)
Enjoy !!!
---------------------------------------------------------------------------------------------------------------
04.04.2021 Build !!!​
Download aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip from HERE.
Changelog: link HERE.
-- There is no GAPPS in the ROM.zip.​Download GAPPS from:
MindTheGapps or OpenGapps Android 11 Nano​
How to install:
1. Go to recovery. Format data if you want to flash clean.
2. Apply Update from ADB
3. then adb sideload aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip
4. Reboot to recovery
5. Flash Gapps via adb sideload GAPPS.zip
** İmportant: Android Auto fails to connect with OpenGapps. All good with MindTheGapps
** There is no DevicePersonalization app in these - if you want, I can provide a modified GAPPS package
6. If you want to switch in between GAPPS packages, just flash other GAPPS package on the new flash. Clean flash isn't trivial, but recommended....
*** Next flashes can go through Updater or adb sideload.
** If you flash via Updater, backup tool will handle your gapps - no need to reflash them again.
** GAPPS need to be flashed on every update if you flash via adb sideload. Flash them as it is described above.
What's new?
** Stock vibration patterns are back
** App Lock from AOSP-A
** Neutrino Kernel updated to 4.19.183
** and many more....
All feedbacks are appreciated, as always.
Cheerz
---------------------------------------------------------------------------------------------------------------
For those who want to ROOT their devices:
Download Magisk 21.4 zip: link HERE
** boot to recovery
** flash via adb sideload magisk.zip:
** reboot.
** Note that you HAVE to do this on every update.
** SafetyNet is fixed on March 5 build !!!
Enjoy !!

Which Camera we can use:
1. Using this Camera: GCam_7.3.018_Urnyx05-v2.1_Wichaya_V3.1.1_snapcam.apk
2. Also I have thix xml file under GCam/Configs7 : nrG Wichaya 7.3.018_v3.1.1.xml

finally! thanks

Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?

mattie_49 said:
Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?
Click to expand...
Click to collapse
No unfortunately. Doubt it'll work on Verizon.

semdoc said:
No unfortunately. Doubt it'll work on Verizon.
Click to expand...
Click to collapse
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?

mattie_49 said:
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?
Click to expand...
Click to collapse
most likely qti telephony....

Rebuilt and re-uploaded initial build. The issue was broken adb sideload . Now fixed and all should be fine.
Download aicp_instantnoodle_r-16.1-WEEKLY-20210305.zip from HERE
Cheers.

Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Will check it out Thanx for feedback

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.

semdoc said:
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.
Click to expand...
Click to collapse
Will update and report back accordingly. Thanks

passion8059 said:
Will update and report back accordingly. Thanks
Click to expand...
Click to collapse
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.

passion8059 said:
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.
Click to expand...
Click to collapse
LUK merged fixes for all 3 op8 devices today...
So you'll get test builds later today...

hello what interests me can we record the conversation natively?

doc411 said:
hello what interests me can we record the conversation natively?
Click to expand...
Click to collapse
Yes, we have that option in our Dialer.

semdoc said:
Yes, we have that option in our Dialer.
Click to expand...
Click to collapse
thank you very much for your quick rest

New build guys.
You can download aicp_instantnoodle_r-16.1-WEEKLY-20210309.zip from HERE.
-- Please test audio, calls - including whatsapp & telegram calls in all aspects..
-- OOS Style Clear all notificaitons button added
-- Kernel Update by Neutrino kernel dev.
Changelog: link HERE
Cheerz guys

Thanks for the update. Ringing at max is distorted still and there is a severe memory lag where you watch YouTube videos it'll play but then buffer then play again. I'm on a good broadband connection (500mb) and WiFi 6 coverage. Have cleared caches and used ex kernel manager to clear memory buffers but still the same.