Develop Bugs

TWRP 2.6.3.2 TeamWin Recovery Project 10/5

Default [RECOVERY] [10/5/13] TWRP 2.6.3.2 - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.6.3.2 for the Galaxy Note 3 (T-Mobile)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Special credits:
Dees_Troy for quick porting.
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
CRudner and Reb0rn for testing
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.6 features
Older Releases
What's new in 2.4:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes
-Support for exFAT formatted sdcards
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Other minor bugfixes and improvements
-cm10.1 build support
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
What was new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
Gerrit Instance - http://review.teamw.in
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
n7100 Device Config: https://github.com/bigbiff/android_device_samsung_n7100
Kernel: https://github.com/bigbiff/kernel_samsung_sgh-i317
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://teamw.in/project/twrp2
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
XDA:DevDB Information
TWRP, a Tool/Utility for the Samsung Galaxy Note 3
Contributors
bigbiff, Dees_Troy
Version Information
Status: Testing
Created 2013-10-05
Last Updated 2013-10-05

Reserved

Reserved 2

good.
using your work on note 2 and now on note3. :good:
But can i use this (tmobile version) on my french mobile (LTE SM-N9005) without problem??

someone have a workong link for 2.6.3.2 version?

does this work on SM-N900?

kenzolo said:
someone have a workong link for 2.6.3.2 version?
Click to expand...
Click to collapse
here http://teamw.in/project/twrp2/198

micky387 said:
here http://teamw.in/project/twrp2/198
Click to expand...
Click to collapse
are you able to download 2.6.3.2 version?

Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4

micky387 said:
Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4
Click to expand...
Click to collapse
come on micky I understand...but I can't downlod 2.6.3.2 version (404 error page note found)

404 - Not Found
micky387 said:
Follow this link...
Click to expand...
Click to collapse
404 - Not Found

Are all hlte devices supported it is only htletmo listed on the official device list
Sent from my SM-N9005 using Tapatalk 4

Works fine on N9008, thank you very much, finally a decent recovery
Using 2.6.3.1, 2.6.3.2 download gives error 404 as someone else said.

I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.

Yeah the devs derped the upload of 2.6.3.2 - neither of the two downloads (typo and no typo) work, both are 404. Been like that since yesterday afternoon. Running 2.6.3.1 for now.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
wencel said:
I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.
Click to expand...
Click to collapse
Once you modify ANY of the phone's partitions, you trip the KNOX_WARRANTY_VOID flag in the bootloader.

With twrp 2.6.3.1...anyone who has sucessfuly created backup and restored without issues? Just asking becoz the cwm recovery still cannot restore properly.
[email protected] from Bad Ass Note III-SM-N9500

Thanks for your hard work! Still waiting on a SM-N9005 version. Not really sure what's required for that or if the above is compatible, but I'm happy to wait until goomanager has a compatible one =)

Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?

dark_dude said:
Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?
Click to expand...
Click to collapse
Just downloadet the TWRP 2.6.3.2 file from Goo.im

inffy said:
Just downloadet the TWRP 2.6.3.2 file from Goo.im
Click to expand...
Click to collapse
Is this link？
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.6.3.2-hltetmo.tar

[BOOT][4.2+][UNOFFICIAL] MultiROM for TF300T [2014-02-13]

