[RECOVERY][h815] TWRP 2.8.6.0 touch recovery [2015-06-02] - G4 Original Android Development

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.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
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.
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 NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.

Note, only for H815 with bootloader unlocked!
Device specific page.
Download page with current and past versions.
Thanks to @wolfgart for testing!

Yes yes yes!

Dees_Troy said:
Note, only for H815 with bootloader unlocked!
Device specific page.
Download page with current and past versions.
Thanks to @wolfgart for testing!
Click to expand...
Click to collapse
:good:
TWRP'd and rooted
{
"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"
}

Great work guys.
Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.
But how do we get root @wolfgart?

nickfury said:
Great work guys.
Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.
But how do we get root @wolfgart?
Click to expand...
Click to collapse
once you have TWRP'd just flash supersu.zip

I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.
Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version

nickfury said:
I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.
Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version
Click to expand...
Click to collapse
Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though

Daptonic said:
Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though
Click to expand...
Click to collapse
So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?
Sorry I don't have the t version on me right now to try it out, but will do in a couple of days

So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?

nickfury said:
So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?
Sorry I don't have the t version on me right now to try it out, but will do in a couple of days
Click to expand...
Click to collapse
I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.

the_scotsman said:
So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?
Click to expand...
Click to collapse
Correct, if you have the h815 model

nickfury said:
Correct, if you have the h815 model
Click to expand...
Click to collapse
Yep, sure do. Tempting...not too fussed about about warranty, but would rather not void it if another way is found soon. What are the chances of this? I'd guess not very likely? I'm only familiar with HTC, no LG dev.

Daptonic said:
I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.
Click to expand...
Click to collapse
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
 @the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol

nickfury said:
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
@the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol
Click to expand...
Click to collapse
Nah, warranty isn't a priority. I always unlocked and rooted my HTC flagships on the day I got them. I'm just new to LG, but it's not really any different. Just need to take that step and void it :laugh:

nickfury said:
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol
Click to expand...
Click to collapse
I understand that I need the file ... for the official method. But that doesn't mean some crafty dev here @ XDA won't come up with a way that doesn't need it. Also, since the 815T, which I have, is NOT currently supported by the official unlock tool, your reply is moot.
There is subtle difference between going to their site, putting in my info and clearly voiding my warranty versus using an unofficial method and maybe sneaking in a replacement if things go pear shaped. I'm not worried about voiding my warranty, but why burn a bridge for no reason?
I thank you for your concern, but this isn't my first rodeo.

Can i use unlock the bootloader for h815t from LG?
Arent they (h815t & h815 for eu) the same?
I am confused....

EDIT: Ignore, didn't see the multiple pages.

calchung said:
Can i use unlock the bootloader for h815t from LG?
Arent they (h815t & h815 for eu) the same?
I am confused....
Click to expand...
Click to collapse
No the H815T is for the Hongkong market not EU. I too have the H815T interesting to see if the unlocking tool works for this version. It might since its a 815 base model. :good:

Waiting for 818P

Related

[RECOVERY/M8_UL_CA] TWRP 2.7.0.4 Touch Recovery [2014-04-09]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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:
What's new in 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://androidfil.es/1mMD
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
Glad to see you here JMZ!!
Hi I'm trying to get a recovery flashed on my phone and I've been working with mike1986 for a couple hours and for whatever reason my phone refuses to flash it. Every time I run the fastboot flash recovery command it gets to: sending 'recovery'... and then just hangs there indefinitely until I reboot. Any ideas? Thanks!
im getting cache errors in the recovery.
fix-this! said:
im getting cache errors in the recovery.
Click to expand...
Click to collapse
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
jmz said:
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
graffixnyc said:
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
Click to expand...
Click to collapse
you on freenode anywhere?
jmz said:
you on freenode anywhere?
Click to expand...
Click to collapse
Not at the moment. I'm in class. I should be home on a couple of hours
Sent from my HTC One_M8 using Tapatalk
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
jmz said:
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
Click to expand...
Click to collapse
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
graffixnyc said:
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
Click to expand...
Click to collapse
What format is your sdcard in
Sent from my HTC One_M8 using Tapatalk
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Fidelio_o said:
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It should just be
Code:
fastboot flash recovery recovery.img
The "adb" at the beginning isn't necessary.
fix-this! said:
How is this different from the one posted in the international m8 section?
Click to expand...
Click to collapse
I'm curious to know too.
fix-this! said:
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
Click to expand...
Click to collapse
Tikerz said:
I'm curious to know too.
Click to expand...
Click to collapse
this is built from source. Not ported from M7. plus this supports external sdcard
im getting error: cannot open recovery.img
NEVERMIND IM AN IDIOT
Uploaded a new version. 2.7.0.2 This has working offmode charging
{
"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"
}
Having the same issue with my SD card as above. 64gb SD formatted in exfat. System uses it fine for photos etc...
Sent from my HTC One_M8 using Tapatalk

