Database Develop

[NIGHTLY][ROM][4.0.4] CyanogenMod 9 for the Samsung Vibrant

Please note that there may be intermittent emergency dialing issues and/or GPS/AGPS issues (including GPS daemon crashing, which does not restart) which could hinder location of you in an emergency.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0.4 (Ice Cream Sandwich), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
This thread is for the development of CyanogenMod 9 nightlies for the Samsung Vibrant (aka SGH-T959), the Galaxy S 4G / Vibrant 4G (SGH-T959V) is not supported here. Nightlies are built each night with the very latest code, for this reason, they are extremely experimental and should be avoided by beginners and people who have important responsibilities tied to the usage of their phone.
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 out Gerrit Code Review.
[font=Calibri, Arial]Known Issues[/font]​Probably still has intermittent emergency dialing issues (such as 911) like CM7
See the rest of the issues here.
Please report new issues here:
http://code.google.com/p/vibrant-cm/issues/list
[font=Calibri, Arial]Downloads[/font]​Did you read known issues? No? Go read them.
DO NOT USE AS A DAILY DRIVER​
ROM: http://get.cm/?device=vibrantmtd&type=nightly
Google Apps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
[font=Calibri, Arial]Installing[/font]​... from another CM9 nightly
Reboot into recovery
Do a nandroid backup (just in case)
Install from ZIP
Reboot
If it gives you trouble later, wipe cache, and reboot. If it still gives you trouble, do a full wipe, install again and reboot.
... from CyanogenMod 7 or a CM7-based ROM
Reboot into recovery
Do a nandroid backup (just in case)
Wipe everything (wipe data/factory reset)
Install from ZIP
Optionally install the Google Apps add-on.
Reboot
... from stock 2.2 Froyo
WARNING: Don't install if it's your first time flashing a phone!
Install CWM Recovery by following this guide.
Reboot into recovery.
Wipe everything (wipe data/factory reset)
Install from ZIP.
Optionally install the Google Apps add-on.
Reboot.
WARNING: If you use Titanium Backup to backup your apps do not backup system data or system apps, restoring either of those on CM9 could cause issues.
[font=Calibri, Arial]FAQ[/font]​Q: I can't add my Google account!
A: Install the Google Apps package from CWM recovery, linked above. This is standard procedure with CyanogenMod ROMs due to licensing issues with Google.
Q: Can you enter service mode with *#*#197328640#*#* like CM7?
A: Yes.
Q: I keep getting "Installation Aborted" error 7
A: Install the Glitch kernel and retry.
Q: Where's the changelog?
A: http://changelog.bbqdroid.org/#vibrantmtd/cm9/latest
Q: When will the Linaro tweaks be merged?
A: Don't know.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

[font=Calibri,Arial]How to Build[/font]​First initialize your build environment.
Now follow the "installing repo" section in this guide:
http://source.android.com/source/downloading.html
Now downloading CyanogenMod source:
Code:
mkdir ~/Desktop/CM9
cd ~/Desktop/CM9
repo init -u http://github.com/CyanogenMod/android.git
repo sync -j24
More setup:
Code:
. build/envsetup.sh
breakfast cm_vibrantmtd-userdebug
Getting proprietary files:
You must have a copy of CM9 for the Vibrant running on your phone for this part.
Code:
( cd device/samsung/vibrantmtd && ./extract-files.sh )
Compiling:
Code:
mka bacon

Reserved for cats...

the changelog page is down...

Finally we have CM9 Nightly for the Vibrant! I just flashed the new CM9 nightly and everything is stable and smooth. Thanks again FE!

Great job guys! Flashing ASAP
W00t, first page

Didn't expect CM9 nightlies to roll out this quickly tbh.

Can't wait!!! Been running ExROM 1.3.1 for a while but backing up now to give this baby a shot!
You guys know if this will drop into ROM Manager by any chance? Just wondering, not a big deal if not.

shrty4luv said:
the changelog page is down...
Click to expand...
Click to collapse
It's up for me?

salazar.r1 said:
Can't wait!!! Been running ExROM 1.3.1 for a while but backing up now to give this baby a shot!
You guys know if this will drop into ROM Manager by any chance? Just wondering, not a big deal if not.
Click to expand...
Click to collapse
Eventually, yes, I imagine. If you want it before it does, you can always download it.

Is it just me or is the gapps link down?

Nice! Flashing ASAP