MultiROM lets you install multiple ROMs into subfolders, just by flashing them using a modified TWRP.
This is an unofficial port of MultiROM originally developed for the Nexus series to our beloved TF300T.
Big thanks @Tasssadar for the original work!
THIS IS AN EARLY VERSION OF THIS PORT, NOT ALL FEATURES ARE FULLY TESTED.
But please test and give feedback, so I can eventually remove above line.
Features
Run a primary Android ROM from the normal partitions.
Run multiple secondary ROMs from subfolders on an SD card or on an external USB stick/drive.
Easily add/update your primary and secondary ROMs using a modified version of TWRP.
Install Ubuntu and Ubuntu Touch as secondary ROMs Not supported yet.
And more...
Changes vs. official MultiROM
This section is mostly useful for people using MultiROM on another device. New users can safely ignore it.
My first test - installing a plain CM 11, installing MultiROM, and then installing OmniROM with its own kernel - failed gloriously. The reason was that the official MultiROM re-uses the kernel of the currently installed Android system and that kernel does not include the kexec hardboot patch required for MultiROM to work properly.
The beauty of MultiROM is that - once installed with a proper kernel - it allows an average user that has never heard about kexec and never installed a custom kernel to run multi-boot at the touch of a finger. So I decided that my first simple use case must be supported.
The obvious solution was to ship a working kernel with MultiROM, save the currenly installed kernel for the primary ROM and boot that via kexec. The idea is to sacrifice another 10 secs on booting the primary ROM for making MultiROM much easier to install and to use. However, this decision led to several changes in the TWRP user interface:
The "share kernel with primary ROM" option was removed. Each ROM has its own boot image and is always booted via kexec.
The "Inject current boot sector" on the MultiROM screen button was replaced with a "Reinstall" button. Use this, if you have overwritten the boot sector, for example via fastboot. Mind, reinstalling MultiROM will save the current boot partition and use it for booting straight into the primary ROM, so better make sure this works, before running reinstall, or you won't be able to boot into your primary ROM after reinstallation.
The "Add/Remove boot.img" button on the ROM management screen has been replaced with "Replace boot.img" and can be used to easily install a custom kernel for that ROM.
Looking forward to your feedback on this major change!
Downloads
Downloads are available from the "Downloads" tab at the top of the page.
MultiROM installer including the modified TWRP:
multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.zip
TWRP for MultiROM (not needed, if you use the installer):
twrp-multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.blob
Installing and Upgrading MultiROM
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet. The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet. I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Make a backup!
MultiROM will modify your system, and if anything goes wrong, this backup will be more than helpful.
Check the version of your bootloader.
On the bootloader screen, check the version shown on the top left. MultiROM was ported and tested on version 10.6.1.27.5. If your bootloader version is 10.6.1.27.1 or 10.6.1.15.3 you should have no issues. Version 10.6.1.8 might work, but is likely to cause issues; upgrading is highly suggested. For any other version, make sure you first upgrade your bootloader, or you risk ending up with a brick,
Flash the lastest multirom-vXX-YYYYYYYY-UNOFFICIAL-tf300t.zip
Reboot right away!
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Now you should be able to boot your primary ROM via MultiROM. For next steps, check out "Installing ROMs" in the next post.
Uninstall MultiROM
The uninstaller for the official MultiROM has not been ported yet, but you can get rid of MultiROM following these steps:
Flash your favourite (not MultiROM) recovery.
Restore your boot partition from a backup or re-flash your ROM.
Remove the "multirom" folder on the sdcard.
The latter is optional. You may keep it around for trying MultiROM again later.
Changes
2014-03-16:
Fixed MultiROM reinstallation from TWRP.
Some fixes for swapping primary/secondary ROMs.
Some fixes for primary ROM initrd.
Added support for Ubuntu Touch (needs upcoming manager app).
2014-03-02:
Support secondary ROMs on SD card (not fully tested).
Use packaged initrd instead of the primary ROM's.
Some bug fixes.
2014-02-13:
Allows flashing 4.2-based ROMs without removing the assert line in the updater-script.
Several bug fixes for more stability.
Note that changes may be documented, before the downloads are available. Please check back a little later in that case.
Future Work
In no particular order:
Provide uninstaller.
Add the missing features listed above.
Fix TWRP for encrypted filesystems.
Allow replacing the kernel for any ROM, keeping the ramdisk.
Remove unnecessary drivers (net, sound, camera) from the kernel (currently breaks building the kernel).
XDA:DevDB Information
MultiROM for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
f69m
Version Information
Status: Alpha
Created 2014-02-11
Last Updated 2014-03-16

