[ROM/WIP][CM-13.0/LOS-14.1][6.0.1/7.0.1] CM13.1 or LOS 14.1 - HTC One X - HTC One X

WARNING: This rom is by far not suitable for daily usage and flashing it is at your OWN RISK! (my HTC One X has survived so far )
I've compiled a CM-13.0 from for the HOX.
While it is kind off working, it is very unstable.
Butttttt, when it's stable it's damn fast for what I've experienced so far.
What is broken:
audio
camera
wifi
gps (needs to be confirmed)
bluetooth (needs to be confirmed)
installing an app doesn't make the app appear in the launcher
I've attached the GDB debugger to the mediaserver process to start viewing the breakpoints but I didn't succeed.
(for people that are curious, here is the crashlog: http://pastebin.com/KN9s7C7K)
The only way this rom currently boots is when the GDB is attached and I am slowly stepping trough the main_mediaserver.cpp source code. I think this works because the mediaserver get's started too soon, and thus some of the hardware related things are not ready. If only I had the tegra3 source code for the audio.primary.tegra.so and the camera.vendor.tegra.so files. That would make my life a lot easier since I'd have just changed the code to be compatible with Android 6.0.
If you've got a spare HTC One X and you'd like to test and help me out, you can flash this rom and let me know what is working or not.
There is a build running right now and I'll let you know the results when it's finished.
XDA:DevDB Information
[ROM/WIP][CM-13.0/LOS-14.1][6.0.1/7.0.1] CM13.1 or LOS 14.1 - HTC One X, ROM for the HTC One X
Contributors
tim687, DevUt
Source Code: https://gitlab.com/endeavoru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: HBOOT 1.72.0000 or higher
Based On: CyanogenMod
Version Information
Status: Testing
Current Stable Version: -
Current Beta Version: -
Created 2017-03-02
Last Updated 2017-05-21

Obtaining device logs
Obtain (boot-) logs
There are a few ways to obtain the bootlogs when the device doesn't (fully) boot.
A recovery with file manager is required (most TWRP's have it)
Get kernel logs:
#1: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#2: Make sure that the sd card is mounted, if not go to the mount menu of TWRP.
#3: Go to Advanced -> File Manager, then navigate to /proc and copy the files last_log and last_kmsg to the sdcard (/sdcard).
#4: Go back to the mount menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#5: Copy the last_log and last_kmsg to your computer and send them in this thread to me (not the actual text, but the files themselves, pastebin is also allowed).
#6: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#7: Make sure that you are able to test a new build and be able to reproduce the crash
Get ADB access
If you need to clean flash a new version of this rom, please do that first, so that the files you are placing inside the /data partition don't get erased.
Locate the adbkey.pub file on your computer.
On Windows it is in C:\Users\<username>\.android\​On Unix (Linux and OSX) it is located under ~/.android​
#1: Make the following directory tree:
misc\adb​#2: In the adb folder create a file named "adb_keys"
#3: Open the file with any editor.
#4: Paste the contents of the adbkey.pub file in the adb_keys file. If you want to authorize multiple computers, just paste the next key in the line below the first key.
#5: Save the file
#6: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#7: Go back to the 'Mount' menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#8: Make sure that the sd card and /data is mounted, if not go to the mount menu of TWRP.
#9: Copy the directory tree you've created in #1 to the sd card of your device.
#10: Go to 'Advanced' -> 'File Manager', then navigate to '/sdcard' and click on the 'misc' folder, then click on 'select' -> 'Copy Folder' -> 'data' -> 'Select' and swipe to confirm.
#11: To start the logs to appear on your screen enter the following command (the same for Windows and Unix users, it requires the ADB binary and executable folder to be in your path):
adb logcat && adb logcat​You might want to save the log to a (text-) file, you can do that by changing the command to (note: If the file exists, it gets overwritten!)
(adb logcat && adb logcat) > adb_bootlog.txt​#12: Post the logfile in this thread (not the actual text, but the file, pastebin is also allowed)
#13: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#14: Make sure that you are able to test a new build and be able to reproduce the crash

Reserved
How to flash:
For full safety, please do a clean flash everytime a new build has come out!
#1: Extract boot.img from the zip.
#2: Flash the zip
#3: Clear data and cache
#4: Restart in fastboot mode and use fastboot flash boot boot.img to flash the boot image
#5 (optionally): follow the steps in the post above to obtain (boot-)logs
Changelog:
20170304:
Used audiowrapper, to hopefully fix the audio

Social links
Social:
{
"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"
}
Telegram Group: https://t.me/htconexwip
Me: https://telegram.me/timkoers

Nice
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
@DevUt

yes... great news for our old One X !!

Guys, the latest build is up, not sure if it will boot though. Please let me know

IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes

DevUt said:
IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes
Click to expand...
Click to collapse
I can't remember if you did or not. I think you were working on it though.

mrbtree98 said:
I can't remember if you did or not. I think you were working on it though.
Click to expand...
Click to collapse
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !

DevUt said:
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !
Click to expand...
Click to collapse
At which three? I might be able to build one today.
I've synced LineageOS 14 with the CM-14 trees, and the compilation doesn't even start, so I'll have to look in to that

I just want to thank you or making this rom. I am on cm12 and once this rom is more stable I will flash it and give it a try.

Might take a while howeve ?
College has started again

Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?

Byrkoet said:
Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?
Click to expand...
Click to collapse
Audio is very difficult, the audio subsystem has changed during the upgrade from 5 to 6.
I haven't got time to try to fix them.
Don't expect very much very soon

Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?

DeepScred said:
Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?
Click to expand...
Click to collapse
I'm working on it

Hey tim687,
really nice what you do. How is it going?

MrSirMan said:
Hey tim687,
really nice what you do. How is it going?
Click to expand...
Click to collapse
It's going very good with me man! Not with the rom however, I haven't found time to start working on it.
I've been very busy with various project for my school and at home.
I am not sure when I'll have time to start working on it again...
Thanks for the interest though!

I just get one today and would help you with testing if any of the issues has been fixed, unfortunately they are major =/

Related

One Plus One Toolkit v1.3.2 BETA + ADB/python library - UPDATED 12/30/2014

i present to you the latest release from my secret underground laboratory.......
THE HALF-ASSED ONE PLUS ONE TOOLKIT v1.3.2 BETA!
{
"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"
}
old screenshots because i'm lazy
UPDATED 12/30/2014
NOW ON GITHUB:
https://github.com/eudemonics/1plus1toolkit
NOW WITH MORE UNIVERSAL FEATURES TO SUPPORT ALL ANDROID DEVICES!
THERE IS A REASON THIS IS CALLED THE HALF-ASSED ONEPLUS ONE TOOLKIT. don't expect frequent regular updates. i respond to support queries when i receive them, which means whenever i check my email or log onto xda-dev, which is not very often. though i do update it every now and then. now that it's on github, you can actually get updates without me having to go update the threads on every forum to make the announcement about it being updated.
USE AT YOUR OWN RISK. i'm not responsible for anything that might happen to your device as a result of using the toolkit. if you use the correct files in the package and follow the toolkit directions onscreen, your device should be just fine. i assume if you have the technical know-how to install python, the android SDK, and run the script, then you've got a pretty good idea of what you're doing already. if you need help, send me a message. the best way to reach me, to get the quickest response, is probably on facebook, as i do not log onto xda-developers or my email accounts regularly:
http://www.facebook.com/dreamcorporation
[***this project was originally posted in the Oneplus One "General" forum, as i'd assumed "Original Android Development" was restricted to ROMs, apps, and themes. i finally read the rules, though, so i hope my toolkit is useful/creative enough to qualify to be here. i could use some beta testers if anyone's brave enough to volunteer - doesn't have to be on the oneplus one, as i am adding more and more functionality to support all android devices. am also open to ideas and suggestions - if you want any features built, just ask. maybe i'll code it for you, and give you credit for the idea too.]
REQUIREMENTS: python 2.7, android SDK, opotoolkit.py, opointro.py pyadb.py. and of course, a machine running ANY OS that supports python and the android SDK (OSX, Windows, Linux, maybe even Chromium OS?)
installation:
download and install python 2.7: https://www.python.org/downloads/
download and install android SDK: https://developer.android.com/sdk/
download toolkit package using GIT:
git clone https://github.com/eudemonics/1plus1toolkit.git 1plus1toolkit
to run from there:
cd 1plus1toolkit
python opotoolkit.py
to update:
git pull https://github.com/eudemonics/1plus1toolkit.git
it should work with the adb and fastboot binaries provided in the github project (*****if on linux rename adb to adb-mac, fastboot to fastboot-mac, adb-linux to adb, and fastboot-linux to fastboot*****), but if not, you should install the android SDK. i recommend even MORE that you create an environmental path variable to the android SDK so you can run the commands from any directory.
setting up an environmental path variable (optional - recommended):
if you're on windows you can go to my pastebin, find the only powershell script on there, and steal/adapt the code to create your own environment path variable. but it's much easier to configure in system properties - i'm not on windows right now so these may not be exact instructions, but you should be able to right click on "my computer", select "properties", go to the "environment" tab in system settings, and add the environment path there. linux and OSX users just need to add the android SDK directory to their ~/.bash_profile or ~/.bashsrc or wherever environment paths are defined. if you still don't understand environmental path variables or symbolic links, i highly recommend google (or startpage.com, the private version).
if you don't want to go to the trouble of creating the environmental path variables, and you want to use the android SDK on your computer, then just extract all the files from the ZIP into your android SDK directory.
how to run the toolkit:
plug phone to computer via USB, turn on android debugging.
open command prompt or terminal window to scripts directory. start toolkit by entering:
"python opotoolkit.py"
if everything is installed and in the right places, you should see a menu like the attached screenshot. if for some reason you get a permission denied error, try launching the command prompt or terminal as administrator or superuser.
i'll continue working on it and adding more when i can so keep checking this space. everything's open source; use, share, steal whatever you want from the code. some credit would be nice, though.
you can use the pyadb.py library to incorporate adb/fastboot commands into your own python projects. i'll be adding more features to that, but for now most of the common features are covered.
here's the github link - it still won't acknowledge my repository exists, and if i try to create it again locally it gives me a fatal error. [[email protected]#[email protected]#] let's just say github and i are not exactly BFF's. you can check to see if the files ever manage to appear: https://github.com/eudemonics/1plus1toolkit
i've been working to expand this so it can be used with all android devices, though it'll require people to supply their own device files to use with it! just because the toolkit can flash device firmware DOES NOT MEAN that the included files meant for the oneplus one will work on a NON oneplus one device! hopefully that's not something i needed to emphasize. if there is enough positive feedback and support i'll create a GUI since people like to click things more than type into a terminal window
not gonna bug you for donations - all my code is open source - if you'd like to donate, please do so by purchasing my EP. hey, you might even like the music, too:
buy it here: http://dreamcorp.bandcamp.com
or search for it on itunes, google play, amazon, spotify, last.fm, cdbaby, and so on.
there are also links in the description for my video:
https://www.youtube.com/watch?v=2i-F4jiKtGg
special thanks to chainfire for superSU, cyanogenmod for CM11S, geohot for the towelroot exploit, team win recovery project for the TWRP recovery, the developers of philz recovery, clockworkmod for the CWM recovery, OnePlus for giving us such an excellent and affordable product, and everyone here on xda-developers for growing and developing the android community into the vital and creative force it is today!
XDA:DevDB Information
Half-Assed OnePlusOne Toolkit in Python/ADB-python library - now on github!!!, Tool/Utility for the ONEPLUS ONE
Contributors
eudemonics
Source Code: https://github.com/eudemonics/1plus1toolkit
Version Information
Status: Stable
Current Stable Version: 1.3.1 STABLE
Stable Release Date: 2014-11-13
Current Beta Version: 1.3.2 BETA
Beta Release Date: 2014-12-30
Created 2014-08-19
Last Updated 2014-12-30
How work sync
mENU 5 HAS SYNC... hOW WORK ? wHAT SYNC ?
I get a "SyntaxError: invalid token" when trying to launch. Did I miss something?
You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.
Mr Woolf said:
You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.
Click to expand...
Click to collapse
It's also quite nice to understand how the Python works as everything is open-sourced in Python without privatized code. Good for educational purposes.
But yeah, I get why you'd say that, haha!
I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???
nedooo said:
I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???
Click to expand...
Click to collapse
did you copy multiple files at once? what did you use for the destination? (syntax)
Single .zip file and syntax : /sdcard
Edit: I needed this tool to transfer files from PC on XP without administrator privileges (MTP was mission impossible), at the end I did it with Airdroid.
Thanks for replay.
Nice, I don't use it, but it has passed my tests

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
​It has LINUX/UNIX and MAC support!
​
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
​ Features: ​
Fastboot​​- Unlock/Lock Bootloader​- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included​- Flash any partition (Flashing submenu)​- Flash full Stock images (you can choose and add images)​- Erase partitions (you can choose which of the partitions)​- Reboot (you can choose again...)​​Adb​​- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included​- Backup (you can choose the name and place for your backup)​- Restore (you can choose your backup)​- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included​- Logs (DMESG and Logcat)​- Screenshots (you can directly take screenshots to your PC with no Root)​- Reboot (lots of choices)​​Others​​- Refresh and delete files/folders from menus (Right-click or key F5 and Del)​- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)​- Tab key support for easier keyboard navigation​- Tool-tips for all buttons​- Check for updates​- Link to xda-thread (here)​​​ Download links: ​
Windows x86|x64 - Linux x64 - MAC x64​​All released versions can be found here.​​
​
(The latest versions are always on the bottom.)​​[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​​
​ Known bugs/limitations: ​
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)​- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​​
​ Changelog: ​
​Check the changelog for each release here.​​​ Tutorials/FAQ: ​
​Q: How do I get in bootloader/fastboot mode?​Turn off the phone and turn it on by using Volume down + Power key.​​Q: How do I check for updates on your tool?​Follow the instructions on the screen below.​
​Q: Where can I find the device driver to install it for windows?​Click here, download the driver, and run the setup.​​Q: How do I root my stock phone?​- Unlock bootloader.​- Flash recovery.​- Use SuperSU 2.62 systemless or higher from here.​(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)​​Q: I get an error "Cannot open file" on MAC, what should I do?​Open the terminal, go to your application path and paste this command:​
Code:
chmod +x LxMultiTool.app/contents/macos/*
​Q: What do I need to do in order to be in Fastboot or in ADB mode.​Fastboot mode will be detected only while being in bootloader.​ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.​Refresh button needs to be used in order to check for what mode you are in.​​Q: Are there any other software that I need to install in order to run this tool?​On Windows and MAC everything is bundled, so nothing needs to be installed, just run.​On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.​If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.​​Q: I have a yellow/orange/red text screen during boot, what's that?​When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.​​Q: Hey, my device is not detected, why?​On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.​Also, make sure you click the connection Refresh button after connecting the device to your PC.​​Q: What do I need to do in order to install a custom ROM?​1. Unlock Bootloader.​2. Flash a custom recovery of your choice.​3. Flash an insecure kernel (boot).​4. Flash custom ROM with no problems via recovery.​All those things are found and can be done via this tool.​​Q: Hi, I just downloaded this tool, how do i use it?​First, extract the folder somewhere.​After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.​​Q: Do I need android-sdk installed or something else?​No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.​This tool is fully portable and stand-alone.​​Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?​Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:​- Enable Developer options​- Enable USB Debugging​- Look for the ‘OEM Unlock’ Option and toggle it.​​Q: How do I use the return to stock feature?​First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89d​that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.​​Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.​
​Q: How do I enable Developer options?​- Launch the Settings​- Scroll Down and Tap on About Phone(or About Device)​- Locate the Build Number Section​- Tap on the Build Number Option 7 Times​- Go Back to the Main Settings Page​- Scroll Down and Tap on Developer Options​​Q: Hi, I just bought a phone what should I do now?​Well, you firstly need to unlock your bootloader...​​Q: What is logcat?​Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.​It is usually used for debugging and entertainment(?).​When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!​​Q: What is a Custom Recovery and why do I need one?​A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.​​Q: There are other guides/tutorials out there. Should I check them instead of this?​If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...​​Q: What is sideload and how do I use it?​Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.​Please note that you need to be in sideload mode on your recovery before doing this.​To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
​ Sources: ​
The official and original repository can be found here.​​
​ Bug reports/feature requests: ​
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.​​
​ Licensing: ​
Please note that this tool is open source and released under the GPL v3 license, which can be read here.​Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​​
​ Tech and stuff: ​
Some additional marketing for stuff used in this tool​​Qt - An awesome cross-platform IDE​Vmware - For letting me test this tool on all platforms (Linux and MAC).​Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)​UnixUtils - For the sed utility for Windows.​AndroidFileHost - For the awesome file-management platform for developers.​​
​ Donations: ​
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.​​This section will also include the hall of fame for donors and on the github repository.​​Special thanks for donations:​- @john7760​​
​ Disclaimer: ​
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16
Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C
You da man! Can't wait for my phone to show up.
That was quick!! Waiting for this phone to be launched in India.
It works great thanks.I mean Tool
Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk
Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Haven't even received my device yet, just wanted to say Thanks in advance!
Showing so much promise
I can't say more for this kind of support.
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.
Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus
Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One
Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...
Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.
I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip

[Tool][Guide] LeeDrOiD and ICE svnZipper | Windows | Linux | Mac

svnZipper​
As you may know developers like @LeeDroid and @baadnewz use Subversion so users can get the latest changes quickly. Although this results in users checking out the Subversion repository and zipping the ROM themselves. This doesn't sound too difficult and it isn't, but to make things easier I made a tool I like to call "svnZipper". It is a pre-built binary with all the dependencies to build a nightly ROM from @LeeDroid and @baadnewz repositories, this has support for Windows, Linux and Mac.
As we are not all perfect the tools does face issues, be it bugs or user issues, I am finding it hard to keep track of all these issues popping up in each thread. Therefore I made this thread to get the latest svnZipper, follow guides and report any issues for me to answers and solve (although it is in HTC 10 thread you can post HTC One M9 and HTC One M8).
The Guide​
Step 1
Download the latest svnZipper:
LeeDrOiD get it here
ICE get it here
Put the svnZipper anywhere you like on your PC, I would recommend a folder you can easily access.
Step 2 (Only Required for Mac and Linux)
For Mac and Linux you will need to set the permissions of the binary to be executable. You are probably be familiar with this process if you are a Linux and Mac user but if you don't know the process I will explain it for you. Open up a terminal and change to the directory of the location of your svnZipper, then type the following command:
Mac:
chmod 0755 macSvnZipper followed by enter
Linux:
chmod 0755 linuxSvnZipper followed by enter
Step 3
Execute the svnZipper
Windows:
Double click the svnZipper.exe or open up command prompt in the location of the .exe and type:
svnZipper.exe followed by enter.
Mac:
With the terminal still open from Step 2, type the following command:
./macSvnZipper followed by enter
Linux:
With the terminal still open from Step 2, type the following command:
./linuxSvnZipper followed by enter
Once you have execute the screen you will be presented with a image as shown below:
{
"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"
}
Step 4
Type the corresponding number next to the device you would like to build for and press enter. This will start the process of checking out files or updating the files that already exist if you have checked out before. This process will vary time consuming depending on how many files are needed to be download from the remote repository.
This process will complete the following steps:
1. Checkout/Update files from the remote repository for your device
2. Make a nightly .zip for your device
3. Make a md5 checksum file for .zip
All checked out files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME
HTC M9 it will be /LeeDrOiD_HIMA
HTC M8 it will be /LeeDrOiD_M8
ICE:
HTC 10 it will be /ice_pme
HTC M9 it will be /ice_hima
HTC M8 it will be /ice_m8
Once completed you will be presented with a screen shot similar to the ones below.
All nightly .zip and .md5 files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME/Builds
HTC M9 it will be /LeeDrOiD_HIMA/Builds
HTC M8 it will be /LeeDrOiD_M8/Builds
ICE:
HTC 10 it will be /ice_pme/Builds
HTC M9 it will be /ice_hima/Builds
HTC M8 it will be /ice_m8/Builds
The builds will be named in the following format:
LeeDrOiD:
HTC 10 it will be LeeDrOiD_PME_RXX.zip
HTC M9 it will be LeeDrOiD_HIMA_RXX.zip
HTC M8 it will be LeeDrOiD_M8_RXX.zip
ICE:
HTC 10 it will be ice_pme_nightly_rXX.zip
HTC M9 it will be ice_hima_nightly_rXX.zip
HTC M8 it will be ice_m8_nightly_rXX.zip
Step 5
If a update comes out and you would like to rebuild the ROM again, follow Step 3 and Step 4
FAQ
QUESTION: The build zip is extremely small and has missing files?
ANSWER: Delete the checked out files and execute the steps above again
QUESTION: The revision checked out by the tool is out of date and doesn't get the latest revision from the remote repository?
ANSWER: Delete the checked out files and execute the steps above again
Note: The FAQ will increase as I get more user experience.
Reporting a Issue
Take screen shot of the errors raised from the tool and post it in this thread. If I don't get as much information as possible I can not help you.
Note: Windows will automatically close is a issue arises, therefore I recommend that you execute the .exe in command prompt instead of double clicking.
XDA:DevDB Information
svnZipper, Tool/Utility for the HTC 10
Contributors
~clumsy~
Source Code: https://github.com/clumsy1991/svnZipper
Version Information
Status: Beta
Current Stable Version: 1.0.4
Stable Release Date: 2016-06-06
Created 2016-06-07
Last Updated 2016-06-07
Changelog
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug
V1.0.4
Considered as initial revision
Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Sent from my HTC 10 using XDA-Developers mobile app
The Great Dane said:
Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Click to expand...
Click to collapse
And press 1 to build
~clumsy~ said:
And press 1 to build
Click to expand...
Click to collapse
Shut up LMFAO [emoji12]
Different filesize
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!
twistednl said:
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!
Click to expand...
Click to collapse
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?
~clumsy~ said:
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?
Click to expand...
Click to collapse
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph
twistednl said:
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph
Click to expand...
Click to collapse
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!
twistednl said:
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!
Click to expand...
Click to collapse
I know! Much appreciated! This why I made the thread so i can capture bugs and peoples experiences.
Thank you!
Though resume download is broken in this SVN tool, it will see the files downloaded as complete and will not give an option to resume or force resume
great job,thanks!
~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Thanks for the heads up....
Sent from my HTC 10 using XDA-Developers mobile app
Just a minor fix, only 1 report case of the bug.
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug
Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.
Ndaoud360 said:
Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.
Click to expand...
Click to collapse
The tool is made for its ease of use and is independent so user don't have to install anything. It was requested by the devs. You can still use a manual solution.
Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Sent from my HTC 10 using XDA-Developers mobile app
I have the same problem as mentioned on the first page. The program does not work correctly if I run it from a network share. It finishes downloading prematurely and it creates a partial ROM which does not work.
I took clumsy's script, stripped some parts in order to create a minimal example and to see what it does (I removed the multiprocess operations). The result: each time I run it, it works for several minutes, then it ends with the following error:
pysvn._pysvn_3_5.ClientError: ra_serf: The server sent a truncated HTTP response body.
It happens each time.
kfasheldon said:
Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Click to expand...
Click to collapse
Sorry man, that will too much work as it wouldn't be possible with my current method.

[OFFICIAL][MM][ROM][ALL VARIANT] Flyme 6.7.7.31R beta for LG G2

{
"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"
}
Hello friends,
I am with Flyme 6, which is developed for the LG G2.
It supports all variants.
Supports all languages.
Android version is 6.0.1
How to flash:
1.Flash the CAF boostacks.
2.Root and Flash the bumped twrp recovery.
3.Wipe.
4.Flash the Flyme 6 Rom.
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: CAF
Based On: LineageOS
Version Information
Status: Testing...
Current Beta Version: 6.7.7.31R beta
Screenshots :
Screen Video :
https://www.youtube.com/watch?v=ETIHLoGxlVQ&t=80s
Download :
http://openrom-dl.flyme.cn/2771457/20170801/1501602480038/flyme_LG-D802_bise_6.7.7.31R-beta.zip
Good use
and for the gapps and root?
can you provide the proppers gapps and root method?
thank
Sent from my LG-D802 using Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
i have already flash current version but no have idea bout gapps and rooting method
Sent from my LG-D802 using Tapatalk
jpunkers said:
and for the gapps and root?
can you provide the proppers gapps and root method?
thank
Sent from my LG-D802 using Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
i have already flash current version but no have idea bout gapps and rooting method
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Gapps and root are not found.
Gapps : opengapps.org ARM/6.0/Pico or Nano
Root : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 Flash from Recovery.
since it base lineage, am i rit? ok thanks bro
Sent from my LG-D802 using Tapatalk
Is it not possible that on android is 7?
(im not speak english - google translate)
its awsome 6.0.1 thanks dev
and for all variant or just 802???
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Huzaifashaikh0012 said:
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Click to expand...
Click to collapse
Could you kindly share how well it works once you tried it ?
Huzaifashaikh0012 said:
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Click to expand...
Click to collapse
Thank you for your thought to change! If you have the opportunity to cast a Screenshot, I will add the subject.
Worth it!
Pag96 said:
Could you kindly share how well it works once you tried it ?
Click to expand...
Click to collapse
At first i thought the performance would be dull because of good appearance but the rom does maintain them both
didn't measure the full battery life but it's better than the stock one's for sure
The sound is pretty low though.(count as a bug ..my speakers are good )
no problem in connectivity the gps is good
thumbs up for the ROM :good:
Try this but stuck on logo screen (ls980)
Aures Batna said:
Try this but stuck on logo screen (ls980)
Click to expand...
Click to collapse
I had the same problem while installing..
I restarted the phone by long pressing the power button(10sec). And then it worked fine after reboot .
I did that on a vs980 though you could try .
Huzaifashaikh0012 said:
At first i thought the performance would be dull because of good appearance but the rom does maintain them both
didn't measure the full battery life but it's better than the stock one's for sure
The sound is pretty low though.(count as a bug ..my speakers are good )
no problem in connectivity the gps is good
thumbs up for the ROM :good:
Click to expand...
Click to collapse
Thank you for your tests, bro
do you have any work arround to change the theme store to english ?
Why we need flash caf bootstack?
Cant i just wipe data and flash rom?
I get random reboots on this ROM model no. D802 and yes you have to wait 20 - 25 minutes for first boot.
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
stalvekio said:
Why we need flash caf bootstack?
Cant i just wipe data and flash rom?
Click to expand...
Click to collapse
because it needs lollipop bootloader. So flash CAF.
I'm on cloudy 3.3 right now.
Do I need to change my bootloader and flash caf or not?
Try it.
Hi, i'm install the rom last day. Device D802TR, stock rom lollipop.
I'm applying root very difficult because first time root my device. Not worked "One Click Root" method. How did i do. Found the how make root and twrp method, using step by step this;
1- Install lg drivers for pc,
and device mount pc usb debugging. OneClickRecovery extract the " C:\1>"
opened the one click recovery folder the cmd.exe
2 -
- C:\1> adb.exe devices -> results my device
- C:\1> adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
- Unplug usb cable and close phone. Volume Up button press after plug the usb cable
open the phone download mode, and back to cmd screen.
- C:\1> Ports.bat -> device mount com port view.
- C:\1> SendCommand.exe \\.\COM7 (my device com7 port)
- # sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
- unplug usb cable and long press power button.Restarting phone and screen message
"upgrading Android" and after 5-10 second showing lg logo screen.
.. And open the phone, install root checker the play store. Open app check,operation succesfully,
my phone is now root.
3 - Install twrp official app, RebootRecovery(qbanin) in phone.
Copying files (caf bootstack, flyme rom, opengapps nano) in device download folder.
twrp application run and agree. And run RebootRecovery application, reboot the device open twrp.
Backup system,data,modem etc. (Making a NANDroid Backup). Reboot and exit twrp(because copying backup files the pc).
Install "root browser" the play store. Copy the files my pc.
again reboot recovery app, device open twrp.
Wipe -> advanced wipe (only dont select internal storage). Back the main menu.
Install -> flymeos file swipe the flash (flashing time maybe less 1.5 minute)
(Note: I did for the first time, i did not add other files. Because i'm beginner.)
Finally finished file flash and show the flymeos installation application.
Language is chinese, only click right bottom text, after again chinese words (me not understand chinese language,
very scary my face), other phone install translate application and take photo translate chinese words,
after a while I saw it for the first time english words.
This sentence "Save log file" and click show chinese text and little chinese word,click word.
This will not happen, and found youtube video.
Watc the video, I'm on the right path. Interesting for me.
Again click bottom right and show the list. Click top words, begin the installation.
install finish and reboot press. Reboot device showing lg logo and show flymeos boot animation.
As for me wait 6-7 minute. And me thinking not opening system, little scary. Because not install caf boostacks file
and opengapps file. But; And the system opening on.
Language selection screen, select lang, finally words I know. Click next,next etc. Start connected without a question.
Close gsm internet connection, select wifi and password (no my language keyboard, CZ and EN, but not found "I, ı").
Continue the installlation and final.
Show Lock Screen, slide the open.Tap to settings (Insist on using chinese applications, of course meizu account).
Anyway do not write more...
Once again install Flymeos. And add file flashing time, rom, gapps, supersu (but not install supersu).
Result ;
# LED Not working (only plug charger orange color working)
# Knock on/ Knock off not working
# Change the Device MAC Adress (interesting)
# GSM LTE very low, usualy lost
# GSM 3G low
# Keyboard Not Support Turkish(for english not char "I and ı" )
# Sometime touch home button restart device.
# Screen button layout do not change, (Back left, middle home, right recent apps) and background
color not chance.(Why no diversity)
# Camera disgrace.
# Sound exit not cool(Even worse)
# Sms message receive (lock screen) show notification and wake up screen, (show buttons read, delete) but buttons not work.
Touch read button notification lost, nothing ! slide and open lock screen but again nothing.Open message box No unread posts.
# Open contacts and 1 number adding Black list, and touch recent apps button, restart.
# Positive action : Moore battery life, this morning %100, take 10 photo and 2 sms write, 2 call (total 4 minute), 8 restart after %91.
Questions :
# Caf boostacks why need ? (Me not flash boostacks)
# Some said it took 20 minutes to installation. (Me 1-2 minute)
# First Boot time 6-7 minute (short or long ? i don't know)
# Why urge use local application (I guess Meizu ports rom)
that's all for now. I think today wipe system, and install LineageOs 14.1 (now downloading files).
dtonkz , this is the best test report i have never seen before here
First boot time 20minutes
Keyboard not change ( change but always rebot)
Battery bad or normal
Permance good
Knock on off not work
Led not work
D 802
Sory my bad English
And sound boost mod https://mega.nz/#!KwJlG...5HxJ4__FiRUvkVMZifbilHU

[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?

Categories

Resources