Related
Hey!
I'm not sure which section is better for this: Q&A or General, so I post it here..
On this (REALLY EASY) Guide I show you how you can make own "Flash-able" ROM from Stock Android ROM on your phone:
Requirements:
Galaxy Nexus toolkit / CWM recovery (I recommend the toolkit) <---- Can be downloaded here
Linux Ubuntu (Can be installed as second OS without any disk) <--- Here
Drivers for Fastboot and ADB: Driver for GSM, Win 32-bit Driver for GSM, Win 64-bit for Sprint and Verizon: check the Nexus Toolkit thread..
Let's Begin:
1. Connect Galaxy Nexus to PC via USB cable and go to settings > developer options > and enable USB Debugging
2. Open the Nexus toolkit program
3. Select your Nexus's model and if the Android version on that doesn't exist then choose the older one.
4. Select number (2) Backup and Restore your Phone
5. Select number (9) and then it asks do you have insecure boot.img or custom ROM, if you are using stock Android ROM with unsecured boot.img then type "no" and follow the instructions on it.., if you are using custom ROM then type "yes"
6. select number (2) Boot, System
7. Wait until it have done everything and then you can close it and go to the C:\Galaxy Nexus ToolKit folder and find folder "backups"
8. on that folder "C:\Galaxy Nexus ToolKit/backups/" you have .ZIP file: backup_2partitions_########.zip Move it to somewhere /users/ folder or to Desktop, E.g to /libraries/documents/,
If you are using Ubuntu on the same computer where you do this then move the .zip package to memory stick/another hradware
9. Now boot to Ubuntu OS "reboot" in "Boot configuration" select Ubuntu if you are using Ubuntu on the same computer then connect Memory stick and move the .zip file from it to Desktop, If you are using Ubuntu on the another computer then you can open users-server and copy file from that to your Ubuntu.
10. On Linux Ubuntu install this dsixda's android kitchen: Here and then extract it to somewhere..
Let's build ROM:
1. Move the .zip package from Desktop to Dsixda's Android Kitchen > original_update folder
2. Open runme.sh and run it via Terminal
3. Select number (1) Set up working folder from ROM
4. Press enter all the time when it asks something. (asks about recovery files what you might want to keep, so if you want keep them then jut press enter and don't type no to the terminal
5. when it is extracting system.img and asks password then type your password to the terminal and press enter
7. When you are in main menu, you may want to De-Odex the ROM, select (0) and then (11) De.Odex and then choose both system and framework folder!
8. You may want insecured boot.img, in Advanced options choose (12) and then choose (w), go to BOOT-EXTRACTED folder and then to boot.img-ramdisk folder, now open default.prop and change line
Code:
ro.secure=1
to
Code:
ro.secure=0
Now in terminal press enter and then (b)
9. Now (if you want) add root permission, zipalign apps, add busybox and its run-parts (init.d) support, add apps e.g. Adobe Flash player.apk to /system/app/
10. when you have modified your ROM then choose (99) and press enter then again enter and choose (2)
11. when all is done then go to OUTPUT_ZIP folder and move the maguro_#########################.zip to Nexus and flash it via CWM or ADB sideload or whatever which works with it...
{
"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"
}
Hopefully this helps someone! DD
I will fix some things on this post when I have fixed my Nexus. EDIT: My Nexus is now OK, have modified this thread quickly..
I made this thread because I was bored and I messed up my Nexus so I had to make flashable ROM form my ROM from my Nexus.. DD
- How badly did you mess up your Nexus to have to use a toolkit and a kitchen to revive it? ADB didn't work? Fastboot didn't work?
- How did you manage to turn on USB debugging inside Android, by going to settings > developer options > USB debugging, if it was messed up? I thought you were on a bootloop, or no system installed?
- I don't get the Ubuntu part, steps 8, 9; care to elaborate?
About ROM building and the script:
- step 4: enter to everything the script asks? What questions? How do I know it's doing everything correctly? Linux isn't Windows, you know?
- step 5, what password do I have to enter?
Thanks...
Edit: it seems the author of that kitchen isn't supporting it anymore.
Edit: oh I see, you're running Ubuntu on a flash drive.
sent from my Google Galaxy Nexus
bk201doesntexist said:
- How badly did you mess up your Nexus to have to use a toolkit and a kitchen to revive it? ADB didn't work? Fastboot didn't work?
- How did you manage to turn on USB debugging inside Android, by going to settings > developer options > USB debugging, if it was messed up? I thought you were on a bootloop, or no system installed?
- I don't get the Ubuntu part, steps 8, 9; care to elaborate?
About ROM building and the script:
- step 4: enter to everything the script asks? What questions? How do I know it's doing everything correctly? Linux isn't Windows, you know?
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
I got the SystemUI has stopped popup by flashing systemUI.apk so when I flashed the original back and when I wiped cache and dalvik cache then it didn't help so then only think that works is to clean everything and then to flash ROM again.
Now I have fixed my Nexus but I have t install many apps again.
To install Ubuntu you open Wubi.exe and then as you can see you should choose install inside Windows, choose the size for Ubuntu which can be 4GB if you don't want to install any updates to it.. so it's easy...
step 8: you can't actually access the C:// drive via users server if you have not enabled any access to it, so I move files that I need from C:/ drive to somewhere /user/ folder or to desktop.
the step 4: you can choose what you want but it asks about deleting recovery files and deleting install-recovery.sh from update-script..
he is not supporting the kitchen anymore, but it works.
the password: It asks permission from you to unpack system.img
Password asking can be disabled somehow but I don't remember how..
And the ROM in my signature is made this way..
manumanfred said:
I got the SystemUI has stopped popup by flashing systemUI.apk so when I flashed the original back and when I wiped cache and dalvik cache then it didn't help so then only think that works is to clean everything and then to flash ROM again.
Now I have fixed my Nexus but I have t install many apps again.
To install Ubuntu you open Wubi.exe and then as you can see you should choose install inside Windows, choose the size for Ubuntu which can be 4GB if you don't want to install any updates to it.. so it's easy...
step 8: you can't actually access the C:// drive via users server if you have not enabled any access to it, so I move files that I need from C:/ drive to somewhere /user/ folder or to desktop.
the step 4: you can choose what you want but it asks about deleting recovery files and deleting install-recovery.sh from update-script..
he is not supporting the kitchen anymore, but it works.
Click to expand...
Click to collapse
Did you set the permissions right tried to fix permissions in cwm?
Regarding systemUI, you just had to restore a backup previously made before flashing. Or, if you had none.. just format /system and reflash ROM.
So, the toolkit only works in windows? Too bad, I don't have it.
Okay... so I don't have to worry about 8) either since I don't have a c:\ drive (they have ':' on paths? Madness.)
Nah, I'll pass.
sent from my Google Galaxy Nexus
bk201doesntexist said:
Did you set the permissions right tried to fix permissions in cwm?
Regarding systemUI, you just had to restore a backup previously made before flashing. Or, if you had none.. just format /system and reflash ROM.
So, the toolkit only works in windows? Not an issue.
Okay... so I don't have to worry about 8) either since I don't have a c:\ drive (they have ':' on paths? Madness.)
Nah, I'll pass.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
It doesn't require C://driver, only that driver where is the installation destination E.g. driver D or F or G or whatever which one it is!
And yes I fixed permissions, it didn't help!
I had same issues when I ported CM9 to my Sasmung Jét, when I changed DPI it still didn't work well but when I deleted all the data, cache and another files e.g. android.log, kernel.log, etc. then it didn't show the SystemUI has stopped popup..
but if I change lcd density to 160 then I get that same popup and it cam be fixed by flashing ROM again without wiping everything..
I messed up my nexus 2 times today and now I try to keep my Nexus alive!
mmm... quite useful since flashing factory image is pain in the ass for noob like me...
Awesome!!
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.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
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
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Reserved
Device Page on our website:
http://www.teamw.in/project/twrp2/203
Downloads:
http://techerrata.com/browse/twrp2/R819
In my OPPO R819 Goomanager says "No recoveries were found for your device"
This is great news. Finally a custom recovery for R819!
Download img file here
http://techerrata.com/browse/twrp2/R819
Flash with MobileUncle MTK tools found from Play Store
https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox
Do this with your OWN responsibility! I am not responsible if you screw around and brick your phone!
1. Put downloaded IMG file in root of SDcard
2. Open Mobileuncle Tools
3. Choose 'Recovery Update'
4. On the top of the list should show the IMG file on you SD card that you downloaded.
5. Tap it and confirm with OK to flash.
Can I flash Stock Recovery Back
I have installed TWRP 2.6.3.0, and I have used it to make Backups of the whole ROM.
However, I tried to install the ColorOS Beta 1.0.0 and found out it would not install, reason unknown.
So I used TWRP to clean the partitions /Data, /System, /Cache etc. and then installed successfully the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation.
The system says that there is a downloadable OTA Update Stock Oppo OS 4.2.1 (Build R819AS_11_A.09_131010). I downloaded it, clicked the greenish-blue button "Install", but the phone is not able to install it, obviously, because the Stock Recovery is different, and the instructions are for it alone. Is there a way to return back to Stock Recovery, despite it looks so bare and ugly, just to update the system?! Or is there another way to do it? Maybe if I knew where is stored the downloaded OTA update, I could flash it via TWRP...
Hmm, strange, I installed Color OS with TWRP. To change to stock recovery all you need is to flash a stock rom, it overwrites the recovery during the install process.
TWRP 2.6.3.0
Sorry, there is no logic in that. I did install Stock ROM, the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation. Via TWRP, of course. Nothing can change the recovery, it stays the same, it is on its own partition, most notably, so that nothing could mess with it. Simple principle - if you are in Recovery, you cannot destroy Recovery itself.
Thanks to a person, who has a phone Oppo Find 5, but told me the problem is with the root privileges, I managed to get past the problem. I preserved the same TWRP 2.6.3.0 Recovery, since I have no other, and I can't change it. I opened the SuperSU program, and checked inside it to "Disable", temporarily. I did not use the "Permanent Uninstall Root" option, which also exists in it. I rebooted to Recovery, and in TWRP wiped the Cache & Dalvik partitions. After that I chose "Install" and the ColorOS 1.0.0 ROM installed perfectly well. It is beautifull and shiny! :good:
{
"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"
}
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
mundano said:
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
Click to expand...
Click to collapse
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
distan7 said:
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
I have the Stock Recovery from 131010, the file is recovery.img 5,865,472 bytes but it can only be flashed with SP Flash Tool, which is not a thing to recommend to beginners, the Tool needs to have the "MT6589_Android_scatter_emmc.txt". That is why I am afraid to post it plainly, open to anyone, just because they might start experimenting without knowledge and break their Oppo R819. Trust me, if you have installed TWRP Recovery from above, using the MobileUncle Tool, you are safe and well, it is a much better Recovery than the plain Stock one.
I understand your point, but I'm not comfortable in flashing non reversible stuff in my phone...
So I will stick with the stock recovery until there is a safe way to revert back to stock.
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Distan7 managed to find a way to revert from TWRP back to Stock Recovery :good:
He has explained it here, has done it twice just to be sure it works every time:
http://www.oppoforums.com/posts/125077/
This is his detailed explanation. Nothing irreversible!
[Oppo R819] Flashing Stock Recovery After Using TWRP
More information on a couple of ways how to recover Oppo R819 are written here:
http://www.oppoforums.com/posts/133578
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
TWRP 2.7.1.0 Updated
TWRP 2.7.1.0 is uploaded to the same place http://techerrata.com/browse/twrp2/R819
vickfred said:
TWRP 2.7.1.0 is uploaded to the same
Looks like development is dead
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 11:15 PM ---------- Previous post was at 10:47 PM ----------
ccav2000 said:
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thats nice
Click to expand...
Click to collapse
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.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
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
DOWNLOAD:
Look in post #2
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
This is an unofficial port, if you have issues dont bother them, you bug me.
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Moto 360 Part
Thread closed so dees_troy can have his official one, go grab that version!!!!!
Download this: 2.8.3.0 with v7 of the 320x290 theme
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
Flash http://shabbypenguin.com/?developer=Tools&folder=Superuser to gain root
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root and testing
mkaymuzik for working on the 320x290 TWRP theme we will be using
TWRP Team for an amazing recovery.
Ok so in hindsight, this post wasnt needed, so now im going to put my device tree down here because... well i need to have something here right?
Device tree source
there, now its used... happy now?
Nice Work cant wait to get this installed and the Theme updated
great! Now we need a custom rom
BerndHhn said:
great! Now we need a custom rom
Click to expand...
Click to collapse
Agreed!!!! Has anyone tried flashing this yet?
Gotroot said:
Agreed!!!! Has anyone tried flashing this yet?
Click to expand...
Click to collapse
I did ;P
You do it over? Or use app
Gotroot said:
You do it over? Or use app
Click to expand...
Click to collapse
Im not aware of any app that will flash it on a watch.
Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..
shabbypenguin said:
Moto 360 Part
Download this: https://mega.co.nz/#!UQ4RwahC!AnFEeNBrGob9NuAyne62OXXW0MiaWeV7kpwrbjSIzjM
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root
TWRP Team for an amazing recovery.
Click to expand...
Click to collapse
Gotroot said:
Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..
Click to expand...
Click to collapse
I use fastboot from my apk tool folder so, so move your recovery.img into your fastboot path ..... My command looked like this " fastboot flash recovery recovery.img" and there you go.
@shabbypenguin could you post screenshots of how it look at the moment? Will start working on a design concept (as discussed).
I also need a ramdisk-recovery.img version of the moto360's twrp and witch theme resolution did you use ?
im using 240x240 as it proved to be far more effective than 320x320, http://imgur.com/WV4G7kb
So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?
NUGZZ420 said:
So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?
Click to expand...
Click to collapse
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it
fakieskr8333 said:
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it
Click to expand...
Click to collapse
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.
NUGZZ420 said:
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.
Click to expand...
Click to collapse
Haha no big deal. I had a total brain fart the other day and had to lookup how to adb reboot. Turns out I forgot I was on a Mac and needed to add ./ to the front. Its funny BC I always use a Mac lol.
Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.
abuttino said:
Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.
Click to expand...
Click to collapse
yup, best bet is to flash supersu though.
as a progress update:
{
"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"
}
Asus T100-TA Magic Stick
{
"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"
}
Since development and hacking for the Asus T100 tablet has been rather slow these past few months, due to the many problems that plagued the kernel and missing drivers, I decided to make a simple-to-use toolchain that works well on the device out-of-the-box. Thus, I have bundled a fully working Ubuntu live CD image and an Android-x86 build into a single usb stick format (I call it the "Magic Stick"), to allow easy testing, booting and updating stuff on the tablet. You can also use it to recover your device and perform maintenance activities without the usual hassle. And you can use it for showing off to your friends and co-workers by triple booting your tablet.
T100 Magic Stick Features:
Dual-boot directly from USB stick into Android or Ubuntu!
Test and play with both systems to see if you like them
Ubuntu 15.04 Live:
Updated 4.0 kernel (thanks to Kirill Belyaev for the kernel build)
No more internal HDD errors (no more rpmb issues)
Suspend working!
Installer working with grub installation! Finally!!
microSD Card working correctly
Wi-Fi working stable since boot
Battery reporting
Hardware buttons
Additional tools by default (gparted, mc, uefi, efibootmgr, grub2)
Android CM13.0.2-rc1 Live:
No more internal HDD errors (no more rpmb issues)
Wi-Fi working
Bluetooth working
Battery reporting
Hardware buttons working
Google Services! (Play Store etc.)
Pre-rooted!
Writable system partition
Persistent data saving on stick (1GB internal storage)
Rotation sensor working
Shrink and change partition layouts
Install and repair bootloaders, grub2 and UEFI
Install, repair, debug and update any operating system
Download and Install:
The installation procedure is extremely simple:
Download the Magic Stick zip file from here: T100 Magic Stick download
Extract the ZIP file
Copy the contents of the extracted folder to a USB stick (at least 3GB free space required)
Disable secure boot in the UEFI firmware configuration (tap F2 at startup to enter configuration)
Boot from the USB stick (tap F2 at startup and choose the stick as boot device from the menus)
Thanks and credits:
Kirill Belyaev, Povilas Staniulis, rbg, Chih-Wei Huang, Brain WrecK, pstglia for their work and contribution + their dedication and their builds.
The whole Asus T100 Ubuntu Google+ Community (chck us out!);
The whole Android-x86 Google Group (check us out!);
Everyone else who contributed patches, fixes, ideas and suggestions!
Download:
v2.0-beta1: Download
Cheers,
C.
Changelog:
v1.5: Ubuntu: no changes or improvements, sorry...
v1.5: Android: microSD card support
v1.5: Android: no more FC bugs at boot...
v1.5: Android: display driver improvements (some games and apps which didn't work will start working now)
v1.5: Android: better overall performance (+2500 points in Antutu than previous version)
v1.5: Android: better browser support (chrome, firefox etc.)
v1.5: Android: streaming support less buggy
v1.5: Android: latest 4.4.2-r3 build included (much more stable)
v1.5: Android: improved bluetooth support (some issues still reported, though)
v1.4: Ubuntu: added bluetooth support (seems unreliable)
v1.4: Ubuntu: updated packages to latest versions
v1.4: Ubuntu: fixed Software Center problems
v1.4: Android: data is saved to the stick (1GB internal storage only!)
v1.4: Android: added bluetooth support (tethering not working, yet)
v1.4: Android: added accelerometer sensor support
v1.4: Android: added rotation sensor support
v1.3: Ubuntu installer does not crash anymore!
v1.3: Added suspend support in Ubuntu
v1.3: Updated to Ubuntu 15.04
v1.3: Added sound for Ubuntu
v1.2: Initial release
Known Issues:
Ubuntu: suspend doesn't work as it should, no bluetooth, no rotation, no camera, no microphone;
Android: suspend doesn't work as it should, no bluetooth, no rotation, no microSD, no camera, no microphone;
Android: at boot, Google text-to-speech will FC a couple of times. This is fixed once you log into google play and update the GApps;
[*]Android: sometimes the keyboard dock is not enabled at boot. This is caused by a race condition at boot and I won't fix it. If you run into it, reboot and try again; (didn't encounter it anymore)
You tell me...
Frequent Questions:
Can I remove the stick after boot?
Answer: No. This works like a live CD.
Will my data be saved?
Answer: In Ubuntu no. This works like a live CD. In Android yes, you can store up to 1GB of data (due to popular request).
Can I install Ubuntu?
Answer: Yes. This works like a live CD.
Can I install Android?
Answer: Yes, but not using the built-in installer.
How can I install Android-x86?
Answer: Manually, but it's easy. Maybe I will create a step-by-step guide later...
Will Android work with ART (before or after install)?
Answer: No.
Can I install xposed framework?
Answer: Yes, but not on the live version, you must install Android locally first.
How can I update the Android-x86 version on the stick?
Answer: Replace the files in the "x86" folder on the stick.
How can I update the Ubuntu version on the stick?
Answer: You can't (not easily anyway).
Windows Tools:
I recommend you download these and save them onto the USB stick you create yourself, to always have them on hand. I did not include them on the stick as they are licensed separately (even if "free") and all credits go to their respective authors. I also recommend downloading the Windows 8.1 drivers for the T100 and saving them to the same stick, just in case you have to re-install Windows. Just make a separate folder on the stick and save whatever you want there. It won't break any functionality.
EasyUEFI - Download
A tool which helps you manage UEFI boot entries, paths and configuration for booting with ease
Ext2Fsd - Download
A tool which helps you mount ro/rw the Android/Linux partitions in windows as regular drives
unsqashfs 4.0 - Download
A tool to extract the ".sfs" and ".squashfs" images to regular ".img" files (to make system.img writable, mountable etc.)
Advanced reboot script - Download
A Windows batch file that reboots the system so you can select the boot device using your touchscreen (boot in Android/Ubuntu directly without the dock attached etc.)
Linux how-to resources:
Unsquash FS: http://unix.stackexchange.com/questions/80305/mounting-a-squashfs-filesystem-in-read-write
Update grub: http://askubuntu.com/questions/281119/how-do-you-run-update-grub
Grub install to separate partition: http://askubuntu.com/questions/472669/install-grub-on-a-different-partition-on-triple-boot-system
Make IMG files: http://ubuntuhak.blogspot.ro/2012/10/how-to-create-format-and-mount-img-files.html
More grub: https://docs.oracle.com/cd/E26502_01/html/E28983/gkvif.html
Even more grub: http://superuser.com/questions/376470/how-to-reinstall-grub2-efi
Android How-to / guides section:
This section contains a set of guides to help you with some basic tasks and activities to easily manage your own installation(s) of Android. This is the part where the Magic Stick itself will prove to be useful and how you can use it to customize and repair or update anything. The Ubuntu related stuff is not documented here, as documentation and forums are available on the internet.
WARNING: These guides are not extremely detailed and include only the activities which have to be performed. Each configuration is different and you need to understand what you are doing to make sure you don't break anything. Worst case scenario is that you will lose all your data. However, you will still be able to boot the Magic Stick to repair or re-install everything (thank me later!)
DISCLAIMER: I am not responsible for any loss of data and you are at your own risk while using the tools, guides and information provided here. Back up your data and do not play around with systems that you use on a daily basis. Only follow these guides if you feel comfortable with the instructions and completely understand what you need to do at each step.
Make the Android system partition writable
When you download an Android-x86 release, you will find in the ZIP or ISO a bunch of files, including a file called "system.sfs" or "system.img".
If you have a file called "system.img" you can stop now, your Android system partition is writable and you can skip to the final step.
If you have a file called "system.sfs", then use the unsquashfs command to convert it into a writable format:
If you are using Windows, download the unsqashfs tool above and extract the zip. Drag and drop the "system.sfs" file on top of the unsqashfs executable to extract the system.img (you can find it inside the generated folder)
If you are using Linux, make sure squashfs-tools are installed and run this command from the folder containing the "system.sfs" file:
Code:
unsquashfs ./system.sfs
That's it, now you can mount the system.img file generated under linux using this command:
Code:
mount -o loop ./system.img /path/to/destination/
Resize the system partition
Usually, the system partition of Android-x86 is made as small as possible (you don't want to download "free space", right?) so if you want to add gapps or other packages to the system partition there will be no space left. Here's how to increase the size of the system partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Browse to the folder containing the system.img file (using 'cd' or 'mc')
Extend the system.img file by 200MB. Replace 200 with the amount of MB you want to add:
Code:
dd if=/dev/zero bs=1M count=200 >> ./system.img
Run gparted to also extend the partition inside the file:
Code:
sudo gparted system.img
In gparted, right click on the partition and select the option to shrink it down by only one MB (so it registers a change) and apply the changes
Close gparted. You're done.
Make space to install Android
Creating a new partition onto which to install Android usually requires shrinking an existing partition. If you want to install Android on the tablet (not the dock base) you will have to shrink the Windows system partition. Here's how to do it in a reasonably safe way:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Run gparted as root:
Code:
sudo gparted
In gparted, right click on the Windows system partition and select the option to shrink it down by at least 2GB. Make sure the partition actually has 2GB of free space, otherwise the process will not work.
Right click the free space and create a new partition and select to format it as ext4. It's important to make it ext4, so keep this in mind. Also give it a name such as "android".
Apply the changes and wait for the partition to be created.
Close gparted. You're done.
To have the partition available in Ubuntu Live, you have to mount it manually or just reboot (to have it mounted at boot automatically)
Install Android locally
Make sure you have the system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have an ext4 partition mounted. The Android-x86 installation is in fact a simple process of copying the ISO/ZIP files onto the destination partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice
That's it, Android-x86 is installed (but not yet bootable!)
Enable data saving for Android
To enable data saving for Android-x86, you have many choices. However, the simplest one is to use an ext4 partition and create a dedicated "data" folder for android. Make sure Android-x86 is installed onto an ext4 partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Navigate to the root of the partition (the mount point folder)
Create a folder called "data":
Code:
mkdir -p data
You're done, Android will save data persistently across reboots.
Note that this only works for ext4 partitions.
Note that using ext2 or ext3 will output errors for Google Play if you use Lollipop builds.
You have been warned.
Install the grub2 boot loader
Resizing partitions and copying (read installing ) Android is a very simple process. However, the bootloader installation is a much more complicated business (usually!). Here's how to make sure everything is installed correctly:
In progress...
Add the Android menuentry to grub2
Once we have grub2 installed and ready to go, it's time to make Adroid-x86 bootable as easily as possible:
In progress...
Update Android with new releases
Once Android is set up and ready to go, all you need to do to update it properly is to overwrite the existing files and reboot. Make sure you have the updated system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have the Android ext4 partition mounted:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice, overwriting the existing ones
That's it, Android-x86 is updated
Cheers,
C.
Reserved....
I am having some problems with this. Granted I am trying to use it for install on the Dell Venue 8 Pro. This tablet is a bay trail base, with most of the same hardware, minus the wireless/bt card. This works fantastic as a live cd, but when I install it I get problems. Is the ubuntu image only i386? When I was trying to change the kernel from the G+ group I kept getting the architecture mismatch (Kernel.deb file is amd64 and system is i386). Also the bootloader is kind of weird. All of the grub settings are correct, but if I want to boot ubuntu from the mmc I have to enter the advanced menu, then boot recovery mode. When recovery mode boots, I hit resume boot and then I am magically loaded into my installed system. Am I doing something wrong here?
The live image is i386 only. For the grub boot loader, try copying the entry contents into the stick boot menu and see if it works as intended. The menuentry file on the stick is in ./boot/grub/grub.conf.
I'll be releasing a new version of the stick with Ubuntu 15.04 (i386) and some additional sound fixes in the next few hours as well.
Cheers,
C.
Ok, v1.3 with new updates and fixes has been posted. Let me know of any improvements and/or problems.
Cheers,
C.
Thank you for great work! One promise: please, fix bug for HP Omni 10. My tablet can't boot in Ubuntu (but works perfectly with Android). Here is a link to the G+ posts with bug disc.
https://plus.google.com/105824122847813147186/posts/4G1BQgD5LNQ
https://plus.google.com/105824122847813147186/posts/gxqsVsNNJoq
The HP omni problem comes from the kernel, which I did not build and I do not maintain. Also, I don't have a HP omni, so I can't test it out.
The bottom line is that I can not promise to make it work, but I will update the kernel when possible. Keep in mind that this is a Asus T100 tool. Follow the thread and when an update for the kernel is posted, try the new version.
Cheers,
C.
Everything runs perfectly. Flawless Android and I'm still testing around Ubuntu. You've helped revitalize my T100! thanks!
Now I just need to figure out how to install the bootloader. Seems simple enough but your instructions say it may be a bit complicated so maybe I'm missing something
For some reason, after Ubuntu installed coulnd open the software manager and didnt have synaptics, also is there a way to turn of the white led,
second do i copy all the android files into the Ubuntu drive or i need to partition the ssd for another partition for android( what are the chances of 5.0/5.1)
thanks for the files and works good, only issue, not home dev but Linux/Ubuntu, that is not finger scroll friendly, and click and hold for right click(context menu) beside chromium that scroll with out having to hold the scroll bar like the rest of the system
It will be great, if you fix it. Thanks for reply!
""Login failed, impossible to establish a reliable connection to the server. This could be a temporary problem or your Android device may not be suitable for data services. If the problem persists, contact customer service. ""
Gives me this error every time I try to log in with my google account. Solutions?
Installation on hdd
I have installed ubuntu on my t100 on the hdd. It works great so manu thanks for that but I have on issue, I need to let the usb stick in on boot in order to make it boot. If I don't grub is in rescue mode saying that : "error : no such device : 25dc1ad7-c268…"
Is there any way to get touch screen working on a Toshiba Encore 2 Write? I know this thread is for the Asus T100, but I tried this flash drive image out on my device and it ran, minus touchscreen. It booted up fine and everything. If anyone is able to help me out, it would be greatly appreciated! I think the issue stems from the device having a Wacom touchscreen, but I can give any information needed!
@feduss: The connection problem did not appear in my tests and I am able to log into Google Services without any problems. Skip the account creation during the initial setup wizard and create it later and see if it works.
@alphaeagle777: try installing plasma-active. You can see it in action here: https://www.youtube.com/watch?v=mOMmp8iEaqY
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
@FiendFyre: The stick will never have Encore 2 support unless one of the kernel developers include it in the configuration. I am not building the kernels myself, so it is best to ask the Android-x86 group for more info.
Cheers,
C.
I tried already to login later...maybe i'll solve the problem creating a new account
cheatman said:
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
Cheers,
C.
Click to expand...
Click to collapse
Thanks for the reply. It was the correct issue, I didn't pay attention during installation. To solve the problem I juste reinstall grub at the right place.
edit : I speak to fast. Just reboot work, not after a shut down.
edit2 : after reinstalling ubuntu with grub at the rigth place, it still doesn't work. Can you explaim me how to install grub correctly ?
Grub entry
Hi cheatman, thanks for your great work and nice tutorials. Now I am trying to figured out, how to edit grub to add entry for android. It is situated in /dev/mmcblk0p5 in folder android. I have alrready installed ubuntu on keyboard HDD. Thanks.
{
"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!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename 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.1 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.65 (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.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[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 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 in your tool?
Follow the instructions in 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 terminal to find out what you're missing from your environment.
Q: I have an 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 it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
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) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others 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 GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full 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, as well as 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!
I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.
Dodgexander said:
I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.
Click to expand...
Click to collapse
It's a bug of the platform tools used in the package, the latest version of platform-tools should work. I will try to update it today.
Edit: Fixed in 1.3.1
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu