Database Develop

[RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27]

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.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.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

You should be able to root using Kingo App or through this towelroot port: http://forum.xda-developers.com/not...t-adb-ghettoroot-v0-1-towelroot-port-t2864125
Device specific page with install instructions.
Mirror with all current and past TWRP versions.

I am wondering why TWRP official site only carries US based models? Whereas we in Asia have a whole multitude of TWRP versions for hundreds and hundreds of models. Even if it is not officially released by TWRP Team it should at least have another "sponsored" site for TWRP collected all over Asia and have its own depositories.Then the official TWRP sites would pales in comparison if somebody would have collected TWRP from unofficial sources. I am using TWRP recovery strictly on my ROMs and only as last resort CWM.
This TWRP official site doesnt do justice to itself and you expect users /modders to download TWRP Manager App from Playstore when we all know that we would never ever find the TWRP version for our devices.??

Please support s4 mini sprint (sph l520).

cracktech said:
I am wondering why TWRP official site only carries US based models? Whereas we in Asia have a whole multitude of TWRP versions for hundreds and hundreds of models. Even if it is not officially released by TWRP Team it should at least have another "sponsored" site for TWRP collected all over Asia and have its own depositories.Then the official TWRP sites would pales in comparison if somebody would have collected TWRP from unofficial sources. I am using TWRP recovery strictly on my ROMs and only as last resort CWM.
This TWRP official site doesnt do justice to itself and you expect users /modders to download TWRP Manager App from Playstore when we all know that we would never ever find the TWRP version for our devices.??
Click to expand...
Click to collapse
I do appreciate your comments. Please allow me to add a few of my thoughts. TWRP is an open source project. When we set out to build TWRP we decided to make it open source in the beginning because we knew that being open source would allow the project to grow and spread much faster than if we tried to keep it closed source. We know that being open source would lead to lots of unofficial builds. The high number of unofficial builds was exactly our intent and we are happy to see so many unofficial builds out there.
The bulk of TWRP development is done by 2 to 4 people. The core work of building official TWRP and adding new devices is the work of only 2 people: myself and bigbiff. Both of us are located in the USA so it's only natural that the supported devices will have a strong trend towards USA devices. We are open to working with other developers to add devices. Many of the devices in our officially supported were added with the help and assistance of other developers like yourself porting TWRP to their device. After those developers port TWRP to their device, they contact us and supply device trees and testing so that we can add that device to our official list.
If you have a device that is not officially supported, feel free to port TWRP to the device, then supply your device tree to us so we can get it added for official support and continue to release new updates of TWRP for the device. We can't afford to buy all of the devices ourselves and many of the devices aren't available in our country anyway. We depend on the support of other developers to help reduce the burden of support and porting. Reducing this burden also helps us focus on what we do best: adding cool new features to TWRP for everyone to use.
We aren't going to take the time to comb the Internet for TWRP builds that may or may not work and that may be incomplete or improperly done. Many of the posts of these unofficial versions are in other languages that we cannot read without translation. We try to maintain a high quality product and it would be a bad idea for us to do this, especially when we would have no way to fix the problems.
I can confirm that we are working towards supporting multiple languages within TWRP. My hope is that the additional language support will cause TWRP to spread even more and reach more people who are unwilling or unable to use a TWRP that isn't in their native language. I'm also hopeful that more developers will reach out to us to add their devices and that more people will get involved with translating TWRP to other languages.

