Sent from my SM-G920F using Tapatalk
As part of this process I’d tried to ise TWRP v3.x to disable Syste, Data to be unchanged before loading the custom firmware. For some reason I was unable to complete this process. So I thought of completely follow the steps given in the original thread.
So I’d decided to downgrade TWRP to v2.8 via Mobile Uncle. The mobile was restarted as part of this process and got into Factory mode. Since then I’d followed multiple steps including back to Stock ROM. But there was no success as the mobile is not detectable via fastboot. The mobile is detected in ADB but as unauthorised. When tried with YGDP the phone was detected but it was unable to switch it to download/flash mode.
Please help me to get this issue resolved. I’m completely stuck with this issue. Thanks a ton for every one’s understanding help prompt help/suggestion/support
Note: re-posting in the general Q&A forum for more views and support.
So today i just wanted to make a flashable update zip, so, i have the zip archive with 2 folders, one is the META-INF, the other one is system, (the system folder is empty!)
And now, when i flash the zip in twrp, i’m getting:
Updater process ended with ERROR: 6
My update-script looks like this:
set_perm_recursive(0, 0, 0755, 0644, "/system");
ui_print("- Mounting...")
mount("ext4", "MTD", "system", "/system");
ui_print("- Installing...");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("- Done, Enjoy!");The only thing what i wanna do is that the /system gets mounted, then, the system should install, and then, /system should be unmounted.
Can someone help me? I have a HTC One M8 and TWRP 3.0.0.1. Thanks.
How To Install via Flashtool
– Extract the zip
– Put the correct android scatter into 1 folder.
– For Android One rom use MT6580_Androidone_blablabla
– For Infinix Rom use MT6580_infinix_ROM_blablabla
– Flash it.
How to Install via Flashable Zip
– Go to TWRP (NOT STOCK RECOVERY)
– Just install the zip
– Reboot recovery
– Done.
Credits:
– Joseph Godslave (For the flashable zip 
)
– Jemmini (For compile this TWRP)
– All Infinix Hot 2 Android One Users
– bbs.infinixmobility.com
– And you :p
How can I fix those 2 errors E: Could not extract to ‘file_contexts': Read only file system and E: Error creating fstab
How can I fix those 2 errors E: Could not extract to ‘file_contexts': Read only file system and E: Error creating fstab
I want to do a full wipe in TWRP, system, data, cache, all of it. I want to know if I’ll lose root. If I will, what is the best way to re-root a Samsung Galaxy S4 in 2016? All the threads I saw on this forum are years old and we’ve had firmware updates since then. Any help is appreciated. Thank you.
What u need
Twrp google play has it
Instructions
1 download twrp der
2 install it make sure u have unknown sources ticked
3 open app
4 click device name
5 find ya phone
6click it
7 under install click first one
8 find right file for ya phone look at build jblah flex
9 know instapl it follow promps know u have latest twrp what ****s over cwm and others
For noobs dont install custom kernals they easy to **** up on will post pics once on pc
How to apply :
1. Download file
2. Install Flashify on PlayStore
3. Open Flashify and click Recovery image
4. Select recovery.img and select Okay
5. After flashing, reboot to recovery via holding POWER + HOME + Vol. Down
Download : https://www.androidfilehost.com/?fid=24421527759886751
Thanks to TWRP Team.
DO NOT APPLY ON G850F
I’m a user of XDA-Developers for about 10 years and never needed to create a thread asking for help because I always solved my problems after many many researchs.
But this time…It will make me crazy. I’m on that for many days, hours and nights. I read almost all threads on xda and google about this blasted phone.
Don’t know what to do anymore.
I got a G2 16gb D805 variant (latin america) with JDI panel.
It’s already rooted with IOROOT method.
And I can’t install TWRP. No way.
Everytime I use AutoRec it blows my screen with white lines and I need get into Download Mode and get back to Stock using FlashTool + KDZ.
Dudes, please.
How can I install TWRP on this ****?
If I can’t install TWRP, how can I get a custom ROM, like CloudyG2 on it?
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:
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.
One of the reasons I gota 128 GB SD card is so that my backup for nightlies install are complete…. So…. What now? I’m out of ideas. BTW there is plenty of room to create the backup
I have successfully flashed twrp 3.0 using adb but when i reboot to recovery, i keep getting cyanogenmod recovery. Romtoolbox even says twrp is my current recovery. What’s the deal? I want to make a backup using TWRP before I flash anything. How do I go back to TWRP?
Thanks!!!
Sent from an alien spaceship