Installing ROMs
Custom 4.2- and 4.4-based ROMs
To install/update your primary ROM, just flash it as usual with the modified MultiROM TWRP, using "Install" from the main screen.
Installing a secondary ROM is just as easy, but use:
Advanced > MultiROM > Add ROM
You can update a secondary ROM by flashing it from the ROM management screen, using;
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
OTA updates using the update manager coming with your ROM should work fine for both primary and secondary ROMs.
Note: It is no longer necessary to remove the assertion from a 4.2 updater-script.
Gaps, SuperSU, etc.
You can flash additional ZIP files for a secondary ROM from the ROM management screen, using:
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
Asus Stock ROM
Asus stock ROM has a different installer and won't work the same way as custom ROMs.
Here are the steps to install stock ROM as your primary ROM:
Sorry, I have not tested this myself yet, please let me know, how it works out.
Unzip the Asus ROM twice to get the blob.
Flash the blob using fastboot.
Boot into stock ROM.
Re-install the modified TWRP using fastboot (use the separate download).
In TWRP: Advanced > MultiROM > Reinstall.
This should give you a working MultiROM setup with stock ROM as your primary ROM.
If you need more detailed instructions on the first two steps, please refer to the guides in the General section.
Ubuntu Touch
Coming soon...
Ubuntu
Not working yet.
Notes on Specific ROMs
CROMi-X 5.3
Don't try to install CROMi-X as a secondary ROM. It has an amazing installer, but that will nuke your primary ROM's /system partition.
Trouble-shooting
If your primary or one of your secondary ROMs is not booting properly, it can help to restore the boot partition of the primary ROM and then do a clean reinstall of MultiROM.
No worries, you can move your installed secondary ROMs to the side and move them back later.
First try restoring the boot partition from your latest backup, before installing MultiROM and reboot.
If your device boots cleanly into your primary ROM, without showing the MultiROM boot screen, you can skip ahad to step 3.
Next try flashing an unmodified recovery, re-flash your primary ROM and reboot.
If your device boots cleanly into your primary ROM without showing the MultiROM boot screen, you are ready to go to step 3.
Otherwise you should post your issue.
Use a root terminal or a root exlorer to remove the folder /data/media/0/multirom.
Alternatively you can rename that folder, keeping your installed ROMs.
Note: though this folder is on the sdcard, you have to use the path given; trying to use /sdcard or /storage you will get "permission denied", when trying to remove or rename the folder.
Reflash the latest multirom-v*.zip and reboot.
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Try booting your primary ROM. It should now start cleanly.
Try installing a secondary ROM, or move it back to /data/media/0/multirom/roms/ from the folder you renamed above.
Just moving back the folder will make it show up on the MultiROM boot screen.
Please read and follow each step carefully.
If these steps do not make all your ROMs boot properly, please post about your issue in this thread.

Source Code Repositories
The easiest way to build MultiROM is using my manifest following the build instructions below.
Here is a list of the MultiROM-specific repositories that can be built by adding them to the OmniROM tree:
Latest manifest:
https://github.com/f69m/android
MultiROM (check out to "bootable/multirom"):
https://github.com/f69m/multirom
TWRP for MultiROM (check out to "bootable/recovery"):
https://github.com/f69m/multirom-twrp
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
TF300T device config (check out to "device/asus/tf300t"):
https://github.com/f69m/android_device_asus_tf300t
TF300T kernel (check out to "kernel/asus/tf300t"):
https://github.com/f69m/android_kernel_asus_tf300t
Look out for branches named "multirom-*" in above repositories.
Please check the manifest for the latest stable branch.
Build Instructions
Using my manifest makes it easy to check out the MultiROM repositories and a small part of the OmniROM tree needed for building.
Code:
repo init -u git://github.com/f69m/android -b multirom
repo sync
manifest/pick-cherries.sh
source build/envsetup.sh
lunch mrom_tf300t-userdebug
make -j4 multirom_zip

Sweet! Thanks man, this looks pretty cool!
Sent from my SGH-T999 using xda app-developers app

Finally, first download is up!
Let me know, how it works for you.

Thanks for your work.
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??

z1022 said:
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
Click to expand...
Click to collapse
Absolutely, just flash the multirom-*.zip file (includes TWRP), and you should be able to boot into CROMi-X via MultiROM.
But I have not tested with CROMi-X yet, so make sure you have a backup!
Sent from my TF300T using Tapatalk

Thanks
I will try later and report back.
CROMi kernel should be not included the kexec. Can I use the Multirom to install second ROM ??

z1022 said:
I will try later and report back.
Click to expand...
Click to collapse
Great, looking forward to hearing about your experiences.
CROMi kernel should be not included the kexec.
Click to expand...
Click to collapse
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Can I use the Multirom to install second ROM ??
Click to expand...
Click to collapse
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk

Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
As Primary ROM i have NIGHTLY CM11 for TF300T. As "virtual" ROM i installed the same ROM (i want to examine the new GRIMKERN_KitKat).
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.

Dasdranamin said:
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
Click to expand...
Click to collapse
Wow, amazing!
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Click to expand...
Click to collapse
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Sent from my TF300T using Tapatalk

f69m said:
Wow, amazing!
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Click to expand...
Click to collapse
Yes. That's what I meant.

Dasdranamin said:
Yes. That's what I meant.
Click to expand...
Click to collapse
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Sent from my TF300T using Tapatalk

f69m said:
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
Click to expand...
Click to collapse
Yes, in TWRP touch works without any problem!
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Click to expand...
Click to collapse
That would be great! Thanks in advance!

f69m said:
Great, looking forward to hearing about your experiences.
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.