es7241 said:
Is it just me or is the gapps link down?
Click to expand...
Click to collapse
Not working for me either.
You can use ROM Manager. Or you can use this link:
http://download2.clockworkmod.com/gapps/gapps-ics-20120304-signed.zip

The changelog page is working, but there seems to be a problem with the link to the gapps.

salazar.r1 said:
Can't wait!!! Been running ExROM 1.3.1 for a while but backing up now to give this baby a shot!
You guys know if this will drop into ROM Manager by any chance? Just wondering, not a big deal if not.
Click to expand...
Click to collapse
Me too! ExRom has been great, wonder what this will be like.

is update-cm-9-20120331-NIGHTLY-vibrantmtd-signed.zip safe to flash I see its 120mb not around 90 like the rest
i get assert failled getprop status 7 error

defconoi said:
is update-cm-9-20120331-NIGHTLY-vibrantmtd-signed.zip safe to flash I see its 120mb not around 90 like the rest
Click to expand...
Click to collapse
Yes. CM9 is bigger than CM7

defconoi said:
is update-cm-9-20120331-NIGHTLY-vibrantmtd-signed.zip safe to flash I see its 120mb not around 90 like the rest
i get assert failled getprop status 7 error
Click to expand...
Click to collapse
Possible bad download or bad copy to SD, I didn't get an error.
edit - I'm wrong, my bad.

Henchmin said:
Possible bad download or bad copy to SD, I didn't get an error.
Click to expand...
Click to collapse
Toggle script asserts.

The boot animation is tits.

[ROM][N5110]Official Nightlies CM11.0[KTU84P][4.4.4]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
INSTRUCTIONS
First time installing CyanogenMod 11.0 to your Galaxy Note 8 N5110, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM11.0 ZIPs to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 11.0:
- Copy CM11.0 ZIP to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Reboot
BUG LIST
-BT Voice Search
[Nightlies] http://download.cyanogenmod.org/?device=n5110
[GAPPS 4.4] http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
[CWM 6.0.4.4 w/ swipe] Heimdall: http://www.androidfilehost.com/?fid=23212708291675367
OUTDATED:
[11/11] ROM: http://www.androidfilehost.com/?fid=23212708291676598
CHANGES:
-Initial Release
[12/2] ROM: http://www.androidfilehost.com/?fid=23252070760972532
Changes:
- Upstream CM merges (yes home button recent apps is back)
- fixed internal sd / storage
[12/10] ROM: http://www.androidfilehost.com/?fid=23252070760974755
Changes:
- Upstream CM changes (includes fix for rotation distostortion)
Source: http://github.com/CyanogenMod

Yes this is an updated build from the one I posted in the 10.2 thread

A quick pointer to the PA Gapps thread:
http://forum.xda-developers.com/showthread.php?t=2397942
There's a lighter version of the Gapps package there if you don't use so many of the Google services, and it should always have links to up to date versions.
Don't forget to format your system partition and re-flash the whole ROM if you are changing between GApps versions, or you may have some leftovers from the previous version.

Wrong Thread......

testing the 11-11 built. Seems like there is a problem accessing files on the /storage/emulated/legacy (or 0).
Can't delete anything. Can't modify anything... but you can browse... Read Only almost like?

Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4

I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?

kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Click to expand...
Click to collapse
If you have a recovery that work with this build, could you share it here ?
thanks

kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?
Click to expand...
Click to collapse
Posted my heimdall in the OP, can you just shoot up a link to your odin copy?
The difference that I've noticed in the 2 are the PA gapps have the "OK google" feature. Maybe they both do but I noticed it after flashing the PA gapps

