Develop Bugs

[July 24th] [Sense 3.5] Energy™ -.¸¸.·´¯ Sense 3.5 build that just works!

{
"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"
}
Welcome to the "Energy" ROM thread !​
This development thread is for my "Energy" custom firmware series for the HTC HD2 !
I build my ROMs with four main goals.
Eye candy ( I want my ROM to look great and for it to all flow together nicely)
Speed !!!
Smoothness, consistency and good aesthetics
Stability through private beta testing before public release
I preconfigure a lot of things in my ROM, because when I flash it on my phone, I want it ready to go. So, the ringtone, sms/email and other notifications to already be set. Doing it this way, makes for a nice ROM that's ready out of the box.
ROM Features
Android 2.3.5 (Gingerbread)
Rosie transparency... modded
Blue overscroll
Blue highlights instead of green
Deodexed, zipaligned, tweaked
Extra Quick Settings
Improved SD card read ahead
Busybox + runparts, TitaniumBackup
Zipaligned
Zipaligns apk's at boot
A few HTC Apps removed, like HTC Navigation and some widgets
A lot of junk removed
clK and MAGLDR supported in ROM ZIP file
TMOUS or EU model supported in ROM ZIP file
Updated hosts file for ad removal
RCMix Tweaks built in!
Dr Dre beats support as well as the normal Dolby, SRS and EQ support !
A lot more stuff... check the changelog below
Fast... Stable.. and GREAT battery life
Please visit this thread for all your questions and answers about this ROM, especially if you can't post here yet!
Please setup a 380MB system partition to use this ROM, on TMOUS handsets.
If you have an EU HD2 (not Tmobile) have a 1Gb ext(2 or 3) partition ready on your SD card and choose the "EU" option when prompted during installation.

Screenshots of the Runnymede Sense 3.5 build
​

FAQ and compilation of useful posts
If you would like to regain the ability to end a call when pushing the red hardware button look at the post below and flash the appropriate file
http://forum.xda-developers.com/showpost.php?p=18922016&postcount=3780

