Develop Bugs

[RECOVERY][UNOFFICIAL][STABLE&DEV] TWRP [TF300T/TF201] | DISCONTINUED

TWRP for Transformer Pad (compatible with Transformer Prime)​DISCONTINUED​
{
"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"
}
Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin team started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of their own features. It is a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DISCLAIMER : TeamWin team and myself will never ever be responsible for any damages you do to your device !
ALL CREDIT GOES TO AND ONLY TO :
-> TeamWin & omnirom teams (TWRP tree)
-> CyanogenMod team (ROM, device and kernel trees)
-> TheMuppets team (vendor tree)
NOTE : i am not affiliated with any of the teams mentioned above...
INSTALLATION :
=> Option 1 : your device does not have any custom recovery yet ! Please download any of the flashable .zip file below that you are interested in Unzip it and flash recovery.img to your device using fastboot (your tablet must be in fastboot mode [bootloader menu]).
=> Option 2 : a custom recovery has already been flashed to your device ! Please download the flashable .zip file below that you are interested in and flash it from recovery as usual (don't forget to disable .zip signature checking in your current recovery...). From now on (2014-09-01) ALL my .zip files will be signed, so you will be able to flash them with .zip signature checking ON from recovery ! :good:
DOWNLOADS : <= CUSTOM RECOVERY FLASHABLE AND WITH DOCK SD CARD SUPPORT AS EXTERNAL STORAGE
=> STABLE branch : stable ! Includes all upstream merged commits ! EXT4+F2FS <= PLEASE DOWNLOAD LATEST OFFICIAL BUILD FROM TEAMWIN WEBSITE ! THANK YOU !
-> custom TWRP for TF300T (TF201 compatible) [without any device checking] | STABLE ()
=> DEV branch : not as stable as the regular one BUT you can safely flash and use it EXT4+F2FS
-> custom TWRP for TF300T (TF201 compatible) [without any device checking] | DEV () <= NO FILES IN THIS CATEGORY ATM...
=> TRYOUTS : because i do not have a TF300T anymore, ALL releases will be community tested BEFORE they are flagged as working... :good: (do not worry if you decide to test one out, i will give you a procedure below to test it WITHOUT installing it to your device )
PLEASE DO PREFER FILES ABOVE (STABLE & DEV), ATM TRYOUTS ARE STILL THERE AS A FALLBACK ! Thank you !
TESTING OUT A RECOVERY IMAGE WITHOUT INSTALLING IT TO YOUR DEVICE : APPLY ANY CASE :good:
-> unzip any of my zipped recovery images you might be interested in...
-> in the unzipped directory where there is recovery.img, simply input the following fastboot command :
Code:
# fastboot boot recovery.img
:highfive: :good: (your device must be loaded to its bootloader menu [fastboot enabled on it]; if you are using Linux and have adb/fastboot installed on your computer, then the above shell command works as is (you may have to add 'sudo' before it onto Ubuntu / Debian based distributions; if your are using Windows then document yourself on how send properly a fastboot command to your tablet...) =>
Code:
# fastboot -i 0x0B05 boot recovery.img
SHOULD work...
INFO 1 : If you get a failure when flashing from recovery with regular / PhilZ CWM or legacy TWRP, please use the corresponding file WITHOUT device checking... thank you ! :good:
INFO 2 : STABLE branch DOWNLOADS ARE ALSO AVAILABLE FROM THE DOWNLOADS TAB OF THIS PROJECT
INFO 3 : The 'take a screenshot' from recovery feature is now merged upstream, so both STABLE & DEV branches ship with it ! :good:... Simply press 'volume down' + 'power' hardware keys on your device in order to save a screenshot from recovery to your microSD card (files are saved on it to 'Pictures/Screenshots' directory...)
Happy flashing
NOTE : I've started building it for myself, now i'm sharing it ! I use it everyday and still do not have any issue ! Anyway you can feel free to report back Any feedback will ever be greatly appreciated !
PS : Flashing KK ROMs with this recovery is OK (it's its main purpose...), Flashing JB ones has not been tested yet so please report back if anything goes wrong with JB ROMs... Thank you !
NOTE : If you are interested in my work and download my files, please report back AND hit my THANKS button if you think i deserve it ! Thank you !​
PS : TWRP for TF300T is available as two separate download categories : STABLE & DEV branches ! The DEV branch is based off the stable one and is including features that are not available in the STABLE one yet (as upstream merged commits...) ! So the DEV branch is as stable as the STABLE one except for currently previewed features...
Have fun with it :good:​
XDA:DevDB Information
TWRP for TF300T/TF201 [UNOFFICIAL], Tool/Utility for the Asus Transformer TF300T
Contributors
ne0zone75, lj50036
Version Information
Status: Stable
Current Stable Version: STABLE
Current Beta Version: DEV
Created 2014-06-04
Last Updated 2015-02-23

Reserved

ALL my TWRP for TF300T builds are now updated to v2.7.1.0 !
Hello all,
Today i am releasing TWRP 2.7.1.0 builds for both STABLE and DEV branches. Both download sources links (Dev-Host on post number 1 and xda downloads tab) are now updated :good:
You will find TWRP 2.7.1.0 changelog below (grabbed from official TeamWin website) :
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
Click to expand...
Click to collapse
Best regards

questions
When go to change file system dont appear f2fs only ext2,3,4 and fat and exfat. What should i do to convert to f2fs? should i convert system and data?
tks

nuno407 said:
When go to change file system dont appear f2fs only ext2,3,4 and fat and exfat. What should i do to convert to f2fs? should i convert system and data?
tks
Click to expand...
Click to collapse
Good afternoon,
F2FS is not supported at all in my TWRP builds for TF300T ATM (kernel side and recovery side) because i really do not know if it is possible to implement F2FS to the CyanogenMod's kernel for TF300T that i am using for compiling the recovery (linux kernel v3.1).
Stay tuned !
Sent from my TF701T

ne0zone75 said:
Good afternoon,
F2FS is not supported at all in my TWRP builds for TF300T ATM (kernel side and recovery side) because i really do not know if it is possible to implement F2FS to the CyanogenMod's kernel for TF300T that i am using for compiling the recovery (linux kernel v3.1).
Stay tuned !
Sent from my TF701T
Click to expand...
Click to collapse
Hey all,
We over at team crombi are working hard to get a CM and Asus based f2fs kernel....
Here is my github of the source code as this one is stock Asus the CM kernel is based off the same thing....
https://github.com/monolithic-droid...mmit/1f898d5b3e15a5681cf4bdfa5c5e3576475d89bd
You are more then welcome to try it out, like I said it needs more testing....
Thx Josh

@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?

scanno said:
@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?
Click to expand...
Click to collapse
Absolutely not... i am using usual build flags BUT i am picking up recovery dock keyboard layout from local recovery tree instead of device's one... that is the only thing i have recently changed in ' .mk'.
With that said, i am building TWRP along with CM 11.0 sources tree (there is no init.recovery.rc) and i am using 'Official Linaro GCC' v4.7 for recovery + kernel.
Kind regards
Sent from my GT-I9195

scanno said:
@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?
Click to expand...
Click to collapse
What do you mean by distorted ?
Do you see two images or does the image slant ?
Thx Josh

lj50036 said:
What do you mean by distorted ?
Do you see two images or does the image slant ?
Thx Josh
Click to expand...
Click to collapse
I am not a native English speaker, so I do not understand what you exactly mean with slant. Only half of the screen is used and it looks like the image is pressed together on the y axes and stretched on the X axes.
The lines are not clear (interlaced)

scanno said:
I am not a native English speaker, so I do not understand what you exactly mean with slant. Only half of the screen is used and it looks like the image is pressed together on the y axes and stretched on the X axes.
The lines are not clear (interlaced)
Click to expand...
Click to collapse
That is very odd... I am sure you are aware of this flag??
RECOVERY_GRAPHICS_USE_LINELENGTH := true -- fixes slanty looking graphics on some devices
Thx Josh

F2FS functionality added to DEV branch ! Update released !
Good afternoon,
I've implemented F2FS ONLY in the DEV branch,... after all this is a testing branch !
To achieve this i've used @lj50036 (from CROMBi-kk team : thank you for your work !) F2FS enabled kernel for TF300T as the kernel of the recovery : THIS PART IS EXPERIMENTAL ! Then i turned ON F2FS support while building the recovery (dedicated TWRP build flag...).
Dev-Host download links are now updated for the DEV branch on post number 1 !
Any feedback on it will be very appreciated BUT please, be very carefull if you decide to test it out ! Thank you !
NB : In order to be able to back F2FS partitions up AND to restore them as F2FS, you will have to back them up when they are already F2FS formatted and after having filled them with data : a backed up EXT4 partition CANNOT BE restored as F2FS and reciprocally !
Very kind regards
PS : F2FS filesystem by itself is probably NOT compatible with crypto ! Please DO NOT TRY to use crypto over F2FS ! Thank you...

iI it possible to iuse this recovery on Memopad HD7 (ME173X)?

bovirus said:
iI it possible to iuse this recovery on Memopad HD7 (ME173X)?
Click to expand...
Click to collapse
Hello,
I will check this out and give you an answer ASAP
Greetings
Sent from my GT-I9195

I asked that because someone explain how to unlock Memopad HD7 and how to load the recovery.
The unlock app it's the same for TFT300
The recovery point to a downlaod link of a file for TF300T
Asus Memopad
Unlock (YouTube vdieo): https://www.youtube.com/watch?v=JUeLp6hkvs0
Asus Unlock APK (v8): http://fs1.d-h.st/download/00033/86c/Unlock_v8.rar
TWRP mod: http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
What's TWRP blob file?
Thanks.

bovirus said:
I asked that because someone explain how to unlock Memopad HD7 and how to load the recovery.
The unlock app it's the same for TFT300
The recovery point to a downlaod link of a file for TF300T
Asus Memopad
Unlock (YouTube vdieo): https://www.youtube.com/watch?v=JUeLp6hkvs0
Asus Unlock APK (v8): http://fs1.d-h.st/download/00033/86c/Unlock_v8.rar
TWRP mod: http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
What's TWRP blob file?
Thanks.
Click to expand...
Click to collapse
Hey mate your in the wrong forum...
You need to start your our, in general and ask for help there not here ...
Its OK that you ask if this recovery would work on your tablet, but this is not a help thread....
Thx Josh

I have both TF300T and Asus Memopad HD7
I already check in ME173X thread and I didn't find any info about recovery.
On internet I found link (posted before) that the recovery for TF300T should be OK for other Asus devices (the bootloader unlock is the same...).
To explain that (not to ask help) I posted the link in previous post.
For this reason i asked it in this thread about TWRP device compatibility.
I believe that could be intersting also for developper if this recovery works with other device to add the device name into the list.
Because if it's true the title can contains also Asus Memopad HD7.
I didn't ask a support about ME173X but just only this specifc recovery.

bovirus said:
I have both TF300T and Asus Memopad HD7
I already check in ME173X thread and I didn't find any info about recovery.
On internet I found link (posted before) that the recovery for TF300T should be OK for other Asus devices (the bootloader unlock is the same...).
To explain that (not to ask help) I posted the link in previous post.
For this reason i asked it in this thread about TWRP device compatibility.
I believe that could be intersting also for developper if this recovery works with other device to add the device name into the list.
Because if it's true the title can contains also Asus Memopad HD7.
I didn't ask a support about ME173X but just only this specifc recovery.
Click to expand...
Click to collapse
Do not worry ! Like i already said i will check your device's compatibility out with my TWRP builds (TF201 is, ME301T seems to...) ASAP BUT i am quite busy ATM...
Now, if it is the case, it will be up to you to unlock your bootloader and then flash the recovery on your own, according to your device's needs and i do think that @lj50036 was meaning that...
Best regards
Sent from my GT-I9195

What do you to add this instruction to help to flash custom recovery first time
- Download the following files and save them to your PC http://www.mediafire.com/?4dx982z93w8z7wk
- Downlaod the TWRP recovery
- Extract the Fastboot.zip file and place the extracted files inside a single folder. You should acquire 4 files, namely:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
- Expand TWRP recovery archive file and rename the downloaded TWRP file as recovery.img (for easier reference).
- Copy or move the recovery.img file to where fastboot.exe is located. You should have a total of 5 files by now.
- Switch off your tablet.
- Boot into Fastboot Mode by pressing and holding down the [Power] and [Volume Down] buttons until you see the message “Press Vol Up to enter RCK”.
- Release the buttons when you see this message and wait for about 5 seconds. A new menu appears. Press the [Volume Down] button to select the USB icon, then press the [Volume Up] button to confirm your selection within 10 seconds, or else your tablet boots into Normal Mode.
- Connect your tablet to your PC via USB cable. Pelase check theat tehd evice is right rcognzied (you should install Asus USB driver)
- On your PC, go to the Fastboot folder and open a command prompt window. You can do this by pressing the Shift key on your keyboard and right-clicking on the empty white space inside the folder, then selecting “Open command prompt here” from the context menu.
- Enter the following command at the command prompt to install TWRP Recovery.
fastboot -i 0x0B05 flash recovery recovery.img
- After installing, disconnect your tablet and reboot.
fastboot reboot

@bovirus
Good morning,
Have you successfully tried this solution for yourself ?!
Now ! Before posting any external download link in MY thread, PLEASE refer to me over PM before doing so ! :angel:
Thank you !
Sent from my GT-I9195

[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

[Rom][5.0.2]UNOFFICIAL FlymeOS 4.5.3.1

{
"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"
}
_________________​Hi XDA Developer
Here another port of flymeos from member:MROM
I saw it on Another website and want to share it with you
The new port has many improvements ....
IAM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS FROM YOUR PHONE
Thanks for topsecret78 for get rom source and change details
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Click to expand...
Click to collapse
Changelog
CHECK DOWNLOAD PAGE FOR CHANGELOG
here some pics
Another screenshots here
Click to expand...
Click to collapse
So we Reach the download part
Note : looks like flyme 5 is officially maintained by (machao) member on (gfan) forum and latest builds will be found HERE
flyme 4.5.4.3 beta Google Drive
Downloaded it?! Let's install it and taste flyme
First ensure your bootloader is unlocked
1. Put Zip file on your sdcard
2. Restart your phone into your favourite recovery
3. Backup your data
4. Wipe (System,Data,cache,dalvik cache) not important to wipe internal memory
5. Install Zip from sdcard
6.restart system
First start will take 5 up to 10 min so don't think it's bootloop
TESTED ON C6903
After start let it 2 min and restart to install Su
You can download it from official website or you can use kingroot or kingo to root

Please sent permission to download file rom.

You can download now
Hit thanks if you like it

abdo.war said:
You can download now
Hit thanks if you like it
Click to expand...
Click to collapse
Where are kernel sources? You can't post a rom without posting kernel sources. Also, could you post a link to rom sources too. Thanks.

I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me

abdo.war said:
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
Click to expand...
Click to collapse
Doesn't matter who the builder is: posting roms without kernel sources is not allowed. For your sake you should post kernel sources or the mods will close this thread.

Report thread to mods to close it
I am sorry but I am still new here

abdo.war said:
Report thread to mods to close it
I am sorry but I am still new here
Click to expand...
Click to collapse
I am not going to report you, but rules are rules. They are part of GPL license...

Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Translate from google
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone

hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..

markakash said:
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
Click to expand...
Click to collapse
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
fastboot flash boot boot.IMG
Then reboot
fastboot reboot
Click to expand...
Click to collapse
Then try to install it
I installed rom from flashfire but it's dangerous

link to download in fisrt post
https://drive.google.com/file/d/0B3yReeEdHxbWSkFrYmhXbjJRaE0/view
or
http://pan.baidu.com/s/1pJXPr8R
I tested and work xperia Z1 C6903
---------- Post added at 16:30 ---------- Previous post was at 16:21 ----------
Info from source
"According to the competition regulations to place the file and naming 2: According to the rules without built-root themselves into the brush to 3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart"
and
"Please read the complete message painted machine
ROM tested before release because of personal consequences Brush problems caused not bear
Built-in networking to promote the software, please support the author can then run reservations can also uninstall (as some promotion app requires placing it under the system needs to RE Manager Entering system / app Delete)
Prohibit secondary modified to personally thank all publication reproduced, please indicate support oil"

Since this is based on CM12 meaning android 5.0.2
Does this have any slow charging issues?

Rom update to Flyme 4.5.4.4R
Change details ========================== ======================
Update fixes
[Contact]
All models support SIM card contacts
【camera】
Repair photographs sound problems can not be closed
Added (some models) Set the option to save photos to SD card
【music】
Repair song not normally know the songs matching problem
【other】
Living repair service hotel category loading problems
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Link to download
http://pan.baidu.com/s/1jGYfpdG
1: According to the competition regulations to place the file and naming
2: According to the rules without built-root themselves into the brush to
3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart

What about C6902??

abdo.war said:
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
Then try to install it
I installed rom from flashfire but it's dangerous
Click to expand...
Click to collapse
whare boot.IMG??

msamsameemo said:
whare boot.IMG??
Click to expand...
Click to collapse
In the Zip file

Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875

topsecret78 said:
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
Click to expand...
Click to collapse
What's the password?

Abu Badr said:
What's the password?
Click to expand...
Click to collapse
you don't need this link i already uploaded it to google drive go to
download at first post under screenshots
i have uploaded too iuni os if you want i can post it
Click to expand...
Click to collapse

[Tool] NFT - Nokia Flash Tool to flash stock ROM (For Unlocked Bootloader)

NFT 2.0.7 & 1.2.3- Nokia Flash Tool to flash stock ROM
This tool can make you easier to install stock roms
This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program
v.1.1.0
{
"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"
}
What the tool can do:
- Flash phone - the tool supports the following phones out of the box: Nokia 8.1, Nokia 9 PureView, Nokia 7.2, all Nokia phones on the SDM_660 family, And other Nokia Phones
- Requires the bootloader to be unlocked.
- Support for more phone models can be easily added by adding a new profile and defining the partitions to flash and matching it to file names to be flashed.
- Able to create custom flash process
- Able to import profile (partition and flash data) from a txt file (check sample format)
- Can dump your current partitions to create a flashable file for recovery (this function needs root access)
- Switch slot on A/B devices which support slot change
Thanks to:
- Hikari Calyx (hikaricalyx.com)
- Narender Singh (TechMesto.com)
System requirements:
- Windows 7, 8, 8.1,10 or higher, 32bit or 64bit
- .NET Framework 4.5.1
- USB Data Cable
- Phone
Downloads:
NFT v.1.2.4 (Stable)
NFT v.2.0.8 ( Stable )
NFT v.2.0.9 ( Stable ) - new 08 Dec 2020
NFT v.2.1.0 ( Stable ) - new 11 nov 2021
Firmware :
Firmware 7.2 (1_390)
Firmware 6.2 (1_160)
*Work with Payload
- install python 3
- make sure user Environment variables link to Python folder and Python folder\script
Bugs:
v.1.1.1
-nokia 9 profile & dump (fix on 1..1.2)
v.1.1.2
- language failed to saved on second times ( fix on 1.1.3)
- some word failed to translate to CN ( fix on 1.1.3)
v1.1.3
- abl skip not work after add language (fix on 1.1.3a)
v1.1.3a
-none
v1.1.4
- on some case Nokia 8.1 switch to A slot After flash (fix on 1.1.5)
v.1.1.5
- dump on nokia 7.2, 6.2 because new naming process (fix on 1.1.6 )
v.2.0.7
- ota flash not work (fix on 2.0.8 )

Update & change Logs
NFT v1.1.0
- New design
- Add support phone
- Add auto-detect mode
- Add some feature on profile management
NFT v.1.1.1
- Fix detect Device for MTK & A-only Device
- Fix dump for nokia 8.1
- add dump profile for nokia 8 & Sirocco
NFT v1.1.2
- FIx Nokia 9 profile and dump
- now dump partition Work on FTM mode And Normal mode
- Add Language Setting : Simplified Chinese & English...
NFT v1.1.3
- fix save language in setting
- Fix some translate in CN language
- Add warning when flash Payload.bin
- Now NFT only process payload.bin with size more than 1Gb
(make sure use full system update payload.bin..)
NFT v1.1.3a
-fix minor bugs
NFT v1.1.4
- support more python name (for multiple python installed) default : python3, python, py . can add more
- add install protobuf on script
- add check slot on dump
- add custom dump setting..
- to change saved filename partition double click file name
*for best restore dump please use default file name for splash partition
NFT v1.1.5
- Fix auto-switch to slot A, after Flashing Nokia 8.1
- add Russian Language
- add Indonesia Language
- dump files Now naming Base installed Rom.
27 Des.
- fix auto-detect for new devices (7.2 ,6.2 , etc)
29 Des
- add Donate link... for donate
- add logs
v1.1.6
- fix dump problem on nokia 6.2, nokia 7.2
- new menu - Create homebrew from OTA FILES (extracted)
3 januari 2020
- fix name file Homebrew ( Minor)
- add error handle homebrew Clean temp files
- update Logs
27 januari 2020
- fix naming dump for some devices... when dump inactive slot
-fix minor bugs
V2.0.0
- New UI
- Restore Partition from ADB
28 januari 2020
V2.0.1
- Fix restore partition From ADB
- Tweak Side menu animation(Faster)
- now support flash partition structure (for convert CN - Global)
V.1.1.7
- now support flash partition structure (for convert CN - Global)
v2.0.2 & v1.1.8
- fix 4.2 & 3.2 Support
- note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2
v2.0.3 & v1.1.9
- fix minor bug for nokia 9
- fix nokia 7.2/6.2 didn't boot after flash ( Vbmeta problem)
v2.0.4 & v1.2.0
- NOw Support .zip file ( Ota File & Cutom rom )
- fix English translate
v2.0.5 & v1.2.1
- NOw Support .zip file ( Ota File & Cutom rom )
- fix English translate
- add separate setting For vbmeta flash script ( because -disabled-verify on some device will cause failed to update ota )
v2.0.8 & v1.2.4
- add support raghu vagma Homebrew Firmware
v2.0.9
- remove unused messagebox
* note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2

Reserved
How to :
* Flash phone
- Open NFT
- Choose Flash Normal
- Select Folder which Contain Firmware File
- Select Profile ( U can create Your Own profile In manage button)
- Flash
* Flash phone With Payload.bin
- Extract Full Ota FIle .zip
- Open NFT
- Choose Payload.bin File
- Choose Slot
- FLash
* Create Dump Partition Profie
- Open NFT
- Select Tools
- Select Dump partition
- Select manage
- Connected Phone with USB Debuging SET ON With Root Permision Granted
- Add New
- Select Which Partition Do you Want to backup
- Naming Profile
- Save
* Dump Partition
- Open NFT
- select Tools
- Select Dump Partition
- Connected Phone with USB Debuging SET ON With Root Permision Granted
- Select Profile
- Select Slot
- Dump Partition
* Homebrew From FULL OTA FIle
- Extract Full Ota FIle .zip
- Open NFT
- select Tools
- Select Make HomeBrew From Full OTA FILES
- Select Payload.bin File
- Choose Folder To save Homebrew
- Make Homebrew
* HomeBrew Security update
- Root Phone
- Follow instruction How to update phone on Magisk forum
- after update don't restart and don't Pacth boot.img to other slot
- Open NFT - Tools -Dump Partition
- Select Profile Homebrew For your Device
- Set inactive Slot on Slot option (if active Slot 'a' then choose 'b' , if active Slot 'b' then choose 'a')
- dump partition

Thank you ? Now I can mod my Nokia 7.2 without worrying too much.

Nice work!

anyone have valid link to stock firmware? thank you in advance

pattiandy said:
anyone have valid link to stock firmware? thank you in advance
Click to expand...
Click to collapse
Click hikari calyx name in NFT to download firmware

I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.

lilmonkw said:
I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.
Click to expand...
Click to collapse
i put information in about button
for payload mode...it only for full rom OTA.. size about 1,5GB or more..
let me know what payload u use..
and what devices???
firmware download click on hikari name on NFT tools...
for 7.2 u need extract every zip in firmware and put it in one folder..
Flash using normal flash

lilmonkw said:
I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.
Click to expand...
Click to collapse
Which device did you flash? And didn't you understand that you need a full OTA to use the payload method?
Check if the device is in QdLoader 9008 mode, then you can still recover it. But if it is in some other mode, then the recovery needs disassembly.

sayaoks said:
i put information in about button
for payload mode...it only for full rom OTA.. size about 1,5GB or more..
let me know what payload u use..
and what devices???
firmware download click on hikari name on app...
for 7.2 u need extract every zip in firmware and put it in one folder..
Flash using normal flash
Click to expand...
Click to collapse
I missed that payload information, and it's my fault. My device is in the 9008 mode now. Nokia 7.2.
I did not use the full OTA, and then I pretty much broke things. The OTA I used was the one I pulled out after it automatically downloaded on my phone. The device had August security patched firmware (the only one on the hikari website) installed.
---------- Post added at 12:49 PM ---------- Previous post was at 12:47 PM ----------
singhnsk said:
Which device did you flash? And didn't you understand that you need a full OTA to use the payload method?
Check if the device is in QdLoader 9008 mode, then you can still recover it. But if it is in some other mode, then the recovery needs disassembly.
Click to expand...
Click to collapse
I messed up with flashing not full OTA, and it's my fault. My device is Nokia 7.2. It's in the QdLoader 9008 mode.

lilmonkw said:
I messed up with flashing not full OTA, and it's my fault. My device is Nokia 7.2. It's in the QdLoader 9008 mode.
Click to expand...
Click to collapse
From QDLoader, we should be able to fix it, but unfortunately, Nokia has not released a rawprogram and patch0.xml files. But you can likely use the one from Nokia X71 after slightly modifying it. Then flash abl and xbl using QFIL tool. Once you have a working bootloader (fastboot mode), you will be able to flash the stock ROM again.
I think @hikari_calyx will have a better idea about which files to use.

singhnsk said:
From QDLoader, we should be able to fix it, but unfortunately, Nokia has not released a rawprogram and patch0.xml files. But you can likely use the one from Nokia X71 after slightly modifying it. Then flash abl and xbl using QFIL tool. Once you have a working bootloader (fastboot mode), you will be able to flash the stock ROM again.
I think @hikari_calyx will have a better idea about which files to use.
Click to expand...
Click to collapse
What would I need to modify in those files? And is there a possibility of Nokia releasing rawprogram and patch0.xml for 7.2 ever?

"use Payload.bin" not support Python3 for Windows Store

[email protected] said:
"use Payload.bin" not support Python3 for Windows Store
Click to expand...
Click to collapse
u need install python 3.
and install protobuf "python install protobuf"
for payload flash
if your python use "python3 / py" for running python...
use latest v1.1.4 its support

On my 7.2 im trying to go back to stock from Lineage 16.0 (unofficial) so that some things will work again and im getting:
"Flash abort!! Phone Looked Bootloader" (not a typo)
"ALL TASK COMPLETE"

Talon Pro said:
On my 7.2 im trying to go back to stock from Lineage 16.0 (unofficial) so that some things will work again and im getting:
"Flash abort!! Phone Looked Bootloader" (not a typo)
"ALL TASK COMPLETE"
Click to expand...
Click to collapse
Hi, is your device critical unlocked? If not, please do it.
Code:
fastboot oem device-info

singhnsk said:
Hi, is your device critical unlocked? If not, please do it.
Code:
fastboot oem device-info
Click to expand...
Click to collapse
The bootloader is, how do you think i got the Lineage on it? I dont how to unlock anything else, this is all new to me on the Android side, im a Windows guy. I have TWRP on it, will that matter?
Nvm, i figured it out, got it unlocked.

It gets to "Flashing system.img to system_b" and aborts. Same thing happens if i switch to system_a.

Talon Pro said:
It gets to "Flashing system.img to system_b" and aborts. Same thing happens if i switch to system_a.
Click to expand...
Click to collapse
You unpacked the system, boot and vendor image to the same folder as well, right? And not to some other folder. The file exists in the same directory?

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