[Toolkit] Mac OS X Toolkit for unlocking, flashing, rooting

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.

[2014-09-22] [MT2-L03] TeamWin Recovery Project

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.

[TOOL] Android Job Box v3.21 [Aug 1, 2017] [Un/Lock | Bak/Res | Recovery | Optimize]

{
"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

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S23 Ultra

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 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.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S23 Ultra S918B/S918N/S9180.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S23 Ultra: AFH: dm3q twrp
3. Reboot to download mode
4. Uncheck auto reboot in Odin and flash TWRP in AP slot and vbmeta_disabled_R.tar in USERDATA slot.
5. Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
6. Go to wipe, format data, and type "yes" to confirm.
7. Reboot to TWRP
8. Flash boot_repack.zip (To fix stock recovery restoration)
9. Flash magisk canary (Optional)
10. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Decryption will only work if no password/PIN/pattern is set in Android.
- No erofs r/w support yet.
Thanks:
TWRP team
@BlackMesa123 for helping me to add encryption support
@dr.ketan for supporting me​Donators
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
mine
afaneh92 said:
Bugs:
- Encryption not fully working.
- No erofs r/w support yet.
Click to expand...
Click to collapse
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
BlackMesa123 said:
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
Click to expand...
Click to collapse
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
afaneh92 said:
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
Click to expand...
Click to collapse
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
BlackMesa123 said:
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
Click to expand...
Click to collapse
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
afaneh92 said:
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
Click to expand...
Click to collapse
We can surely work it out to fix it
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
BlackMesa123 said:
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
Click to expand...
Click to collapse
I hope so.
Nice work!
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
I just want to ask if anyone has tried installing viper4android yet and does it work? If it's like the s22 ultra and doesn't work. I might sound crazy but I wouldn't buy it. Music is more important to me then spen and camera although admittedly they are good to. It's mind blowing to think 1200 dollar won't sound as good as my Poco f3 or even my lg tribute 10 years ago.
lcd047 said:
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
Click to expand...
Click to collapse
I have exactly the same:
- after following all steps one by one there is only a reboot into TWRP itself possible
I compared the steps from this thread with the steps which are successfully working on my Galaxy Tab S8 Ultra ( https://forum.xda-developers.com/t/...-for-galaxy-tab-s8-series-snapdragon.4455491/ ) and I see a difference at step 7:
7. Flash custom kernel and magisk apk in twrp.
Click to expand...
Click to collapse
I do not see any "custom kernel" to download in this thread (at least for now) so I think this is the missing part. Or it only works correct in combination with "dr.ketans rom" (which I do not want to use for now).
@afaneh92: Thank you very much for your work (on "root" and also with "twrp")!
Edit: I just read the installation pdf from "dr. ketans rom". There is written in red letters:
DON'T run multidisabler from TWRP termial/zip or any system-rw script after flashing ROM else device won't boot.
Click to expand...
Click to collapse
So maybe the not booting system is related to the work which the "multidisabler" should do.
I will be happy if there will be some light regarding the non booting system after flashing TWRP.
Maybe I will give "dr. ketans rom" a try and have an eye on this thread how the things go on.
________________________________________
@Techguy777: This is very offtopic but I am with you that "Viper4Android" is a very important part also of my daily used tools. I just have found a (for me) good running workaround.
Search the fDroid store for the app "RootlessJamesDSP". Depending on which parts of "Viper4Android" you care about, the app is an extremely good working replacement. In my example, the "Convolver" with the impulse response files are important and that works wonderfully with the players I use.
hurray said:
I will go back for now to (rooted) stock ROM and Recovery and will have a look how this thread will go on.
Click to expand...
Click to collapse
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
lcd047 said:
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
Click to expand...
Click to collapse
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
hurray said:
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
Click to expand...
Click to collapse
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
Yup, flashing the full ROM works. Many thanks, and keep up the amazing work!
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
hurray said:
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
Click to expand...
Click to collapse
I have seen many users don't want "custom" roms, but my ROM will have complete stock look + single click all critical fix. It won't force users to use customised look. Also it have more options to make modifications in ui but everything will be by user's will.

Categories

Resources