Flashing instructions
Advanced Users:
For the SDEXT version, you need a CWM layout of 5/200/5. If your phone doesn't boot, try a higher than 200 partition.
For the regular version, you need a system partition of 380 MBs.
Begginers:
Follow the instructions below to flash the ROM for the first time.. if you're coming from a Windows Mobile based HD2. It's recommend to have your SDCARD ready with my ROM loaded on it already.
1. Download and install MAGLOADER.
Download and unpack MAGLDR1.13 from (http://nrgz28.sylvester20007.com/HD2Tools/DFT_LEO_MAGLDR113_DAF.rar)
Once downloaded unpack the MAGLDR package with your favorite tool. WinRAR or 7zip recommended. Go to the folder where you unpacked the MAGLDR package and run ROMUpdateUtility.exe. Check the checkmarks and hit next to flash, just like you would flash a Windows Mobile ROM.
The phone will reboot and go to the multi colored bootloader screen. After the flash is complete it will reboot and go IN to the MAGLDR. You'll see a text menu with 12 options. Go to Option 5 (USB Flasher) and hit the Green Send key on your device. It will put MAGLDR in flasher mode and wait for a USB connection. Let it sit on this screen for now...
2. Setup system partition and install Clockworkmod recovery
Download the HD2Toolkit. You can click here to get it > http://nrgz28.sylvester20007.com/HD2Tools/hd2_toolkit_setup.exe (original thread at http://forum.xda-developers.com/showthread.php?t=1090783 )
Run the installer and install it. Now, after you open the HD2 Android Nand Toolkit, it will look like the screenshot at the bottom of this post.
Now... if you have TMobile USA phone (with green/red buttons at the bottom) then choose a custom partition size and just click Repartition in the bottom left corner. After that.. input 380 for size.
If... you have a device with all white buttons at the bottom (an european/asian model) then choose Custom on the left hand side and input 200 in the box that pops up after you hit Partition.
Now you get a green "DFT" screen.
Hit Next until it asks you to put the phone in USB Flasher mode. The phone should already be in USB Flasher mode from step one. The progress bar will go back and forth while the phone is being setup. Hit Finish when it's done.
The phone will reboot on its own and go back to the main Magloader screen with all the options.
3. Flashing the Energy ROM
Now pick Option 8 and go to "AD Recovery". Magloader will load the ClockworkMod Recovery where you can flash your ROM. This is the place to go when flashing future ROM updates or "patches". To get to this screen after you load a ROM, you have to keep the Power key pressed down as you turn the phone on. You don't have to do that now, however.
Now I assume you have my ROM on the sdcard already. If not, take it out and transfer it through your computer or card reader.... and plug it back in to the phone.
If you have a TMobile USA phone, you can skip this section and go straight to installing the ROM below... If you have the euro/asian model continue to read.
Go to the Advanced menu and pick Partition SD Card. Pick a size of 1024M and let it do its thing. Make sure it doesn't error out. If it didn't, continue to flash the ROM below... Make sure to copy the ROM zip back to the SD card by using the "mount USB storage" feature of the recovery.
Go to "Install Zip from sdcard" in the menu options and hit the Send key. Then choose "choose zip from sdcard" using the volume keys on the side and hit the Send
key again. Pick my ROM from the list and hit the Send key again. Pick "No", hit Send. Now the ROM is flashing...
When it's done, hit the Back key. "Reboot system now" is selected. Just hit the Send key to reboot the phone and boot the ROM !
4. Booting up Android for the first time
The phone should now be rebooting and the Magloader screen will briefly show up....
Towards the bottom the words Go! GO! GO! will show and then you'll see the NRG logo which means the kernel is booting up. Wait a few minutes and the phone will
be ready to play with...
5. Enjoy your new operating system !

Downloads and Changelog
7.24.2012
New Kernel from marc version 0.2.3+
Fixed SRS sound processing in HTC Music
Fixed Robo voice issues (maybe!)
GREATLY improved camera recording quality in 480p
Increased amount of RAM available
Unique MAC address for Wifi (the original mac of your device)
Fixed wifi tethering (through external app)
Increased sound volume during calls
DSP manager still in
7.17.2012
Added touch screen Aroma ROM installer + touch screen file manager in recovery
Fixed display of ROM build date
Changed a few more framework graphics
Fixed playback of WMA and other file formats supported
7.16.2012
Fixed 480p recording with Sense Camera. Now using hardware MPEG4 acceleration.
Changed minimum sleep CPU speed to 128Mhz to improve battery life in standby
7.12.2012
Fixed CLK Data issues (stupid build.prop issue)
Enabled Smooth Scrolling Mod by disabling scrollingcache in framework
Changed CPU governor to SmartassV2 for better battery life
Removed OC Daemon and I recommend leaving it off and let the kernel handle that job
Added Sense 4 style keyboard
Optional Sense 4 clock widget
Fixed Polaris Office app
Fixed and enabled option to toggle 4G/H icon (default to H now)
7.4.2012
Added swipe to dismiss on notification manager
Cosmetic changes to notification manager
Fix tabs white text not easily readable
New framework graphics for a more consistent/professional look
SD Card read ahead buffer values optimized
Nice DSP manager with more options
Sense 4 graphics elements throughout ROM (more to be done...)
Revised Tweaks application (mainly remove stuff that didnt work due to RCTeam's taking their addons server down)
Black Sense 4 style dialer !
Chainfire's SuperSU instead of Superuser for root access..
Updated all apps and apks to current releases
Major graphics rework throughout ROM (more color... some ICS theming... more black/blue)
Sense 4.0 ringtones/volume sounds
Small framework tweaks
March 15th, 2012 (3.15.2012.SensationXL)
Marc's new 0.2.0 kernel is in !
andrev_oc daemon settings slightly tweaked for new kernel
Updated all apps and apks to current releases
Major graphics rework throughout ROM (more color... some ICS theming... more black/blue)
Sense 4.0 ringtones/volume sounds
Faster camera
Small framework tweaks
ENJOY!
------
Trimmed !
------
9.15.2011
Initial release
Download here
Credits:
- Thread graphics, screenshots made by George McKinnis Jr.! Thanks buddy!
- to LeeDroid, birgertime, baadnewz, Sergio for great ideas
- dsixda for his amazing kitchen
- flemming for his M10Tools
- brut.all for the apktool
- langthang for always being a Pioneer!
- And all other great devs that share their work for free!

Addons
NEW LINKS WILL BE POSTED SOON!
Boot splashes to match the EnergyROM theme:
flash these with the HD2Toolkit... or like you would any other NBH file.

Awesome!
I will try it out now.

is this .Desire rom

nice me like alot all perfect

hd945157206 said:
is this .Desire rom
Click to expand...
Click to collapse
Read the instructions above.
v5 with the latest zimage

Downloading now but I'm wondering, are you copying android (haret etc) to device storage rather than SD - and if so, are we going to be able to copy/update subsequent droid builds or will any updated droid builds need to be built into a flashable rom by you to use this same method?

Nice))TNKS

Well well...
I was just wondering when you do something like this.
Downloading... ... ...
Regards,
Leluloota

zkid2010 said:
Downloading now but I'm wondering, are you copying android (haret etc) to device storage rather than SD - and if so, are we going to be able to copy/update subsequent droid builds or will any updated droid builds need to be built into a flashable rom by you to use this same method?
Click to expand...
Click to collapse
Well the way I got it now is... Haret and root files sytem files are IN the ROM. The system.ext2, data.img and rootfs.img still need to be on the card. So with future updates, you can just replace those three files. The kernel is IN the ROM, but it can easily be overwritable in \windows with a new kernel. Even a .cab can be developed to be installed by users. I plan on doing that in the future...
Or, you can install the minimal WM build I also uploaded (55 megs) and install all your android files to the storage card and run it that way

Great!
I´ll give it a try later.
Thanks

You seem to be liking this Desire ROM NRGZ28

Brilliant work as always NRGZ28.

NRGZ28 said:
Well the way I got it now is... Haret and root files sytem files are IN the ROM. The system.ext2, data.img and rootfs.img still need to be on the card. So with future updates, you can just replace those three files. The kernel is IN the ROM, but it can easily be overwritable in \windows with a new kernel. Even a .cab can be developed to be installed by users. I plan on doing that in the future...
Or, you can install the minimal WM build I also uploaded (55 megs) and install all your android files to the storage card and run it that way
Click to expand...
Click to collapse
sound good man, thanks for your hard work getting this going! (and the speedy reply )

good sutff!!!

I love you NRGZ (no homo!)

[Build] ThaiDai Android Loader and Setup v2.3 [DISCONTINUED]

