Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
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.
{
"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.
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.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.
Related
Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It has been downloaded over 700 times on MediaFire alone and has been tested by several members, including myself.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock or lock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
* Remove the tamper bit.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver. 1.2.8
- Updated stock image to XNPH38R.
- Updated the stock recovery to XNPH38R's recovery.
- Added an experimental way to restore the old blue lockscreen.
Ver. 1.2.6
- Updated the TWRP image 2.8.0.1
- Updated SuperSU binary to 2.02.
- Removed unnecessary(?) reboot command at the end of the bootloader unlock menu.
- Updated the "reflash back to stock" image to XNPH33R.
Ver 1.2.4
- Updated the TWRP image to 2.7.1.1.
Ver. 1.2.3
- Made it clear that booting custom recoveries without unlocking the bootloader is impossible in OTA 30O or later.
- Made the DMG automatically open after mounting.
- Changed the wget binary to another one. The previous wget was likely built with my personal OpenSSL setup from Homebrew and was thus not compatible with everyone.
- Small fixes
Ver. 1.2.1
- Big bug fix to rooting without installing a bootloader (rebooted you previously into recovery when it was supposed to reboot you into fastboot). Thanks to Nandmp for finding that one.
- Removed the "You need an unlocked bootloader to root" information in the rooting menu.
- Removed a few sudos that weren't necessary.
- Minor fixes here and there.
Ver. 1.2
- Added a way to lock the bootloader.
- Added a special way to unlock a relocked bootloader without wiping the phone. It can also remove the tamper bit! See the devs' thread for more information.:
- Made it possible to root the phone without installing a custom recovery.
- Made it easier to reflash back to stock. It now downloads and the factory image automatically in a designated folder.
- Added locking in the basic adb/fastboot commands.
- Added reflashing the stock image by using a manually downloaded factory image in the basic commands.
- Loads of fixes here and there.
Ver. 1.15
- Fixed critical bug in reflashing back to stock for 64GB devices (thanks to @X10D3 for finding this one)
- Added experimental "boot to any custom recovery without installing it" to the basic fastboot commands.
Ver. 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver. 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver. 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver. 1.00:
-Initial release.
OnePlus thread
Here's a 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"
}
Thank you!!
Warranty will NOT be void Anyway thanks, hoping someone will try it
blak24 said:
Warranty will NOT be void Anyway thanks, hoping someone will try it
Click to expand...
Click to collapse
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Well OnePlus always stated that rooting the phone will not void phone's warranty
Consistant said:
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Click to expand...
Click to collapse
Yeah, I just Googled it and it seems indeed like the warranty isn't voided by unlocking the bootloader. That's a first, props to OnePlus for doing that.
And thanks to you for pointing out! I'll make sure to get that fixed once someone has properly tested it in case it needs additional changes.
When I run the toolkit, this happens?
---------- Post added at 11:35 AM ---------- Previous post was at 11:18 AM ----------
joeg6217 said:
When I run the toolkit, this happens?
Click to expand...
Click to collapse
Seems to have sorted itself out. It's now working
When flashing a recovery:
ERROR: could not get pipe properties
rebooting...
Just posting for FYI.
I've used a few different toolkits for a variety of phones.
This was the best and easiest I've used yet.
Everything worked perfectly.
Brilliant
:good:
in my Mac won't start (mavericks )....
---------- Post added at 09:14 PM ---------- Previous post was at 09:08 PM ----------
only a corrupted downloaded file. noow work on my maverick's imac, sorry
Thank you!
Sent from my One using XDA Premium 4 mobile app
Consistant said:
Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It is under testing by several members, but I cannot test it personally due to not having One. I've gone through it many times now, checked that ADB and Fastboot works on two OS X computers and it should work perfectly fine, but at least keep it in mind.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver 1.00:
-Initial release.
OnePlus thread
Here's a screenshot:
Click to expand...
Click to collapse
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sharp2G said:
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Consistant said:
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Click to expand...
Click to collapse
I've managed to get root access thanks to your application for Mac! THANK-YOU!
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Worked great! Thank you!
X10D3 said:
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Click to expand...
Click to collapse
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Consistant said:
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Click to expand...
Click to collapse
Awesome. Thanks for the update.
this should be added to the tool/utilities section great work man, saw this on the oneplus forum too :good::good::good::good::good::good::good:
I have a question. We need to download anything else like sdk, drivers or just the tool kit? I have see that adb drivers and fastboot can be installed from the tool kit. Thats all?
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"
}
This is for Windows ONLY at the moment.
Features:
Unlock bootloader
Relock bootloader
Backup data (all or selectable sections)
Restore data (all or selectable sections)
Optimize all OGG files on device
Zipalign all APK files on device
Batch install APKs from local PC folder
Reboot device
Reboot into recovery
Reboot into bootloader
Flash recovery
Changelog:
v3.21
* Fixed a couple commands
* Fixed broken backup menu
* Cleaned up some menu spacing
* Removed some unneeded comments
Download: v3.21-FREE
Download method 2:
There is now a free version and a donate version. The donate version requires a minimum donation of $5. First, set up a FREE GitLab account. Once you have donated, send me your GitLab username, in a PM or in this thread, and I'll add you to the repo so you have access.
I will be adding features to the donate version as I get time. I have to balance work/college/family, so my time is limited. General fixes will apply to both versions.
Requirements:
GIT (Windows download)
FREE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-FREE.git
cd Android-Job-Box-FREE
JobBox.bat
DONATE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-DONATE.git
## enter your GitLab.com username/password here when prompted ##
cd Android-Job-Box-DONATE
JobBox.bat
Previous changes:
v3.20
* Updated SOX to 14.4.1
* Updated all binaries in /Data with up-to-date versions from v26.0.1 tools
* Fixed some zipalign commands not pushing back to correct device folder
* Fixed fastboot reboot command
* Fixed main menu crashing with ENTER
* Overhauled the backup/restore sections
* Separated the CAMERA and PICTURES directories in backup/restore
* Switched to TIMEOUT instead of PING (non-skippable)
v3.10 * Updated all binaries in /Data with up-to-date versions from v26-RC tools
* Fixed menu choices in REBOOT menu
* Fixed backup and restore functions
* Fixed timing issue with bootloader lock/unlock commands
* Fixed a ton of misplaced commands
* Reworked terminal output to be more visually friendly
* Made some adb push/pull functions verbose again
* Removed some unused code blocks
* Made reboot options escapable within the script
v3.00
* Updated all data binaries in /Data with up-to-date versions
* Fixed the OGG optimization process
* Fixed mounting of /system in TWRP
* Fixed a couple menu text inconsistencies
* Removed a couple unnecessary subroutines
* Reduced the size of some subroutines
* Optimized the removal of non-apks and empty folders
Installation:
1: Extract the contents of the zip file somewhere (NO spaces in the whole folder path. Need to sort that out)
2: Double-click on JobBox.bat
Installation for method 2:
1: Navigate to a folder where you want the script (NO spaces in the whole folder path)
2: Run the commands for the version you want
3: Run JobBox.bat
NOTES:
To flash recovery, the recovery image must be in "/Data" as "recovery.img"
Optimizing OGG files is done by pulling all audio from the device, into the local computer
where the are optimized, and then pushed back to the device in their original location. HOWEVER,
be aware that optimizing an audio file too many times will break it, and cause serious loss of
audio quality. I have no way to test if the files were optimized already or not, so please keep
track of that yourself.
Optimizing APK files is done by pulling all APKs from the device, into the local computer
where they are optimized, and then pushed back to the device in their original location. There
is no verbose output (by choice), or progress animation. Believe me, its still working. Just
give it time.
No part of this script may be copied,
modified, redistributed, or included
anywhere without my written consent.
Credit goes to Lexmazter for the original template I'm using to make my script. You can find his tool HERE
Credit to Chris Bagwell for SOX
Credit to Google for the adb/fastboot binaries
Will it be able to root as well in the future?
chevycam94 said:
This tool is a work in progress.
As I add features, I'll release new
versions of the tool. This is for
Windows ONLY at the moment.
Click to expand...
Click to collapse
Just a heads up, you need to update the unlock command to "fastboot flashing unlock" as this is the new command for the M devices - oem unlock no longer works.
Thanks for the heads up. Question. Is that for devices that shipped with M?
Is all data wiped when performing the unlock no matter what?
Heads up - This tool does not work for some reason, just times out every time.
FAILED : (Remote : unknown command)
finished total time : ABC-XYZ
Click to expand...
Click to collapse
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
hutzdani said:
Heads up - This tool does not work for some reason, just times out every time.
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
Click to expand...
Click to collapse
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Tung_meister said:
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Click to expand...
Click to collapse
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
I included (just in case) the 4 adb files from my current SDK, v24.4.1. I don't have my 6P yet, so I can't test it.
Also, when someone unlocks their 6P, report back here if it clobber use of the fingerprint scanner and/or Android Pay. I want to add a warning about them in the script if it does.
chevycam94 said:
Thanks for the heads up. Question. Is that for devices that shipped with M?
Click to expand...
Click to collapse
.
It might just be for the Huawei 6P, not all MM devices not certain. Since it's a Nexus device should be fastboot oem unlock not sure why Huawei changed.
Just in case, I added in an option to choose which method to use to unlock/relock the bootloader.
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
hutzdani said:
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
Click to expand...
Click to collapse
make sure you go into developer options and check "oem unlocking"
eneka said:
make sure you go into developer options and check "oem unlocking"
Click to expand...
Click to collapse
All set now had to update my ADB from the SDK, fastboot flashing unlock was not supported or listed as a command until I updated the SDK
Working on a major update to the backup and restore functions. Should really help people out with backing up certain things, not necessarily the whole thing
Ok, updated to v1.20. Now the user can choose to do a backup before unlocking/relocking, without going through two different sections. Fixed the fastboot commands, and added the ability to flash custom recovery.
MAJOR update to the script. Now available in the OP.
Now, in addition to a full backup, you can also backup and restore certain files, such as your downloads, pictures, videos, music, and even Android application data (NOT the apks, just the data user storage (/Android))
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
StephenMSmith said:
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
Click to expand...
Click to collapse
That's the idea. Just data, not apps....yet
Is this using chainfires systemless root method? And thanks for your contribution to the 6p
Sent from my Nexus 6P using Xparent Blue Tapatalk 2
{
"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!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
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
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
For Huawei Mediapad T1 10
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"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"
}
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* 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 ROM
* 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.
*
*/
READ THIS BEFORE DO ANYTHING:
First of all, keep in mind that this recovery is only for the Huawei Mediapad T1 10 variants (T1-A21L and T1-A21W) (codename: hwt1a21l). More details: link..
"How can i know if my device is the right one?":
If you are using EMUI 3.0., go to Settings
About tablet
Check Model number
If your device is T1-A21W (Wi-Fi variant) or T1-A21L (LTE variant) then it's the correct device
So please, if your device is not one of them then this recovery is not for your device.
Click to expand...
Click to collapse
Let me clarify some thing:
Since our device doesn't have any development support (no ROMs, no recoveries, mods, etc) i decided, many months ago, to bring it some development.
You may ask me why i'm posting a completely deprecated custom recovery for our device, and the why is simple:
Since i started trying to bring custom ROMs and recoveries, many months ago, this was one of the successfully ported recoveries i got. The other one, a twrp 2.8.6.0 recovery, it's almost unusable due to problems with the touchscreen response that i couldn't fix. I basically decided after a long time to open a thread for this recovery and share it because my main objetive was to compile a completely TWRP recovery (3.X version) but after a long and unsuccessfull battle i coudn't do it (yet).
So, i decided to share this one while i'm still trying to get the kernel source fully working to port a completely updated TWRP recovery.
Description
"PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI."
Requirements:
-Unlocked bootloader
-One of the devices mentioned before
- A PC+USB cable or compatible aplication+Root to flash the recovery
Changes between the original version
Changed Philz Touch backgound to a more modern and adapted wallpaper.
Features (Careful: Most of them untested)
touch interface:
toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
written from scratch full touch code
basic scroll kinetics for faster scrolling on demand
safe full touch : no wrongly validations while scrolling
when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
adjust scroll sensitivity in a huge palette
adjust menu height in a huge palette
adjust touch accuracy
30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
user custom background png can be selected in addition to 30 solid colors option
show / hide background icon
show / hide bottom virtual buttons
show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
set number of bottom log rows to show
pause on logs mode: no more miss logs during zip installs
auto dim screen after user configurable delay
auto turn off screen after user configurable delay
adjust brightness and turn off screen with a gesture action
show/hide clock and remaining battery %, even during nandroid operations
clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
toggle vibrator on/off on touch
toggle key repeat for volume up/down scrolling when maintained pressed
key repeat also enabled for virtual buttons
set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
capture recovery screen shots with a gesture action (only some devices)
basic theme support
one file to save all settings
backup and restore settings file
backup and restore only GUI settings
reset to default settings option
prompt to restore your settings from a backup when they are wiped by a new ROM install
option to auto restore your settings from a backup without a prompt
all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
toggle menu options are automatically right aligned and menu text left aligned based on device display size
configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
true JB 4.2 migration: toggle between /data/media and /data/media/0
Secure recovery lock with passkey
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
cancel nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors backup/restore in stock clockworkmod or TWRP modes
advanced power options menu
detailed build info in About menu
Click to expand...
Click to collapse
What's working/not working
I have been testing it and all the basic functions (backups, instalations, partitions, brightness, touchscreen, etc) is working without problems as some extra features of the recovery, but i didn't test everything. In summary, is a completely functional recovery.
Instalation instrucctions:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To flash it to the recovery partition:
Code:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
Once finished reboot your device by pressing power and volume up to boot on the recovery.
Download link
Please do not make mirror of the download link, thanks you.
https://www.androidfilehost.com/?fid=745425885120721868
Credits
- eloygomez from HTCMania as the original recovery is from him
- @Koush for having created and maintaining cwm
- CyanogenMod
- @Tallustus from Team Skyfire for his great support over IRC
- @Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- @Chenglu for his unpacking tools and porting i9505
- kbc-developers for the base semi-touch code and much more
- [email protected] for his great job / support
- @sk8erwitskil for his recovery source, a great place to start learning
- @shoe63 for his help from the start across many devices
- @DooMLoRD for his work and help with Sony
- @[NUT] for his ports to Sony
- @wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- @dougiebee for his work on fixing time on many Qualcom devices
- @ausdim for all the support in developing kernels for i9505
- @dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- @Chainfire for his support (stock recovery flash) and all his work for the Android community
- @Phil3759 for the great original thread which is based mine.
- @ThePhantasma for pushing me to open this thread.
Contributors
@mustang_ssc
Created: 04/04/2017
Last update: 04/04/2017
Useful topics:
- Everything Huawei Mediapad T1 10
- How to root our device: Credits to @mann1
Reserved 2
Finally, we have a working recovery for this device! I am glad you share this.
Time to share the good news! :good:
@ThePhantasma for pushing me to open this thread.
Click to expand...
Click to collapse
Thank you.
Thank you for the recovery. Any custom ROMs available??
dilipg98 said:
Thank you for the recovery. Any custom ROMs available??
Click to expand...
Click to collapse
Not yet, i will try to make the stock rom of our device flashable with custom recoveries and after that i may try to port a CM11 or MIUI.
Anyway, that's not my main purpourse, the priority for me is to fix the issues of the kernel source in order to get completely updated recoveries and roms (TWRP 3.X, LineageOS 14.1, Slim7, etc).
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Mo3ta9em93 said:
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Click to expand...
Click to collapse
Here i put a complete topic for it:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
mann1 said:
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
Click to expand...
Click to collapse
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
mustang_ssc said:
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
Click to expand...
Click to collapse
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
mann1 said:
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Click to expand...
Click to collapse
Looks really interesting, i think i never tried to port anything from that device.
It surprise me to see you got a TWRP 3.X to boot, i never got any one to boot. I will try to port some recoveries from that device but i guess to have the same issues that you have because i think i have been doing the same porting procedure you used.
The problems with the touchscreen may be the dtb file but I'm not sure why it happens because in this recovery is working fine, but I'm sure it will be related to incompatible screen resolution and touchscreen parameters (X and Y axis).
Also I've tried to compile many times a completely updated TWRP recovery directly from the source (and also LineageOS 14.1) but the main problem is the kernel source of our device which it gave me a lot of errors. Casually i think the main problem about this is a missing dts file exclusively for our tablet which indicates the screen parameters, and should be located at arch/arm/boot/dts/qcom/huawei_t110p0_a21l of the kernel source folder. Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
I might try what you told me about use the y550 source files to see how it goes. If you want anything feel free to contact me
mustang_ssc said:
Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
Click to expand...
Click to collapse
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
mann1 said:
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
Click to expand...
Click to collapse
I sent you a PM :good:
mustang_ssc said:
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
Click to expand...
Click to collapse
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
PinkOstrich said:
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
Click to expand...
Click to collapse
For now i have 4 different roms: CarbonROM, Pac-Man, CM11 and MIUI8. Obviously (and unfortunately) all of them based on kit kat as i cannot make the kernel source to work.
Now the main problem is that the camera and flash is not working, and a weird bug with the play store that doesn't allow to use it. This last one i don't find it logical as it shouldn't be a rom bug but i have tried many gapps and always getting the same bug (error rh-01)
The camera bug is not very relevant considering that our device is a tablet but if i can fix the play store issue i will probably upload some of the roms while i keep trying to fix the camera and flash.
wifi issues with rooted Mediapad T1 10 T1-A21L
I have access to quiet a few of these tablets (Mediapad T1 10 T1-A21L) - like more than 100 They have been used for various wifi-based demonstrations.
Recently they have begun showing an error message "Unfortunately IntegratedTest has stopped working", like every 2-5 minutes and their storage is filling up with very large logs files (which I also contribute to the IntegratedTest application). I haven't found anyone else with this issue.
The IntegratedTest application is a system app and cannot be removed without root. So I decided to try and follow the "- How to root our device" guide and root one of the devices and remove the application - which succeed. However now the wifi doesn't work.
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
jpihl_ said:
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
Click to expand...
Click to collapse
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
mann1 said:
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
Click to expand...
Click to collapse
Thanks for your response. I tried to follow your instructions - unfortunately without luck.
What I did:
1. "Full unroot" -> Removed SuperSU App (also su command no longer works - as expected) but still can't enable wifi.
2. Ran fastboot flash boot boot.img -> still can't enable wifi
3. Ran fastboot flash recovery recovery.img -> still can't enable wifi
Which leaves me with "still can't enable wifi" :/
{
"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"
}
A Mobile Version of the Ubuntu Operating System
Ubuntu Touch is made and maintained by the UBports Community. A group of volunteers and passionate people across the world. With Ubuntu Touch we offer a truly unique mobile experience - an alternative to the current most popular operating systems on the market. We believe that everyone is free to use, study, share and improve all software created by the foundation without restrictions. Whenever possible, everything is distributed under free and open source licenses endorsed by the Free Software Foundation, the Open Source Initiative.
For more information check out the UBports website.
Known issues:
Recording video doesn't work
Changing volume in-call doesn't work
Contribute:
As not everything is working fully yet helping hands are welcome!
Follow the project management issue over at the Halium GitHub page:
https://github.com/Halium/projectmanagement/issues/98
Instructions (tested on Ubuntu 18.04):
First make sure to wipe /system & /data from within TWRP. The partitions must be ext4.
Make sure to upgrade your device to the latest stock Android 8.0 before continuing: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Download and install the UBports installer: https://github.com/ubports/ubports-installer/releases
OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.
Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using:
Code:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Run the UBports installer and follow the on-screen instructions
Reserved for future use
wtf bro i never expected to see ubuntu touch on any device again great news and good work! keep it up!
Too bad my device broke......gotta fix fast lol
I've updated download links and the instructions to enable call functionality. Testers welcome!
Ready for tests! Just need to install Ubuntu with current manual
Have I need to flash stock rom with android 7 or just flash binaries on stock android 8?
New tests to be done, we've recently gotten video decoding to work and I enabled basic camera support.
OP has been updated with the link to the newest images.
Feel free to post issues here if you are not feeling well with GitHub.
Regarding stock ROM or not:
Any system image should work, you can even wipe system as it's not used.
As long as the ODM partition is flashed everything should be good.
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
samijam said:
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
Click to expand...
Click to collapse
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
beidl said:
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Click to expand...
Click to collapse
Sorry for the late reply. I got it to work now. My problem was using an outdated system.img and boot.img. (oops, sorry, my bad!) I had downloaded the newer versions, but had them in the wrong directory. Once I deleted the old and installed the correct versions, I was able to get audio in calls and had the basic camera functionality.
---------- Post added at 16:43 ---------- Previous post was at 16:37 ----------
matiz098 said:
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
Click to expand...
Click to collapse
boot into fastboot and flash the oem:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
then boot into twrp recovery and wipe /system and /data
while in twrp, run the halium-install.sh script (because the computer needs to connect to phone in adb mode, which twrp provides)
following from there, as you see in the first post, you will run "adb reboot bootloader" (but I think I did have to do it manually) which should put you back into fastboot mode where you'll "fastboot flash boot halium-boot.img"
then you should be able to reboot into ubuntu. The first boot takes a little longer.
Are there any screenshots available?
Fajormein said:
Are there any screenshots available?
Click to expand...
Click to collapse
No but you can find some videos on YouTube, just search for "Ubuntu Touch 2019".
The videos might feature different phones but it's the same on the Xperia X.
Is there any way to install it using a windows pc?
Fardin Rehman said:
Is there any way to install it using a windows pc?
Click to expand...
Click to collapse
Not currently.
please make a porting for kugo (x compact) sir
rizky_zulfikar said:
please make a porting for kugo (x compact) sir
Click to expand...
Click to collapse
Someone else is working on that already, but this port is only for the Xperia X (F5121).
In other news:
Installation instructions have been updated, the Xperia X port is now available from the UBports community channel!
Can you make port for XA 2 (H3113)
As I get the question very often: To support the F5122 variant of the Xperia X (or other devices in general) for Ubuntu Touch I need donations to buy the device.
Use the "Donate To Me" button on XDA or head over to https://fredl.me/donate/ for info on how to do so.
In other news: The Xperia X F5121 has gained support for the official UBports installer. You can now flash the device using a fancy GUI.
I hit 2 problems. For some reason neither Emma nor flashtool wants to flash stock rom correctly. Tried to flash ubuntu through stock 8.0 custom rom, phone reboots and black screen. Also there is was an error with something that the file couldn't be sent to the phone
Click to expand...
Click to collapse
Ok, so I did install the stock rom through EMMA fine. I did enable the usb debugging, installed twrp, wiped system & data, made sure they are EXT4. Rebooted to fastboot, installed SW binaries. Opened UBports Installer & proceeded with instructions. I got this error
Code:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"C:\\Users\\domin\\AppData\\Local\\Temp\\1Uo4H80AYPnCivmpnC8M9LLWxLb\\resources\\app.asar.unpacked\\platform-tools\\win\\adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
Any solutions, did I miss something? I gonna retry without the twrp step, as I am pretty sure the partition format will be EXT4