That's what I just did:
- boot into recovery (rename the attached file to recovery.tar.md5 and flash it with odin) (or download it from here: https://mega.co.nz/#!J18HxR7C!WJMuYhLvpYCPlN-giWs2u0Sr4wRzgBvajTNOP_L5gyU)
- "format /system"
- "format /cache"
- flash cm_n5110-ota-sbrissen_11-11.zip
- flash pa_gapps-full-4.4-20131111-signed.zip
Issues:
- back- and menu-button are not working (sometimes I can close popup-messages with the back-button)
- /storage/emulated/0 not writeable (as already stated by mbze430)
- gallery is not working
- no screenshots
- screen goes a bit crazy during rotations
Edit: I tried to install Root Explorer via the Play Store, but no keyboard showed up. Voice search did work. After I have started Root Explorer and set / to be rw the back- and menu-buttons are working and the keyboard showed up too.

PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.

PdroidAndroid said:
Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4
Click to expand...
Click to collapse
Hey
I got this same error, what I did was that I flashed the TWRP aroma touch recovery from the XDA thread for GT-N5110 and it worked like a charm!
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2483844

mbze430 said:
PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.
Click to expand...
Click to collapse
Checking the extSdCard issue now. CM just forked my repos last night, I'll start the process to get 10.2 nightlies going. They have not start 11.0 nightlies for any devices yet.

I can also confirm the sdcard not being writable. I'm thinking between that and the extSdCard strangeness perhaps the storage just gets mounted weirdly upon boot.
In addition, it seems to me that long pressing the home button no longer brings up the recent apps drawer.

This version installed without a hitch and aside from the SD card issue, works great!
Also, not that important but Im just curious- why can't I get the launcher looking like kitkat? It still retains jelly bean look even after third party launchers and what not.
Thanks and when the funds allow I'd be glad to donate!

Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
Two questions I have:
- When it will be available to download from CM official site.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!

titotito1983 said:
Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!
Click to expand...
Click to collapse
Simple answer is no. From the way things look, it will never. You will need 3rd party apps to get some of those features back

Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Jaimemex said:
Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try the TWRP Aroma Touch recovery, it works like a charm and no error occured to me
Sent from my GT-N5110 using XDA Premium 4 mobile app

kinda quiet in here... did everyone jump back to 10.2?? lol

[ROM][4.4][NIGHTLIES]OmniROM[Xperia T][mint]

OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance, reliability and features over stock Android for your device.
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. Hard. A lot.
*/
OmniROM 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.
All the source code for OmniROM is available in the OmniROM Github repo.
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
Official OmniROM Wiki:
http://docs.omnirom.org
First time installing OmniROM to your Xperia T, or coming from another ROM:
- Read known issues and FAQs
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM ZIP to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Issues:
AFAIK none at all
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
Nightlies:
http://dl.omnirom.org/mint/
Questions:
Feel free to ask here or in #omni on irc.freenode.net
To Kangers:
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open Source doesn't mean Out of Respect!
XDA:DevDB Information
OmniROM, a ROM for the Sony Xperia T
Contributors
tilal6991
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Testing
Created 2013-11-14
Last Updated 2014-05-05

Reserved
Changelog:
30/03:
Switched to the 4.3 kernel from Sony: this fixes stability issues (i.e. blue screens) and MHL (HDMI out)
28/11:
Nighlies begin
26/11:
Sync with Omni sources - many new features and loads of settings have been added
Improve performance by using qcom branches of Omni repos - will become mainline soon
Add SELinux stuff - will become enforcing in the next version
Fix apps disappearing off SD card every reboot.
Other bug-fixes
19/11:
Sync with Omni sources
Hopefully fix any Bluetooth audio issues
Make ART compatible with previously incompatible apps (WhatsApp etc.)
Fix in-built TWRP mounting issues
13/11:
Initial release

Derp.

First!
This is wonderful news! Hope to try it soon thanks
Is this initial build without ril bug right? And can i ask also if gps is working?

moly82 said:
First!
This is wonderful news! Hope to try it soon thanks
Is this initial build without ril bug right? And can i ask also if gps is working?
Click to expand...
Click to collapse
If you had read his messages (for example, in Thomas' threat), you would not ask.

I did read in issues only no hdmi out but who knows.. it seems strange to me that's the only problem in the first experimental build and unfortunately I won't be able to try it before tomorrow evening (no internet) ;( well I'll see tomorrow great job in any case tilal thanks for keeping developing on T :good:

Yes RIL and GPS are both working in any case. That is why HDMI out is listed as the only bug.

You are great at last a official thread about omni can't wait to try it thanks to you!

Downloading
Has anybody tested the multi-window, does it work?
EDIT: Multi-windows IS working, haven't had anny issue so far. Thanks tilal =D

Everything seems to be running smoothly, even without full wiping from CM 10.2. Unfortunately, it seems that the OmniROM features haven't been included in this series of nightly builds, so I'll probably hold until they are merged.
Good work, @tilal6991!!!

Fantastic work @tilal6991!
Just flashed and had a little play. So far so good. Alas, I'm up for work in 5 hours so I need to sleep. Will use fully tomorrow and will report back.
Again, nice one.

Great!!! Good luck
Sent from my Xperia T using XDA Premium 4 mobile app

Awesome stuff Tilal, typically i had a few hours off to play some BF4 so will have to flash this tomorrow now :good:

Bootloader should be unlocked to install this ROM, correct?
Sent from my LT30p using xda app-developers app

acr82 said:
Bootloader should be unlocked to install this ROM, correct?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Yeap, as always!
Sent from my Nexus 10 using Tapatalk 4

why I see status 7 when I Was Flashing And Flashing failed???
What should I Do???

Mahthenewgamer1998 said:
why I see status 7 when I Was Flashing And Flashing failed???
What should I Do???
Click to expand...
Click to collapse
Make sure the file you downloaded isn't corrupt, you can also wipe data before flashing

for any reason I am always stuck on boot after flashing...I followed instructions in OP precisely of course...feel a little noobish :silly:
EDIT: ok, got it workin now...that's what I did (maybe useful for others in same situation):
- flashed OMNIRom 4.3 first
- booted in Recovery
- flashed OMNIROM 4.4
- Full Wipe
- reboot
- booting back in Recovery
- flashing Gapps
- reboot
fyi, I was coming from latest MIUI

First of all, thanks tilal for your great work!
Not any major issue so far. Sound seems a bit laggy though. I also got 2 blue screens.

Suggested recovery for flashing this? TWRP?

[ROM] Official LineageOS 14.1 for Falcon (WEEKLY)

Code:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* 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.
*/
About
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
some words of wisdom:
WIP
Latest features :
XDA:DevDB Information
LineageOS 14.1 for Falcon (WEEKLY), ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, LineageOS Team, Motorola
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2017-01-26
Last Updated 2017-02-01

Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
​HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: as with CM14.1, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
HOW TO DIRTY UPDATE
Same as above, without the need of wiping of reflashing gapps.
HOW TO COME FROM CM13/14?
The Best practice way is to follow the clean install way.
BUT it is also possible to update from CM13/14 using an EXPERIMENTAL data migration build.
Here are the Official recommendations :
This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
The process for this installation will be as follows:
Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
Reboot
Install LineageOS weekly build
Reboot
Re-setup your application permissions
Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.
Click to expand...
Click to collapse
As Always, DO A TWRP BACKUP before trashing your device!

Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Question?[/SIZE]answer​ [SIZE=+1]Q2: How to get Root?[/SIZE]
go to : https://download.lineageos.org/extras
and choose "su (arm)" download.​

It's been a long journey since I brought this device... Thank you so much Dev for supporting my 4 years old device... Downloading... LineageOS for falcon... Fingers crossed...

Long live falcon!

Great job!

Question, is there a list of what is working and not working on this rom as far as of hardware?
Thanks

Finally... Officially Supported.
thanks man.

Long live falcon and God bless the developers.
Sent from my Moto G using Tapatalk

theplagueisback said:
Question, is there a list of what is working and not working on this rom as far as of hardware?
Thanks
Click to expand...
Click to collapse
Basically, what worked on CM14.1 works on Lineage on this device, I didn't thoroughly tested it, but I didn't encounter much regressions after the migration (I performed the "Experimental" migration, to be in worse case scenario)

long live my (g)old device

ROM installed, so far so good, device performs as good as a brand new kick ass phone.
Keep up the good work!

Clean installed, seems to be good...

Someone tried if it works Xposed?

seba2907 said:
Someone tried if it works Xposed?
Click to expand...
Click to collapse
:facepalm:

seba2907 said:
Someone tried if it works Xposed?
Click to expand...
Click to collapse
Xposed is not yet available for nougat.

abeloman said:
:facepalm:
Click to expand...
Click to collapse
Sorry for not being at your senior level
BryanByteZ said:
Xposed is not yet available for nougat.
Click to expand...
Click to collapse
Thanks for your answer, I'm in cm13 and i thought it already worked for nougat

seba2907 said:
Sorry for not being at your senior level
Thanks for your answer, I'm in cm13 and i thought it already worked for nougat
Click to expand...
Click to collapse
I'm preying for that its the only thing that hold me on MM.

My 5X is dead. It's time to revive my g1

noice. falcon ftw!

[UNOFFICAL] [RECOVERY] [FBE_V1/V2] OrangeFox Recovery R10.0 / R12.1 for Xperia 1 II

WARNING: THIS IS UNOFFICAL BUILD, USE IT AS YOUR OWN RISK.​
Code:
/*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*
*/
OrangeFox R12.1 build Support ROMs which using FBE_V2 only, for example: Lineage OS 19.1/20 by @clfbbn.
About FBE_V2, see Google's documents please: https://source.android.com/docs/security/features/encryption/file-based
If you're using ROM with FBE_V1, you should use the recovery which support FBE_V1 to make data decryption works well.
OrangeFox R10.0 build Support ROMs which using FBE_V1 only
for example: Lineage OS 17.1 by @Sjll , sony stock Android 10/11
INSTALLATION:
First, reboot your phone to bootloader and connect your phone with PC.
Then type in your terminal(like CMD, powershell and so on):
Code:
fastboot flash recovery <the-file-name-of-recovery-image>
If you wanna reboot to recovery now, type:
Code:
fastboot reboot recovery
Okay, you can enjoy it imperfect UNOFFICAL recovery now
WORKS:
Decryption (R12.1 build only work on FBE_V2 ROMs, R10.0 build only work on FBE_V1 ROMs)
Fastbootd
Adb sideload
Flash zip file(You can use it flash @clfbbn's Lineage OS).
Touchscreen.
Vibration (It has been fixed on OrangeFox R12.1 230221 builds)
NOT WORKS:
Vibration (Sorry, I am a real noob, ask our pro plus ultra dev bootloopuru who build TWRP without ANY XPERIA device to solve it xD)
Decryption on Sony Xperia Stock Android 12 ROM (I am not sure about the reason: maybe TWRP branch 12.1 only support FBE_V2 decryption for device which using Android 12+ ROM with FBE? )
Some strange layout (I don't want to do anything about it for now, because OrangeFox's UI is not compatible with our 21:9 long screen）
Vibration has been fixed on R12.1 branch after 230221 builds, thanks to @sekaiacg.
Layout has been fixed after 230215 builds, sorry for OrangeFox team, I am noob, I forget to set OF_SCREEN_H values.
I am sorry for my blame and my noob jobs.
OTG (Okay, I will try to fix it if I have enough time.)
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
* clfbbn - for his kernel source
* sekaiacg - for his twrp device tree for umi
* cramfs28 - for his help
* lolipuru - Okay, he got a real Xperia 5 II and fix many issues now, I really thank to him, but I still hate someguy build rom/recovery without devices.
Downloads:
Please download the LATEST build for the branch you need to use (R10.0 or R12.1).
My noob project in sourceforge, flash it as your own risk: https://sourceforge.net/projects/homosenpai/files/Recovery/OrangeFox/
Device Tree:
GitHub - ShirokaneShizuku/twrp_device_sony_sm8250
Contribute to ShirokaneShizuku/twrp_device_sony_sm8250 development by creating an account on GitHub.
github.com
(Actually who care about it lol, The open source community is getting worse, some pro guys even build ROM for the device they don't have, haha)
Bug Report:
Please report it wit log please, and because this is a noob UNOFFICAL build, I can't fix bugs as soon as possible, thanks for your understand.
Donation:
Hey guys,Why would you donate to someone who hasn't contributed to the open source community?

1. Why you keep repeating that this is an UNOFFICAL build？
Because some bad guy thinks my previous releases are pretending to be an official build (actually I put UNOFFICAL tag in the title every time)
2. Hey guys, can you help me compile a ROM or Recovery for a XXX device?
NO, absolutely NOT, I would not do such a thing. All released builds should be rigorously tested by developers, at least to ensure that the basic functions are effective, which is the basic guideline of the open source community.
I'm not an unprincipled and no bottom line guy like lolipuru, if you want bootloop go for that guy, they're good for nothing but messing with the community
3. Hey man why are you so aggressive can you calm down？
Sorry I may seem grumpy, but I can't stand someone taking something from the open source community and doing it badly irresponsibly
4. What can I do if I am using FBE_V1 ROMs ?
Please use OrangeFox-R10.0-Unofficial-pdx203-230217.img.
5. When I use OrangeFox-R10.0 on Android 11 ROMs, I got some error about APEX, what can I do?
I am sorry for that, but please ignore it now, or wait for the OrangeFox 11.0 builds.
6. Why you don't build OrangeFox-R11.0 for Xperia 1 II ?
I am sorry about it, I face some strange issue: like decryption dead or touchscreen not work, I need time to figure out about it, as you see, I am noob here QwQ.
7. Hey, why not you build TWRP bro?
I am tired, I don't wanna sync source again now. If I have enough time, I will build it.

Update Log:
2023-02-15:
Fix strange layout, sorry for OrangeFox Team, I am very sorry for that QwQ
2023-02-17:
Fix strange layout for OrangeFox R10.0 build (which build for FBE_V1) and release it now.
2023-02-21
Fix vibration for OrangeFox R12.1 build, thanks to @sekaiacg and TWRP Teams. (Our device should use QTI AIDL for haptic)

Thanks for making the recovery, and after some update it's became very good. Also waiting for your derpfest update

leomate said:
Thanks for making the recovery, and after some update it's became very good. Also waiting for your derpfest update
Click to expand...
Click to collapse
You're welcome bro, but I will not update derpfest build because I am busy until July this year.
Absolutely I can build it, it only take my PC's 3 hours, but I need to test and debug it (basicly I need to make sure it's bootable), I will not release ANY build that have not been tested.
No matter what, thanks for your appericate

RealNoobKanger said:
You're welcome bro, but I will not update derpfest build because I am busy until July this year.
Absolutely I can build it, it only take my PC's 3 hours, but I need to test and debug it (basicly I need to make sure it's bootable), I will not release ANY build that have not been tested.
No matter what, thanks for your appericate
Click to expand...
Click to collapse
Ahh that's okay. I just feel when this recovery saving me from the hassle. That's what I'm using from my old phone.
As long the ROM stable enough for me (no memory leak like stock rom) its good, and the 3-finger screenshot feature that I'm miss a lot when switch to Xperia phone. It's rare to see a flagship SOC with microSD slot.
Anyway, thanks for once again for the effort making Recovery :3

leomate said:
Ahh that's okay. I just feel when this recovery saving me from the hassle. That's what I'm using from my old phone.
As long the ROM stable enough for me (no memory leak like stock rom) its good, and the 3-finger screenshot feature that I'm miss a lot when switch to Xperia phone. It's rare to see a flagship SOC with microSD slot.
Anyway, thanks for once again for the effort making Recovery :3
Click to expand...
Click to collapse
Vibration should be fixed on 230221 R12.1 build, enjoy it!

Is there no hope for decrypting stock 12? What kind of bullcrap did Sony pull off with it

Xspeed said:
Is there no hope for decrypting stock 12? What kind of bullcrap did Sony pull off with it
Click to expand...
Click to collapse
TWRP's decryption might be work now on Xperia stock Android 12, refer to it:https://github.com/TeamWin/android_bootable_recovery/commit/9ab7cf500595c9809142c3294ca477fcedf7e56d

Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before

Xspeed said:
Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before
Click to expand...
Click to collapse
Do you change the fstab? Maybe you need to change it to adapt to Stock Android 12

Xspeed said:
Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before
Click to expand...
Click to collapse
Do you using Xperia Stock android 12 bro? I am using MIUI for Xperia 1 II now, I don't wanna flash to Stock android 12 again (backup take too many time for me)
If you wanna try to decrypt Stock android 12, you can change the mount flags about data and Metadata, make sure it same with Stock ROM

RealNoobKanger said:
1. Why you keep repeating that this is an UNOFFICAL build？
Because some bad guy thinks my previous releases are pretending to be an official build (actually I put UNOFFICAL tag in the title every time)
2. Hey guys, can you help me compile a ROM or Recovery for a XXX device?
NO, absolutely NOT, I would not do such a thing. All released builds should be rigorously tested by developers, at least to ensure that the basic functions are effective, which is the basic guideline of the open source community.
I'm not an unprincipled and no bottom line guy like lolipuru, if you want bootloop go for that guy, they're good for nothing but messing with the community
3. Hey man why are you so aggressive can you calm down？
Sorry I may seem grumpy, but I can't stand someone taking something from the open source community and doing it badly irresponsibly
4. What can I do if I am using FBE_V1 ROMs ?
Please use OrangeFox-R10.0-Unofficial-pdx203-230217.img.
5. When I use OrangeFox-R10.0 on Android 11 ROMs, I got some error about APEX, what can I do?
I am sorry for that, but please ignore it now, or wait for the OrangeFox 11.0 builds.
6. Why you don't build OrangeFox-R11.0 for Xperia 1 II ?
I am sorry about it, I face some strange issue: like decryption dead or touchscreen not work, I need time to figure out about it, as you see, I am noob here QwQ.
7. Hey, why not you build TWRP bro?
I am tired, I don't wanna sync source again now. If I have enough time, I will build it.
Click to expand...
Click to collapse
我想知道这可不可以在中国版本上使用？
I want to know if this can be used on the Chinese version?

I have sony xperia 1 ii au version. I have unlocked bootloader and downloaded europe rom from sony xperfirm and installed it now I’m getting no sim card emergency only. How to solve this please help me