ThaiDai Android Loader is a program for Windows Mobile 6.1.
--------------------------------------------------------------
A few words why I stopped development:
I had to stop this project for personal reasons (reason called baby).
And this was easy because nearly nobody (or only a few < 10) used my loader.
But more important for me now: I do not see any improvements on bugs or missing features for Blackstone with Android, there is no real kernel developer community anymore. Sound problems, BT, battery and performance aren't funny if you want to use the device. For playing with Android it was ok and I learned a lot. But not for every day use. So I switched back to WinMo 6.1.
And yesterday I bought a Samsung Galaxy Note. Android rules!
--------------------------------------------------------------
(6.5 builds will not work because there is an error in writing files with Windows Mobile 6.5 which will appear when linux makes a fsck. So no support for 6.5
You can use builds like Damn Small Topix (Rapidshare works) or other 6.1 builds)
If you run into problems and want help, please provide me with the generated log files in folder "thaidaiboot/Logs".
No Logs = No help!
With the loader you can start Android or you can install Android without doing the usual things: no copy, no edit, no changes etc.
The setup (a normal cab-file) prepares the necessary files on your sd card automatically.
With the program you select what you want to do (install, backup, restore, change device, choose Android Build, edit startup.txt and build.prop) and press "Boot". That's it.
Program is installed in autostart folder and will automatically boot into last chosen OS after a number of seconds (default 100 s, you can change of course). Stopping countdown is easy: klick somewhere or change a value).
FRX07.1 build is included as default. More builds to come from tomorrow.
{
"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"
}
-------------------- v2.3, 2011/09/18 --------------------
Changelog: including 2.0/2.1/2.2 changes, starting with 2.3 ;-)
---- 2.3 ----
Editor for build.prop for each build
Explanations for entries in build.prop (just started to gather them)
additional logging information in window mobile stage of installation
selected builds stay in original folder (so no system.tgz in folder thaidaiboot) and are used in rootfs.img for installing /system
---- 2.2 ----
Timer option for booting into Android automatically after n seconds is working correctly now.
I added the option to select Apps for installation - but I do not change the apps delivered with the specific build. So this part ist only for your own flavour of apps you want to add.
Next big change: Editor for startup.txt. You can easily change the commandline parameters (like display density or OC or ...). The set parameters cannot be changed until now (I didn't see the necessarity).
Resolution changed to 480x800 and using it. So from now concentrating on Blackstone. Other 480x800 devices may work but still no guarantee.
Resolved some stupid error with choosing Kernels (I just found this one today, nobody else did before)
---- 2.0/2.1 ----
Changed format for builds to tgz. Now it is easier for me to prepare cwm based builds
New rootfs.img for installation and updates with tgz files
Added download links for build thunderbolt
In every build I checked I have to make changes to build.prop: double entries, wrong entries, obsolete entries, stupid entries, optimized entries. That's why I started adding a build.prop-editor to my program.
As default I still use NeoFroyo. (without GAPPS).
Added GAPPS as Update-Package (selected on first start, please install)
New setup package and installation file for windows mobile
For all typical devices like Blackstone, Diamond, Raphael, Rhodium, Topaz
New user interface in windows program
autostart into Android after n seconds (changeable)
new UI (Hubs)
switched from comboboxes to lists for selection (better information on first look)
new ts-calibration for Topaz (thanks to Aggy in Neopeeks forum)
changing Hubs color possible (just for fun)
removed Apps from system.ext2 to folder APPS, so the different Builds will be much smaller and I have to install and upload Apps only one time
with apps in folder Apps the selection of Apps in loader program will soon be possible
Downloads:
One big cab file (about 95 MB) including everything.
Setup for ThaiDai Android Loader v2.3 with FRX07.1
Bugfix for Exe, please copy to your program files folder with thaidailoader, will give a complete new cab file next days.
Some more builds:
Setup for Build Froyo Blue
Prepare SD card:
You need 4 primary partitions on sd card (I use MiniTool Partition Wizard Home Edition)
All sizes here are only examples. Start with them, feel free to change.
All partitions have to be "primary" (ignore warning in Windows)
Partition 1: FAT32 (at least put folder "thaidaiboot" from zip here)
Partition 2: EXT2, about 150 MB (used for Android system partition)
Partition 3: EXT2, about 250 MB (or more for Android data partition)
Partition 4: EXT2, about 100 MB (for Android cache partition)
Size of partition 1: [Size of sd card] - [Size of 3 EXT2]
Installation:
Delete folder thaidaiboot on sd card and deinstall Loader program before using this setup (copy cab to sd card and start it).
- copy first big cab to sd card
- execute cab and start setup
- install on sd card (not on internal memory!)
- start "ThaiDai Android Loader" from start menu
- select your options and boot into Android
Adding new builds:
- copy cab for build to sd card
- execute cab and start setup
- install on sd card (not on internal memory!)
- start "ThaiDai Android Loader" from start menu (build will be copied - takes some time)
- select different build and install (Please start program one time before adding builds!)
Warning:
- Do not edit or change files in folder "thaidaiboot" on your own. Use the program.
- I hope it will install now in all language versions of Windows Mobile. I tested it only with an english installation. And maybe some foreign fonts (like Thai ;-)
aren't recognized by haret.exe or linux.
-------------------- ThaiDai Android Loader options: --------------------
Administrative Tasks
backupSystem
backupData
make Clean
installSystem
fixSystem
fixData
restoreSystem
restoreData
When started in Windows Mobile no Task is selected!
After "haret.exe" is started my installation script will go through the selected tasks
Device Selection
Select "startup.txt" and "ts-calibration" from folder "Startups" for possible devices in FRX07 like Blackstone, DIAM, RHOD, RAPH, Topaz
Build Selection
Select the build you want to install
NeoFroyo (default)
XDAndroid FRX07 (the original)
THUNDERBOLT
... (tell me what you want to see here)
Kernel Selection
Select the kernel you want to use
1342
1346 (default)
Typical Tasks:
For a new and clean installation (data is deleted) choose: "backupSystem", "backupData", "makeClean", "installSystem"
For an update of your system (no data changed) choose: "installSystem"
You can always choose to start with backups first and choose: "backupSystem", backupData"
Tasks with "fix..." are only necessary for updates I will post here
Select Device [Blackstone]
When you select another device, the program checks if there is a "startup.txt" in the folder of this device. If not found, nothing is changed. When a "startup.txt" is found it is copied to the folder "thaidaiboot" and you can start your device.
If a "ts-calibration" is found, it is copied. Please be careful: I do not know if all ts-calibration files are ok.
-------------------- OK-not OK: --------------------
Tested only on Blackstone
OK
Wifi works right from the first start
Market ok
Phone ok
Camera and Video
Root access ok
3.5 jack ok
3G (UMTS HSDPA in Germany) ok
Not OK
Audio stuttering
Youtube not really good (HD problems, normal ok)
Bluetooth starting, but no pairing

Audio, not ok: stuttering
BLAC100-kernel-modules-2011-04-11-1302528888.zip
Audio work on my phone
http://forum.xda-developers.com/showthread.php?t=999544

I don't have any problem with your thread, in fact, I'm glad you made it work
This is a communitary effort, and I'm only an average tester, so couldn't be more far from angry for this.
Thank you!

Hi ThaiDai,
Thanks for sharing your work.
Quick questions:
- have you modified the Roofts.img from FRX07 adding CMW? or modified the roofts from Neopeek CMW 1.8?
- What is the size of the cache partition you recomend as it is now? Neopeek CMW 1.8 recommends between 50-100mb.
I'll try as soon as I finish working.
Brgds

Downloaded the last version of rootfs.img from XDAndroid rootfs Build Service and used this as a starting point.
As far as I understand we do not need a cache for the Android build FRX07 anymore. But for CWM (and his logs) we need. So I will try later to flash the next version with a very small cache partition size.
But first I want to try and repair (if necessary) the scripts, so that other devices can be used (tried?) with this build.
Wait and see...

Update to Version 0.99 (Full Install and Update Only)
First post updated with new version 0.99.
Included download links for Full Install (complete npkboot folder) and Update only (zip-file inside npkboot).
And it should be possible to test this build on other devices now. Tried to restore the multi-device-usability. But no garanty.

Tried the previous version and worked nice and fast. (with cache partition of 50 Mb)
I'll download and try the new version now!

Please try if the Update Only works. I have to check myself later. Didn't do this right now. Thanks

ThaiDai said:
First post updated with new version 0.99.
Included download links for Full Install (complete npkboot folder) and Update only (zip-file inside npkboot).
And it should be possible to test this build on other devices now. Tried to restore the multi-device-usability. But no garanty.
Click to expand...
Click to collapse
update only dowload not working can you check it please thanks
its working now thanks

Thanks man, the first Android that works on my Blackstone. I tried several builds CWM and not CWM, but this seems to work w/o probs - so far

phsnake said:
Thanks man, the first Android that works on my Blackstone. I tried several builds CWM and not CWM, but this seems to work w/o probs - so far
Click to expand...
Click to collapse
Please give these credits to the developers of XDAndroid. I didn't do very much here, only made a CWM build from the original ext2 based build.
But I'm happy you can use Android on Blackstone with this one.

BTW, remember to update SU binary fron superuser app, and better if you don't reuse app data from previous builds. It will surely make your wifi fail, probably other things.

I've been using the XDAndroid FRX07 CWM by ThaiDai 0.99 build from last nigth, and so far so good.
Performance is quite good, batery life acceptable, and the problems are the same as XDANDROID FRX07 running on the Sd (BT, audio stuttering and wifi disconnecting intermittent).
questions:
- have you tried to change the behaviour of the red button using spareparts? it didn't worked for me.
- have someone use the old fancy widget (the one HTC weather clock replica)? it does not work.

Sorry if this question sounds stupid. I already tried to read the info in neopeek but still don't fully understand it, so anybody that is willing to explain to me, thanks!
I have been using the FRX07 and the previous version of XDAndroid in the normal build (one folder in the SD Card). What is the benefit and the difference of running it in this CWM way? Is it better performance, better battery life, or better management?

lie_ui said:
Sorry if this question sounds stupid. I already tried to read the info in neopeek but still don't fully understand it, so anybody that is willing to explain to me, thanks!
I have been using the FRX07 and the previous version of XDAndroid in the normal build (one folder in the SD Card). What is the benefit and the difference of running it in this CWM way? Is it better performance, better battery life, or better management?
Click to expand...
Click to collapse
Some have claimed better performance, but in my testing it's actually worse.
I guess one benefit with having a dedicated data partition is USB mass storage (should) work properly. Other than that it's a lot of work for very little reward - perhaps if you jump builds a lot, CWM has a nifty backup/restore feature built-in to it...

Eodun said:
BTW, remember to update SU binary fron superuser app, and better if you don't reuse app data from previous builds. It will surely make your wifi fail, probably other things.
Click to expand...
Click to collapse
I didn't change the apps, only took them from the official FRX07 build

arrrghhh said:
Some have claimed better performance, but in my testing it's actually worse.
I guess one benefit with having a dedicated data partition is USB mass storage (should) work properly. Other than that it's a lot of work for very little reward - perhaps if you jump builds a lot, CWM has a nifty backup/restore feature built-in to it...
Click to expand...
Click to collapse
You should give it another try

ThaiDai said:
I didn't change the apps, only took them from the official FRX07 build
Click to expand...
Click to collapse
I was referring to a problem posted above, sorry. The thing is I got some nasty problems (in fact had to reinstall again) because I tried to restore some data+apps with TB and it ruined wifi.

Hi Eodun, what do you think the benefits of the CWM build of FRX07?
Its really faster, better battery life, etc? Can you give some insight?

lie_ui said:
Hi Eodun, what do you think the benefits of the CWM build of FRX07?
Its really faster, better battery life, etc? Can you give some insight?
Click to expand...
Click to collapse
It could be faster,you'd get usb storage to work,battery life shouldn't change.

[ROM] [AOSP 5.1.1] Lollipopalooza | manta/Nexus 10 | LMY48M | 2015/09/18

This is my very own personally maintained custom ROM for the Nexus 10 (manta) called Lollipopalooza!! It is an AOSP (Android Open Source Project) 5.x based ROM with a simple aim... add a few useful features to AOSP without deviating too much.
{
"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 will be a spin-off of my previous Nexus 10 ROM ThunderKat, but from scratch and obviously based on Android 5.x.
I don't expect this to compete with the big boys (CyanogenMod, AOKP, Paranoid Android and the like) and this ROM will have a considerably limited feature-set compared to them. If you want a lot of customisations and configurations, they are definitely the way to go.
Please note that since this is a fully de-odexed ROM, it will take a while to boot up the first time. Please follow the installation instructions carefully.
IMPORTANT: Since I no longer own this device, I have not tested this. In my opinion it should work just fine since I am using the same code-base for my Nexus 9 builds, but if you are not sure, wait for feedback from others who are brave enough to take the plunge.
Due to my limited availability, I will now no longer support builds older than 2015/05/23
Changelog:
1. Update to Android AOSP 5.1.1_r14 (LMY48M)
2. Includes stagefright exploit fixes
3. Update to Layers Type 3
4. Multi-toggle Location QuickSettings tile (toggles between the different location modes - Off -> Sensors Only -> Battery Saving -> High Accuracy)
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 Layers/RRO themes
3. Visit this XDA thread for a comprehensive list of Layers/RRO themes
4. Send a positive shoutout to the Layers Team for their awesome work
Older Changelogs:
2015/05/23
1. Update to Android AOSP 5.1.1_r3 (LMY48B)
2. Updated proprietary files and binaries from stock LMY47V ROM
3. Layers/RRO 2.1 updates
4. A lot of Layers/RRO legacy code cleanup
5. Enhanced AOSP Launcher3 from OptiPop with features like customisable grid size, hide/show search bar & materialised settings
6. Updated ARM Google Apps Pack as of 2015/05/23
PLEASE FLASH THE Lollipopalooza_aosp_manta-LMY48B-20150523-BuildPropFix.zip IMMEDIATELY AFTER FLASHING THIS ROM. THIS WILL ONLY BE REQUIRED FOR THIS BUILD.
2015/04/24
1. Prefer Google WebView over AOSP WebView because AOSP WebView is older, but automatically fallback to AOSP WebView if Google WebView is not installed.
2015/04/23
1. Updated to AOSP Android 5.1.1_r1 LMY47V
2. Added Layers/RRO 2.1 (backwards compatible with Type 1 & Type 2 Layer/RRO themes) - All credits to the Layers Team
3. ART is the new kid on the block. Remove Dalvik VM
4. Disabled a lot of framework debugging
5. Speed up animations
6. Disabled Google OTA services
7. Tune ART flags to optimize everything (this makes first boot and app installs slower, dex files are large, but performance improvements are noticeable) [MAKE SURE YOU WIPE CACHE/DALVIK-CACHE]
8. Miscellaneous optimisations and fixes
10. Updated tzdata to the latest timezone data 2015c from IANA.
11. Updated ARM Google Apps Pack
2015/03/17
1. Updated to AOSP Android 5.1.0_r1 LMY47D
2. Show "Installing application x of y" on first boot
3. FAB (floating action button) for clear recents
2014/12/09
1. Updated to AOSP Android 5.0.1_r1 LRX22C
2. Code cleanup and stability fixes for existing features
3. Latest vold and filesystem support updates from CyanogenMod
4. SELinux policy updates
5. Update Google Apps pack
6. Move back to block-based update zip which is a million times faster to flash.
7. Enabled bluetooth LE (low-energy)
2014/11/28
1. Updated to AOSP Android 5.0.0_r7 LRX21V
2. Movable navigation bar buttons (Settings > Display > Navigation Bar Position)
3. Volume rocker wake (Settings > Display > Volume rocker wake)
4. Volume rocker cursor control (Settings > Language & input > Volume key cursor control)
5. Native status bar battery percentage display (Settings > Display > Battery percentage)
6. Per-app keyguard/lockscreen notification controls (Settings > Sound & notifications > App notification)
7. Fixes and UX updates for clear-all recents
8. Android volume daemon and file system automount support updates (Added groundwork for NTFS, exFAT & EXT4 support)
9. OTG automount for NTFS partitions with R/W access
10. Support for TWRP recovery (updater script validates flounder or volantis)
11. Updated Google Apps Pack
2014/11/16
1. Updated to AOSP Android 5.0.0_r6 LRX21T
2. Enabled AppOps (Settings > Apps > AppOps)
3. Advanced Power Menu (Shutdown, Advanced Reboot, Users, Sound, Airplane Mode, Settings, Lockdown)
4. Back button long-press kill app (Enable via Settings > Developer options > Kill app back button)
5. Custom device hostname (Change via Settings > Developer options > Device hostname)
6. Enabled Ambient display (Settings > Display > Ambient display)
7. Clear all recents (Credit 0xD34D)
8. Root-friendly stock kernel [IMPORTANT! This ROM is not rooted. In built root support will come soon. For now, please flash SuperSU or Superuser separately]
9. Tweaked ART flags
10. Proprietary audio configs from stock ROM
11. User triggered media scanner (Settings > Storage)
12. OTG USB storage automount to /storage/usbdisk with full R/W access (VFAT/FAT32 only) [IMPORTANT! This depends on the modified ramdisk included with this ROM boot image. You may lose this feature if you another boot image]
13. Updated MAC permissions (SELinux stuff)
14. Miscellaneous framework fixes and tweaks
15. Enabled Google Location Services
16. Fixed Google back/restore.
17. Added busybox
18. Enabled translucent navigation and status bars
19. Google Apps Pack zip with latest updated apps
Download:
Lollipopalooza_aosp_manta-LMY48M-20150918.zip
GoogleAppsPackARM-5.1.x-20150423.zip
Source:
GitHub
Manifest
Requirements:
1. Nexus 10 with Unlocked bootloader
2. Latest bootloader
3. Custom recovery like TWRP 2.8.6.0+ or CWM 6.0.4.7+
Instructions:
1. Wipe data/factory reset if you are moving from any ROM other than a previous version of Lollipopalooza
2. Wipe cache/dalvik cache for every update
3. Flash the ROM using a custom recovery
4. [Optional] Flash SuperSU 2.46+ using a custom recovery if you wish to root the device
4. [Optional] Flash Google Apps Pack using a custom recovery. You can choose to install any other Android 5.0 compliant Google Apps Pack
Disclaimer
Lollipops are fun, but too much is not good for your health. If you chose to enjoy the Lollipops in this thread, remember that you do so at your own risk. I am not responsible for cavities, stomach aches or any other ailments your device may have if you use this ROM. I do test these Lollipops prior to releasing them, but I make no guarantees.
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, Samsung, ARM, Chainfire, 0xD34D, CyanogenMod tea,, SlimRoms team, rascarlo, Chroma team, BitSyko team, AndroidFileHost

ive been lookin everywhere for some gapps that work with this device haha, thanks!

Great to see you in here Craig! Loved the Roms you did for the transformer. Guess its time to go install a custom recovery and try this out!

I am rooted and my bootloader is unlocked. I made a mistake and formatted my system img. Is it possible to flash this via adb?

Any word on getting OTG/CIFS working?
Also, the "DRM Libraries" .. these, I assume - allow things like Play Movies and Hulu Plus to work? I'm actually interested in TRADING OFF those features with the ability to get HDMI out without protection on the signal. Thoughts on that?
Thanks for the hard work already!

momulah said:
I am rooted and my bootloader is unlocked. I made a mistake and formatted my system img. Is it possible to flash this via adb?
Click to expand...
Click to collapse
Reboot into TWRP recovery, use adb to push it to /sdcard and flash it... it will work even if your system partition is formatted!

craigacgomez said:
Reboot into TWRP recovery, use adb to push it to /sdcard and flash it... it will work even if your system partition is formatted!
Click to expand...
Click to collapse
what is the adb command to push it to my sd card? I just finished the download!!

momulah said:
what is the adb command to push it to my sd card? I just finished the download!!
Click to expand...
Click to collapse
adb push rom.zip /sdcard/
or
adb push rom.zip /data/media/0/

darkuni said:
Any word on getting OTG/CIFS working?
Also, the "DRM Libraries" .. these, I assume - allow things like Play Movies and Hulu Plus to work? I'm actually interested in TRADING OFF those features with the ability to get HDMI out without protection on the signal. Thoughts on that?
Thanks for the hard work already!
Click to expand...
Click to collapse
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!

craigacgomez said:
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!
Click to expand...
Click to collapse
Thanks man I pushed the rom to my sd card and was able to flash it. Now Is there anything that doesn't not work that works in the stock rom?
May'be its his new kernel! Anyone try gong back to his stock kernel to see if it brings usb back.

craigacgomez said:
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!
Click to expand...
Click to collapse
Yeah, essentially, I want to be able to RECORD the output of the tablet with an HD capture system via HDMI. Completely legal reasons (which is why I don't care if any movies or TV work). But, unfortunately, the HDMI out (no matter WHAT) seems to be encrypted with HDCP.
I had it working on my TF101 - I had to use a little software trick on the PC, but it worked. Not anymore

Thanks, flashed and running fine... forgot to wipe data the first time and wouldn't boot

momulah said:
Thanks man I pushed the rom to my sd card and was able to flash it. Now Is there anything that doesn't not work that works in the stock rom?
Click to expand...
Click to collapse
I've tested everything except the DRM stuff... I don't use any DRM apps so I'm not sure... maybe someone who uses an app like Hulu Plus can let me know!

Wow...just finished installing...very nice. Absolutely love the aosp browser, beats the living crap outta chrome. Got the old news app and widget back too!

Just got my Nexus 10 yesterday and this is my first flash. Working well. Thanks!

I have preliminary OTG support done... need to fix permissions and get it to show up in Setting -> Storage

How do I enable the settings pull down? I liked that feature a lot. Being able to have notifications on left and settings on right.
Sent from my SAMSUNG-SGH-I727 using xda premium

momulah said:
How do I enable the settings pull down? I liked that feature a lot. Being able to have notifications on left and settings on right.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Flash ROM + GApps, sign in and you will see them

Is there any way to go back to the old tablet style interface? Not digging the phone style with bars on the top and bottom of the screen.

Added custom kernel with a few extra goodies... see OP for details!!!

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro

{
"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"
}
I am proud to present first Dualboot project For Redmi Pro. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Redmi Pro to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-omega-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some ​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Redmi Pro Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03

Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Changelogs
-19/08/2017
Initial Release, waiting for adding officially

Much thanks

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
Here are the screenshots

yshalsager said:
-19/08/2017
Initial Release, waiting for adding officially
Click to expand...
Click to collapse
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back

daffa ZRN said:
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
Click to expand...
Click to collapse
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines

daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
You can choose zip using any explorer app like ES File

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Sorry but can you show me how(I'm a noob)

Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?
Error log:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kate/kate:6.0.1/MMB29M/V8.2.4.0.MHRMIDL:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 13581, tid: 14315, name: pool-1-thread-1 >>> com.github.chenxiaolong.dualbootpatcher.snapshot <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
Abort message: 'invalid address or address of corrupt block 0x7fa60f0090 passed to dlfree'
x0 0000000000000000 x1 0000007faf7ba7d0 x2 0000000000000001 x3 00000000007fabf9
x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010
x8 7f7f7f7fffff7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 0101010101010101
x12 0000007faf7ba7c8 x13 58934240ef78b85e x14 58934240ef78b85e x15 0030f907887041ba
x16 0000007faf7b4a58 x17 0000000000000000 x18 0000007faca2a000 x19 0000007fa60f0090
x20 0000007faf7bb000 x21 0000007fa60f00a0 x22 0000007faf7bba70 x23 00000055995187e8
x24 0000000000000002 x25 0000005599529258 x26 0000000000000000 x27 0000000032e3dbe0
x28 00000055995a5860 x29 0000007f93a7f060 x30 0000007faf753580
sp 0000007f93a7f060 pc 0000007faf753588 pstate 0000000060000000
backtrace:
#00 pc 0000000000047588 /system/lib64/libc.so (dlfree+408)
#01 pc 00000000000195a8 /system/lib64/libc.so (free+20)
#02 pc 0000000000029054 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#03 pc 0000000000029224 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#04 pc 0000000000011b40 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so (_ZN2mb8format_vERSsPKcSt9__va_list+132)
#05 pc 000000000000abd0 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader11set_error_vESt10error_codePKcSt9__va_list+84)
#06 pc 0000000000009588 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader9set_errorESt10error_codePKcz+108)
#07 pc 000000000000d300 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#08 pc 000000000000c96c /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#09 pc 0000000000009ed8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader4openEPNS_4FileE+308)
#10 pc 0000000000009a88 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader13open_filenameERKSs+216)
#11 pc 0000000000011ec8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmiscstuff-jni.so (Java_com_github_chenxiaolong_dualbootpatcher_nativelib_libmiscstuff_LibMiscStuff_getBootImageRomId+300)
#12 pc 0000000000603934 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/oat/arm64/base.odex (offset 0x35c000)

I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help

zhaodelin2002 said:
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
Click to expand...
Click to collapse
You know how to fix my issue?

daffa ZRN said:
You know how to fix my issue?
Click to expand...
Click to collapse
sorry,my way isn't same as yours......

Ivan Torres said:
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?)
Click to expand...
Click to collapse
The problem is from app. Not from your device. For me r199 works perfectly. You can use version in this thread also

daffa ZRN said:
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
Click to expand...
Click to collapse
Remove from starting of file to the end of line 3
The file should be started with "package" line

zhaodelin2002 said:
sorry,my way isn't same as yours......
Click to expand...
Click to collapse
What's your way, maybe I can try

daffa ZRN said:
What's your way, maybe I can try
Click to expand...
Click to collapse
modify build.prop

yshalsager said:
Remove from starting of file to the end of line 3
The file should be started with "package" line
Click to expand...
Click to collapse
Still not working do you have a ROM already modified?

[Alpha][miatoll] Droidian (Debian Bookworm) for Xiaomi Redmi Note 9 Pro - 9 Pro Max - 9S - Poco M2 Pro

{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.
This is accomplished by using well-known technologies such as libhybris and Halium.​Carefully read the whole post before jumping to installation.​They are important to give you the best idea of the current state of the OS.​
What is working:​- Alarm Clock (bullseye/stable only. Doesn't work on bookworm/nightly)
- Manual brightness
- Vibration
- Carrier info, signal strength
- Data connection (read bugs section)
- Incoming, outgoing calls
- SMS in, out
- Change audio routing
- Voice in calls
- Volume control in calls
- Bluetooth
- WiFi
- Proximity
- Rotation
- Touchscreen
- Earphones
- Headphones
- Loudspeaker
- Microphone
- Volume control
- Pin unlock
- Waydroid
- Wireguard
What doesn't work:​- Most of the things not mentioned above.
Bugs:​- RIL gets broken after switching airplane mode or modem off/on. Fixed after a reboot.
- Mobile data stops working after making or receiving calls. Toggle mobile data on and off from the settings app.
- Mobile data doesn't work in the first 2-3 minutes after reboots. Toggle mobile data on and off from the settings app after waiting a while to get it working.
- Droidian has no power management yet so you're left with only the 5020mAh battery which can last up to 6 hours without heavy usage.
Installation:​
Make a backup now, as your device will be wiped.
Click to expand...
Click to collapse
Download the needed files and tools
Droidian rootfs (specific build required)
Android 10 (Q) stock firmware
Latest TWRP recovery
Adaptation (unofficial)
Device preparation
A USB 2.0 port/hub with an actual USB 2.0 controller is recommended (Using fastboot on a USB 3.0 port may cause errors with some Xiaomi devices)
Save your APN (Android)
The Access Point Name or APN can be found in the Settings menu of Android
Take a piece of paper or a text editor, and write down everything that you see on that screen
These are likely to include a URL (e. g., internet.carrier.net), a username, and possibly a password
Unlock the bootloader (Computer)
Refer to the instructions provided by the device manufacturer
Other useful sources include the LineageOS wiki and xda-developers
Boot into recovery (Computer)
Boot TWRP by running fastboot boot twrp-VERSION-miatoll.img
Wipe the device (TWRP)
Go to the Wipe menu
Select Advanced wipe
Tick the boxes called Dalvik / ART cache, Cache, System, Vendor, Data
Swipe to Wipe
Go back to the previous menu
Choose Format data and type yes
Go back to the main menu and select Reboot
Choose Bootloader
Boot TWRP again by running fastboot boot twrp-VERSION-miatoll.img
Copy the files to the device (Computer)
When TWRP is booted, open the device’s Internal storage from your computer
Copy all of the files you downloaded to this folder
Droidian installation (TWRP)
Install recovery
Install the file called twrp-VERSION-miatoll.img as an Image to the Recovery partition
Install Droidian rootfs
Install the file called droidian-rootfs-arm64_YYYYMMDD.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload droidian-rootfs-arm64_YYYYMMDD.zip
Installation is optional for stable releases, but it is recommended, because it helps with debugging
Finalizing the installation
Install adaptation package as a flashable zip (TWRP)
Install the file called adaptation-droidian-miatoll.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload adaptation-droidian-miatoll.zip
Boot your device
Go to the Reboot menu and choose System
TWRP might complain that there is no OS installed, but that’s fine
The first boot may take longer, and at least one spontaneous reboot is expected during the process
You should be greeted with the lock screen, the default password is 1234
Congratulations, if everything went well, now you should be running Droidian.
Notes:
Recovery
Use the recovery linked at the start of this page. The installation might fail with other recoveries that the one mentioned above.
Default password
The default password is 1234.
Apn
Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls
Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Broken calls
Switching airplane mode on and off or switching the mobile modem off and on from the Quick Settings or the Settings App will break calls. If that’s the case reboot the phone to fix it.
Out of storage
By default when flashing Droidian it allocates 8GB of memory to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
Status
Droidian GSIs are experimental! Bugs and missing features are expected.
SSH access
Connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications
You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
Credit:​Marcel Alexandru Nitan
Droidian Mobian UBports
You can ask for assistance specific to this device at Droidian for miatoll devices.
Sources:​- kernel
- adaptation package
Donate:​- PayPal
- Revolut

Announcement/Update ~ Droidian
Support for Droidian Bullseye has been discontinued. Droidian Bookworm has become more stable while the old Bullseye version hasn't received any updates from the devs since December 2021.
Users that are still on Bullseye are recommended to backup their data and install the Bookworm version for Droidian by following the new instructions located at https://devices.droidian.org/devices/miatoll/
For already Bookworm users:
Until now we've used the same ramdisk Ubuntu Touch uses because Droidian had no dynamic partition support. That has been changed on the previous days and a new adaptation package has been created to update the old ramdisk we used.
I've disabled the old miatoll ppa repository so the kernel won't get updated since it will "wipe" all the data and modifications.
To continue to receive kernel updates add the new miatoll ppa repository:
Your data and system changes will be cleared but will remain in /userdata/rootfs-overlay which will no longer be used after updating to the latest kernel as all the changes are now written into the Droidian rootfs.
Bash:
sudo curl -# --proto '=https' --tlsv1.2 -Sf https://miatoll-linux.github.io/repo/miatoll.gpg --output /usr/share/keyrings/miatoll.gpg && \
echo "deb [signed-by=/usr/share/keyrings/miatoll.gpg] https://miatoll-linux.github.io/repo/ bookworm main" > ~/miatoll.list && \
sudo mv ~/miatoll.list /etc/apt/sources.list.d/miatoll.list && \
sudo apt update
sudo apt upgrade

Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.

Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!

ProtoDeVNan0 said:
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
Click to expand...
Click to collapse
Not to go off topic but that's one of the reasons I stopped making Roms on XDA and instead keep them for myself lol.
Anyways OP, Amazing to see people working on Debian based Roms for our device. Will definitely be checking this out sometime this week!

[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Unfortunately I can't. The recoveries we have available for our phones are not able to mount the raw img file (rootfs.img) so sideloading the devtools and the adaptation package is not possible so we have to manually fix the mount via losetup and make the extraction of the packages above ourselves.
Probably everything will be fixed when we're going to get a fully working and stable recovery.

hi! what is it the current situation of battery drain, i really want to give a try

[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Installation steps reduced

[email protected] said:
hi! what is it the current situation of battery drain, i really want to give a try
Click to expand...
Click to collapse
Well it improved since the last time. Don't expect days of battery life but it's enough to get you through the day
*Waydroid can decrease the battery like a lot btw.

Hi, I really love your work @nitanmarcel
Thanks

How is this for daily use?
Mobile data problems fixed?