Quantcast
Channel: admin » TWRP
Viewing all 1595 articles
Browse latest View live
↧

Building for bacon: question about TWRP and libncurses.so.5 missing

February 24, 2016, 11:30 pm
$
0
0

Hey Guys,

So happy that there’s a new AOKP coming. I’d like to work towards Device Maintainer. I’ve got a 1+1 that I want to get going first, then I’ll look at your list of other phones that need maintainers. I have two current issues:

1) My 1+1 is running MultiROM TWRP 2015-08-03 (v2.8.7) and multi-rom v32k tramponline v26. I have two 4.4 ROMS but my AOKP ROM seems to be having issues with the kernel. So my question is: can I just blow away my current roms and flash AOKP-Marshmallow?

2) I’m trying to build for Bacon using the Barbeque (Arch) linux distro. When running make I get the following:
$ time make rainbowfarts
…
Header: /home/russellh/Android/AOKP/out/target/product/bacon/obj/include/time-services/time_genoff.h
host C: mkbootimg <= system/core/mkbootimg/mkbootimg.c
prebuilts/clang/linux-x86/host/3.6/bin/clang: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
build/core/binary.mk:817: recipe for target ‘/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o’ failed
make: *** [/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o] Error 127

#### make failed to build some targets (01:01 (mm:ss)) ####

real 1m0.514s
user 0m22.750s
sys 0m16.210s

So I checked what is installed:
[russellh@barbeque AOKP]$ pacman -Ss ncurses
core/ncurses 6.0-4 [installed]
System V Release 4.0 curses emulation library

I tried creating a symbolic link to libncurses.so -> libncurses.so.5 but that didn’t work.
Any suggestions would be great.

Thanks,

Russ

↧
Search

Official Recovery for Zenfone 2 Laser TWRP 3.0.0+ Z00T Z00L

February 25, 2016, 1:42 am
$
0
0

Here is the Official TWRP builds for Zenfone 2
ZenFone 2 Laser 720p Z00L & 1080p Z00T

Download

↧
↧

HTC one M8 official Android 6,0- Sense 7 root and twrp?

February 25, 2016, 5:33 am
$
0
0

Hi i am the proud owner of an htc one m8,
But i’ve been wanting to root my android 6,0 device and could not find any tutorials on how to do this on this android version and install twrp aswell.
Now i was wondering if it is the same as on Lollipop or is there not a devellopmend threat yet?
I would love it if you guys could help me,
Tim
P.S its an international version

↧

TWRP 3.0.0.0 for Marshmallow?

February 25, 2016, 12:21 pm
$
0
0

Hey guys,

as you might know, the ‘standard’ TWRP is not compatible with Marshmallow and has to be patched. There are several images of a patched 2.8.7.0 available in the forum.
I took one of these and compared the files with the standard version of TWRP for the S6 edge.
So I figured that the changed files are ramdisk/sepolicy and also the kernel.

Kernel in standard 3.0 seems to be the same which is used in 2.8.7.0.
After knowing all this, I tried to modify the existing version of TWRP 3.0 with the modded kernel and the sepolicy file from the modded 2.8.7.0. I repacked the thing, flashed it and…

…… IT BOOOOTS!

…..but only once :(

When I restart the device (doesn’t matter if I go to system or recovery), it won’t ever again enter the new recovery.
Maybe you can help me figure out, why this is happening (or you can try it for yourself).

Are there any logs I can look at?

↧

[Q] Fire HDX 7″ (Thor) Unlocking Bootloader and Installing TWRP

February 25, 2016, 12:30 pm
$
0
0

Hey Guys,
I just got the Fire HDX 3rd Gen and would like to get Cyanogenmod on it.
It is running FireOS 4.5.5.1 right now and i would like to know if there is a way to unlock the Bootloader and how to install TWRP :p
I read through some threads but didnt find an answer since i cannot downgrade to 3.2.3 =(
Hope you guys can help me fix that.

Thanks in advance :)

↧
↧

I’ve Lost TWRP and unable to reinstall it and Unable to root with SuperSu

February 25, 2016, 12:33 pm
$
0
0

I think I screwed the pooch here… 😮

I tried to update TWRP to 3.0.0.2 through TWRP 3.0.0.0 and chose the recovery partition. Didn’t work and have lost all TWRP functions, unable to reboot into recovery mode.
I tried to do it through the CMD screen and didn’t work either.
Then tried to install TWRP as an apk from Google Play and rooting with SuperSu via Google Play… it won’t update the binaries though.
I have the S-ON too.
Any suggestions or help available, I am quite frustrated. The phone is working though as I have a CM Nightly 6.01 version installed.

HTC phones are a little more difficult (for me at least) compared to the LG G3 I had and the One PlusOne.

Thanks in Advance

↧

Lost twrp recovery by flashing another recovery on LG G2 VS980

February 25, 2016, 8:31 pm
$
0
0

On my LG G2 VS980 I lost my TWRP recovery by trying to flash CWM Touch. Now when it boots into recovery I see a black screen with some tiny writing that instantly disappears back into a black screen and stays there until I hold power down for about 15 seconds. Originally I had stock 26A (KitKat), rooted with Stumproot and used Autorec to put TWRP on and that worked fine. Then I flashed CyanogenMod 12.1, that worked fine. Today I decided since I had CyanogenMod, I would try out their Touch recovery instead of the older TWRP. I downloaded Flashify and the latest CWM Touch recovery and downloaded Flashify and flashed the recovery with no error messages. I gave it root permission (the built-in CM root permission) and then booted into the mess I have now. I have tried to flash TWRP, but it does the same exact thing- same for trying CWM regular (non-Touch) recovery flash. None of the button combinations except power + up buttons do anything except boot into the regular phone or they boot into the broken recovery that shows the white writing that turns to the black screen of death. I tried going into settings and turning the developer settings on that says Update Recovery When Updating ROM, but that doesn’t change anything. I also tried using ROM Manager, but it never worked flashing, even before. (It still does the same thing, it acts like it flashes, says its successful, then the recovery is the same. Useless.)
One thing that is odd is that I tried to use Autorec again. I downloaded the latest version from Play Store and when I tried to flash recovery with it it told me my phone was not supported- that it only works on VS980 model!?! That IS my model. So that’s the gist of it. I really would appreciate any help at all. I love my phone.

↧

Note II dead with only access to Odin and TWRP – cannot access file systems

February 26, 2016, 9:31 am
$
0
0

I woke up last week to a dead phone. It had been running the same rom for months so that is unlikely to be the cause.

TWRP cannot mount anything. Not even the sd card which does work on another phone. I can also get into Odin.

I tried factory reset in TWRP but it just complains it can’t mount the file systems. If I try Advanced-Repair Filesystem it gives me an error 16 which is "Inconsistent filesystem structure".

It would seem that the equivalent of the partition table has gotten corrupted. Is there a way to low level format the phone and start over?

Cheers,
Tim

↧
Search

[UNOFFICIAL][G920F] Official Android M -bootloader- compaitable TWRP {2.8.7.2}

February 26, 2016, 12:31 pm
$
0
0

Hi guys

I repacked @bigbiff ‘s TWRP Recovery (2.8.7.2) with latest Adam kernel by @wanam , so we got a proper working custom -SELinux permissive- recovery on official Android M bootloader

Bugs;
– Vibration not working
– MTP not working and it can cause ADB failure. Disable it.

THIS IS NOT TWRP-FLASHABLE ZIP!!!

You can install it via Odin. I also uploaded official 6.0.1 bootloader (U3DPAD) if you need.

↧
↧

[INFO][ TWRP & CyanogenMod for Huawei G8 & GX8 ]

February 26, 2016, 4:37 pm
$
0
0

Hello !

I’ll start to work on this device very soon …

Actually, I already managed to make a functionally recovery ( TWRP ) . Also I’ll start soon on CyanogenMod !

Because I have ONLY G8 version (dual sim) , I need some info from GX8 .

Please, if someone can post here a result of this command :

Quote:

> adb shell
> cat proc/app_info

For starters , I need only this information, as we later I’ll request further information …

Thank you very much for your help .

Best regards !

↧

Tested Guides – Root, Unlock Bootloader and Tethered TWRP On ZE500CL

February 26, 2016, 5:33 pm
$
0
0

Hello there!
I’ve noticed the resources for us using the ZE500CL variant of the ZenFone 2 line of phones are few and far between, so I decided to make this list of methods I personally tested for rooting, unlocking the bootloader and temporarily flashing TWRP (tethered recovery).
I apologize in advance if I’m breaking any forum rules, but I’ll make sure to credit everyone who’s guides and files I’ll be presenting here. I am only posting this to help fellow ZE500CL in finding all the necessary tools and methods for various things they need. None of the tools and guides below are my work, all credit goes to their original creators.

I’ll update this when I test more things, so keep an eye on this post in the future 😉

Root

Both methods worked for me, but I’d still recommend the second method in combination with temporary (tethered) TWRP in the last guide. Credit: @Chinaphonearena

Guide:
http://forum.xda-developers.com/zenf…3/post60872347

Unlock Bootloader

So, we’ve finally officially got the Bootloader Unlock tool from ASUS. It was uploaded in the "Driver & Tools" section on the ASUS ZenFone 2 ZE500CL official page just yesterday (I’ve checked it two days ago, it wasn’t there, so it was most likely yesterday). I’ve got the information from this ZenFone 2 ZE500CL ZenTalk Forum post.

You can download it from here:
ZenFone 2 (ZE500CL) – Support

Please note: Only do this is you’re absolutely sure you know what you’re doing. Your warranty will be void and you will not receive further OTA updates. I am not responsible for damage to your device.

Temporary (Tethered) TWRP

This works like a charm tethered, but I didn’t try flashing it. When I do, I’ll update this post with new information. If any of you try it before me, please say if it worked here. This was, after all, not built specifically for the ZE500CL. Credit: @TheSSJ

Guide:
http://forum.xda-developers.com/zenf…2/post61076508

I hope this was helpful. Again, the only intention of this post was to help out fellow ZE500CL users, since it’s hard to find necessary tools for this device.

Thanks to all the wonderful people of XDA for working on the projects and helping out in the forums!

↧

[Request] TWRP v3.0.0 for E7

February 26, 2016, 10:33 pm
$
0
0

Please can anybody provide
me the latest TWRP Recovery
v3.0.0 for SM-E700H?

Thanks

↧

facing overheating issues with new twrp 3.0.0-1

February 27, 2016, 3:39 am
$
0
0

my device heats up to 88° c while flashing, and taking back up. any soln?:p

↧
↧

About TWRP Nandroid backups.

February 27, 2016, 6:25 am
$
0
0

Hi guys!
Is it possible to move from MM to LP or from LP to MM by restoring from a TWRP Nandroid backup? Can one of the expert members please answer this? If that’s possible then, that makes life so much easier for all of us. All we need a collection of clean TWRP Nandroid backups for all versions and a TWRP recovery that is compatible with MM, LP and KK.
I’m asking this because I tried to update my L09 B331 to B5113 using the normal method (update.zip…) but it stops in the recovery mode at %5 and gives me a failed to update message!
Anyone have a solution? or an answer?
Thanks! :)

↧

VS980 On CyanogenMod 12.1 Lollipop lost TWRP 2.7.0.0 trying to flash CWM Touch

February 27, 2016, 10:45 am
$
0
0

I had my LG G2 VS980 (Verizon) on stock 26a KitKat with root and TWRP 2.7.0.0 recovery and I flashed CWM 12.1 using TWRP which worked great. I still had the TWRP recovery, which I believe uses an exploit on a 24a KitKat. Then, I decided to try CWM Touch recovery and used Flashify to download and flash, which, by all outward appearances seemed to work. (It gave success notification.) Then, after rebooting into recovery, it showed the LG boot logo, then black screen with tiny white writing that scrolled down about 4-6 lines, and then disappeared into a black screen that can only be escaped by holding the power down for about 10 secs. It boots into phone just fine (thank God), and if I hold the up + power at boot, it still shows download firmware mode, and if I hold the down + power and release and repress again at LG logo, I still get the Restore Factory screen, which is promising, but I am extremely reluctant to try that since I have no idea what would happen after upgrading to CWM 12.1 and my recovery is in the shape that its in. One thing that’s interesting that no matter which app I use to try to flash a TWRP or CWM recovery, it always seems to flash too fast to be really doing anything at all, and it always goes back to that same tiny white writing then black screen. Also, another weird thing is that if I try to use Autorec which I downloaded to try to flash TWRP that way, it says Invalid Model, VS980 4G required, but that is what I have. Anyone who can figure this out and I will rename my firstborn after them! Thank you.

↧
Search

[RECOVERY] [tate] TWRP 3.0.0 touch recovery

February 27, 2016, 3:29 pm
$
0
0

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.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!

Test build 20160217: coming soon
fastboot -i 0x1949 flash recovery tate_recovery_150227.img

restore old recovery:fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img

↧

[RECOVERY] [jem] TWRP 3.0.0 touch recovery

February 27, 2016, 3:31 pm
$
0
0

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.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!

Test build 20160217: http://www.mediafire.com/download/gn…ery_150227.img
fastboot -i 0x1949 flash recovery jem_recovery_150227.img

restore old recovery:fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img

↧
↧

As long as I have a Nandroid backup in TWRP, can I modify system files such as…

February 27, 2016, 4:30 pm
$
0
0

As long as I have a Nandroid backup in TWRP, can I modify system files such as Mixer_Paths.xml to increase my volume on a LG Phone without having to worry about it corrupting and me having no sound on my phone? Please Answer, thanks :)

↧

g pad uk410 intalled TWRP to bootimg slot

February 27, 2016, 7:29 pm
$
0
0

i rooted my us cellular uk410, got in a hurry and installed TWRP zip to the boot image zip slot and never boots. now it’s essentially soft bricked. is there any way to recover my tablet?

↧

How to Convert .tar Stock ROm to .zip TWRP Flashable ROM

February 27, 2016, 9:29 pm
$
0
0

Hello members and devs on XDA
Anyone here knows how to convert .tar Stock rom into .zip flashbale
This could be the only way on how to downgrade COJ5 > COi4/COH4

↧
Viewing all 1595 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>