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
Related
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.
{
"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 x64All 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-mda89dthat 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 OptionsQ: 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 toolQt - An awesome cross-platform IDEVmware - 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
{
"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"
}
Credits: @duraaraa (great guy from Xda), @inside!out, @VirusPlus, HRT Chinese team, Maximo76
1. Download this file
Ver. 1.6 ---------------------------> DOWNLOAD
2. Extract in a directory on your PC Rayglobe_Knife.exe
3. Launch this exe
XDA:DevDB Information
[Tool] Rayglobe Mate 8 Italian Knife, Tool/Utility for the Huawei Mate 8
Contributors
acer73, Inside!out, Virusplus, HRT Chinese Team, Maximo76
Source Code: http://forum.hdblog.it/index.php?/topic/49051-italian-knife-tool-by-hdblogit-huawei-mate-8/
Version Information
Status: Alpha
Created 2016-01-17
Last Updated 2016-02-06
Reserved
HELP
************************************************** ***********************************************
--------- User Manual HUAWEI MATE 8 Italian knife by Raimondo Martire (aka acer73) V1. 2 ----------
*
*
================================================== ========================================
**************The following points can be activated only with ADB and FASTBOOT active
**
*****0: FIRST START
*****1: BOOTLOADER
*****2: Recovery
*****3: Root
*****4: gapps
*****5: debrand
6: UNBRICK
7: EXTRA
8: Download EMUI
9: Thread Huawei Mate 8 on HDBlog.it
**
*****Q: Donate and Thanks? HELP (hdblog.it) X: CLOSE
================================================== ========================================
*
Before you start remember stop/freeze the antivirus because it may interfere with the download
*
================================================== ========================================
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
================================================== ========================================
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
================================================== ========================================
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
================================================== ========================================
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
================================================== ========================================
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
================================================== ========================================
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
================================================== ========================================
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
================================================== ========================================
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
================================================== ========================================
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
================================================== ========================================
*
MENU 9: Thread Huawei Mate 8 on HDBlog.it
*
Italian forum when I've published first my work
*
================================================== ========================================
*
MENU D: Donate
*
This tool and 'released for purely private. Any commercial use without permission
the author will be prosecuted according to law.
If you want to keep this tool active currency the possibility to donate to the purchase of space
Web and to give me comfort with a glass of good Italian wine
*
================================================== ========================================
*
Menu?: Help
*
To choose the menu 'for help and' exclusively in Italian
*
================================================== ========================================
*
MENU X: Close
*
Closes this tool
Changelog
1.5
Smaller exe
Rayglobe Twrp recovery Multilanguage
1.3
New Twrp multilanguage
Remake Extra section with 2 new stuff
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
You are the hero we need, we just didn't know it! Massive thanks for your work mate.
lorenzw said:
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
Click to expand...
Click to collapse
You have driver problem. Have you used driver that I punt in first start command?
Extensive help please
Just looking for some more detailed help, ill post the issues I have with understanding.
Sorry if some things I ask are basic or stupid, I have never had an android phone and haven't had the opportunity to check your tool out with a phone yet.
acer73 said:
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
Click to expand...
Click to collapse
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
acer73 said:
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
Click to expand...
Click to collapse
So whats this first menu do?
Link me to these two places?
acer73 said:
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
Click to expand...
Click to collapse
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
acer73 said:
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
Click to expand...
Click to collapse
How do I get boot decrypt?
acer73 said:
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
Click to expand...
Click to collapse
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
acer73 said:
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
Click to expand...
Click to collapse
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
acer73 said:
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
Click to expand...
Click to collapse
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
acer73 said:
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
Click to expand...
Click to collapse
So this menu gives the user the option to boot into different modes?
acer73 said:
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
Click to expand...
Click to collapse
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
So whats this first menu do?
Link me to these two places?
Install correct adb driver. remember to activate usb debug in developer menu
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
Twrp in a custom recovery to flash unsigned zip
How do I get boot decrypt?
In menu 3
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
Micro GApps package for chinese rom
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
Yes european rom work on chinese model
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
So this menu gives the user the option to boot into different modes?
You can boot in recovery or fastboot mode. Some command can be made in recovery mode other one in bootloader mode
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
Yes you can flash from chinese to european and return to chinese
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
hisuite actually has the USB drivers included...
davoidd said:
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
Click to expand...
Click to collapse
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Can I use your tools for Factory Reset Protection (FRP) rest?
VirusPlus said:
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Click to expand...
Click to collapse
Sorry mate. I created this thread as you can see with right credits in the first time and put your name also in contributors. I put your name in contributors in this way xda system send you an email and you can verify work just because you have choose to not receive Pm so no possibility to contact you. I don't think only to give credit in OP and tool . I'll upload new version with credit in OP according your right desire and I've modified first image for better visibility. :good:
copysat said:
Can I use your tools for Factory Reset Protection (FRP) rest?
Click to expand...
Click to collapse
No, I don't test for it. Use this option only in an emergence fase
jbmc83 said:
hisuite actually has the USB drivers included...
Click to expand...
Click to collapse
Yes right
lorenzw said:
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Click to expand...
Click to collapse
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
acer73 said:
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
Click to expand...
Click to collapse
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
lorenzw said:
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
Click to expand...
Click to collapse
I'll change tool to ver 1.0.0.1 try with this . I'm sure that now you can flash without problem
https://www.androidfilehost.com/?fid=24369303960690339
happy to report that ur tool saved me a lot of work @acer73 im now on L29 firmware with decrypted boot, twrp and supersu installed, everything running smoothly. so far no issues with notifications, but still watching out for this...
Sent from my Huawei Mate 8 using Tapatalk
{
"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"
}
Multirom v3 , DualBoot Patcher
tutorial also changed please read again
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* dead phones , car explosion , your phone explosion
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tool
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction :
I'm proud to present you the first dual boot project for the Qualcomm-based Samsung Galaxy S3 Neo and Samsung Galaxy Grand 2 and Galaxy S5 mini ! This will allow any ROMs and as many as you want to be installed at the same time. It works by patching the secondary's ROM installation scripts and boot image to load the ROM files from an alternate location (/system/dual, /cache/dual, and /data/dual). Because of the way this is implemented, no changes to the primary ROM are necessary
About :
Hello guys, as some of you guys know and some of you dont I was working on dual boot and dual boot v1 beta, which was released in our great Telegram group, but not in XDA, because of some reasons and rude MAXSIMUS96 that doesn't have any respect to a great development. But anyway I dont care
Lets Start
Well here's v3 + dbtools removed
patched files are flashable with recovery now
added full s3 neo support :angel:
added full grand 2 support :angel:
added full s5 mini support :angel:
more
Now you can have unlimited ROMs!
Tested with 4 CMROMs + 2 stock ROMs
Here's the topic of the base tool used: Dual Boot Patcher
Here
Make sure you leave a like on the great post of base tool I used here
What is Dual Boot or Multiboot?
DualBooting or multi Booting means having 2 or more ROMs at same time on the phone and choose between what you want to boot on next reboot
Why i need this? Is it even useful???
Yes it is! You can fix offline charging on some ROMs like CM12.1, you can have stock battery life, motion beauty, CM12.1's and CM11's performence at the same time without flashing any of them. Just one click from changing to the ROM you like
Whoa that sounds awesomeeee! is it difficult to install??
In v1 yes, but now on v1.5 i added dbtools (DualBootTools) that make most of things automated and even easier for noobs
now v2 things got even easier full s3 neo support
Any ScreenShots !?
see post #3 attachments
I want to see how it is ! is it possible , any videos ?? !?
see post #3 post
First Things first ! Go and make Backup of your files
Requirements :
an S3 NEO
root access of course
busybox if you are on stock ROM
recovery (twrp 3.0.0 is the best)
brain (the most important)
time and being relaxed
downloaded files
installation tree:
download and preparing files
setting kernel
patching the ROM
flashing
switching ROM
updating ramdisk
extras...
done enjoying
Explaining the tools
First: dbtools (removed due v2)
DualBootPatcher:
the great app mentiond above that made dualbooting possible
installation :
Now we know all about the tools,so it's time to use our brain
Step 1
download and install DualbootPatcher app
if you are in motion rom do this
if you are on motion rom install Motion fix zip at downloads section . it will change device codename back to s3ve3g
Step 2
Open the app
Slide the menu and go to ROMs
It will request for root access
Allow the root access
and a message will ask about to set the kernel
Select "set now" and after it said kernel set now
Step 3
reboot your device
Now after device is turned on
Go to the app and navigate "Patch Zip File" from the menu
and tap that + button select zip of ROM you want to patch
A window will come up and if you see in "your device selected by default" you done everything right.
then:
If you are CMuser ( means you have a cm12.1 , cm11 or ... on your primary rom)
and want to install another cyanogeonmod rom (cm11 , cm12.1 ...)
Select the partition configuration as "Secondary"
If you are trying to install another ROM that has a huge system
Select partiton configuration as "data slot" and select an ID for the ROM
better to be a number
(It will be installed on data partition this means it will use the device internal storage space )
and select continue and set where to place patched file .
you can add more files to patch there .
and after you are ready to patch the files tap that tick button in action bar
to start patching
Step 4
After you patched the zip ROM go ahead and navigate to ROMs from the menu
select button down corner and select patched zip you patched
and then select keep location (or if you want you can change the location ) and add more patched zips or tap the up corner tick to start install
note : if any thing wrong happend PM me on telegram and send me multiboot.log in internal storage.
Step 5
after ROM is installed
it should be selected the installed rom .
tap and switch to primary rom
now use three dot on side of primary and select update ram disk
and then select reboot now
now after device rebooted go back to the app navigate to roms
now use three dot on side of new ROM you installed and select update ram disk
after it said done
select the rom you installed . ( tap on the icon of it or name )
( if you saw a message about checksum select continue )
reboot the device and see the magic !!!!
your new ROM is booting !!!!
Cool, let's stop enjoying and continue
Step 6
now after your new ROM booted
take your time to setup the device
and go and install dualboot patcher app again
now open the app
Go to ROMs and allow root access and
now use three dot menu in side of primary ROM and select update ramdisk
now use three dot in side of new ROM and select update ramdisk
and reboot
Step 7
now ENJOY your dual booted phone
for now on you just need to select the ROM and boot into it
it doesnt need updating ramdisk any more.
now go to the browser and navigate to this topic and leave a thanks
it helps to keep up the work
How to flash a kernel gapps, camera fix, etc.?
Just patch the file to same partition configuration and flash with app
or patch it with recovery tools and flash
How to flash a kernel gapps, camera fix, etc. on primary rom ?
Just patch the file to primary configuration and flash with app
or patch it with recovery tools and flash
How to boot into other rom if you have boot loop with the current rom ?
boot into recovery twrp 3 and select images , navigate to /sdcard/multiboot/ and you see your ROMS listed in folder , like primary , dual , etc .... open the folder of ROM you desire to boot and flash boot.img to boot partition and reboot the phone
How to Wipe the roms ?
go to rom options in dualboot app select wipe rom and tick all of them and done .
or use the dualbootpatcher utility
How to use dualbootpatcher utility ?
flash in the recovery and BOOOOM !
Thanks & credits
It's all done now, thanks for reading carefully
Please at least leave a THANKS to the topic, it make me feel better and work harder on v2 for our device.
I can't receive any donation due to my country. It will be really nice if you send me donations with google gift cards
credits : DualBootPatcher Developer : @chenxiaolong
@LGaljo for his great help about fixing grammar mistakes and thanks to @Swp1996 for testing on grand 2 and thanks to @sasukesama for testing and helping with s5 mini and thanks to @ziad311 for testing v2 & thanks too @German Developer for video tutorial
hitting thanks button isn't that hard guys
Version Information
note SEANDROID ENFORCING is not a bug it's needed so please don't try to edit the work without permission or try to fix SEANDROID ENFORCING!!!!
What is working and what is not working on the ROMs?
Everything works great
Only bug is about CM11 :
Files created by CM11 ROM can't be opended with the other ROM :B
That's only problem .
Status : stable
version : 3
dbtools version : removed in v2
Downloads and changelog
Downloads
Fixed Grand2 not Detecting
DualBootPatcher-V3 s3 neo and grand 2 & s5 mini
Orginal DualBootPatcher app You can download the utility here
S3 Neo MotionFIx fixed thanks to @Antix2835 for reporting an issue
S3 Neo Duos MotionFIx
Grand 2 motion fix
updated to v3 tutorial changed also make sure u read tutorial AGAIN
if you used v.1.5 u need a clean install for using v2
Code:
v3
added s3ve3gdd ( fixed )
added s5 mini lte version
new design ( im sorry for v2.7 bad design )
fixed cm13 completely
added db-wiki
--------------------------------
v2.7
added in app tut
added fixes for cm13 possibility fix ( my device doesn’t have cm13 so i cant test it )
--------------------------------
v2.6
added new design
--------------------------------
v2.5
optimized Samsung devices
--------------------------------
v2.4
fixes
added multi patch ( more then 2 )
--------------------------------
v2.3
security updates
--------------------------------
v2.2
added support s5 mini
--------------------------------
v2.1
added grand 2 device support
added grand 2 motion fix
--------------------------------
v2
files are flashable with recovery now
dbtools removed
easier to install
update to last sources
new design
fixed partitions
added full s3 neo support
--------------------------------
v1.5
Now you can have unlimited ROMs!
bug fix with system partiton
added data slot support (fixed)
this post will be the ROM suggestions and combinations and screenshots
here is a video by @German Developer https://www.youtube.com/watch?v=ePRdE1OzRWE
my own best :
stock or motion as primary cm12.1 as other
app data sharing is on beta DONT USE IT TILL V2.1 . ( it make apps use same data )
any tw rom should be as primary to work ! this means if u want use any motion or motion based it should be in primary
THIS MEANS YOU CAN NOT INSTALL MOTION OR ANY STOCK AS DATA OR ANY OTHER SLOT !
You can install stock , and install motion on data BUT ! You will face RIL Problem .
with this intruction :
first install motion normally on the data slot,
note : you need 2 gbs space .
then install a custom kernel for motion rom :highfive:
Man, it's great, but I have some questions... If I install a new ROM, I'll not have to reinstall my apps, right?
EDIT: Sorry for my bad english
MarcusBS said:
Man, it's great, but I have some questions... If I install a new ROM, I'll not have to reinstall my apps, right?
EDIT: Sorry for my bad english
Click to expand...
Click to collapse
if you install a new rom like u normal yes . if you install a rom as dual or data slot you have a clean rom you can install any apps you want
Okay, and... About my storage, this will fill my storage?
Sorry for my bad english again
MarcusBS said:
Okay, and... About my storage, this will fill my storage?
Sorry for my bad english again
Click to expand...
Click to collapse
you can install telegram and talk to me there with this link : http://telegram.me/imthemr
yeah it will but if you install on dual ( if it have enough space ) it will not
Excellent
salah eltony said:
Excellent
Click to expand...
Click to collapse
it's a pleasure use thanks button !
I'mTheMr said:
you can install telegram and talk to me there with this link : http://telegram.me/imthemr
yeah it will but if you install on dual ( if it have enough space ) it will not
Click to expand...
Click to collapse
Thank you so much, man...
Great Job mate !!
I'm waiting for v2
Thank!!! Please, make video instruction
iYaro said:
Thank!!! Please, make video instruction
Click to expand...
Click to collapse
Please wait I think @German_Developer is making a little video about this
I will make a video, don't worry, but first when the v2 comes out
twrp 3.0
Sorry bit i don't find the twrp recovery versione 3.0, can you past a link please? Thanks
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Can install the blisspop ROM?
Great work mr!
emabertax said:
Sorry bit i don't find the twrp recovery versione 3.0, can you past a link please? Thanks
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Can install the blisspop ROM?
Click to expand...
Click to collapse
wait for v2 it will be released today
thanks !
sev3n1985 said:
Great work mr!
Click to expand...
Click to collapse
Thanks !
So, in V2, can I boot any S3 Neo Rom as secondary rom? (for example FIUI?)
Antix2835 said:
So, in V2, can I boot any S3 Neo Rom as secondary rom? (for example FIUI?)
Click to expand...
Click to collapse
its not about possibility (everything is possibe) its about space u got . u cant install as dual partition on motion rom and stock however you can install it on data slot as many as you want
WARNING: This rom is by far not suitable for daily usage and flashing it is at your OWN RISK! (my HTC One X has survived so far )
I've compiled a CM-13.0 from for the HOX.
While it is kind off working, it is very unstable.
Butttttt, when it's stable it's damn fast for what I've experienced so far.
What is broken:
audio
camera
wifi
gps (needs to be confirmed)
bluetooth (needs to be confirmed)
installing an app doesn't make the app appear in the launcher
I've attached the GDB debugger to the mediaserver process to start viewing the breakpoints but I didn't succeed.
(for people that are curious, here is the crashlog: http://pastebin.com/KN9s7C7K)
The only way this rom currently boots is when the GDB is attached and I am slowly stepping trough the main_mediaserver.cpp source code. I think this works because the mediaserver get's started too soon, and thus some of the hardware related things are not ready. If only I had the tegra3 source code for the audio.primary.tegra.so and the camera.vendor.tegra.so files. That would make my life a lot easier since I'd have just changed the code to be compatible with Android 6.0.
If you've got a spare HTC One X and you'd like to test and help me out, you can flash this rom and let me know what is working or not.
There is a build running right now and I'll let you know the results when it's finished.
XDA:DevDB Information
[ROM/WIP][CM-13.0/LOS-14.1][6.0.1/7.0.1] CM13.1 or LOS 14.1 - HTC One X, ROM for the HTC One X
Contributors
tim687, DevUt
Source Code: https://gitlab.com/endeavoru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: HBOOT 1.72.0000 or higher
Based On: CyanogenMod
Version Information
Status: Testing
Current Stable Version: -
Current Beta Version: -
Created 2017-03-02
Last Updated 2017-05-21
Obtaining device logs
Obtain (boot-) logs
There are a few ways to obtain the bootlogs when the device doesn't (fully) boot.
A recovery with file manager is required (most TWRP's have it)
Get kernel logs:
#1: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#2: Make sure that the sd card is mounted, if not go to the mount menu of TWRP.
#3: Go to Advanced -> File Manager, then navigate to /proc and copy the files last_log and last_kmsg to the sdcard (/sdcard).
#4: Go back to the mount menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#5: Copy the last_log and last_kmsg to your computer and send them in this thread to me (not the actual text, but the files themselves, pastebin is also allowed).
#6: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#7: Make sure that you are able to test a new build and be able to reproduce the crash
Get ADB access
If you need to clean flash a new version of this rom, please do that first, so that the files you are placing inside the /data partition don't get erased.
Locate the adbkey.pub file on your computer.
On Windows it is in C:\Users\<username>\.android\On Unix (Linux and OSX) it is located under ~/.android
#1: Make the following directory tree:
misc\adb#2: In the adb folder create a file named "adb_keys"
#3: Open the file with any editor.
#4: Paste the contents of the adbkey.pub file in the adb_keys file. If you want to authorize multiple computers, just paste the next key in the line below the first key.
#5: Save the file
#6: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#7: Go back to the 'Mount' menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#8: Make sure that the sd card and /data is mounted, if not go to the mount menu of TWRP.
#9: Copy the directory tree you've created in #1 to the sd card of your device.
#10: Go to 'Advanced' -> 'File Manager', then navigate to '/sdcard' and click on the 'misc' folder, then click on 'select' -> 'Copy Folder' -> 'data' -> 'Select' and swipe to confirm.
#11: To start the logs to appear on your screen enter the following command (the same for Windows and Unix users, it requires the ADB binary and executable folder to be in your path):
adb logcat && adb logcatYou might want to save the log to a (text-) file, you can do that by changing the command to (note: If the file exists, it gets overwritten!)
(adb logcat && adb logcat) > adb_bootlog.txt#12: Post the logfile in this thread (not the actual text, but the file, pastebin is also allowed)
#13: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#14: Make sure that you are able to test a new build and be able to reproduce the crash
Reserved
How to flash:
For full safety, please do a clean flash everytime a new build has come out!
#1: Extract boot.img from the zip.
#2: Flash the zip
#3: Clear data and cache
#4: Restart in fastboot mode and use fastboot flash boot boot.img to flash the boot image
#5 (optionally): follow the steps in the post above to obtain (boot-)logs
Changelog:
20170304:
Used audiowrapper, to hopefully fix the audio
Social links
Social:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Telegram Group: https://t.me/htconexwip
Me: https://telegram.me/timkoers
Nice
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
@DevUt
yes... great news for our old One X !!
Guys, the latest build is up, not sure if it will boot though. Please let me know
IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes
DevUt said:
IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes
Click to expand...
Click to collapse
I can't remember if you did or not. I think you were working on it though.
mrbtree98 said:
I can't remember if you did or not. I think you were working on it though.
Click to expand...
Click to collapse
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !
DevUt said:
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !
Click to expand...
Click to collapse
At which three? I might be able to build one today.
I've synced LineageOS 14 with the CM-14 trees, and the compilation doesn't even start, so I'll have to look in to that
I just want to thank you or making this rom. I am on cm12 and once this rom is more stable I will flash it and give it a try.
Might take a while howeve ?
College has started again
Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?
Byrkoet said:
Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?
Click to expand...
Click to collapse
Audio is very difficult, the audio subsystem has changed during the upgrade from 5 to 6.
I haven't got time to try to fix them.
Don't expect very much very soon
Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?
DeepScred said:
Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?
Click to expand...
Click to collapse
I'm working on it
Hey tim687,
really nice what you do. How is it going?
MrSirMan said:
Hey tim687,
really nice what you do. How is it going?
Click to expand...
Click to collapse
It's going very good with me man! Not with the rom however, I haven't found time to start working on it.
I've been very busy with various project for my school and at home.
I am not sure when I'll have time to start working on it again...
Thanks for the interest though!
I just get one today and would help you with testing if any of the issues has been fixed, unfortunately they are major =/