Related
Hello!
This is development thread of TWRP Recovery v2.8.0.0 by NovaFusion.
Credits:
marcin1147
Macław
Huge thanks to TWRP team.
You can get it from http://novafusion.pl/.
Download is directly provided from our servers - it's fast, stable and fully resumable!
If you appreciate our work, please, use thanks button!
XDA:DevDB Information
TWRP v2.8.0.0, Kernel for the Samsung Galaxy S III Mini
Contributors
New Macław, marcin1147
Kernel Special Features: Only one recovery with full KitKat support!
Version Information
Status: Stable
Current Stable Version: 20140911
Stable Release Date: 2014-09-11
Created 2014-03-11
Last Updated 2014-09-11
Changelog
20140911 (v2.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 1440×2560, 280×280, and 320×320 resolutions and update 240×240
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
What's new in 2.7.1.1 from 20140720?
upstream changes in TWRP
updated kernel
device updates
What new in 2.7.1.0 from 20140612?
full f2fs support for S3 Mini!
What's new in 2.7.1.0?
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don’t have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
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
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
Downloads
All releases are available for download from:
http://novafusion.pl
Download is directly provided from our servers - it's fast, stable and fully resumable!
Sources: http://github.com/NovaFusion
Thanks
Sent from my GT-I8190 using Tapatalk
:thumbup::thumbup::thumbup:
Great, Thanks!
Awesome work. Thanks a lot Mac & Marcin, you guys rock:good:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
Will check right now Of course if it's true, we will fix it as soon as possible.
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
New Macław said:
Will check right now Of course if it's true, we will fix it as soon as possible.
Click to expand...
Click to collapse
Just make a backup (stored on the sd card) & works flawless, so...:good:
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
TWRP Backup and restore from and to sdcard works. Also apps like helium works with my 32gb sdcard.
Also ok for me. Thanks for fast reply guys!
Ok, i flash recovery and works fine. What about SElinux, is still disabled?
Backup to and restore from extSd is working without any issue for me. Good work!
Btw : I like the Panda in recovery :thumbup:
Silly question maybe...
Why use this one when the official TWRP (now at 2.7.0.1) is available? Is there a subtle difference that means this works when theirs doesn't?
(Edt: having asked the dumb question - I discover that the "official" download appears to be a 10 KB empty tar file! *laughs*)
giociampa said:
Silly question maybe...
Why use this one when the official TWRP (now at 2.7.0.1) is available? Is there a subtle difference that means this works when theirs doesn't?
Click to expand...
Click to collapse
TWRP team doesn't support s3 mini anymore, so, Marcin made his magic, just for us
mauam said:
TWRP team doesn't sipport s3mini anymore, so, Marcin made his magic, just for us
Click to expand...
Click to collapse
So I've just discovered (see edit above)
giociampa said:
Why use this one when the official TWRP (now at 2.7.0.1) is available?
Click to expand...
Click to collapse
Are you sure?
http://teamw.in/project/twrp2
Not even for the N7² it has a newer version.
Hi. i flashed previous version from cwm so i have twrp . for update flash new version with twrp or odin ?
Thanks.
mahdik.m said:
Hi. i flashed previous version from cwm so i have twrp . for update flash new version with twrp or odin ?
Click to expand...
Click to collapse
With TWRP
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.
TWRP 3.0.1 Changelog: http://teamw.in/site/update/2016/04/05/twrp-3.0.2-0-released.html
Installation instructions: Download the latest available version from the link below, and flash it using with THIS APP (requires root).
DOWNLOAD: https://dl.twrp.me/armani/
* More info: https://twrp.me/devices/xiaomiredmi1s.html
* TWRP manager app doesn't have the latest official builds of TWRP, so to avoid installing old versions it's best not to use the 'App Install Method'.
Device repo: https://github.com/TeamWin/android_device_xiaomi_armani
* The kernel is based on cm-13.0 kernel source: https://github.com/armani-dev/android_kernel_xiaomi_armani
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the Xiaomi Redmi 1S
Contributors
owaisnaim, fefifofum, Dees_Troy, Kra1o5
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Stable Release Date: 2016-04-01
Created 2014-10-16
Last Updated 2016-04-14
CHANGELOG:
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
3.0.0-0
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks.
i already have twrp so how to update the recovery.
garva1 said:
i already have twrp so how to update the recovery.
Click to expand...
Click to collapse
To do update on your phone
1.Download the latest Recovery '.img' file
2.Download Rashr from play store
3.Use recovery flashing method in Rashr(Manual or offline-The Auto flashing have old TWRP)
4.Done & Enjoy
Mate, u should've asked to me about posting that, no problem this time, but official xda rules say u must first ask to the original thread author...
Dark-Nightmare said:
Mate, u should've asked to me about posting that, no problem this time, but official xda rules say u must first ask to the original thread author...
Click to expand...
Click to collapse
Sorry for that I haven't seen u in xda that's why I hve posted..
If u want to take over the thread then I can surely close this thread..
owaisnaim said:
Sorry for that I haven't seen u in xda that's why I hve posted..
If u want to take over the thread then I can surely close this thread..
Click to expand...
Click to collapse
No problem this time, but always try to meet XDA Forum rules, mate.
Dark-Nightmare said:
No problem this time, but always try to meet XDA Forum rules, mate.
Click to expand...
Click to collapse
because this is original developer section is a MUST to change the owner of the thread. That's the rule in XDA.
Xiaomi Redmi 1S has official TWRP support, and Dees_Troy is using this for the builds: https://github.com/armani-dev/twrp_device_xiaomi_armani
From my point of view, there is no need to change the owner of this thread. Also, there is no need to point to the htcmania thread, that was the "official" one before Dees started using the code in armani-dev (on september 23rd).
will i lost stock recovery by flashing TWRP ??
ngakan.made said:
will i lost stock recovery by flashing TWRP ??
Click to expand...
Click to collapse
Yes...!
You can flash stock Recovery anytime you need though ! It's available here in this forum (Search it )
Added @Kra1o5, @jsevi83, @Dark-Nightmare as the contributer of the thread,
report... not working on official rom v45, signature verification failed
I am not able to access my external SD card. Is this a bug!?
Sent from my HM 1SW using XDA Premium 4 mobile app
Not working in V45
ngakan.made said:
report... not working on official rom v45, signature verification failed
Click to expand...
Click to collapse
Same here.
ngakan.made said:
report... not working on official rom v45, signature verification failed
Click to expand...
Click to collapse
nithishsaji said:
Same here.
Click to expand...
Click to collapse
Guys....if the zip not working for you (like it didn't for me in Mi Recovery )
1.Download latest .img file of twrp site
2.Download Rashr-Flashtool from playstore
3.Open Rashr and choose recovery
4.Navigate twrp .img (Since online is old-in Rashr )
5.Choose it and Confirm !
6.Done
Note : You need Root for this
Doesn't work from v43, what I had done was flash cwm and then flash twrp through that
If you just someone who posted this for others to download, how are you one of the "contributed"?
@Kra1o5.... Any Plan for MultiRom bro :fingers-crossed:
ngakan.made said:
report... not working on official rom v45, signature verification failed
Click to expand...
Click to collapse
First properly unroot the phone.
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11
Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.
Yup... just the system partition.
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.
YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !
DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks
sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers
Ok, will test it now without wipes
redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully
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.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Unofficial TWRP 3.0.2-8 for Elephone P9000
Mirror 1
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
[RECOVERY] Unofficial TWRP for Elephone P9000, Tool/Utility for the Elephone P9000
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_elephone_p9000/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-8
Stable Release Date: 2016-08-24
Created 2016-07-26
Last Updated 2016-09-11
FAQ:
Attention ROM Devs - You need to update your ROM's updater-script to use the correct by-name parts for this recovery, the old M2 ported one had this:
Code:
/dev/block/platform/mtk-msdc.0/by-name
The correct by-name parts for the Elephone P9000 are:
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-8:
-Updated Kernel to an early version of my DarkSense kernel
-Possible fix for F2FS support (if it doesn't work we have a few theories as to why)
3.0.2-7:
-Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
3.0.2-4:
-Fix USB-OTG Mounting
3.0.2-3:
-Use Toybox mount and grep
3.0.2-2:
-Fully built from source for Elephone P9000 - unlike the other one which was ported (repacked recovery.img) from the Elephone M2
Current TWRP "bugs" for Elephone P9000:
NONE
Jonny said:
Current TWRP "bugs" for Elephone P9000:
NONE
Click to expand...
Click to collapse
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.
andy radical said:
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.
Click to expand...
Click to collapse
Done, the Mega link has been renamed to Mirror 1.
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Thanks, I'll look into it.
3.0.2-4:
-Fix USB-OTG Mounting
andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Further info on the battery meter issue. I spoke to some of the guys over on the twrp freenode IRC channel and after a bit of experimentation it turns out that this is an issue with the way the kernel links to the battery level, some proprietary lib or bin is needed to help link them, at this moment in time I haven't a clue which one but I'll keep looking.
Does this work on P9000 Lite?
Jtig said:
Does this work on P9000 Lite?
Click to expand...
Click to collapse
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.
3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
Jonny said:
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.
Click to expand...
Click to collapse
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
Jtig said:
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
Click to expand...
Click to collapse
I just don't particularly like doing blind builds, never have done.
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
fatalhh said:
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
Click to expand...
Click to collapse
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs
Jonny said:
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
fatalhh said:
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
Click to expand...
Click to collapse
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs
Jonny said:
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
Really confusing my friend.....I am newbie in the side of rooting....flashing....etc.....and reading a lot to learn.....everytime I flash something my stomach get butterflys.....like when you are in love:laugh::silly:
Thanks mate
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
Jonny said:
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
Click to expand...
Click to collapse
Hi @Jonny, when I backup with twrp i must choose every voice or i must untick system image? Thank you
Inviato dal mio P9000 utilizzando Tapatalk
Build 16/12/2018 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower Oreo 8.1.0_r52 30.0 LineageOS #laos #OnePlus #OMS #SubstratumRootLess
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
Please be sure you are using one TWRP that can handle firmware flash and can decrypt sucessfull.
Your TWRP also need to be hable to mount and flash vendor partition.
Starting on O 25.0 the required firmware its 5.1.5 and is treblish, you need to have the vendor partition created, if you dont have you need to follow this steps:
Flash firmware 5.1.4 on TWRP
https://sourceforge.net/projects/ch...firmware/firmware_5.1.5_oneplus5.zip/download
Reboot TWRP
Flash firmware 5.1.5 on TWRP
https://sourceforge.net/projects/ch...firmware/firmware_5.1.5_oneplus5.zip/download
Reboot TWRP
Flash TugaPower O 26.0
Reboot phone
Relative to gapps, the advised ones is nano package ( ARM64):
http://opengapps.org/?api=8.1&variant=nano
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Full support to Substratum OMS RootLess without Andromeda
Powered by Magisk root v16.x
Direct unlock with face like OP5/OP5T OOS, credits to PixelExperience team
Safety Net checks patched to pass ( thanks to @Sultanxda )
Three fingers screenshot
WireGuard Support added
What does not works:
Let me know to add here
Changelog: TugaPower O 30.0
Magisk updated to latest canary version
Project name: proprietary_vendor_oneplus
msm8998: upgrade blobs from 5.1.7
Project name: android_device_oneplus_msm8998-common
msm8998: upgrade to 5.1.7
Project name: android_device_oneplus_cheeseburger
cheeseburger: update fingerprint
cheeseburger: require 5.1.7 firmware
Project name: android
manifest: android-8.1.0_r50 -> android-8.1.0_r52
Project name: android_frameworks_base
GlobalScreenshot: Fix screenshot not saved with some languages
ClipboardService: Restore different method calls to AppOps to fix PG
SystemUI: Clean duplicated CONFIGURE_WIFI_DISPLAY permission
Make adb use a custom prop for adb root
Rotation related corrections
Project name: android_packages_apps_Trebuchet
Trebuchet: move to default screen on home intent
Project name: android_packages_apps_SetupWizard
SetupWizard: fix SpannableString (Privacy Policy)
Project name: android_packages_apps_Settings
Make adb use a custom prop for adb root
Project name: android_packages_apps_LineageParts
PartsActivity: Prevent actionbar NPE
Project name: android_packages_apps_Messaging
Messaging: Add "Mark as read" quick action for message notifications
Allow intent shared subject or title to be mms subject
Project name: android_packages_apps_Bluetooth
Bluetooth: Clean duplicated READ_CONTACTS permission
Project name: android_packages_apps_LockClock
Release the wakelock before worker thread termination
Project name: android_packages_apps_Contacts
Project name: android_packages_apps_TvSettings
Make adb use a custom prop for adb root
Show Trust in security settings
Add button to shut down device
Project name: android_packages_apps_Exchange
Rename translations for new language code mapping
Project name: android_bootable_recovery
Fix making adb use a custom prop for adb root
Make adb use a custom prop for adb root
Project name: android_device_qcom_sepolicy
legacy: Resolve hal_gnss_default denial
Project name: android_device_lineage_sepolicy
common: Allow adbd to set a system_prop
Label lineage.service.adb.root as system prop
Project name: android_vendor_lineage
common: Allow custom vendor to override properties
Project name: android_hardware_qcom_power
power: Drop default POWER_HINT_INTERACTION routine
Project name: android_system_core
Make adb use a custom prop for adb root
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/OREO/TugaPowerO30_OP5.zip
MD5: cde6e88ef9d0bd947215e5b4f998288a
Please dont mirror for now the roms zips, thanks
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/LineageOS/android_device_oneplus_cheeseburger
Kernel:- https://github.com/LineageOS/android_kernel_oneplus_msm8998
Reserved for bug reports
Two thread! :/
Volte working?
ShiShTuBaBu said:
Two thread! :/
Click to expand...
Click to collapse
Where ?
Edit: See now, probably some bug on XDA creating the thread, asking to delete the other one
Cheers
G0dofWar said:
Volte working?
Click to expand...
Click to collapse
Dont have way to test because on my country ( France ) there is no network provider that uses VoLTE, try and let me know if is working.
If not working have few stuff to you guys to test if make it working.
danieldmm said:
Dont have way to test because on my country ( France ) there is no network provider that uses VoLTE, try and let me know if is working.
If not working have few stuff to you guys to test if make it working.
Click to expand...
Click to collapse
Downloading will report back!
This ROM is only for decripted device?
AleAndroid96 said:
This ROM is only for decripted device?
Click to expand...
Click to collapse
No, this rom works on encryption, assuming you current base is compatible, factory reset, flash rom, flash gapps, try to boot, if dont boot, remove the encryption and repeat the steps, after setting up phone it will be encrypted by default.
danieldmm said:
No, this rom works on encryption, assuming you current base is compatible, factory reset, flash rom, flash gapps, try to boot, if dont boot, remove the encryption and repeat the steps, after setting up phone it will be encrypted by default.
Click to expand...
Click to collapse
Thanks for the ROM, I will try on my decrypted device using noverity zip and report.
I'm on the encrypted RR 6.0, I did a factory reset, clean system, date and cache and flashed this rom with the gapps.
When the phone was restarted after the boot logo, the recovery started.
AleAndroid96 said:
I'm on the encrypted RR 6.0, I did a factory reset, clean system, date and cache and flashed this rom with the gapps.
When the phone was restarted after the boot logo, the recovery started.
Click to expand...
Click to collapse
And did you removed the encryption you have ?
Also prior to remove the encryption try again this, factory reset, flash rom, flash Gapps, factory reset again, then try to reboot the phone. If still a no go probably is the encryption you have the issue, remove encryption and repeat steps, then after setting up phone it will be encrypted by default.
To remove encryption I must format the sd from twrp, right?
To remove encryption I must format the sd from twrp, right?
Click to expand...
Click to collapse
Yes
OOSCAM with Portrait?
How I promise just flashed on my decrypted device with MicroG package with the unofficial installer (tried opengapps unofficial but setup crash), all seem working fine.
Thakyou very much for this great Rom
idelnon said:
OOSCAM with Portrait?
Click to expand...
Click to collapse
No portrait on OOS Cam except on one and only one custom rom as of now.
VampireHeart said:
How I promise just flashed on my decrypted device with MicroG package with the unofficial installer (tried opengapps unofficial but setup crash), all seem working fine.
Thakyou very much for this great Rom
Click to expand...
Click to collapse
Wich Gapps did you flashed? The Setup FC is probably issue with gapps package. But if you like MicroG just stick with it
danieldmm said:
Wich Gapps did you flashed? The Setup FC is probably issue with gapps package. But if you like MicroG just stick with it
Click to expand...
Click to collapse
I tried the nano gapps from the link in the op, rebooted but not solved so flashed microG.
VampireHeart said:
I tried the nano gapps from the link in the op, rebooted but not solved so flashed microG.
Click to expand...
Click to collapse
Like said before, if for you MicroG is good and you do not need of Gapps stick with that, if you need Gapps check the thread of gapps in OP and read last pages, they talk about setup fc and a fix is on the way.
Cheers