Sorry all for the delay in dev time, I have progressed to an new organization that will be helping support my development and work. The WMD Package, Framework, and Project as a whole will see new developments and features as I progress. Thanks to all for following and I will keep all updated.
-Kizz
WMD NEWS - THE Motorola Xoom WILL BE NEXT!!!BOOM!!! ENCOURAGEMENT!!
___________________________________________________________________________
WMD 1.0: Devil's Hand Edition LIVES!!!!Is NOW AVAILABLE FOR DOWNLOAD!!
{
"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"
}
Sorry to all that downloaded it and could not extract it, I must have still been a little bit hung over from the conferences this weekend and posted links without the password.
The password for ALL files is: [email protected]
WMD 1.0: Devil’s Hand Edition – 8GB MicroSD card required
www.kizzmyanthia.com/WMD/DHE/DHE.zip
www.kizzmyanthia.com/WMD/DHE/WMD_1.0-8GB.zip
WMD 1.0: Devil’s Hand Edition – Lite – 4GB MicroSD card supported
www.kizzmyanthia.com/WMD/DHE/DHE.zip
www.kizzmyanthia.com/WMD/DHE/WMD_1.0-LITE.zip
WMD 1.0: Devil’s Hand Edition – Install required Initrd.gz
www.kizzmyanthia.com/WMD/DHE/WMD_DHE_Install.zip
— You will need to download one of the above versions and this initrd.gz file to use the installed version, if you choose to create a SWAP partition on the MicroSD card you will need to edit the FSTAB file located at /etc/fstab once you launch The WMD Package. If you choose not to create a full swap partition include the swap.img file that is included in the above downloads on the FAT32 partition and it will be used as extended swap space.
WMD 1.0: Devil’s Hand Edition – Background Image
www.kizzmyanthia.com/WMD/DHE/wmd-dhe-back-1.jpg
WMD: Living Dead Edition 0.2 HAS ARRIVED!!!!
Full Details, Downloads, and Instructions available in post 16, click here to jump to the post.
NEW!!! Unsplit links have been posted to HERE.
- WMD: FFB Edition 0.1 -
* Mobile Penetration Testing Platform and the Weaponizing of the Smartphone *
**** More Information at KizzMyAnthia.com****[/CENTER]
Twitter: @kizz_my_anthia
Facebook: /KizzMyAnthia
Ok, first I want to say this has no direct relationship to the ORIGINAL BackTrack provided by Remote Exploit, http://www.backtrack-linux.org/.
BUT a huge shoutout goes out to everyone at Remote Exploit, Offensive Security, and all of the community members. Without you guys, your dedication, and vision I would not be where I am today.
Please!! Visit the site http://www.backtrack-linux.org/ show them some love, they need it.
I also want to give props and shout outs to the devs from Rhobuntu
• Gzwalter79
• Andrewinworking
• Ondraster
• Calaghan4410
• Boushh
And Props go out to everyone on the XDA Developers site.
I know I am either forgetting someone or have not listed someone, don’t take it as an offence by all means it is not meant to be, but You’ll be alright, You’ll bounce back
Ok, Ok, Ok to get on with it.
This while in production was called BackTrack Mobile Beta 0.1
I have given it a little naming update as we get ready with the FFB Edition.
From here on out this will be known as WMD: FFB Edition.
This project started as just a minute thought of DAMN, how cool would it be to have backtrack on my phone. I looked at running this under Debian, but ran into some power management issues on the testing platform, AT&T Fuze.
So now thankfully from the Devs over at Bactrack-Linux and Remote Exploit BackTrack is now based on Ubuntu. SCORE!!
And being a member of the XDA-Developers forum I have been following the ROMs and smartphone development for a number of years.
I am posting this in the Rhodium forum because that is the platform that I have been able to do my development on.
This release is based on Ubuntu 9.04.
Using Haret and as many of the apps and tools from Backtrack 4 that I could possibly stuff into the build.
The next version will be much lighter, have the swap partition load automatically, and have an all around smoother run.
The image can be downloaded from : IT IS FINALLY HERE
WMD: FFB Edition Live MicroSD Version – YOU MUST DOWNLOAD ALL 11 FILES
Code:
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.zip
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z01
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z02
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z03
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z04
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z05
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z06
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z07
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z08
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z09
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Live.z10
Looks like there was a little mix up when I packaged everything for download.
Here is the proper INITRD.gz file for the above WMD: FFB Edition Live 0.1
Code:
http://www.kizzmyanthia.com/WMD/WMD_LIVE_INITRD.zip
WMD: FFB Edition Installable MicroSD Version – YOU MUST DOWNLOAD ALL 11 FILES
Code:
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.zip
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z01
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z02
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z03
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z04
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z05
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z06
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z07
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z08
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z09
http://www.kizzmyanthia.com/WMD/WMD_FFB_Edition_Install.z10
These were split using IZArc, freely available at www.izarc.org, and I recommend using it to rejoin the files. I have no association with IZArc, but have used it for a very long time.
To give you a better understanding of what WMD and Backtrack is below you will find an excerpt from http://backtrack.offensive-security.com/index.php/Offensive-security.com:General_disclaimer with a few details.
What is BackTrack ?
BackTrack is the most Top rated Linux live distribution focused on penetration testing.
It’s evolved from the merge of the two wide spread distributions – Whax and Auditor Security Collection. By joining forces and replacing these distributions, BackTrack has gained massive popularity and was voted in 2006 as the #1 Security Live Distribution by insecure.org.
Security professionals as well as new comers are using BackTrack as their favorite toolset all over the globe.
Being superior while staying easy to use is key to a good security live cd. We took things a step further and aligned BackTrack to penetration testing methodologies and assessment frameworks (ISSAF and OSSTMM). This will help our professional users during their daily reporting nightmares.
Currently BackTrack consists of more than 300 different up-to-date tools which are logically structured according to the work flow of security professionals. This structure allows even newcomers to find the related tools to a certain task to be accomplished. New technologies and testing techniques are merged into BackTrack as soon as possible to keep it up-to-date.
What Backtrack is NOT?
- A Script Kiddy Heaven
- A General Purposes OS
Conditions of Usage & Law related disclaimer :
As an express condition of this License, You agree that You will use BackTrack and WMD in compliance with all then-applicable local, state, national, and international laws, rules and regulations as may be amended or supplemented from time to time, including any then-current laws and/or regulations into Your country of residence.
We do not condone any illegal activity at all. Any advice/information offered in these forums is to be used for the legal informational/professional/educational purposes for which it is intended.
Our liability is limited and excluded to the maximum extent permitted under applicable law.
We will not be liable for any direct or indirect loss or damage arising under this disclaimer or in connection with the misuse of BackTrack, WMD, or the installed tools. We will not be liable for any loss of profit, contracts, business, goodwill, data, income, revenue or anticipated savings in connection with our software, whether direct or indirect.
Violation of any of the foregoing will result in immediate, automatic termination of this License without notice, and may subject you to state, national and/or international penalties and other legal consequences.
So what do I do???
How do I use it, will this thing actually work?????
First and foremost, EVERYTHING YOU DO IS AT YOUR OWN RISK!
One more time.
EVERYTHING YOU DO IS AT YOUR OWN RISK!
Your device was not designed to run GNU/Linux and that is why the expectation should be understood that everything will not be perfectly safe. If you do not want any issues to arise then LEAVE YOUR PHONE ALONE. At the same time, running and using this build, WMD, and the associated tools is probably safer than installing a cooked ROM. This is because of the way WMD and Haret interact with the host. These applications do not touch the host ROM and run completely from the Micro SD card they are copied to. If there is an issue that arises you can remove the battery and when the device reboots it will return you to the Windows Mobile host. At the same time, THERE IS NO GUARANTEE that anything works and I am NOT LIABLE FOR ANY DAMAGE THAT MAY OCCUR. IF YOU HAVE ISSUE WITH THIS OR ARE NOT SURE DO NOT INSTALL IT.
Per the Rhobuntu Wiki – This is detailed due to Rhobuntu being the base for WMD:
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
• After booting back into WinMo, you can’t install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset.
o I have NOT experienced this issue during ANY testing.
• Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them.
Rhobuntu related legal information:
Rhobuntu basically consists of three parts, namely the kernel, the original rootfs and tweaks to the original rootfs.
The kernel comes from this repository http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm . You can download it already compiled from here http://glemsom.anapnea.net/android/htc-msm-android/# For more information please visit http://htc-linux.org/wiki
The original rootfs originates from the Ubuntu ARM Port Project https://wiki.ubuntu.com/ARM. Ubuntu developers provide a tool called rootstock which allows everybody to create a preconfigured rootfs. That’s how we created a rootfs for Rhobuntu.
Neither the kernel nor the original rootfs are in any way related to the Rhobuntu project. We only use them according to the terms of the GPL license.
The main task of the Rhobuntu developers is combining the kernel and the rootfs in a way that it can become a proper linux distro for the supported HTC devices. To achieve that we mostly modify the rootfs, by adding/removing/tweaking drivers, apps or services.
The above is also directed towards WMD as RHOBUNTU is the base for the entire OS.
What’s Working, What’s Not
Working as of: 19.09.2010
• Phone
• Sound (partial)
• SMS
• GPS (partial)
• Display Calibration (all devices)
• Keyboard & Hardware Key Mappings
• Screen Rotation* Virtual Keyboard (End Call button on Rhodium 100)
• Backlight (all devices)
• WiFi (bcm4329 has problems with Ad-hoc, workaround for Ad-hoc ; for wl1251 you need to change eth0 to wlan0 in wicd preferences)
• 3G Data with HSDPA – thanks amiPro (all devices)
• Shutdown (via Menu -> Log off -> Reboot, all devices)
• Installing Apps via apt-get or Synaptic (all devices)
• SD card access (all devices)
• Charging (all devices?)
• Dynamic CPU scaling (all devices?)
• Sleep (partial, backlight is still on, must be disabled via brightness control) on pressing Power (Rhodium only?)
• Manual brightness control via Shift+4 and Shift+5 (Rhodium and Tilt2 only?)
• Bluetooth (partial)
Not Working as of: 19.09.2010
• FM Radio (all devices)
• Full “Sleep”; Power Management (all devices)
• Full Sound (all devices)
• Camera (all devices)
• Sensors, LEDs etc.(all devices)
• Aircrack-ng (all devices)
OK SO HOW DO I GET THIS THING ON MY PHONE???
There are three options to getting this working.
1. The first two are to follow the steps below. Just a heads up, you WILL need high speed internet to download this or you will be waiting for a LONG LONG time.
a. Live OS Version (Limited Storage Space)
b. Installed OS Version (Storage Space Limited To Size of MicroSD Card)
2. The third option is to order a preconfigured SD Card and I also offer pre-configuration options. CHECK “The Black Market” ON www.KizzMyAnthia.com FOR MORE INFORMATION ON ORDERING YOUR PRE-CONFIGURED SD CARD.
We will follow similar installation steps as setting up Rhobuntu:
I AM AWARE THAT THE LOADING TIME STILL IS LONGER THAN REALLY WANTED (+/-10 min to completely load) BUT ONCE FULLY LOADED RUNS SMOOTHLY, ESPECIALLY WITH THE ADDED SWAP PARTITION.
Be patient during loading, it may seem that it has frozen or stalled, but this is not the case.
This requires a minimum size of an 8GB SD Card.
Step 1
For the LIVE VERSION follow the instructions below:
• Download the WMD_FFB_Edition_Live.zip files
• Extract the contents
• Copy the files to your MicroSD card as follows:
o /Storage Card/UBUNTU/haret.exe
o /Storage Card/UBUNTU/STARTUP.txt
o /Storage Card/UBUNTU/INITRD.GZ
o /Storage Card/UBUNTU/zImage
o /Storage Card/Ubuntu.img
o /Storage Card/swap.img (OPTIONAL IF YOU WANT TO USE EXTENDED RAM/SWAP SPACE)
• **OPTIONAL** When WMD: FFB Edition 0.1 has completed to boot run the following to load the swap partition
o Open the terminal
o Type: cd /sdcard/
o Type: swapon swap.img
* To verify the swap space is available type: free –m
For the INSTALLED VERSION follow the instructions below:
Download the WMD_FFB_Edition_Install.zip
Step 1
• First split your SD Card into 2 partitions
o The first partition should be 600mb – 1GB in size (This can be done via Gparted)
* This is where the boot applications and SWAP space will reside as well as any files that you would like to transfer into WMD from WinMo
o The second partition should be the remaining space on the SD Card.
• Copy the files from the UBUNTU folder to the first partition of your SD Card.
The file structure should look like this
• /Storage Card/ubuntu/haret.exe
• /Storage Card/ubuntu/STARTUP.txt
• /Storage Card/ubuntu/initrd.gz
• /Storage Card/ubuntu/zImage
• /Storage Card/swap.img
You will see a file called wmd.img. We will need to mount this file and copy the contents to the large, “second”, partition of the SD Card.
Execute the following to begin the transfer (THIS SHOULD BE DONE AS ROOT OR ENTER SUDO PRIOR TO EACH COMMAND)
• cd <enter location where you extracted the downloaded files>
• mkdir /wmd/
• mount wmd.img /wmd -o loop
• gksudo nautilus
o Browse to /wmd
o Copy ALL files to the “second” partition of the SD Card
* “Skip All” when prompted, this is an expected error, ignore it
Step 2
Rhodium / Touch Pro2 / Tilt 2 owners
• Edit STARTUP.txt and change the “physkeyboard” option. At the moment you can choose between “physkeyboard=rhod100uk”.
rhod100_de –> german rhodium
rhod100_fr –> french rhodium
rhod100_it –> italian rhodium
rhod100_uk –> english rhodium
rhod210 –> rhodium 210
rhod400 –> rhodium 400
tilt2 –> tilt2
• If your Rhodium is CDMA, edit STARTUP.txt and change “htchw.force_cdma=0″_ to “htchw.force_cdma=1″
Topaz / Touch Diamond2 owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2293″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=”0x9f.0x39a.0x35c.0×78″
Diamond owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 1805″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=”0xc5.0×399.0×367.0x4d”
Raphael / Touch Pro / Fuze owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 1910″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0x7a.0x5e.0x35a.0x37f”
• change “physkeyboard=rhod100uk” to “physkeyboard=raph” or “physkeyboard=fuze”
Blackstone / Touch HD owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2030″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0×395.0x3c9.0×79.0×77″
Kovsky / Xperia X1 owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2006″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0xc5.0×399.0×367.0x4d”
• For keyboard setting read this: http://forum.xda-developers.com/showpost.php?p=6993913&postcount=1105
Step 3
Launch Haret.exe
* Browse to /Storage Card/UBUNTU/Haret.exe and Launch
For more information related to using your phone while in WMD:
• Read this: http://forum.xda-developers.com/showpost.php?p=6453098&postcount=900
For more information on how to work with the WMD, Rhobuntu GUI, interface, what apps do and do not work on the platform read here, http://forum.xda-developers.com/wiki/index.php?title=Ubuntu_on_the_Rhodium
If you would like to import your contact list into WMD you can find more information about it at:
• http://forum.xda-developers.com/showthread.php?t=709101
.
As the project moves forward I will post updates and more information, but Please let me know what does and does not work.
AND ONCE AGAIN, PROPS TO EVERYONE THAT HAS WORKED ON THESE APPS LONG BEFORE I WAS EVER A PENTESTER. THANK YOU GOES OUT TO EVERY DEV OUT THERE THAT GAVE ME A FEW MOMENTS OF YOUR TIME TO ANSWER MY QUESTIONS, DEAL WITH MY RANTING, AND OTHER LATE NIGHT QUANDARIES.
The following links helped me get through issues, questions, google searches, etc and I wanted to say thank you for others asking questions before I ever could.
• http://ubuntuforums.org/showthread.php?t=519859
• http://forum.xda-developers.com/showthread.php?t=640785&page=99
• http://www.ubuntu-unleashed.com/2008/04/howto-restore-all-installed-packages-in.html
• http://wiki.mediatemple.net/w/Backup_and_Restore_Installed_Packages
• http://forums.remote-exploit.org/bt4beta-howtos/20328-ubuntu-backtrack-few-easy-steps-2.html
• https://bugs.launchpad.net/nexenta/+bug/335056
There are many other posts, blogs, and searches that I performed, but these are some noted ones. To any that I have forgotten, once again, Thank you.
Holy $HIT!!! Is this truly feasible? This is a dream for me! BT is one of my all-time favorite custom distros, as far as unique feature sets is concerned. This is probably going to upset my wife, when I don't sell my Rhodium to pay for my Nexus S...
Boot time baby!!
Just fixed the boot time issue.
Brought the complete boot time back down to a respectable 3-4 minutes for a complete boot.
I will post the updates here and on www.kizzmyanthia.com as soon as I have complete details.
Technical Specs and Installed Applications - Version - Description
I have just posted the complete details of the hardware and the installed applications. The details are to long to post on this forum check out the following:
Technical Specs:
http://kizzmyanthia.com/?p=88
Installed Apps:
http://kizzmyanthia.com/?p=113
Money Shot
As Promised!!
Screenshot Posted
............
First of all, congratulations for this amazing job. This is a truly fantastic achievement.
I've been trying to install this in my Rhodium but have had some issues. It looks like it can't mount the partition. I've kept one partition as Fat32 where I have the Ubuntu folder and all other files accessible by WM and created an extended partition where I copied all the files in the image file.
It is able to boot but stays in the command prompt, doesn't load into graphical mode.
Can you help me figuring this out? I was considering selling my Rhodium to buy any WP7 but if this works I don't think I'll do it anymore.
Boot Issue
I have run into this problem in the past.
The two things that have usually fixed it are either rebooting and letting it sit for about 10 minutes. ( This was my solution during the early development phase)
The second is that the initrd.gz is not the correct one and if this is the case then I will have to recreate the install upload to replace the one that is included with the proper one. The issue is that the initrd.gz is looking for the image file and not the ext2 partition.
Here is the correct one:
www.kizzmyanthia.com/WMD/initrd_ext2.zip
If neither of these answer the issue let me know and I will try to work through it with you.
I've managed to fix it. I suppose I must have made any mistake the first time I've tried. Started from scratch and it's working now. A little bit slow but it's running on a mobile phone. of course.
Thanks and once again, congratulations for this fantastic job.
vtec_screamer said:
I've managed to fix it. I suppose I must have made any mistake the first time I've tried. Started from scratch and it's working now. A little bit slow but it's running on a mobile phone. of course.
Thanks and once again, congratulations for this fantastic job.
Click to expand...
Click to collapse
The slow speed was a MAJOR issue for me as well. I have gotten the speed of boot to be increased by 300% by adding the swap partition to the boot sequence.
when you have booted WMD: FFB Edition 0.1 open a terminal and enter the following:
**LIVE VERSION ONLY**
echo '/sdcard/swap.img swap swap defaults 0 0' >> /etc/fstab
**INSTALL VERSION ONLY**
echo '/dev/mmcblk0p3 swap swap defaults 0 0' >> /etc/fstab
********IF YOU HAVE CHANGED THE DRIVE DESIGNATION THIS WILL NOT WORK CORRECTLY, LET ME KNOW AND I WILL TRY TO HELP TROUBLESHOOT**********
This will add the swap partition or swap image to the boot sequence and you will see an all around speed and performance increase.
I'm having an issue with the live version, its trying to mount /dev/block/mmcblk0p2 as ext2, instead of mounting the image file.
Initrd for wmd: Ffb live edition
Ok, something got backwards when i made the package i guess...
----PUBLIC SERVICE ANNOUNCEMENT---
KIDS DON'T PROGRAM AFTER 3AM.
And now you know, and knowing is half the battle.
Any way
Here is the proper INITRD file for the WMD: FFB 0.1 Live edition
Code:
http://www.kizzmyanthia.com/WMD/WMD_LIVE_INITRD.zip
Thanks, that got it working. I also had to rename the .img to ubuntu.img before it would boot. When do you expect version 0.2 to be out?
WMD: FFB Edition 0.2
HDR said:
Thanks, that got it working. I also had to rename the .img to ubuntu.img before it would boot. When do you expect version 0.2 to be out?
Click to expand...
Click to collapse
Working on it now, have some package updates, sound updates, and more that I am currently working into it.
Hope to have this posted in the next week or so.
THANKS FOR CHECKING THIS OUT!!!
WMD: Living Dead Edition 0.2!!!!
That's Right 0.2 WILL BE HERE SOON!!!!!!!!!!!
I am currently uploading the live version. The install version will be going up right after.
This one includes the swap, has a new kernel, and is based off of Ubuntu 9.04 just for starters.
WMD: Living Dead Edition 0.2
It's streamlined, it's fast, IT'S ALIVE!!!!!!!!!!!
That's right boys and girls, I have built in some of the new updates that our fellow friends over at the Rhobuntu page have been working on as well as tweaking our own favorite tools.
I know I spoke of videos with the 0.1 release, but I thought these fixes would be much more appreciated. The videos will come!!
SO, WITHOUT FURTHER ADIEU!!!!
WMD: Living Dead Edition 0.2
I am building in a little further security into the packages as well.
* The packages have been secured with the following password: Kizz MyAnthia
* You will also notice an accompanying MD5 Hash for each file.
.
WMD: Living Dead Edition 0.2 Live:
Code:
http://www.kizzmyanthia.com/WMD/WMD_LDE_0.2_Live.zip
WMD: Living Dead Edition 0.2 Live MD5:
Code:
9ed8582ef6f64a14d5c8f64595f26d04 WMD_LDE_0.2_Live.zip
.
WMD: Living Dead Edition 0.2 Live IMAGE:
Code:
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.zip
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z01
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z02
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z03
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z04
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z05
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z06
http://www.kizzmyanthia.com/WMD/LDE_0.2_Live/WMD_LDE_0.z07
WMD: Living Dead Edition 0.2 Live IMAGE MD5:
Code:
932c018cd43bfdc76a14f28179cd4a15 WMD_LDE_0.2_Live_Image.zip
.
.
.
WMD: Living Dead Edition 0.2 Install:
Code:
http://www.kizzmyanthia.com/WMD/WMD_LDE_0.2_Install.zip
WMD: Living Dead Edition 0.2 Install MD5:
Code:
9ed8582ef6f64a14d5c8f64595f26d04 WMD_LDE_0.2_Live.zip
.
WMD: Living Dead Edition 0.2 Install IMAGE:
Code:
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.zip
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z01
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z02
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z03
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z04
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z05
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z06
http://www.kizzmyanthia.com/WMD/LDE_0.2_Install/WMD_LDE_0.z07
WMD: Living Dead Edition 0.2 Install IMAGE MD5:
Code:
08ad4a93ae0e5db531813a26da66fbc1 WMD_LDE_0.2_INSTALL_IMAGE.zip
.
These were split using IZArc, freely available at www.izarc.org, and I recommend using it to rejoin the files. I have no association with IZArc, but have used it for a very long time.
.
.
WMD: Living Dead Edition 0.2 Installation Instructions
Ok, so I am changing this up a little bit. It will keep all of the required versions a little easier to track and update.
So, lets get started.
1. First Download the WMD: Living Dead Edition 0.2 Package and Image of your choice.
.
.
2. You will need to follow similar instructions as setting up WMD: FFB 0.1
WMD: Living Dead Edition 0.2 Live
Download the WMD: Living Dead Edition 0.2 Live and the WMD: Living Dead Edition 0.2 Live IMAGE files
* Extract the contents
* Copy the files to your MicroSD card as follows:
* /Storage Card/ubuntu/haret.exe
* /Storage Card/ubuntu/STARTUP.txt
* /Storage Card/ubuntu/INITRD.GZ
* /Storage Card/ubuntu/zImage
* /Storage Card/ubuntu/modules-2.6.27.46-01165-gfc1639f.tar.gz
* /Storage Card/ubuntu/playwav2
* /Storage Card/Ubuntu.img
* /Storage Card/swap.img
* /Storage Card/sound.sh
* /Storage Card/wmd_LDE_0.2.jpg
.
.
For the INSTALLED VERSION follow the instructions below:
Download the WMD: Living Dead Edition 0.2 Install and WMD: Living Dead Edition 0.2 IMAGE files
Step 1
• First split your SD Card into 3 partitions (This can be done via Gparted)
* The first partition should be 128mb – 1GB in size and format as fat32. This will be the partition that Win-Mo will read from.
* The second partition should be the remaining space on the card. This will be the total filesystem space available.
* The third partition should be 512mb – 1GB in size and formated as linux swap, the more space you dedicate to this partition the smaller the filesystem space will be.
The structure should look like (if you change the partition structure I can NOT guarantee that the SWAP partition will be added during boot properly):
• Copy the files from the UBUNTU folder in the WMD: Living Dead Edition 0.2 Install file that was downloaded earlier to the first partition of your SD Card.
The file structure should look like this
* /Storage Card/ubuntu/haret.exe
* /Storage Card/ubuntu/STARTUP.txt
* /Storage Card/ubuntu/INITRD.GZ
* /Storage Card/ubuntu/zImage
* /Storage Card/ubuntu/modules-2.6.27.46-01165-gfc1639f.tar.gz
* /Storage Card/ubuntu/playwav2
* /Storage Card/sound.sh
* /Storage Card/wmd_LDE_0.2.jpg
You will see a file called Ubuntu-Install.img. We will need to mount this file and copy the contents to the large, “third”, partition of the SD Card.
Execute the following to begin the transfer (THIS SHOULD BE DONE AS ROOT OR ENTER SUDO PRIOR TO EACH COMMAND)
• cd <enter location where you extracted the downloaded files>
• mkdir /wmd/
• mount wmd.img /wmd -o loop
• gksudo nautilus
o Browse to /wmd
o While still in the gksudo’d nautilus window browse to the “third” partition of your MicroSD Card and copy ALL files to the “second” partition of the SD Card
* “Skip All” when prompted, this is an expected error, ignore it
.
.
.
Step 2
Rhodium / Touch Pro2 / Tilt 2 owners
• Edit STARTUP.txt and change the “physkeyboard” option. At the moment you can choose between “physkeyboard=rhod100uk”.
rhod100_de –> german rhodium
rhod100_fr –> french rhodium
rhod100_it –> italian rhodium
rhod100_uk –> english rhodium
rhod210 –> rhodium 210
rhod400 –> rhodium 400
tilt2 –> tilt2
• If your Rhodium is CDMA, edit STARTUP.txt and change “htchw.force_cdma=0″_ to “htchw.force_cdma=1″
Topaz / Touch Diamond2 owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2293″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=”0x9f.0x39a.0x35c.0×78″
Diamond owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 1805″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=”0xc5.0×399.0×367.0x4d”
Raphael / Touch Pro / Fuze owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 1910″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0x7a.0x5e.0x35a.0x37f”
• change “physkeyboard=rhod100uk” to “physkeyboard=raph” or “physkeyboard=fuze”
Blackstone / Touch HD owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2030″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0×395.0x3c9.0×79.0×77″
Kovsky / Xperia X1 owners
• edit STARTUP.txt and
• change “set mtype 2292″ to “set mtype 2006″
• change “wl1251mac=00:1f:df:b1:23:30″_ to “wl1251mac=YOUR_MAC_ADDRESS”_
• change ” msmtscalib=0x9f.0x39a.0x35c.0×78 to msmts_calib=0xc5.0×399.0×367.0x4d”
• For keyboard setting read this: http://forum.xda-developers.com/showpost.php?p=6993913&postcount=1105
.
.
Step 3
Launch Haret.exe
* Browse to /Storage Card/UBUNTU/Haret.exe and Launch
* When WMD: Living Dead Edition 0.2 Install has completed booting, connect to the internet either via wireless or 3G, open a terminal, and execute the following to fully enable sound:
cd /sdcard/
chmod +x sound.sh
./sound.sh
.
.
.
.
For more information related to using your phone while in WMD:
• Read this: http://forum.xda-developers.com/showpost.php?p=6453098&postcount=900
For more information on how to work with the WMD, Rhobuntu GUI, interface, what apps do and do not work on the platform read here, http://forum.xda-developers.com/wiki/index.php?title=Ubuntu_on_the_Rhodium
If you would like to import your contact list into WMD you can find more information about it at:
• http://forum.xda-developers.com/showthread.php?t=709101
Oh my.... I knew I kept the fuze for good reason. Do you drink beer or coffee?
From a phone
boborone said:
Oh my.... I knew I kept the fuze for good reason. Do you drink beer or coffee?
From a phone
Click to expand...
Click to collapse
Guinness and LOTS of coffee
Good, Bad, Ugly?
Soooooooo.........
I have watched this post grow in views, have heard of a few people that have tried it, and have seen 130+ downloads.
YET!
No feedback.
hmmmmm, must be perfect!!
I mean, I know I really like it, I have used it a few times now for some work related items.
Anyone out there? Anyone tried it? Anyone find bugs? Think it is sweet? Anything?
**Looking for feedback for 0.3**
I have a few items that I will be working in, but looking for more info, more devices, etc.
I REALLY want to try it, but I don't have an 8gb micro sd card
Wait... would the live version fit on a 2gb card?
Related
DL Desire Series v 5.x
by dandiest & freak
New features:
Totally new init, using full power of aufs, lzma squashfs and ram.
new vinit, with automatic configuration for nand, magldr and sd launch
re-odexed builds
re-engineered packages
working with data2sd/data2ext
Versions and Links:
[4 jun ] - dlz test version - go to this post
[30 apr] - (changelog)
version 5.21.51.18: DesireZ 1.85.72 base: download [CWM] [DAF]
version 5.12.51.18: DesireZ themed 1.85.72 base:download [CWM] [DAF]
[10 apr]
Be careful, actually there is problems with cwm and users with wp7 on nand.
version 5.03.50.15: IncredibleS 1.43.415.3 base: download [cwm] [DAF] (battery percentage is wrong)
Kernel:
current kernel: 1.8 download
You can take a look on current kernel source at : (NOT YET SYNCHRONIZED) http://www.linux4freak.com/gitweb/?p=kernel-freak/.git;a=summary
Tips:
Please remove dialer button sound to prevent robotic voice
If using SD/haret, do not set pin code under wm65
Do not change Desire_DL folder name, our detection method is based on this name
Do not use another kernel, none of them works with our new builds
for data2ext, please reboot your phone twice in order to have all working fine (2nd boot take a long time)
Please use shutdown instead of reboot for your phone
you can use 200M or 250M for cwm
Make a fresh install is highly recommended
sdcard is highly recommended for leo1024 phone.
How to report:
- Using dlreport :
I have created dlreport to have a photography of your system. You can use it with a terminal or with adb. After running it, an archive file /system/dlreport.tar is generated. Please attach this file to your post.
If you don't have adb, use this archive: http://www.multiupload.com/YOZYJGI09N
Code:
adb shell dlreport && adb pull /system/dlreport.tar
- If dlreport not working for you , please usethis naming method:
[DL VERSION] - 5.01.50.19
[LOAD TYPE] - NAND
[LOAD METHOD] - CWM
[DATA TYPE] - EXT4 (2 PARTITIONS 1GB-300Mo)
[DATA LOAD] - From previous build
[CONFIG.TXT] - (if tweaked)
[INIT.LOG/DMESG] - as attachment
Click to expand...
Click to collapse
Options:
no need to put any options at startup, our init detect your phone and launch mode, and apply tweaks accordinly
if you want to modify some options, you have all these possibilities, after creating config.txt file inside Desire_DL folder on sdcard:
load_mode=
0 // (default) load cache.sqsh file to ram
1 // load cache.sqsh normally
data_img=
0 // not using data.img file on sdcard to store data apps
1 // using data.img file on sdard to store data apps
2 // try to increase data.img filesize ( ! experimental !) works with data_size
data_size=
512 // (default) size in Mb of data.img/1st ext4 partition
sd_boost=
0 // (default) load 1st ext4 partition with default (tweaked) options
1 // load 1st ext4 partition without journal
ppp_mode=
0 // rmnet enabled
1 // ppp enabled
format_ext4=
0 // (default) no effect
1 // format all ext4 partitions on sdcard with default (tweaked) options
2 // format 1st ext4 partition with ext2 instead of ext4 - all other ext4 partitions formatted normally
8 // simulate format_ext4=9 to show in init.log future partitions size
9 // works only on nand - remove all data from sdcard and partition it to 4 partitions: FAT / EXT4 / EXT4 / SWAP; the 2nd partition size can be defined with data_size= option
cache_mode= [for WM65/SD/WP7 users]
0 // (default) copy downloaded apps and tmp files to /data
1 // copy downloaded apps and tmp files to ram
sched_mode=
bfq // (default) use bfq scheduler
cfg // use cfq scheduler
noop // use noop scheduler
vdd_mode=
0 //
possible values are: +50 +25 0 -25 -50 -75 -100 -125 -150
Increase/Reduce voltage of phone. For frequencies higher than 576Mhz, vdd is limited to -50 (you can safely use -100 value)
mac_virt=
use your own wifi mac address
gps_zone=
defining your region for gps
backup_img=
0 // (default) no effect
1 // create backup.tgz on sdcard: store /data contents
restore_img=
0 // (default) no effect
1 // restore backup.tgz from sdcard to /data
repair_mode=
0 // (default) no effect
1 // delete dalvik-cache and fix permissions
2 // only for magldr/sd: mount system yaffs2 partition to /mnt/rescue and copy zImage / initrd.gz / vinit from sd to nand
9 // only for magldr/sd: mount system yaffs2 partition to /mnt/rescue
Video and screenshots:
Many thanks to Sklar for this video.
Features details:
aufs + squashfs. This is the 1st android version that can support the aufs+squashfs, we even worked with the author of aufs to make it usable to android. a lot of innovations within this build from the technical perspective, for users, the benefit of it are:
high performance
despite of squashfs is used to reduce the size of file system, user still be able to change any file directly with the power of aufs.
a lot of frequent accessed files are squashed and loaded into ram to improve the performance.
re-odexed. there flood a lot of misleading messages in xda of odexed, same as squashfs. Odex can actually improve system performance, and at the same time, reduce the whole system's size (because the odex is optimized dex), and odex build has less chance of system crash that lead to wipe the davlik-cache. an odex build doest not generate the davlik-cache which is odexed.
re-engineered. we re-packaged all the apk, jar in the build after optimized the png file and etc, to reduce the apk&jar size, which will reduce the consuming of ram.
Naming convention:
the 1st digit is for the build base, 5.
the 2nd field is for the subversion and build model, normally, 5.0x means the first relase which should based on a totally new base, 5.x1 is for dlz, 5.x2 is for dlz themed, and 5.x3 is for incredibleS
the 3rd field is for the init version, actually 5.0 ->50
the 4th field will be used for the kernel version, actually 1.5c ->15
Thanks! :
to all devs at xda and at irc-logs, kernel devs
to Jim, as a linux expert, he gave us a lot of good idea and suggestion.
to J.R. Okajima, the author of aufs, who helps us solve the last performance of aufs on android.
to kajos, manu33xtro, pascalsg2, vlad48, darkony, ..., they are working with us for months to test a lot of builds we released (about 10 builds we released for testing before this version)
Credits:
All these builds and init are made by dandiest and me
Please respect our work, and don't forget to mention ou names and authors if you used some technologies. Don't forget gpl too.
Put a link to this thread if you want to share it.
Changelog:
[30 apr]
- new kernel 1.8: modifying a bit smartass and cpufreq, added more than 50 patches from kernel mainline (2.6.32.28 to 2.6.32.39, 2.6.33 and 2.6.34)
- modified cache/system squashfiles, now cache.sqsh is lzma compressed and system.sqsh is gzip compressed
- re-added htc locations (Laputa) for 5.22 build
- minor things ...
- better reactivity with proximity sensor when calling.
Click to expand...
Click to collapse
[15 apr]
- new version:
modifying bcm4329 branch to _245
corrected init when only 1 partition on sdcard
- no need of setcpu, managing it in kernel with perflock and smartass
- new wpa-supplicant, then wifi tethering now works fine with new kernel
- working dspmanager
- shared media working
- modifying cached/uncached apps
- adding new script: dlreport, which generate a tar file with all we need to have a "photography" of your system.
- modifying swap size to limit out_of_memory errors when installing lot of apps at once.
- modifying vinit/init to solve (i hope so) cwm / wp7 / sd-haret issues.
- kernel 1.6: totally backported net stack from rafpigna instead of tytung, adding 2 way call recording, new bt stack, tweaked smartass and bfq as default scheduler, activating htc boot perflock.
Click to expand...
Click to collapse
[10 apr]
Initial 5.x release
- desireZ, themed and incredibleS version
- aufs/lzma by default
- kernel freak 1.5c
Click to expand...
Click to collapse
MINI HOWTO
No need of config.txt for the first startup.
config.txt is for tweaking your build.
For Nand users:
Download your preferred version, you can choose daf or cwm method.
Magldr 1.13/cwm is already installed on your phone
For daf:
- choose USB Flasher on you phone inside magldr bootloader
- extract archive
- run inside Desire_DL folder: EnterBootloader.exe
(don't forget to run it as administrator).
- After flashing, let our init make everything to setup.
For cwm:
- you can choose cwm 200M or 250M.
- there is lot of threads about how to use cwm.
- Once done, let our init make everything to setup.
Click to expand...
Click to collapse
For magldr users:
- extract daf version in your sdcard
- Desire_DL folder must be on the root of your sdcard
- DON'T RENAME FOLDER
- Enter inside magldr bootloader, choose your AD/SD dir in services
- Run Boot AD/SD option.
- That's all
Click to expand...
Click to collapse
reserved for future use 6
Data2Ext? right?
awesome, will be downloading as soon as you get it upped.. thanks much, guys
[leo model] - eu :d:d
Refresh Refresh Refresh wait download
What is the CWM partition recommended for this?
shared media work with this new builds ??
waiting 4 changelogs - except "initial release" which is Fastest rom in this new series???
I've got Wifi WPA cannot connect in Imilka's Incredible S1.1. Is ur rom working fine?
super a new build !
is the Camera fully working? (preview and sending)
keep up the good work !!
UOT kitchen
Is it possible to flash UOT kitchen with your ROMs?
thanks
for 5.01.50.15, i think it's possible. No idea for 5.02 or 5.03. Dandiest past a long time to have a good framework for 5.03, it should be possible too, but not so easy
matmar said:
Is it possible to flash UOT kitchen with your ROMs?
thanks
Click to expand...
Click to collapse
There is a lot of changes internally. But you can read features and features details to know "the mind" of builds.
All these versions are good, incredibleS is a little but more smoother, but all of them are fast.
arifqur said:
What is the CWM partition recommended for this?
Click to expand...
Click to collapse
dont you read !?
freak007 said:
[*]you can use 200M or 250M for cwm
Click to expand...
Click to collapse
kernel
Is you kernel compatible with eb ?
Goodbye Lollipopalooza... Hello Marshmallicious!!
{
"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 started out as a personal project... a way for me to learn how to develop and custom features for Android. And I decided to share my work with the amazing Android community... something to give back to the community. Back then, this was a ROM called ThunderKat, based on Android 4.4 KitKat. Over time, it evolved into Lollipopalooza, based on Android 5.0. And now, here's Marshmallicious, based on Android 6.0.
Now, before you go on ahead, let me be clear about one thing. This is and will remain a minimal AOSP based ROM. It will include a small, but useful set of features... features which add a bit more flare to Android AOSP. Beyond this minimal feature set, this will also include some relevant spit and polish (bug fixes and asset/image updates). As time progressed, so did the quality of the work behind the features this ROM offers. Whenever I look back at a feature I developed before, I look for ways to improved. If you expect a lot of additional features, I recommend using one of the more popular ROMs available like CyanogenMod, SlimRoms, ParanoidAndroid, etc.
I develop and maintain this ROM on my own for the most case, occasionally seeking help and porting useful features and fixes that others here in the community have developed. You will see all the relevant references in the cherry-picked commit in my GitHub repositories.
Due to my limited availability, I will now no longer support Lollipopalooza builds
Now that I'm done with the fancy introduction, let's get down to business...
Changelog:
2015/11/07
1. Fixed force close when choosing keyboards in Language & input settings
2. Enabled doze/ambient mode auto power saving modes (More details)
3. Removed SVELTE (Nexus 9 LTE) init configs from Nexus 9 Wifi init configs
4. Disabled bug report service (which is triggered by holding down volume down, volume up and power)
5. Updated SELinux policies for experimental systemless root using open source Superuser (instruction below)
6. Fixed experimental systemless root for devices with encrypted userdata
2015/11/04
1. Android Marshmallow 6.0.0_r2 (MRA58N) base [Includes November 2015 security patches by Google]
2. Movable on-screen navigation bar buttons (centre, left or right) [Settings > Device > Display]
3. Cursor control within text boxes using the volume rocker [Settings > Personal > Language & input]
4. Long-press of back button to kill foreground app [Settings > Personal > Language & input]
5. Native Android Marshmallow recents dismiss/clear all
6. User-defined custom device hostname [Settings > Wireless & networks > More]
7. Displays apps installing and optimising storage progress on first boot
8. Uses Google pre-built WebView if it is installed. Falls back to AOSP WebView
9. SystemUI Tuner enabled by default
10. Dessert Cake dream enabled and set as default doze dream
11. Enhanced Location QuickSettings tile (toggles between the different location mode [Off > Sensors Only > Battery Saving > High Accuracy])
12. Long-press action for all QuickSettings tiles (opens relevant Settings section)
13. Enhanced power menu [Power Off, Reboot, Aeroplane Mode, Users & Sound Toggle]
14. Advanced reboot [Reboot, Reboot to recovery, Reboot to bootloader] (only available for primary user when device is unlocked)
15. Default required permissions set for Google applications to allow GoogleApps packs
16. F2FS support for the cache partition in addition to the userdata partition.
17. Additional filesystems supported (with vold auto-mount capabilities not available yet) [exFAT and NTFS (NTFS-3G)]
18. Forced encryption of userdata partition is disabled
19. DM-Verity (key-based partition verification) is disabled system-wide
20. Full-screen on-screen keyboard in landscape mode is disabled
21. Sysinit supported (init.d scripts)
22. @Captain_Throwback's BeyondStock kernel 2.0.0 included [support NTFS, exFAT and fast-charge]
23. Several assets and images updated to Material-styled versions
24. Ambient (Doze) mode enabled along with burn-in protection
25. A lot of unneeded debug logging disabled
26. Default wallpaper replaced with Marshmallow stock default wallpaper and Marshmallow stock bootanimation added
27. Includes bionic busybox (credit CyanogenMod)
28. Increased number of status bar notification icons from 5 to 8
29. Miscellaneous bug-fixes and tweaks included (for more details, check the GitHub commits)
30. Full GoogleApps pack (with ARM64 320DPI apps where applicable) with the latest updates
Instructions:
1. Download the Marshmallicious ROM package and the Prerequisites package
2. [OPTIONAL] Download the GoogleApps package
3. Reboot into recovery [A custom recovery like TWRP is required]
4. Wipe as required
a. Full wipe when coming from another ROM
b. Wipe cache and dalvik-cache when flashing a Marshmallicious update5. Flash the packages in the following order
a. Prerequisites package
b. Marshmallicious ROM package
c. [OPIONAL] GoogleApps package6. Reboot and let the device boot up and remember that the first boot will take a while since this is a de-odex ROM
Root:
I do not support SuperSU because it is closed-source and, hence, cannot be audited. Anything granting low-level privileges to apps and process need to be open-source and auditable. But I will not blankly turn down support requests involving SuperSU if you have chosen to root your ROM using SuperSU.
That said, I am closely following the development of systemless open-source Superuser by @phhusson as well as the SELinux policy changes by @doitright. This is still experimental and may not support all root apps yet.
Because this is currently experimental, this ROM is not pre-rooted. But I have provided a separate ExperimentalRoot package. This package contains a modified boot image with the su binary, init changes and SELinux policy changes and has been built from source. The su binary was built with the latest changes in @phhusson's Superuser GitHub repository. The init and SELinux policy changes are a slightly varied version of the patch created by @doitright. Also included in the zip is the Superuser apk built with the latest changes in @phhusson's Superuser GitHub repository.
I have branches in my GitHub repository which have the SELinux policy and init changes required for systemless Superuser which include all doitright's changes as well as my modifications.
platform_external_sepolicy
platform_system_core
Instructions:
1. Download the ExperimentalRoot package provided above (make sure it matches the ROM release date)
2. Flash the boot image included in the ExperimentalRoot package using fastboot [fastboot flash boot boot.img]
3. Install the Superuser apk included in the ExperimentalRoot package as a regular app
Downloads:
AndroidFileHost
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
BasketBuild
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
Theming:
This ROM support RRO/Layers themes. But please be aware that not all RRO/Layers themes support Android Marshmallow yet. If you encounter force closes after installing a theme, reboot into recovery mode and delete /vendor/overlay.
Layers/RRO Themes Info:
1. Join the BitSyko Google+ Community for the latest information and themes
2. Download the Layers Manager app to install/uninstall/preview RRO/Layers themes
3. Download the Layers Showcase app to browse available RRO/Layers themes
4. Visit this XDA thread for a comprehensive list of RRO/Layers themes
Help and troubleshooting:
1. Ask for help if you need, but make sure you do your research first.
2. Be patient. It could take a few minutes to flash the ROM.
3. If you flashed a kernel which replaced the SELinux policy file, you may encounter errors and issues. To recover, you will need to reflash the ROM boot image.
4. If you get "failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP", unmount the system partition and try again
5. If you flashed a kernel with SELinux disabled like the one provided by @USBhost on a previous build, make sure you flash that kernel after flashing the update (before you reboot), or you will get a bootloop and will have to perform a recursive restorecon on the /data partition to restore the SELinux contexts.
6. If you have a folder created in TWRP recovery mode which you cannot access when you boot up the ROM, you will need to perform a recursive restorecon on that folder restore the SELinux contexts.
7. Be ready to provide a clear description of your issues and please provide logcats, dmesg logs and kmesg logs whenever possible.
Sources:
Marshmallicious Manifest
All repositories
Disclaimer
Marshmallows are always delicious... but be careful!!! Make sure you know your limits!!! If you don't know what you are doing, the marshmallows provided here could be life-threatening and render your device inedible. Every marshmallow here has undergone extensive scrutiny, but there is always a chance that something slipped through the cracks since baking is more an art than a science. So if you use the marshmallows here, don't hold the chef responsible for baking these goodies (me!)
Support this project:
If you like my work, buy me a beer so that I can pass time while my laptop churns out builds...
Paypal
Google Wallet (Send Money to craigacgomez[at]gmail[dot]com)
Credits:
Google, NVidia, ARM, Chainfire, 0xD34D, CyanogenMod team, PureAOSP team, Chroma team, BitSyko team, AndroidFileHost, BasketBuild, phhusson, doitright, XDA (any probably some more I can't remember)
Reserved...
And one more... just in case!!
Will test and report back
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
craigacgomez said:
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
Click to expand...
Click to collapse
Can you edit the ROM to not encrypt data
BTW love the Disclaimer!!
USBhost said:
Can you edit the ROM to not encrypt data
Click to expand...
Click to collapse
Definitely planning on doing that next. I will spend some time on this tomorrow...
Awesome, the first rom is out! let the flashing begin!
craigacgomez said:
Definitely planning on doing that next. I will spend some time on this tomorrow...
Click to expand...
Click to collapse
hows its going
found it?
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
USBhost said:
hows its going
found it?
Click to expand...
Click to collapse
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
craigacgomez said:
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
Click to expand...
Click to collapse
So i change it
Then do a factory reset
And i should be good?
jarjar124 said:
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
Click to expand...
Click to collapse
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
craigacgomez said:
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
Click to expand...
Click to collapse
I can wait. Thanks for your hard work!
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
USBhost said:
So i change it
Then do a factory reset
And i should be good?
Click to expand...
Click to collapse
Yes...
USBhost said:
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
Click to expand...
Click to collapse
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
craigacgomez said:
Yes...
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
Click to expand...
Click to collapse
ok awesome doing a factory reset now
Edit: can you add long back to kill app
---------- Post added at 07:34 PM ---------- Previous post was at 07:13 PM ----------
it booted
and it worked cheers tytyty
---------- Post added at 07:45 PM ---------- Previous post was at 07:34 PM ----------
it feels so much faster now
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
craigacgomez said:
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
Click to expand...
Click to collapse
1
Then in about 6-9 months 2
USBhost said:
[/COLOR]it feels so much faster now
Click to expand...
Click to collapse
It doesn't just feel faster. It is faster. And logically so. With encryption enabled there is extra overhead involved in decryption.
Language:
Traditional Chinese English Simplified Chinese Traditional Hong Kong
core:
Android 5.1.1
Based version:
Carbon Lollipop5.1.1 latest source
Fit models:i
Samsung Galaxy S3 NEO + / 9300I
maker:
moonlight-roms
ROM type:
Carbon Lollipop5.1.1
ROM Style:
Avant-garde version of the multi-function version
DISCLAIMER
Code:
1) The ROM is already in my test.
2) Make sure that the battery is at 60 % or more of the process and to ensure that the computer will not brush off.
3) Brush risk, please read the tutorial Brush Brush carefully and bear the risk, and I've Brush liable for any failure of any liability.
4) He does not hold ROM and software copyright, please research and study for the purpose of lawful use.
5) prohibit any son team (individual) so-called quadratic optimization, modify or re-packaging and other acts .
6) I hereby declare to the ROM use it does not provide any guarantee, does not guarantee any user of the ROM applicability does not guarantee trouble-free produce; nor for any user to use this ROM encountered any theoretical or actual losses Take responsibility.
7) I ROM release Baidu network disk account is unique: Andrews DreamWorks, plagiarism or other modifications I packed party ROM disk network link for this release are not, and if found not to link this site disk, do not download, copy or pack party the works may be added Trojans chargeback applications, if I brush into a non- ROM network disk ROM , please bring consequences to bear!
8 ) issue Feedback: weibo.com/diyroms
ROM feature
Brush before please read: 9300i is currently only a single third-party ROM card normal use, the second card being no way, if it is to brush into the official ROM must be upgraded as you type the corresponding version 4.2.2 and third-party recovery
Part of the machine if the boot after boot interface settings infinite loop, please restart your phone can solve the problem!
Carbon Lollipop5.1.1 open source project based on the latest production source compiler, which added the source text come and go electric attribution and other support, the card comes back like a lot of features, prohibit copying other issues please see the following description
Carbon functional parts using tips:
1. Theme: simultaneously press the volume down + power button for 2 seconds to achieve
2. Change the weather location: Set -Carbon Settings - interface - Clock Widget Settings - Weather Panel - Custom location update can be!
3. For the part of the machine or restarting after power does not show attribution Lunar Solution: Go to Settings - Language & input - default language can re-select Simplified Chinese!
4. The developer mode hidden by default, you need to go to open Settings - About This Mac - Click the version number and then go after more than five times
5. Press the Home key part of the machine does not appear in the Recent Tasks Solution: Set -Carbon Settings - button - Long press the home key to modify what you can inside
6. For background lock function, Recent Tasks panel is sliding to the left to the application lock, to prevent the end, again to the left slide to unlock, slide to the right end of the process
Compiled adaptation works, prohibit any person to modify or to publish a package or after handling AZ and gfan forums in any form! Plagiarism party to prohibit copying ROM cottage House (www.romzhijia.net) and Brush House (www.shuajizhijia.com)!
Flashlight comes in the drop-down notification bar which can be seen, click to open and close.
For the latter part of the root Brush failure, please set - which re-select Developer mode adb root permissions and applications can be!
If the card has a brush screen, please upgrade your CWM or TWRP Recovery to the latest version after performing twice wipe painted machine brush machine before. Brush can be patient!
In order to ensure the process does not exist Brush transfer data to 0 folders or missing, the latest TWRP or cwm of rec brush or save data to a memory card on your computer.
Thanks for groups and individuals: Cyanogenmod team, ghbhaha, kylindev, Carbon team, etc.
Carbon Final5.1.1 latest version update log:
1.carbon code update to the latest
2. Set contents Reconstruction
3. Reconstruction of the frame contents
4. Update Statistics Contributors
5. Protection Application: Short Action dialog box does not show progress
6. Set: Fix crash secondary user preferences LCD Density
7. Set: Update layout
8. The protected application: Add some side padding in the application list view
9.slim immediate tasks: Set the default switch to false
10. Set: Forgot consistent behavior after network
11. The switch to using CMSettings not involved in setting bootclasspath
12. Set: When forget your network, clear dialogue state
13. Multi-LED: lighting column support
14. Settings - Status Bar: Color of VPN icon
15. Battery location text option repairs
16. Set: Fix battery icon and select Clear settings
17. Set - styles and extended battery options title
18. Setting: repair RuntimeException set in InputMethod
19. The date security patches humane format
20. Setup: set the security patch level
21. Setting: Fix NPE in PowerMenuActions
22. Repair inconsistent battery statistics icon
23. Setting: fuelgauge: Always display bright screen time
24.PERF: add additional power profiles support
25.base: show security mode Restart Options
26. Wireless Title: Do not set a non-UI thread visible item
27.AssetAtlasService: Fixed a potential race conditions
28.SystemUI: Improved string play queue
29.base: Background initialization of reference before using it ContentResolver
30. Lighting mode: Avoid conventional value update
31. supports faster response to changes in the brightness of the light.
32. For more updates and code merger cm from the
33. More information at your own experience
Carbon Part functions:
1.Carbon boot animation
2.cm all functions
3. Status bar brightness control
4. The status bar clock and date settings
5. Status bar battery settings
6. Status Bar mobile and wifi network icon set
7. The status bar network traffic
8. The instrument displays network traffic and
9. The status bar notification icons and system
10. The navigation bar and its settings
11. The hardware keys and backlighting
12. The set of keys
13.Toast and animation settings
14. Freedom gesture and its settings
15. Display and animation
16. The system animation
17. Scroll modified
18. scrolling effect
19. Application of the circle sidebar
20. Application Bar
21. Clock Widget settings
22. A drop-down notification bar and set
23. Custom Color Options
24. The status bar title
25. Recent Tasks panel settings
26. Advanced Options
27. Uninstall Applications
28. Touch gestures (some machines support)
29. Other features please more experience on their own
5.1 ROM, do not delete the input method, whether the return of keys, house keys and other keys will fail!
If you need to delete the input method, install other input methods before you can delete and set default
NOTE: 4.4 or more ROM, USB debugging mode turned on: Click Settings - About the version number inside the unit more than five times, and then return to Settings - Developer options which you can see
; Join and display text messages come and go electric attribution
; T9 dialing
; Adjust the language, time zone, etc. The default startup Chinese
; Replace the system comes to Baidu Pinyin input method
; Adding third-party software uninstall
; Integration of several mainstream applications, allows developers to work if you can keep using, if not support, you can uninstall itself
; Enabled by default unknown source
; The system comes with Root privileges
; Rapid smooth and stable
; Add the complete localization of Chinese string set has been basically finished ok
Precautions
NOTE: 4.4 or more ROM, USB debugging mode turned on: Click Settings - About the version number inside the unit more than five times, and then return to Settings - Developer Options to see inside, check the developer mode before connecting a computer inside the USB debugging
5.1 ROM, do not delete the input method, whether the return of keys, house keys and other keys will fail!
If you need to delete the input method, install other input methods before you can delete and set default
Screenshot
{
"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"
}
BUGS
Offline charging
NFCkeyboard:
CREDITS
@Rox
@n1kolaa
Installation:
1. Boot into recovery;
2. Wipe data,cache, dalvik cache;
3. Install ROM, install GAPPS (for example GAPPS);
4. Install fix Audio sim-card
5. Reboot. Enjoy
To correct the audio of the sim-card put fix of the added file.
DOWNLOAD
How is battery, better than cm 12.1?
I lose 1~2% of battery per hour with cm 12.1.
malucovisk said:
How is battery, better than cm 12.1?
I lose 1~2% of battery per hour with cm 12.1.
Click to expand...
Click to collapse
I used it for 4 hours . Battery hold a charge well .
MAXSIMUS96 said:
Language:
Traditional Chinese English Simplified Chinese Traditional Hong Kong
core:
Android 5.1.1
Based version:
Carbon Lollipop5.1.1 latest source
Fit models:
Samsung Galaxy S3 NEO + / 9300I
maker:
moonlight-roms
ROM type:
Carbon Lollipop5.1.1
ROM Style:
Avant-garde version of the multi-function version
DISCLAIMER
Code:
1) The ROM is already in my test.
2) Make sure that the battery is at 60 % or more of the process and to ensure that the computer will not brush off.
3) Brush risk, please read the tutorial Brush Brush carefully and bear the risk, and I've Brush liable for any failure of any liability.
4) He does not hold ROM and software copyright, please research and study for the purpose of lawful use.
5) prohibit any son team (individual) so-called quadratic optimization, modify or re-packaging and other acts .
6) I hereby declare to the ROM use it does not provide any guarantee, does not guarantee any user of the ROM applicability does not guarantee trouble-free produce; nor for any user to use this ROM encountered any theoretical or actual losses Take responsibility.
7) I ROM release Baidu network disk account is unique: Andrews DreamWorks, plagiarism or other modifications I packed party ROM disk network link for this release are not, and if found not to link this site disk, do not download, copy or pack party the works may be added Trojans chargeback applications, if I brush into a non- ROM network disk ROM , please bring consequences to bear!
8 ) issue Feedback: weibo.com/diyroms
ROM feature
Brush before please read: 9300i is currently only a single third-party ROM card normal use, the second card being no way, if it is to brush into the official ROM must be upgraded as you type the corresponding version 4.2.2 and third-party recovery
Part of the machine if the boot after boot interface settings infinite loop, please restart your phone can solve the problem!
Carbon Lollipop5.1.1 open source project based on the latest production source compiler, which added the source text come and go electric attribution and other support, the card comes back like a lot of features, prohibit copying other issues please see the following description
Carbon functional parts using tips:
1. Theme: simultaneously press the volume down + power button for 2 seconds to achieve
2. Change the weather location: Set -Carbon Settings - interface - Clock Widget Settings - Weather Panel - Custom location update can be!
3. For the part of the machine or restarting after power does not show attribution Lunar Solution: Go to Settings - Language & input - default language can re-select Simplified Chinese!
4. The developer mode hidden by default, you need to go to open Settings - About This Mac - Click the version number and then go after more than five times
5. Press the Home key part of the machine does not appear in the Recent Tasks Solution: Set -Carbon Settings - button - Long press the home key to modify what you can inside
6. For background lock function, Recent Tasks panel is sliding to the left to the application lock, to prevent the end, again to the left slide to unlock, slide to the right end of the process
Compiled adaptation works, prohibit any person to modify or to publish a package or after handling AZ and gfan forums in any form! Plagiarism party to prohibit copying ROM cottage House (www.romzhijia.net) and Brush House (www.shuajizhijia.com)!
Flashlight comes in the drop-down notification bar which can be seen, click to open and close.
For the latter part of the root Brush failure, please set - which re-select Developer mode adb root permissions and applications can be!
If the card has a brush screen, please upgrade your CWM or TWRP Recovery to the latest version after performing twice wipe painted machine brush machine before. Brush can be patient!
In order to ensure the process does not exist Brush transfer data to 0 folders or missing, the latest TWRP or cwm of rec brush or save data to a memory card on your computer.
Thanks for groups and individuals: Cyanogenmod team, ghbhaha, kylindev, Carbon team, etc.
Carbon Final5.1.1 latest version update log:
1.carbon code update to the latest
2. Set contents Reconstruction
3. Reconstruction of the frame contents
4. Update Statistics Contributors
5. Protection Application: Short Action dialog box does not show progress
6. Set: Fix crash secondary user preferences LCD Density
7. Set: Update layout
8. The protected application: Add some side padding in the application list view
9.slim immediate tasks: Set the default switch to false
10. Set: Forgot consistent behavior after network
11. The switch to using CMSettings not involved in setting bootclasspath
12. Set: When forget your network, clear dialogue state
13. Multi-LED: lighting column support
14. Settings - Status Bar: Color of VPN icon
15. Battery location text option repairs
16. Set: Fix battery icon and select Clear settings
17. Set - styles and extended battery options title
18. Setting: repair RuntimeException set in InputMethod
19. The date security patches humane format
20. Setup: set the security patch level
21. Setting: Fix NPE in PowerMenuActions
22. Repair inconsistent battery statistics icon
23. Setting: fuelgauge: Always display bright screen time
24.PERF: add additional power profiles support
25.base: show security mode Restart Options
26. Wireless Title: Do not set a non-UI thread visible item
27.AssetAtlasService: Fixed a potential race conditions
28.SystemUI: Improved string play queue
29.base: Background initialization of reference before using it ContentResolver
30. Lighting mode: Avoid conventional value update
31. supports faster response to changes in the brightness of the light.
32. For more updates and code merger cm from the
33. More information at your own experience
Carbon Part functions:
1.Carbon boot animation
2.cm all functions
3. Status bar brightness control
4. The status bar clock and date settings
5. Status bar battery settings
6. Status Bar mobile and wifi network icon set
7. The status bar network traffic
8. The instrument displays network traffic and
9. The status bar notification icons and system
10. The navigation bar and its settings
11. The hardware keys and backlighting
12. The set of keys
13.Toast and animation settings
14. Freedom gesture and its settings
15. Display and animation
16. The system animation
17. Scroll modified
18. scrolling effect
19. Application of the circle sidebar
20. Application Bar
21. Clock Widget settings
22. A drop-down notification bar and set
23. Custom Color Options
24. The status bar title
25. Recent Tasks panel settings
26. Advanced Options
27. Uninstall Applications
28. Touch gestures (some machines support)
29. Other features please more experience on their own
5.1 ROM, do not delete the input method, whether the return of keys, house keys and other keys will fail!
If you need to delete the input method, install other input methods before you can delete and set default
NOTE: 4.4 or more ROM, USB debugging mode turned on: Click Settings - About the version number inside the unit more than five times, and then return to Settings - Developer options which you can see
; Join and display text messages come and go electric attribution
; T9 dialing
; Adjust the language, time zone, etc. The default startup Chinese
; Replace the system comes to Baidu Pinyin input method
; Adding third-party software uninstall
; Integration of several mainstream applications, allows developers to work if you can keep using, if not support, you can uninstall itself
; Enabled by default unknown source
; The system comes with Root privileges
; Rapid smooth and stable
; Add the complete localization of Chinese string set has been basically finished ok
Precautions
NOTE: 4.4 or more ROM, USB debugging mode turned on: Click Settings - About the version number inside the unit more than five times, and then return to Settings - Developer Options to see inside, check the developer mode before connecting a computer inside the USB debugging
5.1 ROM, do not delete the input method, whether the return of keys, house keys and other keys will fail!
If you need to delete the input method, install other input methods before you can delete and set defaultScreenshot
BUGS
Offline charging
NFC
keyboard:
(I installed this)
Installation:
1. Boot into recovery;
2. Wipe data,cache, dalvik cache;
3. Install ROM, install GAPPS (for example GAPPS);
4. Install fix Audio sim-card
5. Reboot. Enjoy
To correct the audio of the sim-card put this fix
Patch
DOWNLOAD
Click to expand...
Click to collapse
Since you used my and rox sources as base add us in credits
GT-9301 ?
No. Stuck con boot
Screenshot ?
delimatkap said:
Screenshot ?
Click to expand...
Click to collapse
open your eyes
wetito said:
open your eyes
Click to expand...
Click to collapse
????
[url=http://hizliresim.com/Pkop79]
[/URL]
I tested and works the kernel n1kernel_R2.2.zip and renkernel but does not work the chip
Please email patch file [email protected]
Because patch file link not working...
correct the audio of the sim-card put this fix Patch link not wroking plase past new
correct the audio of the sim-card put this fix Patch link not wroking plase past new link becouse i use two sim dualcard in my wrok plasezzz
fras60 said:
correct the audio of the sim-card put this fix Patch link not wroking plase past new link becouse i use two sim dualcard in my wrok plasezzz
Click to expand...
Click to collapse
Added patch. See the attached files.
thank you
MAXSIMUS96 said:
Added patch. See the attached files.
Click to expand...
Click to collapse
thank you man intall from recovery just select a .Zip file and flash it ??????
---------- Post added at 10:57 AM ---------- Previous post was at 09:58 AM ----------
MAXSIMUS96 said:
Added patch. See the attached files.
Click to expand...
Click to collapse
ok all work good for me thank you:laugh::laugh:
This rom works with gt-i9301l??
Michael1995Mazza said:
This rom works with gt-i9301l??
Click to expand...
Click to collapse
Try. I don't know
MAXSIMUS96 said:
Try. I don't know
Click to expand...
Click to collapse
I tried.. i have a infinite boot animation..i try to reboot but nothing...
Can you add support for i9301i???
I have installed rom on i9301i with philz recovery no bootloop,but after showing window for android loading,it shows again C icon.
What is the difference between this and Rox version ?
---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------
@n1kolaa are you working on CM13.?
Here’s my build of LineageOS 16.0 for Raspberry Pi 3 Model B and Model B+. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.
Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!
{
"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"
}
https://konstakang.com/devices/rpi3/LineageOS16.0/
lineage-16.0-20200713-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=8889791610682891697
md5:3689e767c41858bb53db20190b6542a5
Working:
Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
Audio DAC (using PCM512x DACs e.g. Hifiberry DAC+)
Bluetooth
Camera (using official Pi camera modules & UVC USB webcams)
GPIO
GPS (using external USB modules e.g. U-Blox 7)
Ethernet
Hardware accelerated graphics (VC4)
HDMI display
I2C
IR remotes (using external GPIO IR modules e.g. TSOP4838)
RTC (using external GPIO I2C modules e.g. DS3231)
Serial console (using external GPIO serial console adapters e.g. PL2303)
SPI
Touchscreen/multi-touch (using official 7” display with SwiftShafer software renderer)
USB (mouse, keyboard, storage, etc)
Wifi
Wifi tethering
Not working:
Hardware video decoding & encoding
Issues:
SELinux is in permissive mode
and more…
Sources:
kernel
Thanks:
peyo-hd and everyone who has contributed to android-rpi
brobwind for graphics and bluetooth fixes
Eric Anholt for VC4 graphics driver
Google for Android Things platform
Android-x86 project
LineageOS team & everyone who has contributed to LineageOS 16.0
How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About tablet -> Click ‘Build number’ several times
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> System -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> System -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: Settings -> Storage shows total system size of 4 GB. There's unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Or you can flash my resize zip in TWRP.
Q: My display is not working. I can only see the rainbow screen but no Android boot animation. What should I do?
A: This build only supports HDMI displays that report supported resolutions using EDID. See this page under 'Which values are valid for my monitor?' to see how to check which resolutions your display supports using Raspbian. 1280x720 resolution is used by default with this build. If your display doesn't support 1280x720 resolution, you can try changing value in /boot/resolution.txt to something it does.
Q: I have official 7” LCD display and touchscreen. What should I do?
A: Official 7” touchscreen is only supported using SwiftShader software renderer. See below how to switch between different graphics drivers. You will also need to change display size under Settings -> Display -> Display size (or change ro.sf.lcd_density to 120 in /system/build.prop) to adapt to the smaller resolution.
Q: I need to use SwiftShader software renderer to use the official 7” display or I want to boot without any display connected. What should I do?
A: Warning, SwiftShader is a software renderer and using it affects graphics performance. You can switch between MESA and SwiftShader graphics drivers by executing following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal):
Code:
su
rpi3-graphics.sh swiftshader
Code:
su
rpi3-graphics.sh mesa
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to create a DIY hardware power button?
A: You can send power button events by connecting GPIO21 to ground.
Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) to enable the feature and reboot your device:
Code:
su
rpi3-powerbutton.sh
You can also use the DIY power button to boot the device to TWRP recovery. Press and hold the button while powering on the device until you see the TWRP screen. If you use this method to boot to recovery, you can ignore what is said about booting into/out of TWRP later in the FAQ.
Q: How to enable audio through 3.5mm jack?
Execute following commands in 'adb shell'/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) to enable the feature and reboot your device:
Code:
su
rpi3-audio-jack.sh
Q: How to boot from USB device?
A: Warning, this is an experimental feature and there’s still some issues with it. Android shows USB storage notification for each partition and you should ignore these. TWRP shows errors in few places but everything seems to be working regardless of this.
Follow the official instructions on how to enable USB boot on Pi 3 B (this step is not needed on Pi 3 B+)
Write image to your USB device as above
Mount the USB device on your computer and rename following files on the boot partition:
Code:
mv ramdisk.img ramdisk-sdcard.img
mv ramdisk-usb.img ramdisk.img
mv ramdisk-recovery.img ramdisk-recovery-sdcard.img
mv ramdisk-recovery-usb.img ramdisk-recovery.img
Plug in the USB device to your Raspberry Pi, remove any sdcard, and boot
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: You can execute the same script in TWRP terminal (Advanced->Terminal) if you have boot and system partitions mounted (Mount->Boot & Mount->System):
Code:
rpi3-recovery.sh boot
Or you can flash my recovery2boot zip in TWRP.
Q: How to update from previous LineageOS 16.0 build without losing data?
A:
Boot to TWRP recovery with the build you want to keep the data (see FAQ)
Plug in an external USB storage device and select 'Backup'
Use 'Select Storage' to choose the USB device and 'Swipe to backup' (it's only necessary to backup the data partition so you can uncheck other partitions to speed up the process)
Write new LineageOS 16.0 image to the sdcard following installation instructions
Boot to TWRP recovery with the new build (see FAQ)
Select 'Restore' and find the backup you created from the USB device ('Select Storage')
Make sure you only have data selected as partitions to restore (uncheck other partitions if available) and select 'Swipe to Restore'
(Flash Google apps package/other add-ons you had previously installed)
Boot out of recovery (see FAQ)
Q: How to install Google apps?
A: Warning, installing gapps slows things down especially on low-end devices with limited amount of RAM such as this one.
Download open_gapps-arm-9.0-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install open_gapps-arm-9.0-pico-xxxxxxxx.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)
Merged commits not mentioned in the changelog.
13.7. changelog:
add ir-keytable tool to configure IR remotes
enable USB gadget support & fix adb toggle in developer options
add support for storage devices with exFAT filesystem
hide su binary when root access is not enabled in developer options
add support for PCM512x audio DACs (tested with Hifiberry DAC+)
improve support for Waveshare HDMI touchscreens
fix recording videos with camcorder
add TWRP flashable zip to resize data partition (see FAQ)
update TWRP to 3.3.1-1
update to MESA 20.1.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
update to Linux 4.19.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 July 2020 (merged)
7.2. 2020 changelog:
add camera HAL to support Pi camera modules and USB webcams (thanks to Android-x86)
update to MESA 19.3.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
enable hardware overlays (improves graphics performance)
add option to switch to SwiftShader software renderer e.g. to use official 7” touchscreen or to boot without any display connected (see FAQ)
fix portrait apps on forced landscape orientation (thanks to Ladehunter)
update GPS HAL
option to use DIY hardware power button to boot to TWRP recovery (see FAQ)
initial support for IR modules and remotes (tested with TSOP4838)
update to Linux 4.19.102 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2020 (merged)
22.12. changelog:
update to MESA 19.3.1 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
set default resolution using a configuration file (see FAQ)
add vendor init library to set serial number, revision, and resolution properties
add health HAL to fake battery/charging
add script to enable audio through 3.5mm jack (see FAQ)
add initial support for RTC hardware (tested with DS3231)
update to Linux 4.14.160 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 December 2019 (merged)
27.6. changelog:
initial LineageOS 16.0 build
hardware accelerated graphics (thanks to brobwind for putting the final pieces together)
VC4 using Mesa 19.1 with drm_hwcomposer & minigbm gralloc
fix bluetooth on Pi 3 B+ (thanks to brobwind)
add initial support for booting from USB devices (see FAQ)
add support for DIY hardware power button (see FAQ)
update TWRP to 3.3.1-0
update to Linux 4.14.129 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2019 (merged)
Previous builds:
AndroidFileHost
Thanks for the build. Going to try this out today. Is there any way to connect this to a PC as an android device (like someone would connect a phone to PC)?
sabaatworld said:
Thanks for the build. Going to try this out today. Is there any way to connect this to a PC as an android device (like someone would connect a phone to PC)?
Click to expand...
Click to collapse
Not using an USB cable if that's what you're asking.
ADB works over wifi and ethernet and you can use adb push/pull to transfer files to/from the device (or use an external thumb drive).
KonstaT said:
Not using an USB cable if that's what you're asking.
ADB works over wifi and ethernet and you can use adb push/pull to transfer files to/from the device (or use an external thumb drive).
Click to expand...
Click to collapse
Sad to hear that. Was hoping I could use this RPi as a cheap android device.
感謝 有個問題 有些APP會在開啟時改變螢幕的方向和尺寸 同時發送出權限請求 系統UI崩潰 配置config有辦法強制禁止對顯示器做任何更改嗎?
Thanks! There is a problem. Some apps will change the orientation and size of the screen when they are turned on. Send a permission request at the same time. System UI crashes. Is there a way to configure Config to forcibly disable any changes to the display?
che0033 said:
感謝 有個問題 有些APP會在開啟時改變螢幕的方向和尺寸 同時發送出權限請求 系統UI崩潰 配置config有辦法強制禁止對顯示器做任何更改嗎?
Thanks! There is a problem. Some apps will change the orientation and size of the screen when they are turned on. Send a permission request at the same time. System UI crashes. Is there a way to configure Config to forcibly disable any changes to the display?
Click to expand...
Click to collapse
What app are you using? Steps to reproduce the issue? Logcat?
Hi I wanted to ask if you plan to add support for USB? I mean to raspberry act like phone when connected though USB to PC. It would make it perfect as phone replacement for using with android auto/AAgateway. Thanks for answer
Nice! I like seeing stuff like this for the pi. I remember having so much fun tinkering with building the oreo lineage15.1 rpi3 stuff a bit ago. Also, I heard something about someone trying to sell your builds of lineage for pie, so will the lineage-16.0 branch for some of the files on the github page for this not be released to the public? Either way, I appreciate your work a lot and hope you can continue as these are amazing!
darkchmatak said:
Hi I wanted to ask if you plan to add support for USB? I mean to raspberry act like phone when connected though USB to PC. It would make it perfect as phone replacement for using with android auto/AAgateway. Thanks for answer
Click to expand...
Click to collapse
No current plans.
My LineageOS 14.1 and 15.1 builds are fully open source so there's nothing stopping you/someone else doing this yourself. Shouldn't be any problem adding it here after that (I'll credit the author of course as always ).
turtleletortue said:
Nice! I like seeing stuff like this for the pi. I remember having so much fun tinkering with building the oreo lineage15.1 rpi3 stuff a bit ago. Also, I heard something about someone trying to sell your builds of lineage for pie, so will the lineage-16.0 branch for some of the files on the github page for this not be released to the public? Either way, I appreciate your work a lot and hope you can continue as these are amazing!
Click to expand...
Click to collapse
Wasn't trying - was and still is selling builds for $9! Nothing but builds from lineage-rpi sources with some apps bundled in. It was even promoted on Pi Foundation's own MagPi Magazine as his work and the article was brought to my attention. I spent _a lot_ of time on this last fall but couldn't really get anywhere. You can read about it e.g. here and here.
What makes this very problematic for Exton is that he is not complying with GPLv2 that Linux kernel is licensed under. GPLv2 obligates anyone distributing a binary to release a complete corresponding source code. Even if the only modification you make is stick your own name on other people's work...
That is exactly why I haven't published lineage-16.0 branches apart from the Linux kernel (https://github.com/lineage-rpi/android_kernel_brcm_rpi3/tree/lineage-16.0) as that is naturally also my legal obligation. You can't do Android with just the Linux kernel source, though. I was thinking about putting up a private GitLab project where I could share the source code with reputable developers who actually have some ideas how they want to improve what is already available. I know some companies are you using my previous LineageOS builds which is why I've licensed some stuff under non-commercial license in this one. They've been asking for private tech support but I still can't get as much as a donation even when promised.
KonstaT said:
Wasn't trying - was and still is selling builds for $9! Nothing but builds from lineage-rpi sources with some apps bundled in. It was even promoted on Pi Foundation's own MagPi Magazine as his work and the article was brought to my attention. I spent _a lot_ of time on this last fall but couldn't really get anywhere. You can read about it e.g. here and here.
What makes this very problematic for Exton is that he is not complying with GPLv2 that Linux kernel is licensed under. GPLv2 obligates anyone distributing a binary to release a complete corresponding source code. Even if the only modification you make is stick your own name on other people's work...
That is exactly why I haven't published lineage-16.0 branches apart from the Linux kernel (https://github.com/lineage-rpi/android_kernel_brcm_rpi3/tree/lineage-16.0) as that is naturally also my legal obligation. You can't do Android with just the Linux kernel source, though. I was thinking about putting up a private GitLab project where I could share the source code with reputable developers who actually have some ideas how they want to improve what is already available. I know some companies are you using my previous LineageOS builds which is why I've licensed some stuff under non-commercial license in this one. They've been asking for private tech support but I still can't get as much as a donation even when promised.
Click to expand...
Click to collapse
Wow that's really horrible! I can't believe that it still is happening. I love building stuff on my own(in fact, I was considering trying get any device I have laying around to work for a custom rom someone I semi-know started) and that really makes me sick that you have to deal with that. Hopefully you can get that situation resolved, because I'm sure that's a huge hit in the stomach for that to happen. Really sours the whole open-source nature of things when someone takes advantage of the community.
Hi. I am not capable in this kind of development. What would be involved in making the build detect a wired ethernet connection?
BarryHavenga said:
Hi. I am not capable in this kind of development. What would be involved in making the build detect a wired ethernet connection?
Click to expand...
Click to collapse
Nothing. Ethernet works just fine the last time I checked.
Edit. Tested again and it works fine on Pi 3 B at least. Android has no settings options for ethernet but a small statusbar icon appears when you're connected using ethernet.
This is the best implementation of Android on pi till date. Super smooth no more random force close and app not responding.
Note : I have not installed gapps.
@konsta Any chance of running the Android in 1080p instead of 720p
Can some one suggest a remote control Android app which controls raspberry pi. I know lot of wireless mouse available in the market.
Right now Im using a wired mouse I have to go near to tv every time for controlling
reversegear said:
@konsta Any chance of running the Android in 1080p instead of 720p
Click to expand...
Click to collapse
You can try editing debug.drm.mode.force property in /system/build.prop and see how it goes (also change display density property or display size from display settings). Already struggling with the limited amount of RAM so this is likely going to affect performance.
Hi @KonstaT, is it possible to dual boot your build using PINN (Noobs)?.
Thanks for your efforts!
anthony24x said:
Hi @KonstaT, is it possible to dual boot your build using PINN (Noobs)?.
Thanks for your efforts!
Click to expand...
Click to collapse
You need to contact procount who is developing PINN and ask him. Some time ago he said that he had some problem with adding LineageOS 16.0 support but I don't know about the current status.
Generally speaking I don't recommend using anything else than the latest build from my site. There was PINN support for some previous LineageOS versions but they were never updated and quickly fell out of date. Not that there's currently any plans for any LineageOS 16.0 updates, though...
Okay I see, thanks anyway.
Kind regards
- - - - - -
This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
- - - - - -
{
"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"
}
FEATURES
We provide a secure and up to date ROM, check the Lineage Trust status of your phone!
Secure ROM
Fine-grained SELinux policy
Latest 4.14 Linux Kernel release
Improved performance
Wireguard support
USB restrictions
AES-256-XTS File Based Encryption (FBE)
Signed with developer keys
Nice features
FDroid and AuroraStore preinstalled
Bluetooth phone calls
KNOWN ISSUES
Don't be scared by the "BETA" label. Our ROMs are always rock solid.
Some audio effects are missing
Miracast not working
Wideband SCO
IMS not working (No AOSP solution yet)
Some minor issues are described in the FAQ below.
DOWNLOAD
You can download the latest version under the following links:
S10e
S10
S10+
INSTALLATION
Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.
Make sure you select: Zip signature verification.
This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.
SECURITY ADVICE
Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Do not flash Multi Disabler on this ROM!
What a Wurst!
This ROM is developed by derf elot, linux4 and modpunk
Contributors
modpunk, derf elot, linux4
Source Code: https://github.com/whatawurst
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.236
ROM Firmware Required: XXSBFUF3
Based On: LineageOS
REQUIRED FIRMWARE: XXSBFUF3
CHANGELOG
2021-07-23 | 2.2
Update to Linux 4.14.239
2021-06-23 | 2.1
Update to Linux 4.14.236
Fixed GPS
Improved autobrightness (Thanks to linux4)
2021-06-07 | 2.0
Added support to disable fast charging
Kernel fix to disable the touchscreen during handheld phone calls
Improved auto-brightness
2020-12-17 | 1.4
Add support for glove mode
2020-10-26 | 1.3
Update to Linux 4.14.206
2020-10-26 | 1.2
Update to Linux 4.14.202
Added Seedvault (Video)
Fixed bluetooth regression
Fixed NFC service registration (SELinux denials)
Fixed camera issues
Fixed LineageOS recovery
2020-09-11 | 1.1
Update to Linux 4.14.196
Added Kernel changes from CTG4 (fixes usb audio issues)
Improved DT2W support (thanks linux4)
Fixed camera access to some sensors
2020-08-08 | 1.0
Update to Linux 4.14.192
Performance improvements
New thermal HAL for better overheating protection
Fixed light sensor auto-brightness
Fixed extended-length NFC (required for ePerso App)
2020-07-13 | RC2
Update to Linux 4.14.188
Fixed reboot issue with new Power HAL
Fixed crash issue with power HAL
Update to latest Security release
Removed su for adb root
2020-07-06 | RC1
Update to Linux 4.14.187
Performance improvements (new power HAL)
2020-06-17 | BETA3
Update to Linux 4.14.184
Update to Wireguard 1.0.20200520
Fixed HDR support
Upstreamed vibrator service implementations
2020-05-20 | BETA2
Update to Linux 4.14.177
Added Wireguard support
Added support for L1 widevine security level (Netflix etc.)
Added in-screen fingerprint support for S10(+)
Added "Wireless Powershare" support
Get the full list of sensors working, including tilt, rotation_vector, game_rotation_vector and pick_up_gesture
Fixed USB tethering
Fixed wifi hotspot
Fixed proximity sensor
Fixed phone calls over bluetooth
Fixed phone off charger with nice animation now
2020-04-14 | BETA1
Update to Linux 4.14.175
Added magisk building support
Added USB Trust HAL
Added "Always On Display" quick setting tile (merged upstream)
Fixed performance issues
Fixed video calls (e.g. in Signal)
Fixed proximity sensor
Fixed significant motion sensor
2020-04-05 | BETA0.1
Fixed Play Store
Fixed permission list
Added missing vendor properties
Fixed product definitions
2020-04-03 | BETA0
Initial release
OUR UPSTREAM EFFORTS
Common SELinux policy for Samsung devices
AOD Quick Setting Tile
In-screen fingerprint HAL for LineageOS
Powershare support for LineageOS
Common timed_out vibrator service for Samsung devices
Features + Known Bugs Summary:
This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.
Ratings Description
++ perfect (in depth tested, performs like stock or better)
+ good (lighly tested only or has minor flaws but is good enough for normal use)
o ok (can be used with some limitations)
- broken (doesn't work at all)
x not supported (unlikely to be implemented, relies on samsungs closed source code)
? can't test, please give feedback
Performance
++ geekbench 5 score: 2267 (gsmarena stock: 2141)
++ antutu v8.4.1 score: 403909 (gsmarena stock: 389694)
Speed (values in MB/s, sr =seq. read, sw = seq. write, rr = random read, rw = random write)
++ internal SD 128GB
AndroBench5: sr 815.0, sw 193.1, rr 138.7, rw 24.7 (= notebookcheck stock)
CPDT 1GB: sr 735.3, sw 139.2, rr 19.2, rw 4.52
++ external SD, 128GB Samsung Evo Plus
Androbench5: sr 68.2, sw 34.5, rr 5.75, rw 2.56
CPDT 1GB: sr: 75.2, sw: 29.5, rr: 4.08, rw: 1.71
++ USB 3.0 MTP, sw 105MB/s (PC CrystalDiskMark -> mtpdrive -> internal SD)
++ USB 3.0 OTG, sw 105MB/s (Sandisk Extreme 64GB -> internal SD, 10.8GB file, 102s)
+ bluetooth file transfer, 0.1MB/s (29MB; from other phone 4m42s, from PC 5m24s) (theoretical max. is 0.3 for BLE4.0, 0.8 for BLE4.2 and 1.4 for BLE5.0)
Connectivity
++ phone calls, 3G, LTE; also with dual sim
++ wifi (delivers 50Mb/s, the maximum my provider supports)
++ bluetooth (file transfer to phone & pc; headphons incl. mic; speakers; keyboard incl. special keys)
++ NFC (only card read tested)
x VoLTE
Screen
+ 10 finger multitouch, "high touch sensitivity" mode not available
++ full brighness range available
++ double tap to wake
+ AOD works, but might be dimmer than stock and brightness cant be changed. While active the proximity sensor is used an its LED blinks dimly next to the camera
Sound
++ dual laudspeaker for media, quality as expected, high volume selectable
+ earpiece (no in depth test)
+ headphones (3.5mm jack) have clean audio, high volume selectable, limited to 16bit/48kHz (instead of 24bit/192kHz) possibly by ROM
+ build-in mic, limited to 16bit/48kHz (instead of 24bit/192kHz), volume should be normal (test)
+ headphone mic, limited to 16bit/48kHz (instead of 24bit/192kHz)
+ some external DACs supported, limited to 24bit/48kHz; (reported by @El Dun)
Camera (with opencamera + camera API v2)
++ wide, ultrawide, front, front-crop
++ PDAF autofocus, face tracking optional (main + front camera, ultrawide is always fixed focus)
++ manual setting for exposure/ ISO/ shutter/ focus
++ raw files option (main camera)
++ optional HDR
+ dual apperature (main camera), only manual switch (default f1.5)
+ video up to 2160p/30fps, 1080p/30fps (all cameras should support 60fps, but OpenCamera only produces 30fps files)
+ 1080p/240fps (main)/ 1080p/120fps (front) high speed/ slow-mo works in stock cam + GCam
x no 720p/960fps super slo-mo
x no supersteady
- S10, S10+: no telephoto camera (details + help wanted)
x S10+: no front depth camera
Sensors
++ gps, quick fix with A-GPS data
+ fingerprint (all variants), can glitch during setup (see bug list)
++ accelerometer, gyroscope, magnetometer, pressure, light (front) (all values are within tolerance)
+ light sensor, but only the front/ under-screen sensor, not the rear sensor
++ IR/RGB sensor outputs values for IR/Red/Green/Blue/Clear (test) (COM.SAMSUNG.SENSOR.LIGHT_IR)
++ grip sensor
+ front proximity (makes only one measurement per second, if you put it quickly to your ear it may touch the screen before it's turned off; reported by @Lav64)
++ software sensors: step counter, rotation vector, gravity, linear acceleration, compass
++ S10/S10+ heart rate/ SpO2 (confirmed by @Ned)
o several software sensors don't produce data, but don't do it on stock either. Affected are the IDs: PICK_UP_GESTURE, COM.SAMSUNG.SENSOR.PROXIMITY_POCKET, COM.SAMSUNG.SENSOR.HALLIC, COM.SAMSUNG.SENSOR.BIO_IR (proof thanks @Brembo109, more info from modpunk)
Charging & Battery
++ 15W quick charge
++ 4.75W reverse charge (with USB OTG adapter)
+ 7.5W+ qi-wireless charge (limited by my charger)
+ 2.5W+ reverse qi-wireless charge (limited by the receiver IC BQ51013)
+ low 40mW idle power consumption (details)
+ ACCA (advance charging controller app) works with limited settings
Misc
++ all buttons, bixby can be reprogrammed (workaround for other functions)
++ wired headphone buttons (pause/play, vol+, vol-)
+ flashlight has only one brighness option (instead of 5 on stock)
- S10e: no fingerprint swipe up/down geture, not even with 3rd party app "Quick Fingerprint Geture"
Known bugs:
when phone is shut down, it reboots instead (fixed in RC2)
reboot to recovery boots directly into system (fixed in RC2)
reboot takes long, about 30s (fixed in RC2, now it only takes a few seconds)
double tap to wake not always working (should be fixed in RC2)
holding fingerprint too long during setup can cause problems details
in full screen apps there may be a black bar to hide the camera cutout which can not be disabled (details, workaround)
high sensitivity touch screen / "glove mode" not available (details)
bixby-button hold-shortcut does not work (details)
google backup does not work with 4x4 or 5x5 pattern. This is an LineageOS issue, but important enough to deserve a note here. (details (thanks @Ivo_Todorov)
Installation:
How do I install this ROM on my phone for the first time?
Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.
Confirm the firmware version
Check the top of the ChangeLog which firmware version is required for the ROM release to work well
Go to settings/software-update and update only if the new version matches the requirement!
Alternative: flash with odin/heimdall (details see below)
Unlock your device
Backup all data, unlocking will factory reset your phone
Enable developer mode to and enable the OEM-unlock switch there
Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
Follow instructions on-screen
Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
Install our TWRP (official thread) | more details (thanks @AndrOdin)
Download our TWRP recovery and the vbmeta-disabled.img file
Unpack the .xz file with 7zip
Check integrity of TWRP (optional, but important for security)
Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
Install Samsung USB drivers and odin, (direct link)
Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
Turn off device, boot to bootloader and, once odin detects it, click "Start"
When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
When the secondary warning appears, release everything but VolumeUp
Swipe slider to allow for modification
Install LinageOS
copy the ROM ZIP file an external SD card
Boot into the recovery
Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
Optional: Flash GAPPS (e.g. OpenGAPPS)
Reboot to system
How do I update LineageOS?
Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:
Backup all important files optional, but very helpful if something goes wrong)
Remove any pin/password/pattern to prevent "retry after 86400 seconds"
Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
Boot into the recovery, do not reboot until you've installed the new ROM and firmware
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
(Optional: Update GAPPS to the latest version)
Wipe dalvik and cache
Reboot to download
Flash new firmware with instructions below
(Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
Reboot to system
How do I update the firmware?
On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.
How do I update the firmware manually?
Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:
If you use Heimdall:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
Extract the package
Flash the firmware files with this command:
Code:
heimdall flash \
--BOOTLOADER sboot.bin \
--PARAM param.bin \
--UP_PARAM up_param.bin \
--CM cm.bin \
--KEYSTORAGE keystorage.bin \
--UH uh.bin \
--DTB dt.img \
--RADIO modem.bin \
--CP_DEBUG modem_debug.bin
If you use Odin:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
Flash the 3 files with Odin (tested with latest Odin 3.14.x)
You can download the repacked firmware from the links below.
S10
S10e
S10+
If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:
From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
CP_G97?FXX*.tar.md5
Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4
Try again after 86400 seconds?
With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)
You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.
3rd Party Software:
How do I install Google apps?
You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.
Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!
Can I use GPay? What about other banking apps
GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).
Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!
How do I get MicroG with this ROM?
MicroG is an open source alternative to GAPPS. , but unfortunately not recently updated and therefore not recommended.
If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14 . Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)
Does this ROM have root?
Not by default. If you need root (eg. for AFWall) you can get it through Magisk.
How do I install Magisk?
Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Option 1 (recommended):
Download the boot image for Magisk: S10e -- S10 -- S10+
Verify the integrity of the file -> See INTEGRITY
Unzip the boot image using xz or p7zip
(Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
Install https://******************/
Option 2:
Patch TWRP
Which camera app do you suggest?
OpenCamera:
Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
All cameras supported (except telephoto, this is a issue with the ROM)
Manual change of exposure, aperture, shutter speed, ISO
The (main) developer uses an S10e himself so you can expect good HW support
You can get it from F-Droid or Play Store
GCam Variants:
There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).
In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
simpler user interface
better single-shot HDR
better panoramas + photospheres
SlowMo video (1080p @120/240fps)
I've also written a more detailed comparison. You can have both camera apps installed at the same time, so you can always choose the better one depending on the scenario.
Getting Help:
General:
Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here We do this in out free time and it may take us some time to answer, so please be patient.
How to report a bug?
To fix any bug we first have to be able to reproduce it. Please include all relevant information:
device (S10e/S10/S10+)
ROM version
is gapps/ microg/ magisk installed?
steps to reproduce the issue
When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).
How to create a logfile?
To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:
install adb drivers
open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
Connect your phone via USB
Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
Clear the log using: adb logcat -c
Start loggingwith: adb logcat | tee beyond.log
Reproduce the issue
Stop logging by pressing CTRL+c
Send us the log (in a PM)
How do I enable USB Debugging?
To enable USB Debugging you need to do the following steps:
Go to Settings -> About Phone
Look for Build number
Tap on Build Number several times till you get the message that Developer Options have been enabled
Go to Settings -> System -> Advanced -> Developer Options
Enable USB Debugging
About this FAQ:
This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.
Changelog:
20200813 (v1.0)
update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
update: firmware update section (thanks @Stef4n82!)
update: ROM update section
update: getting help section, rewritten for clarity
update: proximity sensor, slow sample rate (thanks @Lav64)
update: audio section with my test and @El Dun's report
add: gpay/safetynet explanation
change: link formating to stay under the 30k character limit
20200809 (RC2)
update: audio output with limited frequency range, limited DAC support (thanks @El Dun)
update: double tap to wake works well, used it for a few weeks now without issues
update: "86400 seconds" section (thanks @Exilion90)
add: links to each version of this FAQ, just click one of the datecodes
add: ACCA to feature list
add: ADO works kinda
add: dual sim to feature list (thanks @Exilion90)
20200802 (RC2)
update: microG section (thanks @ichmyselfandi)
update: unlock instructions, setup with wifi required (thanks @Lunat1c)
update: "86400 seconds" section (thanks @Lunat1c & @Stef4n82)
add: gapps/ microg/ google framework requirement for the GCAM (thanks @KanyT & @ned14)
add: bug google backup pattern with 4x4 or 5x5 pattern (thanks @Ivo_Todorov)
fix: twrp "more details" link (thanks @Lunat1c)
20200719 (RC2)
update: rgb light sensor, all channels working
update: software sensors don't output values on stock either (thanks @Brembo109)
add: gcam information (thanks @ned14)
add: grip sensor
add: microg appendum (thanks @ned14)
add: workaround for black status bar in fullscreen
add: bug no glove mode (thanks @raggatip)
add: bug bixby button hold shortcut (thanks @Lav64)
20200713
update: feature/ bug list (previously called working/ not working) with fixed from RC2
update: instructions for microG (thanks @ned14)
update: magisk install instructions
update: wireless power share works fine, the phone just didn't like the synthetic load I used for testing
add: black bar on camera cutout in fullscreen apps (thanks @Sradgads)
20200707 (RC1)
update: section "get help" with copy & paste template
update: font for cmd to Courier New
confirm: removing pin/password/pattern solves the 86400 second wait delay (thanks @fishnetfancy)
add: working/not working section
add: this changelog
add: telephoto lens not working (thanks @Ned)
add: several RC1 issues (thanks @angela5246)
add: vbmeta_disabled note to firmware instructions (thanks @okloloi)
add: reminder to update Magisk alongside lineage (thanks @fishnetfancy)
20200705 (Beta3)
first FAQ update by me (ctrej)
change: order to the "natural" installation flow
change: install section into a more detailed checklist (thanks @AndrOdin)
add: sub-sections (install/ 3rd party/ support)
What is difference between this and Ivan's lineage os?
BratoMo225 said:
What is difference between this and Ivan's lineage os?
Click to expand...
Click to collapse
The most obvious one is that we provide SELinux enforcing and care about security and privacy. For the rest I can't give you an answer as Ivan doesn't want to release the source of his device tree. It would be great if Ivan would join our effort and contribute.
Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.
angela5246 said:
Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.
Click to expand...
Click to collapse
If you switch, you have to format /data I'm sorry. We decided to go with AES-256-XTS encryption for this ROM and also the code is signed with my developer keys! There are package signature checks in place for apps which would prevent you to use the ROM.
If you want to build it yourself, instructions are in the beyond0lte README.
However you can just go to Settings -> Apps and disable FDroid and AuroraStore.
Also I've added and AOD (Always On Display) Quicksetting Tile, but this hasn't been merged upstream yet. You might want to pick those changes.
I cant flash it. Im using latest twrp 103
BratoMo225 said:
I cant flash it. Im using latest twrp 103
Click to expand...
Click to collapse
Which TWRP are you using? Do you use the one we built?
No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what
can i flash magisk via twrp or are there any extra steps i need to do before it will work?
BratoMo225 said:
No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what
Click to expand...
Click to collapse
Did you also flash a vbmeta image which disables vbmeta checking?
catormeme said:
can i flash magisk via twrp or are there any extra steps i need to do before it will work?
Click to expand...
Click to collapse
I'll upload a boot.img which is pre-patched for Magisk 20.4. You can flash this via twrp and Magisk should work, just need to install the Magisk Manager.
edit: Here it is https://www.androidfilehost.com/?fid=4349826312261761185 Unzip the file. If you wish, you can verify it using gpg, then flash the boot.img via TWRP.
modpunk said:
Did you also flash a vbmeta image which disables vbmeta checking?
Click to expand...
Click to collapse
nope. nothing. I will fix my phone with odin right now and then ill try those steps
BratoMo225 said:
nope. nothing. I will fix my phone with odin right now and then ill try those steps
Click to expand...
Click to collapse
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.
modpunk said:
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.
Click to expand...
Click to collapse
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?
BratoMo225 said:
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?
Click to expand...
Click to collapse
You need to unpack it.
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....
vomad said:
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....
Click to expand...
Click to collapse
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.
modpunk said:
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.
Click to expand...
Click to collapse
"Good news everyone!" So I'll be waiting for the S10/S10+ release and immediatly will flash this rom (and magisk boot image I hope)