Related
Team Win Recovery Project 3.0.0.x ONLY For MS01LTE SM-G7105
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.
Phone look:
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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.
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.
DOWNLOAD:
ON post #2
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.
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Nice job perfectly working in 7102.
Bro how can I flash this recovery???????
Thanks a lot for helping ms01lte???
Sanjay8787 said:
Nice job perfectly working in 7102.
Click to expand...
Click to collapse
This is only for Lte
Yuen.Jason22 said:
Bro how can I flash this recovery?������������
Thanks a lot for helping ms01lte������
Click to expand...
Click to collapse
No u need to use flashify to flash this
What will happen if there is a failure in flashing?? I can't brick my phone in this period before I get a new one
Yuen.Jason22 said:
What will happen if there is a failure in flashing?�� I can't brick my phone in this period before I get a new one
Click to expand...
Click to collapse
If this wont work then u can flash another recovery from odin it will repair
how to install
adityaupreti said:
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Click to expand...
Click to collapse
İ'm on motion rom v17.my 7105 allways open download mod when i flash with flashify.
SM-G800H cihazımdan Tapatalk kullanılarak gönderildi
hey friends
diid it work for samsung galaxy grand 2 duos g7102?
plz reply fast:crying:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I root the device using "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Then after rooting (I understand that I can't install the recovery without root first), and without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP 3.0.0 recovery.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
mouadk said:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I flashed root rom "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP recover.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
Click to expand...
Click to collapse
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
SoUnd001 said:
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
Click to expand...
Click to collapse
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
mouadk said:
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
Click to expand...
Click to collapse
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
SoUnd001 said:
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
Click to expand...
Click to collapse
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
mouadk said:
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
Click to expand...
Click to collapse
You need to flash kitkat firmware with odin
SoUnd001 said:
You need to flash kitkat firmware with odin
Click to expand...
Click to collapse
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
mouadk said:
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
Click to expand...
Click to collapse
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
SoUnd001 said:
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
Click to expand...
Click to collapse
Thank you. Unfortunately there are no updates, says "your device has the latest updated" !
It seems my cell provider decided they don't want to upgrade it.
TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variantshttps://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)
Remember to do backup of your current recovery before installing
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.
No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds.
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.
I downloaded and installed (from twrp.me the new version 3.2.0-0 of the TWRP recovery for our Honor 7 and installed it using version 3.1.1-0. Installation OK but the device remains locked on bootlogo. I reinstalled version 3.1.1-0 with fastboot and the phone started without problems. I reinstalled version 3.2.0-0 with fastboot, the installation was successful but the phone remains locked on bootlogo. Has anyone tried?
yes, I did today and the same problem. I'm using 3.1.1.0
i wrote a message to Team TWRP and they removed v3.2.0.0 from the download site.
The TWRP team has released version 3.2.1-0-plank.img for the H7. Same problem as 3.2.0-0 except that this time the phone succeeds in rebooting in normal mode, but can not reboot in recovery (locked on bootlogo)... Back to 3.1.1-0 ... wait & see
p.s: I warned them
I thought the twrp team was a serious team. But do the recovery tests before publishing them?
no they don't test every release....
i assume there is an automatic build structure - as soon there are a new 'core'-version of twrp the changes are pushed to the device specific trees and at night the build will produce a new recovery for all devices....
TWRP 3.2.1-0 removed from the download site.
Hi, TWRP team response: "Thanks for the report. I will disable the job until the device tree is fixed. The files have been removed."
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Dattel01 said:
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=818070582850504177
thanks for your reply...
in the meantime i switched the device and my old H7 will have its eventide in the hand of my wife
Is you link a working copy or is it still the old version that crashes?
Twrp
Why there is no option for honor 7x in twrp?
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_blanc_0.1.img - initial test release
twrp_bkl_0.2.img - OEMinfo partition is available for backup
twrp_bkl_0.3.img - /cache mounting is fixed,backup /vendor as image (vendor still can't be mounted)
twrp_bkl_0.4.img - /vendor mounting/unmounting is now fixed (thx @ante0 for the script)
twrp_bkl_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
twrp_bkl_0.6.img - Cache wiping issue is now fixed
twrp_bkl_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
Pretoriano80 said:
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Click to expand...
Click to collapse
Thanks man! :laugh: Need to test this!
IcipherPT said:
Thanks man! [emoji23] Need to test this!
Click to expand...
Click to collapse
No problem! Please report back if it's working or not.
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
wipe everything to decrypt?
ngoralph said:
wipe everything to decrypt?
Click to expand...
Click to collapse
Nope, just decrypting, like you do when your phone is starting and asks for PIN! [emoji6]
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
@youtuber123
did you try a nandroid backup?
youtuber123 said:
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
Click to expand...
Click to collapse
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Pretoriano80 said:
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Click to expand...
Click to collapse
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
youtuber123 said:
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
Click to expand...
Click to collapse
There's not much stuff to flash for this device! [emoji16]
Good, finally a useful twrp....
Can we flash LOS using this now?
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
kurvenmeister said:
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
Click to expand...
Click to collapse
Which version? Another user reported that is working.
Edit: More details about your device?Which version do you have exactly?
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
kurvenmeister said:
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
Click to expand...
Click to collapse
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
kurvenmeister said:
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
Click to expand...
Click to collapse
The custom rom might be the culprit!I didn't tested on custom roms.
Pretoriano80 said:
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
Click to expand...
Click to collapse
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img does work fine.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also just fine.
I'll let you know how it goes :fingers-crossed:
Hope we get 8.1 kernel sources soon so I blu_spark this blue beauty
Rommco05 said:
I succesfuly make full backup (except data) and flashed busybox. I dont need decrypted data all seems to be fine. In backup section just missing OEM
Click to expand...
Click to collapse
Latest version should have Oeminfo available for backup! Did you tested that version?
eng.stk said:
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img did.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also jsut fine.
I'll let you know how it goes :fingers-crossed:
Click to expand...
Click to collapse
Hi! My favourite kernel developer is here, nice!
I have a guess on what may be wrong, but i'm not sure. Let me know if you figure out! [emoji6]