PREAMBLE
My name was djolivier in former times and our little Wildfire S has NOT died yet, just so you know!
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
You can alwayss get the latest build from here.
SCREENSHOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 2.8.0.0:
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
P.S.: Our device does not support MTP as of yet.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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
CHANGELOG for 2.7.0.0
- Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
- Allow sideloading from /tmp on encrypted devices
- Check for a crypto footer before asking for a password to prevent user confusion
- Additional checks for validity to auto generated backup names
- Text wrap in the console output
- Proper caps lock support in the keyboard
- Mouse support via USB OTG for devices with a broken digitizer
- Improve scanning of storage locations for OpenRecoveryScript
- Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
- Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
- Update SuperSU to 1.93 and improve installation process
- Added selinux contexts restoration to fix permissions
- Load RTC offset on Qualcomm devices to fix the date/time in recovery
- USB Mass Storage fixes Add SELinux support checking
- Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
- Add 4.4 decrypt support
- Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
- Various SELinux fixes and bug fixes
CREDITs
- My awesome team (izi501, Kevinjoa, thehacka1, Mazer.One and WinSuk)
- benjamingwynn
- modpunk
- WoeFullDerelict
- Jdevs
- niks255 and the OWL team
- alquez
XDA:DevDB Information
TWRP for HTC Wildfire S, Tool/Utility for the HTC Wildfire S
Contributors
Olivier
Version Information
Status: Stable
Created 2014-09-28
Last Updated 2014-09-28
how to install ?
Flash it using fastboot, adb or a terminal emulator. I prefer fastboot:
Code:
fastboot flash recovery recovery.img
Gesendet von meinem Xperia S mit Tapatalk
If anyone wants to use terminal emulator
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Assuming the img file is in the root of the sdcard
And are there any bugs @Olivier?
There are no bugs, at least I couldn't find any. However like on TWRP 2.3.x.x, you cannot flash ROMs with old/deprecated update-binaries. But that's not a bug. Also, this recovery is capable of flashing KitKat ROMs.
So we are getting KitKat yay
ZANKRUT.DOSHI said:
So we are getting KitKat yay
Click to expand...
Click to collapse
This only means that we have a way to flash Kitkat, the matter of will we get it is upto to the people working on it
Exactly and development doesn't progress fast since all my team mates have other devices to work on (I have Xperia S, Xperia L, my Lenovo tablet and of course the WFS) and apart from that we have real lifes (exams...) so I don't want to promise anything. Though CM10.2/11 is certainly possible.
Gesendet von meinem Xperia S mit Tapatalk
Olivier said:
Exactly and development doesn't progress fast since all my team mates have other devices to work on (I have Xperia S, Xperia L, my Lenovo tablet and of course the WFS) and apart from that we have real lifes (exams...) so I don't want to promise anything. Though CM10.2/11 is certainly possible.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
I cannot wait for kitkat
anyhoo keep up the brilliant work guys.
Sent from my HTC Wildfire S using xda app-developers app
Cool, this is more motivation for me to try and port KitKat ROMs over for this device! But then I don't have the time...
Sent from my GT-I9305 using Tapatalk
Guys so i flashed this recovery and its pretty damn neat!
i used to have CWM 5.0.2.8 before , ok firstly im a noob when it comes to all this recovery stuff in detail,
so i noticed that there isnt a way to partition the sd card like in the CWM recovery, ordered a 16GB class 10 , awaiting the delivery , cant wait to partition , any ideas?
Zeehan said:
Guys so i flashed this recovery and its pretty damn neat!
i used to have CWM 5.0.2.8 before , ok firstly im a noob when it comes to all this recovery stuff in detail,
so i noticed that there isnt a way to partition the sd card like in the CWM recovery, ordered a 16GB class 10 , awaiting the delivery , cant wait to partition , any ideas?
Click to expand...
Click to collapse
I'm using TWRP 2.7 on nexusOne. But it should be same about partitionning.
Go To :
Advanced
Partition SD Card
Then you can select the size of each partition (SD-EXT and SWAP)
And also the filesystem (EXT3/4)
A little question,does it work on WFS 2012?
EDIT:Working on WFS 2012
Sent from my HTC Wildfire S using my WFSY10.1
Why can't it install any of INT2EXT script?
AmirNajjar said:
Why can't it install any of INT2EXT script?
Click to expand...
Click to collapse
What's the problem/error?
@Olivier i am a huge fan of ur work and wanted ur help in a little venture im making.....
1. I'd like to Port ur CM10 rom over to the HTC Legend..... and wanted to know if u would give me permission to do so..?
2. second, id like to also build a recovery from source for the htc legend and would like to know if u could point me in the right direction as to where i could start from....
Olivier said:
What's the problem/error?
Click to expand...
Click to collapse
Don't know exactly as I don't remember,but it almost doesn't flash a thing!but kk and kk's gapps
I tried all int2ext scripts and also tried tweakzv6 which perfectly works on your cwm6.
BTW,your cwm6 can't format /sd-ext but can mount it,while it is formattable in every other recovery,any idea?
Sent from my WFS 2012 using CyanogenMod 11.0
@AmirNajjar
NEW CWM and TWRP can't format sd-ext yet, we need to add some basic selinux policy configuration in our sourcecode and then it should work.
Kevinjoa said:
@AmirNajjar
NEW CWM and TWRP can't format sd-ext yet, we need to add some basic selinux policy configuration in our sourcecode and then it should work.
Click to expand...
Click to collapse
But TWRP can format /sd-ext but can't install any additional script like int2ext or tweakzv6 for example
Sent from my Wildfire S A510e using xda app-developers app
Updated to TWRP 2.7.1.0, check the OP.
Related
This is my very own personally maintained custom ROM for the Nexus 10 (manta) called Lollipopalooza!! It is an AOSP (Android Open Source Project) 5.x based ROM with a simple aim... add a few useful features to AOSP without deviating too much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This will be a spin-off of my previous Nexus 10 ROM ThunderKat, but from scratch and obviously based on Android 5.x.
I don't expect this to compete with the big boys (CyanogenMod, AOKP, Paranoid Android and the like) and this ROM will have a considerably limited feature-set compared to them. If you want a lot of customisations and configurations, they are definitely the way to go.
Please note that since this is a fully de-odexed ROM, it will take a while to boot up the first time. Please follow the installation instructions carefully.
IMPORTANT: Since I no longer own this device, I have not tested this. In my opinion it should work just fine since I am using the same code-base for my Nexus 9 builds, but if you are not sure, wait for feedback from others who are brave enough to take the plunge.
Due to my limited availability, I will now no longer support builds older than 2015/05/23
Changelog:
1. Update to Android AOSP 5.1.1_r14 (LMY48M)
2. Includes stagefright exploit fixes
3. Update to Layers Type 3
4. Multi-toggle Location QuickSettings tile (toggles between the different location modes - Off -> Sensors Only -> Battery Saving -> High Accuracy)
Layers/RRO Themes Info:
1. Join the BitSyko Google+ Community for the latest information and themes
2. Download the Layers Manager app to install/uninstall/preview Layers/RRO themes
3. Visit this XDA thread for a comprehensive list of Layers/RRO themes
4. Send a positive shoutout to the Layers Team for their awesome work
Older Changelogs:
2015/05/23
1. Update to Android AOSP 5.1.1_r3 (LMY48B)
2. Updated proprietary files and binaries from stock LMY47V ROM
3. Layers/RRO 2.1 updates
4. A lot of Layers/RRO legacy code cleanup
5. Enhanced AOSP Launcher3 from OptiPop with features like customisable grid size, hide/show search bar & materialised settings
6. Updated ARM Google Apps Pack as of 2015/05/23
PLEASE FLASH THE Lollipopalooza_aosp_manta-LMY48B-20150523-BuildPropFix.zip IMMEDIATELY AFTER FLASHING THIS ROM. THIS WILL ONLY BE REQUIRED FOR THIS BUILD.
2015/04/24
1. Prefer Google WebView over AOSP WebView because AOSP WebView is older, but automatically fallback to AOSP WebView if Google WebView is not installed.
2015/04/23
1. Updated to AOSP Android 5.1.1_r1 LMY47V
2. Added Layers/RRO 2.1 (backwards compatible with Type 1 & Type 2 Layer/RRO themes) - All credits to the Layers Team
3. ART is the new kid on the block. Remove Dalvik VM
4. Disabled a lot of framework debugging
5. Speed up animations
6. Disabled Google OTA services
7. Tune ART flags to optimize everything (this makes first boot and app installs slower, dex files are large, but performance improvements are noticeable) [MAKE SURE YOU WIPE CACHE/DALVIK-CACHE]
8. Miscellaneous optimisations and fixes
10. Updated tzdata to the latest timezone data 2015c from IANA.
11. Updated ARM Google Apps Pack
2015/03/17
1. Updated to AOSP Android 5.1.0_r1 LMY47D
2. Show "Installing application x of y" on first boot
3. FAB (floating action button) for clear recents
2014/12/09
1. Updated to AOSP Android 5.0.1_r1 LRX22C
2. Code cleanup and stability fixes for existing features
3. Latest vold and filesystem support updates from CyanogenMod
4. SELinux policy updates
5. Update Google Apps pack
6. Move back to block-based update zip which is a million times faster to flash.
7. Enabled bluetooth LE (low-energy)
2014/11/28
1. Updated to AOSP Android 5.0.0_r7 LRX21V
2. Movable navigation bar buttons (Settings > Display > Navigation Bar Position)
3. Volume rocker wake (Settings > Display > Volume rocker wake)
4. Volume rocker cursor control (Settings > Language & input > Volume key cursor control)
5. Native status bar battery percentage display (Settings > Display > Battery percentage)
6. Per-app keyguard/lockscreen notification controls (Settings > Sound & notifications > App notification)
7. Fixes and UX updates for clear-all recents
8. Android volume daemon and file system automount support updates (Added groundwork for NTFS, exFAT & EXT4 support)
9. OTG automount for NTFS partitions with R/W access
10. Support for TWRP recovery (updater script validates flounder or volantis)
11. Updated Google Apps Pack
2014/11/16
1. Updated to AOSP Android 5.0.0_r6 LRX21T
2. Enabled AppOps (Settings > Apps > AppOps)
3. Advanced Power Menu (Shutdown, Advanced Reboot, Users, Sound, Airplane Mode, Settings, Lockdown)
4. Back button long-press kill app (Enable via Settings > Developer options > Kill app back button)
5. Custom device hostname (Change via Settings > Developer options > Device hostname)
6. Enabled Ambient display (Settings > Display > Ambient display)
7. Clear all recents (Credit 0xD34D)
8. Root-friendly stock kernel [IMPORTANT! This ROM is not rooted. In built root support will come soon. For now, please flash SuperSU or Superuser separately]
9. Tweaked ART flags
10. Proprietary audio configs from stock ROM
11. User triggered media scanner (Settings > Storage)
12. OTG USB storage automount to /storage/usbdisk with full R/W access (VFAT/FAT32 only) [IMPORTANT! This depends on the modified ramdisk included with this ROM boot image. You may lose this feature if you another boot image]
13. Updated MAC permissions (SELinux stuff)
14. Miscellaneous framework fixes and tweaks
15. Enabled Google Location Services
16. Fixed Google back/restore.
17. Added busybox
18. Enabled translucent navigation and status bars
19. Google Apps Pack zip with latest updated apps
Download:
Lollipopalooza_aosp_manta-LMY48M-20150918.zip
GoogleAppsPackARM-5.1.x-20150423.zip
Source:
GitHub
Manifest
Requirements:
1. Nexus 10 with Unlocked bootloader
2. Latest bootloader
3. Custom recovery like TWRP 2.8.6.0+ or CWM 6.0.4.7+
Instructions:
1. Wipe data/factory reset if you are moving from any ROM other than a previous version of Lollipopalooza
2. Wipe cache/dalvik cache for every update
3. Flash the ROM using a custom recovery
4. [Optional] Flash SuperSU 2.46+ using a custom recovery if you wish to root the device
4. [Optional] Flash Google Apps Pack using a custom recovery. You can choose to install any other Android 5.0 compliant Google Apps Pack
Disclaimer
Lollipops are fun, but too much is not good for your health. If you chose to enjoy the Lollipops in this thread, remember that you do so at your own risk. I am not responsible for cavities, stomach aches or any other ailments your device may have if you use this ROM. I do test these Lollipops prior to releasing them, but I make no guarantees.
Support this project:
If you like my work, buy me a beer so that I can pass time while my laptop churns out builds...
Paypal
Google Wallet (Send Money to craigacgomez[at]gmail[dot]com)
Credits:
Google, Samsung, ARM, Chainfire, 0xD34D, CyanogenMod tea,, SlimRoms team, rascarlo, Chroma team, BitSyko team, AndroidFileHost
ive been lookin everywhere for some gapps that work with this device haha, thanks!
Great to see you in here Craig! Loved the Roms you did for the transformer. Guess its time to go install a custom recovery and try this out!
I am rooted and my bootloader is unlocked. I made a mistake and formatted my system img. Is it possible to flash this via adb?
Any word on getting OTG/CIFS working?
Also, the "DRM Libraries" .. these, I assume - allow things like Play Movies and Hulu Plus to work? I'm actually interested in TRADING OFF those features with the ability to get HDMI out without protection on the signal. Thoughts on that?
Thanks for the hard work already!
momulah said:
I am rooted and my bootloader is unlocked. I made a mistake and formatted my system img. Is it possible to flash this via adb?
Click to expand...
Click to collapse
Reboot into TWRP recovery, use adb to push it to /sdcard and flash it... it will work even if your system partition is formatted!
craigacgomez said:
Reboot into TWRP recovery, use adb to push it to /sdcard and flash it... it will work even if your system partition is formatted!
Click to expand...
Click to collapse
what is the adb command to push it to my sd card? I just finished the download!!
momulah said:
what is the adb command to push it to my sd card? I just finished the download!!
Click to expand...
Click to collapse
adb push rom.zip /sdcard/
or
adb push rom.zip /data/media/0/
darkuni said:
Any word on getting OTG/CIFS working?
Also, the "DRM Libraries" .. these, I assume - allow things like Play Movies and Hulu Plus to work? I'm actually interested in TRADING OFF those features with the ability to get HDMI out without protection on the signal. Thoughts on that?
Thanks for the hard work already!
Click to expand...
Click to collapse
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!
craigacgomez said:
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!
Click to expand...
Click to collapse
Thanks man I pushed the rom to my sd card and was able to flash it. Now Is there anything that doesn't not work that works in the stock rom?
May'be its his new kernel! Anyone try gong back to his stock kernel to see if it brings usb back.
craigacgomez said:
The DRM libs are for Hulu & apps which use the Widevine DRM... Are you referring to HDCP? I'm not sure if this affects that... I haven't done any much HDMI related stuff with Android yet, but I'll check it out...
I will work on OTG and CIFS soon!!
Click to expand...
Click to collapse
Yeah, essentially, I want to be able to RECORD the output of the tablet with an HD capture system via HDMI. Completely legal reasons (which is why I don't care if any movies or TV work). But, unfortunately, the HDMI out (no matter WHAT) seems to be encrypted with HDCP.
I had it working on my TF101 - I had to use a little software trick on the PC, but it worked. Not anymore
Thanks, flashed and running fine... forgot to wipe data the first time and wouldn't boot
momulah said:
Thanks man I pushed the rom to my sd card and was able to flash it. Now Is there anything that doesn't not work that works in the stock rom?
Click to expand...
Click to collapse
I've tested everything except the DRM stuff... I don't use any DRM apps so I'm not sure... maybe someone who uses an app like Hulu Plus can let me know!
Wow...just finished installing...very nice. Absolutely love the aosp browser, beats the living crap outta chrome. Got the old news app and widget back too!
Just got my Nexus 10 yesterday and this is my first flash. Working well. Thanks!
I have preliminary OTG support done... need to fix permissions and get it to show up in Setting -> Storage
How do I enable the settings pull down? I liked that feature a lot. Being able to have notifications on left and settings on right.
Sent from my SAMSUNG-SGH-I727 using xda premium
momulah said:
How do I enable the settings pull down? I liked that feature a lot. Being able to have notifications on left and settings on right.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Flash ROM + GApps, sign in and you will see them
Is there any way to go back to the old tablet style interface? Not digging the phone style with bars on the top and bottom of the screen.
Added custom kernel with a few extra goodies... see OP for details!!!
{
"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"
}
------------------------------------- UPDATE 2 -------------------------------------
hey guys this seems to be harder than I thought, but till now I manged to create a solid code to base my work on
and I'm thinking of "HOX-BOX" as a name for my baby, what do you think?
Done since Update 1
- ADDED: dynamic shell (context) menu for faster flashing .. including the choice to enable/disable it
- ADDED: an advanced detection system, far better then the simple "devices" known command, this tool will be able to detect a 100% accurate state of the device including (adb/mtp - mass storage/camera p2p - fastboot - connected with no drivers - current drivers version - the path for the mass storage)
This toke me 2 days of hard work and it's based on the detection of system Drivers/Vendor ID status, so it can't go wrong
- ADDED: advanced model detection command before flashing to prevent wrong flashes
- IMPROVED: Interface and logging
- INCLUDED: HTC Drivers 32 and 64-bit adb/fastboot
- INCLUDED: USBDeview (helps with retrieving HTC's vendor IDs and Product IDs)
- IMPROVED: data size by removing unnecessary platform tools
Still Struggling with
- Live Stats
Normal stats are OK and ready but keeping the CPU stats alive is making the software unstable, I'm still working on this
- Drag n' Drop handlers
- Flashing a ROM through PC
haven't really gave it the time yet, i'll be looking into it as soon as I stabilize other current commands.
------------------------------------- UPDATE 1 -------------------------------------
The Tool Is now under construction
I Finished the following so far
- UI main Menu
- INCLUDED: platform-tools_r16.0.1-windows
- INCLUDED: 7z.exe and 7z.dll (to flash boot.img without user interference)
- One Click Flasher for kernels and recoveries is now ready (CWM, TWRP and BOOT)
- Logging system that creates user-friendly (humand readable) logs and Advanced Log that lists command and their returns
Now Working on
- Live stats about battery and processor
- a 100% PC based flash code you just plug in your HOX, select a ROM , and the tool will transfer it to the SD, flash it in recovery, erase cache and delvik, do selected wipes and flash the boot.img
this is a tricky process but I have all the info I need , and now I'm on it
------------------------------------- OP -------------------------------------
Hey Guys
Lately I've been thinking of Creating a Tool that works with PC to make common tasks easier
I have a good experience in programming/ui/animation/batches
The Tool is basically an AIO TOOLBOX for our One X (for now)
I have some Ideas , but I need some feedback before Starting
it will be User-Friendly.. Noob proof and really well themed
WHAT I HAVE IN MIND
• basic functions
- mode detection
- get device props (CID, Mainver, Current ROM, Free Space, Model and so)
• Includes
- fastboot environment
- latest drivers
- SU flashables
- recovery Images
• Commands
- help connecting your device by installing the drivers automatically, detect the current mode (and enable/disable options based on the mode)
- help with the bootloader unlock
- flash boot.img (even if not extracted) you can just select the ROM zip and the tool will extract the boot and flash it automatically
- flash recoveries
- push (transfer) files using adb (even if stuck in recovery) without writing any code (WYSIWYG), just choose files and click push
WHAT I NEED FROM YOU
(Done!) 1. should I do this? .... does it worth the time, or there is similar tools
2. if you think I should do it, should it have more features (than the mentioned above) , and please name them with details if possible
3. suggest a name for the tool
I have the ability to integrate any fastboot/adb command you can think of into the UI, with a nice animated design
but I can't do miracles such as unlocking the phone without the help of (HTCdev) or S-OFF your device, so please don't request such things
Re: I need your thoughts - The Ultimate HOX ToolBox
1. Definitely you should do it! (although there is toolkit which can unlock bootloader and flash a recovery already) More advanced features would be welcome!
2. A few things:
Maybe fetch a RUU automatically based on main version from
BugsyLawson's server
or
ruu.androidfiles.org and automatically install it.
A tool that fetches a firmware zip based on cid and flashes it.
Adb shell
Boot repacker
3. NoobKit-9000
Sent from my One X
TToivanen said:
1. Definitely you should do it! (although there is toolkit which can unlock bootloader and flash a recovery already) More advanced features would be welcome!
Click to expand...
Click to collapse
Glad you feel this way
TToivanen said:
2. A few things:
Maybe fetch a RUU automatically based on main version from
BugsyLawson's server
or
ruu.androidfiles.org and automatically install it.
A tool that fetches a firmware zip based on cid and flashes it.
Adb shell
Boot repacker
Click to expand...
Click to collapse
- Communicating with servers and downloading is a tricky thing, they would have to work with me for this
if I get enough help from them , I Would deferentially do it.
but at the very least I will include a guide that will tell you the exact name of the RUU/Firmware that needs to be downloaded (maybe even search for it)
- adb shell .... Will Do :good:
- boot Repacker ... I have to do some more reading about this, but I think I can do it :good:
TToivanen said:
3. NoobKit-9000
Click to expand...
Click to collapse
:laugh:
Re: I need your thoughts - The Ultimate HOX ToolBox
Like the idea of a nice clean tool.
I haven't felt the need to root or flash yet, but as there is no s-off yet the process seems slightly more involved than it was for my old Desire, so it is a bit off putting. If there are tools that can help - will use them.
I know that sounds noobish - and it is
Sent from my HTC One X using xda app-developers app
Re: I need your thoughts - The Ultimate HOX ToolBox
One click kernel flasher would be nice lol
A
Htc One X Viper 3.4.2
Re: I need your thoughts - The Ultimate HOX ToolBox
There's always one click flash tools they do a lot of what u said flashing, a useful tool would be to indicate where memory is used these devices are limited on memory biggest downfall on htcs part Imo
Sent from my HTC One X using xda premium
Hey mate,
Do it !! Competition is good, Hasoon already has a toolkit but as mentioned choice is brilliant ! So get on it and goodluck, can't wait to see your final program .
PS - Check your banner image !! You missed the "U". It is "Your ltimate tool flasher".
Wilks3y said:
Hey mate,
Do it !! Competition is good, Hasoon already has a toolkit but as mentioned choice is brilliant ! So get on it and goodluck, can't wait to see your final program .
Click to expand...
Click to collapse
Thank You!
and Yes I do like clean Competition , and giving people choices.
Wilks3y said:
PS - Check your banner image !! You missed the "U". It is "Your ltimate tool flasher".
Click to expand...
Click to collapse
OOPS!
-"Live stats" would be great, showing instant info about cpu cores in use and freq, battery % and mA flow, ram usage, live logcat + kmesg, gpu freq...
-A good file explorer that allows to edit files "on the fly"
What do you think? want more ideas?
Juanig said:
-"Live stats" would be great, showing instant info about cpu cores in use and freq, battery % and mA flow, ram usage, live logcat + kmesg, gpu freq...
-A good file explorer that allows to edit files "on the fly"
Click to expand...
Click to collapse
I Will definitely Try to include every feature I can with time
I have a lot of reading to do, but if it is possible then I'll do it, even if not in the first release, I WILL try to include everything as future versions build up
Juanig said:
What do you think? want more ideas?
Click to expand...
Click to collapse
Thank you, and if you have any other useful ideas, why not
Re: I need your thoughts - The Ultimate HOX ToolBox
Great idea, I initially used a toolkit when first flashing mine but it's nice to know what your actually doing to your phone and I have since learnt all the commands. So my request is to somehow show the user what your automating so they understand what's going on with their phone. Maybe like a log/command type window that can be shown or hidden for those that want to see what's happening.
Cheers
Sent from my HTC One X
Re: I need your thoughts - The Ultimate HOX ToolBox
Yes agree with herbie u wanted to use a toolkit but would have also benefitted from knowing the commands as something went wrong during the flash with the tool kit
Htc One X Viper 3.4.2
Re: I need your thoughts - The Ultimate HOX ToolBox
Great idea
Thank you, I must have this in my tool
Sent from my HTC One X
ADDED UPDATE 1 TO THE OP
a beta release should be available soon :fingers-crossed:
Maher88 said:
ADDED UPDATE 1 TO THE OP
a beta release should be available soon :fingers-crossed:
Click to expand...
Click to collapse
cant wait!
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
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD
will it be fine to flash disk over e975 unlocked using freegee?
Yesssss!! you did it at last. Thanks @JustinXu.
yeah
thanks bro :crying:
flashed it for e975... i don't know t the twrp does not recognise/see the flash memory of my devise. i tried to mount it but nothing happen.
i'm doing something wrong or the 2.8.0.1 version have a bug like this
anyway at first i want to thank you
igli83 said:
flashed it for e975... i don't know t the twrp does not recognise/see the flash memory of my devise. i tried to mount it but nothing happen.
i'm doing something wrong or the 2.8.0.1 version have a bug like this
anyway at first i want to thank you
Click to expand...
Click to collapse
+1
No any drive for mount.
it seems something wrong, i will check it later.
i have deleted the file on google drive. stop downloading guys.
guys, i just uploaded a gee TWRP build, sdcard seems work. give it a try and tell me the result.
JustinXu said:
guys, i just uploaded a gee TWRP build, sdcard seems work. give it a try and tell me the result.
Click to expand...
Click to collapse
Seems to work now. Thank you man. Really a good work
Anyway the version is 2.8.0.0 not 2.8.0.1
Works great on art rom with solid kernel
igli83 said:
Seems to work now. Thank you man. Really a good work
Anyway the version is 2.8.0.0 not 2.8.0.1
Click to expand...
Click to collapse
i found it too. i build it with the lastest sources, and i don't know why it is not 2.8.0.1
Hi i ve a problem with an lg optimus g e975 of my friend...i've flashed twrp 2.8.0.0 from download page...but now i cant flash anything!!trying roms , recovery...
{
"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"
}
Inviato dal mio LG-D802 con Tapatalk
enr88 said:
Hi i ve a problem with an lg optimus g e975 of my friend...i've flashed twrp 2.8.0.0 from download page...but now i cant flash anything!!trying roms , recovery...
Inviato dal mio LG-D802 con Tapatalk
Click to expand...
Click to collapse
Try using the /data/media/0/ directory rather than /sdcard to select the zips.
Sent from my LG Optimus G using Tapatalk
Leavard said:
Try using the /data/media/0/ directory rather than /sdcard to select the zips.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
I flash twrp to and I don"t find the folder 0 in data / media / ?
Why, when I select wipe cache and wipe dalvik cache from recovery (twrp) , it's delet all data from sdcard?
same thing happened to me! reverted to older one! keep away from this version unless some one fix it!
also you cant make backups, someone said they cant install kit kat roms (or any at all), mtp function doesnt work correct! i can only copy from the phone and NOT into the phone!
Please give me link with older twrp!!
Thanks so much.
Thread closed by OP request.
{
"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?