Thanks for your response! at least I know that the TEAM is an open source , open minded TEAM. I am not a developer per se as you all are ( I consider you all as the Gurus and I am just half a student) We need to have a depositories of all the versions thats flying around out there ( the bad side to the open source approach is when somebody made a blunder out of the Recovery but using the "TWRP" brand) like I recently experience when I tried to wipe dalvik-cache/cache it corrupted and removed with "root" and system partition. Luckily I had another backup and was able to use that version to RESTORE but after that I told my users to uninstall the so called TWRP 2.8.0.0 and revert back to 2.7.1. This would tarnish the TEAMS name as I exclusively port my ROMs with only TWRP 95% of the time. Anyway thanks again for your response , maybe I will set-up a depositories of TWRP and link up with the main TWRP depositories.
---------- Post added at 06:34 AM ---------- Previous post was at 06:18 AM ----------
I dont want to recommend Kingoroot/or other one-click root other than Vroot since it doesnt have any funny name files scattered all over the system folder (for example KingoRoot uses the name KingoRoot.apk as the Superuser app this might cause some problems when other Superuser app needs to replace another "Superuser.apk" app and in the xbin folder , instead of "su" binaries (be it Chinese "su" or otherwise) the Kingoroot renamed it "ksu" and that files are sometimes also left in the "bin" folder and they becomes orphan but operational files. (Maybe I got the names wrong but I know that KingoRoot doesnt follow the normal naming rules) Whereas Vroot/iRoot (as it now called) uses "Superuser" and "su" nomenclatures for easier recognition by e.g Chainfire SuperSU = "Superuser" and "su" binaries. and dont leave behind any orphan files. Vrot/iRoot has 98% success rate in rooting unrootable devices as I had experience. No need to test out any exploits just one-click root from PC and within 3-5 minutes you're all done!

Kazam Tornado 348 AKA. BLU Vivo Air AKA. Gionee Elife S5.1
Someone can check if that can RUN with BLU Vivo Air or Gionee Elife S5.1 ... Because Tornado 348 is EXACTLY THE SAME PHONE... Just a RE-BRAND to can be more Likely to a specific market =D
Gionee -> Asian/ Chinese Market
BLU -> North/South America
Kazam -> Europe Market i Think...
Anyone can check the reviews... SAME OS, SAME HARDWARE, SAME PHONE... ;D (I Will replay that on BLU Vivo Air General Topic)

I've had no luck getting twrp to work on my gionee elife s5.1
Tried flashing with mobileuncle, fastboot and "dd" through android terminal.
After flashing, a reboot to recovery just boots to fastboot...
-- edit --
Twrp manager app is still a no go -although it seems to be playing nicer after replacing the iroot/vroot superuser with superSU, the recovery partition location warning before installing is simply /dev/recovery. This is not the location on my device...
-- end edit --
The Chinese cwm for the gionee s5.1 floating around out there does work for me. Flashed it in fastboot...

The driver you used to get fastboot work is from where?.. We stay making a huge progress with Blu Vivo Air topic... The ideia is fuse kazam tornado menu topic with blu vivo air menu topic... And we stay in touch with Russian developers from 4PDA too... They have some news and i think their MiUi v6 work with your Gionee phone ;D

I can't find Kazam device in the TWRP Manager . Now I don't know how to install the recovery

Hello . Any other way to install twrp as i have a locked phone . Cant remove passcode. I had it laying around for some time and i cant find the password. Any idea ? thank you

Work Container Detection

I have been trying to do dynamic analysis of an app that has to run in work profile (container).
When I activate the phone with the UEM, the phone is instructed to create a work profile but fails because the phone has been rooted in order to install the Xposed framework:
Cannot create work profile
The security policy prevents the creation of a work profile because a custom OS has been installed on this device
The device is a Samsung S7 with the warranty void flag set to 1.
Is there a way to create a work container on a rooted phone (could be Samsung or any other model)?

Dynamic analysis of Android for Work apps
Has anyone had any success using dynamic analysis tools like Inspeckage with Xposed on rooted devices to assess apps that must run within the Android for Work container?
Is this something that "Test DPC" can help with? The Test DPC app failed to run in a physical rooted device because it could not create the work profile ater it detected a custom OS. However it seemed to get further on a virtual rooted device if I disabled encryption. Unfortunately I am having other issues with Genymotion virtual devices that is hampering my ability to proceed.

elmo8klay said:
Has anyone had any success using dynamic analysis tools like Inspeckage with Xposed on rooted devices to assess apps that must run within the Android for Work container?....
Click to expand...
Click to collapse
This topic has been discussed on the following thread and you may be able to obtain some member guidance within it as well.
https://forum.xda-developers.com/showthread.php?t=3681139
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

OUTDATED! [Project] Galaxy OStool

#####################################################################################################
This project is outdated! If you were interested, stay tuned on latest posts on my profile. A totally re-coded and re-designed version of this tool will be rolling out soon!
#####################################################################################################
---------------------------------------------------------------------------------------------------------------------------------------
First of all I must admit, that i can't create a DevDB post instead (I don't have permissions, or something).
--------------------------------------------------------------------------------------------------------
Recently, i used Androxyde's Sony FlashTool, and I had an idea to create something like this, but for Samsung devices.
That's how Hackaye's Galaxy OStool was created.
It's based on VB.net and Heimdall CommandLine.
You may ask: Mate, but what the heck is it for? We have Odin and Heimdall Frontend!
Yeah, but can Odin and Heimdall download firmware for your device and install it with one click?
Do they have One-Click Root and TWRP installation options?
I guess not.
The app is currently available for Windows users, and requires latest .NET Framework installed.
---------------------------------------------------------------------------------------------------------
How to use the OStool:
Choose your device from the list (currently only Galaxy S5 SM-G900F but if the project gets some fame, i'll add more )
Then click what you want to do, you can choose Repair/Re-stock, Rooting with Chain Fire's AutoRoot, or installing TWRP.
After selecting, the program will download all the necessary files from my MediaFire account, and will notify you, that it's ready to flash.
You will be instructed how to go to download mode (the program is directed to begginers, so i had to add that), and will prompt you to install Zadig drivers, if needed.
Then after clicking the red "FLASH!!!" button, a CMD windows will appear with heimdall running, informing you about the installation progress.
----------------------------------------------------------------------------------------------------------
Some info about the project:
I am open to contribute with anyone that has knowlege about VB.net coding, i am also looking for better server to host files on, so please tell me if you know about one
Also, I couldn't test the program, cause my PC is autistic, and I can't install the necessary Zadig drivers, which ends with Libusbx error -12 (PLEASE HELP ME HOW TO FIX THIS!!!)
You should also know, that this version is only for testing the engine, the GUI will be TOTALLY redesigned.
If you want to contribute, download the SPECIAL Dev Pack from the link below. If you only want to test it, download a standard setup.
That's all from me,
Hackaye (WHY I CAN'T CHANGE MY NICK FROM EUKON TO HACKAYE?!!)
----------------------------------------------------------------------------------------------------------
Download Links:
OStool v0.1a Standard Setup: bit.ly/2LSRz9T
Dev Pack link (You need to have standard version installed first!!!): bit.ly/2O6jrVn

Super-root vs Root

I want to start a thread cuz I think it's confusing to "only root" your device. (I personally hate Unix based system btw, the way they handle processes in intelligent multi thread way unlike windows which concentrates on one process based on its priority, Mac otherwise work on dm ready structure)
In Android and WINDOWS, SELinux there is LSM (AKA SYSTEM) (also Sudo) which is root (system user). System user > Admin user > Basic user > Quest user as well as root (kernel service) > index root > service root > service user > low level services.
Root. In order to become true root not only system user you need usually to flash custom recovery. But this way it's possible to become fake device Super-root to obtain the 0-index kernel service permissions Linux distro is needed to be installed.
Super root is a startup service such as stock recovery. In order to become true Super-root you need to perform rooting actions such as flashing TWRP or CMS. The custom recovery however won't backup kerning-based oses.
Hyperoot would be network (shell) service
And meta-root would be hardware engineering service. This is f. e. Use modified processor of the microntec car head unit with IC service in order to be able to use sound card different way.
So these are different levels of managing and servicing the devices. Then the root and Jailbreak (of Android phone too even if it's open source project) is clearly the different things
Servicing the phone (also cracking but it's rather bad thing)
1. Unlock phone (bootloader)
2. Customise system (custom recovery)
3. Root/system user
4. Obtain all partitions
5. Flash modules (not only software of internal card)
6. Assembler hacks and kerning, overclocking, adding ram etc.
Mtc 916
Hacking the phone
Will be 1, 2, 3, 4 and 5
Google Nexus, Hackintoah
Rooting (full root) the phone
Will be 1, 2, 3
Most devices
Hardness: Huawei > Manta > Nokia > sony > Acer > Asus > lg > one plus > google
Debunk phone
Will be 2, 3
Some Acer decices like s1
Simple root of a phone 3 only
Lyf flame and exotic phones from mgsm
Jailbreaking the phone
2* (apply customisation, become superuser)
Some unnown models and IPhone of course
Tweaking the phone
1 and 2*
Symbian devices, custom bloatware
What do you think, let's talk ;D
BTW As I have a lot of knowledge of computing, scripts and C in Microsoft visual I always have been soft hardware bricking my devices cuz I am dull and can't think abstractive math lab way xd
DEMANDS
Give us the hacking guide rather with rw FIXES! I don't want to spend hours typing stuff into twrp or cmc recovery (AdAway, magisk and so on)
Edit as of 19.3.19
Aroma device - is unlocked and extended device
Types of bricks:
Softbrick - "nice bootloop", simple flash from twrp or pulling system.img is enough usually
Modbrick - OTA bootloop, may require mod tool like flash tool
Hardbrick - QUSB - lack of fastboot, EMMC CMOS controller related problems, needs patents to retrieve, so its basically dead phone (when no boot at all and no signs of life, device is called "dead-boot" or "no screen device")
BAnD (Broken Android Device) is term describing hardware related problems with phone. Its not as serious as hardbrick.

Same thing :/

Potato. :good:

KlarkDevlin said:
Does root go to a new level?
Click to expand...
Click to collapse
YES
Actually smartphones are more complex than desktop pc and the trends such as Meizu Zero are begin to happen.... In the past we have had writeable system, now even the root is restricted. Until this I had always been using one click root tools, nowadays I need to spend often weeks to gain FULL administration rights to my devices (including but not limiting only to TA Backup, booting custom recovery to backup all partitions, flashing prepatched rom (along with kernel - the root of root), gapps, magisk, xposed). And it somehow hardbrick itself without reason (smartphone is working, but after one month it simply wont boot). These drms are so stupid, these companies should learn from Windows.
One of better brands: Google, Oneplus
More likely to be broken but easier to root: LG
Avoid these brands: Samsung, Verizon, Apple, Xiaomi (bad hardware I quess, but good performance)
Preferred type of rom: stock vanilla without bloatware, AOSP ones (not AOKP due to problems with ogyoutube).
!!!
The new trend by developers that occurs lately is freakin annoying, every Rom should come prerooted using universal method (magisk) and the rest should be hosted on github (clean Rom and super su Rom, Eventually tool like pfr creator). The rooting is harder than NASA microkernels oses really due to the varying versions.
!!!
BTW this is proposition by me of perfect microcomputer
(micromobile)
Other

Rooting Android 9 TV (University project, no harm intended)

I have a Sharp Aquos LC-32Bi6E Android 9.0 smart TV and I need to install my own certificates for a university project (I need to set up a transparent proxy and no, unfortunately, I cannot change the project). Searching online I've found the only solution to be rooting the TV and then install those as system certs.
I never rooted anything (certainly not a TV) so I have no expertise in the field. I have tried with the main apks such as KingRoot et similia but none of those work (device not supported).
I am trying to explore the TWRP recovery + Magisk option but I am stuck.
Anyone can help or suggest another solution?