z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
I successfully installed just now on TF201 Omni 4.4.2. ROM TF300T Homebuild versions [20140126] (it's last ROM with MultiWindow feature) + Gapps Mini Modular Package.
All works properly. :good: MultiWindow too.

how long omni finished the booting.
---------- Post added at 11:59 PM ---------- Previous post was at 11:50 PM ----------
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
Try CM11 in second ROM. still stick in CM11 booting screen.

z1022 said:
how long omni finished the booting.
Click to expand...
Click to collapse
First time about 5 min (with Gapps).
Next times about 2 min.

Nice! cant wait to try this, thanks for your hard work!

Hi f69m,
I found: in "MultiROM menu that comes up after boot" I can select a ROM by VOLUME UP/DOWN and confirm by POWER (like in "old" CWM). :laugh:

[ROM+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc-4.4.4

This is unofficial cm11 kitkat android 4.4.4 for the Virgin Mobile Optimus V (runs on Sprint Optimus S as well)
Uses my 3.08 kernel.
I'm offering this over here because skinbark has been busy for quite a while and my builds are way more updated these days.
Purely experimental builds. No real support, I'm sharing my personal builds plus making equivalent internal builds for those of you who like them.
newest builds offering f2fs os2sd!
also fixed camera, and kernel updated to 3.0.101 with HardLight's patchset.
second post mostly outdated, now it's opengapps instead of pa for example. I haven't been updating this in literally years.
now using some of
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
not right now said:
now built with linaro gcc 4.7 (kernel is built with homebrew ct-ng armv6k tweaked linaro gcc 4.7) with -O3 optimizations, except -Os thumb.
Click to expand...
Click to collapse
Wifi AP will reboot if turned on/off/on.
Everything else should work, tell me if it doesn't.
OS2SD /data mounting tweaks from HardLight's OS2SD version.
Smaller, more limited, standard nand-flashable internal builds offered for backwards compatibility or the less adventurous.
Use only THIS RECOVERY (info) (download)
archived said:
OS2SD friendly TWRP recovery, handles partitioning of sd card for OS2SD thanks techvendetta
Click to expand...
Click to collapse
download folder for internal builds:
download folder for OS2SD builds:
here's partitioning info for the OS2SD recovery.
advise: whatever leftover on your card for VFAT/sdcard, either 1Mb or 864Mb swap, 512Mb-768Mb for system, 1Gb or more for data.
expand /sdcard and/or /data as preferred if you use a bigger card. more space in /system? dunno why. doubt there's enough armv6 system apps to fill 512Mb.
current internal build: cm-11-20141014-EXPERIMENTAL-bigsuperROM_internal-thunderc.zip
current OS2SD build: cm-11-20141018-EXPERIMENTAL-f2fs_os2sd_bigsuperROM-thunderc.zip
this should be considered a dev thread since it's on XDA, there's an earlier and discussion thread here.
Sprint and Verizon fix zips attached. Flash in recovery after the ROM before first boot.
OS2SD info in 2nd post.
almost forgot: source
https://github.com/bigsupersquid/android_roomservice
Gapps:
advise: Skinny_4.4_Gapps_new_internal.zip for easy gapps. From here Optimus S won't fit the larger Skinny_4.4_Gapps-new.zip but the V should.
Be patient on first boot. Some reports are as long as 10 min to get past the bootanimation. Takes me at least 5 min.
Carrier Fixes:
Sprint and Verizon. Want another? Got an apns-conf.xml, then post it and your other carrier info.
Basic instructions for internal install:
in twrp, wipe internal data, internal system, and cache.
flash rom, internal carrier fix, gapps.
reboot system.
androidarmv6 turned on TLS in the kernel, and swapped the /system and /data partitions for more room on /system, so you have to use the newest TWRP-multi now as well.
thanks androidarmv6, cyanogen, aosp, thekraven for TheJBC and help, skinbark for initial booting and much work on kitkat for these phones, and techvendetta for his TWRP port. Thanks androidarmv6 and thunderg devs for 3.08 kernel I ported over to thunderc, and HardLight for f2fs in kernel and fstab flags.

OS2SD
OS2SD information
I have been playing with rom-from-sd for quite a while.
kitkat and cm11 make it easy, just by changing the fstab you can mount the ext partitions instead of the mtd partitions in init.*.rc
OS2SD (skinbark named it, it was my mod) uses the regular VFAT plus 3 extra ext4 (or one linux-swap and 2 ext4) partitions on the SD card to hold /swap, /system, /data. Recommend in order: leftover after other 3, 512MB, 512Mb, 1024Mb.
This allows virtually unlimited storage without link2sd methods of any kind. /system can handle whatever you want to flash to it without running out of space, which is handy because kitkat has to be trimmed down to fit an Optimus S or V with their respective 15*Mb or 165Mb of /system space.
when android is running from the card, mount external storage allows manipulation of /system and /data from your linux file manager.
Yeah, yeah, it's all a security hole, but I don't care. It's experimental and fun, and you can fit hundreds of apps on this four year old phone that is labelled 'obsolete' by LG and Qualcomm both.
I still need to remove the 'format sd' and 'unmount sd' from the storage menu in settings to avoid crashes.
Gapps:
advise: Skinny_4.4_Gapps-new.zip for easy gapps. From here
if you want a REAL gapps package...
I made pa_gapps flashing facilitator for twrp/os2sd.
Go get current micro pa_gapps, don't touch the zip.
flash after rom, pa_gapps_modular_micro*.zip no reboot needed.
then after flashing pa_gapps you flash the facilitator (it gets rid of armv7 keyboard libs and installs compatible play services framework.)
Click to expand...
Click to collapse
if you want to use any bigger pa_gapps packages (and you can even install the 200+Mb Stock package on os2sd!) you'll have to follow the instructions for the pa_gapps remover zip TKruzze posted up to remove Google+ (or you'll have fc'ing nightmares) and don't let it install Chrome either (there's another text file needed on the card like the remover, TKruzze left instructions.)
Remember, if you install Google Now (Search) go as quickly as possible into app drawer>Google settings>Search and Now>Voice>Hotword Detection and turn it off, then back up one submenu to Voice again and turn off all the checkboxes.
You can install voice search and talkback from market (enable talkback in accessibility settings) for those functions without fc. (and voice search wrapper from xda if you want voice control over Search.)
or just go the easy way on os2sd and use the Skinny_4.4_Gapps_new.zip which don't need a facilitator. But it's harder to get current Google Search that way since Play thinks we can't handle it.
Basic instructions for OS2SD install:
Use NEW twrp.
Wipe system, data, cache. Flash ROM carrier fix, gapps.
reboot.

reserved

Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app

I cannot believe this phone is still going. You are the man, bss!
Sent from my SPH-L710 using xda app-developers app

Maestertk said:
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
Click to expand...
Click to collapse
I forgot to link gapps. the skinnygapps from ac are the basic model.
I just tried pa gapps and they work ok without onetimeinitializer and setupwizard,
I haven't seen reference to art running on any armv6. I tried to walk it thru compilation early on, but ran out of free time to keep translating the thumb2 asm to thumb1 (or finding source where others had already done so) so it'd work.

new os2sd build.
zram turned on, p500 ami304d to match their kernel drivers (long-standing whoops there.)
probably other cm changes. I don't track em I just build and use it.

update. new builds up.

Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app

ghostswagking said:
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
check your overclock, if it's too high you'll get random reboots. Best way I've found is run gallery while OC'd and play with it until it reboots. Set OC down on notch below where it doesn't reboot in gallery or camera.
If you're not OC'd then I'm not sure why it's doing that. some apps cause issues. logcat or /data/tombstones may have stuff you can pastebin if you want me to look into why.

4.4.3 update later today .

bigsupersquid said:
4.4.3 update later today .
Click to expand...
Click to collapse
bump... rom update, carrier fixes need updated but should work as long as you don't mind settings showing old build.

bump for really new release.
now using
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
now built with linaro gcc 4.8 (kernel is only linaro gcc 4.7) with -O3 optimizations.

4.4.4
Looks like next rev be along here soon.
4.4.4
Gotta see if anything really changed.

big update
requires new recovery.

carrier fixes updated to 4.4.4

new release.
BUG:
ADB debugging needs toggled off and on to recognize cable.
Otherwise, optimized, with linaro kernel.
Might need to update your TWRP (since this is experimental, after all, things change.)

bugfix release.
takes care of adb toggle to connect cable issue.
adds armv6k-specific toolchain optimizations.

bump
new kernel toolchain (I built a linaro 4.7.4 with crosstool-ng with armv6k-specific flags)
p500 config imports... zram reenabled and selinux enforcing.
probably other upstream changes.

no screenshot

ROM UPDATED May 19, 2015 [ROM] LP 5.1 Resurection-Remix Hardened Unofficial

Rom updated on May 19. This is LP 5.1 release 2. Latest Google/CM/Resurrection sources + all hardened features. Plus cleaned IP addresses (got rid of Google, Level 3 communication, AT&T, Orange, Department of Defense and other shady ips). Also enabled is Volte (enhanced LTE), which is Voice over LTE. This depends on the service provided by your carrier. In the States, for example, T-Mobile provides such services, which include high definition voice. Usually, you need special update done by the manufacturer in conjunction with your carrier. This rom does not need that. Your Z1 is already provisioned for Volte. You will see in Mobile Settings another entry: Enhanced 4g LTE Mode. ALso, in test menu/phone (*#*#4636#*#*), you will see a Volte Provisioned Flag. So, as soon as your carrier starts Volte, you are all set.
Sources are the same...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12531
_____________________________________________________________________________________
Rom updated to latest sources on May 4. In addition to regular hardened features, more than 40 instances of Google IP, Level 3 Communication and Department of Defense IPs removed from sources both for IPV4 and IPV6. The same is replaced with Opendns IP. Keep in mind that those ips go not only in configuration files, but libs also and the latter cannot be decompiled and fixed...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12289
______________________________________________________________________________________
Rom Updated to LP 5.1.1. All hardened/security features implemented. Kernel used from Slimroms 5.1.
TWRP 2.8.6 is integrated in kernel.
Obviously, this is an alpha version...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12110
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Rom updated to 5.1: all hardened features enabled.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=11901
___________________________________________________________________________________________________
March 31: kernel updated to include screen color calibration:
See Download link: http://forum.xda-developers.com/showpost.php?p=59801528&postcount=94
_________________________________________________________________________________________________
March 27: New build is up, latest CM and Resurect changes; kernel includes voltage table, syncookie and TWRP.
Download Link: http://d-h.st/lw2s
Mirror Link: http://forum.xda-developers.com/devdb/project/dl/?id=11744
_________________________________________________________________________________
March 15: New build is up including latest sources, TWRP integrated in kernel, led lights fixed
DOWNLOAD LINK: http://d-h.st/UO7W
_______________________________________________________________________________________________
Marchh 7: Rom Updated to the latest version + plus all security enhancements. Sources for security changes are the same as posted
See Download section for update
Here is Resurection Remixed Lollipop hardened and secure. Built from sources on February 24.
Changes:
First of all, as many know, encryption on lollipop slows down the device to almost unusable. I was able to resolve that. The culprit was Qualcom crypto module and drivers that collide with graphics. In this rom, when you encrypt your device, there is no noticeable slow down at all. Your master encryption key is no longer stored in crypto module (which rumor has it is backdoored anyway), but rather hashed and salted on the drive itself.
1. Modified kernel to disable creepy SElinux and enable Tomoyo security. Now you can safely use Xposed framework and some modules such as Xprivacy, Appsettings and ShowDialpad, as well as many others
2. Modified kernel to disable qualcom module and drivers
3. Disabled creepy qualcom random number generation and enabled all other methods
4. Enabled 256 bit AES drive encryption as opposed to Google's default 128 bit
5. Enabled all ciphers and hashes available in kernel and disabled by default (thanks Sony and Google)
6. Latest CM changes
7. Omniswitch (to be flashed separately after flashing the rom)
Maybe more
INSTALL:
1. Be on Kitkat, rooted with CWM or TWRP
2. Enter Recovery, wipe System, Data, Cache
3. Flash the rom
4. Flash Omniswitch
5. Reboot and enjoy
If you want to encrypt your device, you need to do 2 additional steps before or after encryption. Go to Developer Options and enable "Force GPU rendering" and "Disable HW overlays. Yes, you have to enable (not disable) "Disable HW overlays" option. The latter won't stick after reboot. So, manually transfer the attached init.d script to /system/etc/init.d and set permissions to at least 744. This way the option will be set at boot and you won't have any noticeable slowdown. In fact, I don't see any difference in speed between encrypted and non encrypted device.
CREDIT: Resurection-Remix Team, Cyanogenmod, AOSP and Omniroms
WARNING:
I am not responsible if your device explodes and kills everyone around. You are doing it on your own. Russians, who are definitely coming, won't help you either :laugh:
Download links
Rom: http://d-h.st/l1rB For Update see Download Section
Omniswitch: http://d-h.st/AbGH
Init.d script (in case you want to encrypt your data): http://d-h.st/QIiE
Sources: https://github.com/ResurrectionRemix
https://github.com/HonamiZ1/android_system_vold
https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Resurection-Remixed Lollipop 5.1.1 Hardened, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Cyanogenmod
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-05-19

screenshots
Screenshots added

Kernel updated with CPU voltage table
Kernel updated to allow under/over volting. See attachment.
Instructions:
1. Unzip the file
2. Flash in fastboot: fastboot flash boot boot.img and fastboot reboot
Enjoy

Thanks for this ROM, are there any known bugs?

wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
All CM bugs as of February 24. You can go on their site and see the list of changes...

optimumpro said:
All CM bugs as of February 24. You can go on their site and see the list of changes...
Click to expand...
Click to collapse
So just need to look at http://forum.xda-developers.com/xperia-z1/general/rom-official-cyanogenmod-12-nightlies-t3007118 is that right?
Sorry I have to confirm, there are multiple threads (Official/Development) for CM12.
This ROM will maintain root and recovery, right?
I'll flash and let you know if I find any other issues.

Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.

Kyrius said:
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Click to expand...
Click to collapse
I use Textsecure as sms replacement. Microphone works great...

Very buggy
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE

darkdevu said:
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
Click to expand...
Click to collapse
1. Learn the rule about not posting bug reports without logcat
2. Camera works fine: verified
3. Always wipe System/Data/Cache before flashing
4. Are you sure you have Xperia Z1?
Cheers

his profile says Z3. lol

Any further reports on this ROM? Interesting to know how it performs and about stability

Deleted

wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
Rom Updated to the latest version. See Download section in the OP.

and where is the link to the update?

shikimafia said:
and where is the link to the update?
Click to expand...
Click to collapse
It is in Download section:
http://forum.xda-developers.com/devdb/project/?id=8412#downloads

Screenshots added in post #2. Note that only this rom and SlimLP work with the latest Xpivacy module. Tried on Crdroid and others and there is bootloop as soon as you enable Xprivacy.

Has no one tried this rom as not reports or posts
tried flashing update from scratch and get play services fc on every gapps i used............i am guessing i may have to flash initial release and dirty flash this over it? excuse me if i may have got it wrong

shingers5 said:
Has no one tried this rom as not reports or posts
Click to expand...
Click to collapse
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...

optimumpro said:
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
Click to expand...
Click to collapse
I'm having issues flashing the new version as getting play services errors.... Was gonna try dirty flash over previous versions

(CM13.0)(LTE)(UBERTC)Logix 04/12/16

Welcome to my little Rom I noticed a lack of LTE roms that worked on xda for hte nexus 9 so I made this for you guys
Stripped down and minimal CM with latest ubertc 6.0/4.9 full LTE/WIFI Support
Instructions
make sure your on latest bootloader & recovery :here/here
full wipe
flash vendor img if your not on MMB29R vendor : here
flash rom :here
flash fire-ice kernel the cmm version(and say thanks) :here
flash latest su: here
flash opengapps (arm64) here
reboot
I work for T-mobile so my time is very limited but im going to try to update each time a new vendor comes out:good:
shout out to usb-host for being a |30$$ and making the nexus 9 great!
i only support fire-ice kernel with my rom !!!

mine
ChangeLog
build 4/12/16
vendor MMB29R
Initial device files bring up
removed some fm radio files from cm (we dont have a fm radio)
removed stock lwp
removed cm reporting
removed cm ota
introduced latest ubertc
removed inline kernel and apps below (some people didnt want )
ran out of time/booze
The apps I like to use /mods i do to stock are as follows:
Busybox : https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Adaway: http://adaway.org
Kernel auditor: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
LMT (pie launcher) :http://forum.xda-developers.com/showthread.php?t=1330150
liveboot (verbose boot):https://play.google.com/store/apps/details?id=eu.chainfire.liveboot&hl=en
People keep asking me how to get my custom pie launcher and what my theme is
I simply just disabled my nav bar by adding "qemu.hw.mainkeys=1 "
to my build.prop you can use this app
im using this theme for black and red and matched the colors in the settings of LMT and positioned pie to launch from the bottom
any questions just let me know and please try to provide a logcat! Thanks for testing :highfive: