[RECOVERY][TF700T] TWRP 3.1.1-0 touch recovery [2017-05-19]

Search This thread

MartyHulskemper

Senior Member
Jun 5, 2008
1,597
443
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

the last couple of days I've been trying out some different roms and done a few backup and restores back and fourth. What I have done is restored Clean ROM Inheritance over a Baked Bean 7 installation and now my entire previous SD-card content has been moved to a folder called 0 and a new root folder has been created. Furthermore, TWRP (2.4.0.0 btw, I've updated to 2.4.1.0 but the problem prevails) doesn't recognize this structure, but instead shows the sdcard/0 as my root folder, and going up a level from there takes me to the root folder, not the sdcard folder I see on my computer or via ES.

Any advice on how to fix this? I am considering some sort of major reset and re-installing everything, but do you think that will work? I am a bit worried that this will mess up further flashing and so on so I would very much appreciate any ideas you might have about this issue!

Thanks in advance, but more are obviously coming to any replies ;)

Has been handled on the last page of the CROMI thread as well, by chance. The fork is created by AOSP ROMs, I gather, and you could try and rename itand see what happens. Your data are still in there then, and if nothing unusual happens, you might just delete that folder. Read sbdags' advice, though: if it actualy is still in use and you delete it, you will lose your data! (Can you back all the files up to FTP or the cloud?)

Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.
 
  • Like
Reactions: BloomTwig

Apollos_eyes

Senior Member
Apr 9, 2011
74
11
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

I've had the same problem twice tonight. Locked up solid whilst choosing options in 2 different aroma scripts.

Is there a problem with the latest version?

What was your battery level when you were installing in Aroma? I've heard from different sources that aroma doesn't like your battery level to be below 70% when flashing/patching. I was told the safest method is to actually have the charger plugged in if under 70%. I think it's an aroma bug not TWRP.

Sent from my LG-LS970 using xda app-developers app
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,558
Kenilworth, Coventry
OnePlus 9 Pro
What was your battery level when you were installing in Aroma? I've heard from different sources that aroma doesn't like your battery level to be below 70% when flashing/patching. I was told the safest method is to actually have the charger plugged in if under 70%. I think it's an aroma bug not TWRP.

Sent from my LG-LS970 using xda app-developers app

Probably below 70%, but why would Aroma not like that?
 

_that

Recognized Developer / Inactive RC
Oct 2, 2012
4,821
4,211
Can you get logcat and/or dmesg via adb when it hangs? Or is it completely dead?
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,558
Kenilworth, Coventry
OnePlus 9 Pro
Can you get logcat and/or dmesg via adb when it hangs? Or is it completely dead?

I have never got adb working with TWRP. Works fine with CWM and when in OS. I switch regularly to CWM to reodex as scripts don't run on TWRP and it has never once hung on CWM.

It happened rarely on 2.3.1.0 , it was one in ten on 2.3.3.0, and it was very frequent o 2.4.1.0.

When it locks it locks good. Only way out is a 10 second power boot.
 

_that

Recognized Developer / Inactive RC
Oct 2, 2012
4,821
4,211
I have never got adb working with TWRP. Works fine with CWM and when in OS.

adb works fine here with TWRP - maybe you have the wrong OS on your desktop PC. :D Maybe you are expecting a wrong serial number using -s or ANDROID_SERIAL? TWRP reports "0123456789ABCDEF".

I switch regularly to CWM to reodex as scripts don't run on TWRP and it has never once hung on CWM.

Scripts should also run on TWRP since it has Busybox installed...

When it locks it locks good. Only way out is a 10 second power boot.

Ouch, that could mean that adb also doesn't work. Would be interesting if it does. And check /proc/last_kmesg after such a reboot, maybe it contains relevant info.
 

Apollos_eyes

Senior Member
Apr 9, 2011
74
11
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Probably below 70%, but why would Aroma not like that?

This was the explanation ,
"One of the BIGGEST issues most if not all Aroma issues come from are having inadequate power when flashing. Aroma is VERY sensitive to the strangest things on the phone. If there are errors in a previous flash, it can throw it off. If there is not enough power, it'll kick out. The best way to flash with Aroma is to make sure that the phone is OVER 75% battery, reboot into recovery. Have phone plugged into the WALL OUTLET (NO PC...VERY IMPORTANT NOT TO DO THAT). Then flash the ROM."

I'm not educated enough in the specifics to say this is a definitive reason for the freezes. However, some have reported good results following the directions above. Hope this helps in some way :)

Sent from my LG-LS970 using xda app-developers app
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,558
Kenilworth, Coventry
OnePlus 9 Pro
adb works fine here with TWRP - maybe you have the wrong OS on your desktop PC. :D Maybe you are expecting a wrong serial number using -s or ANDROID_SERIAL? TWRP reports "0123456789ABCDEF".



Scripts should also run on TWRP since it has Busybox installed...



Ouch, that could mean that adb also doesn't work. Would be interesting if it does. And check /proc/last_kmesg after such a reboot, maybe it contains relevant info.

Already spoke to OP about scripts and he has confirmed why they won't work. They need recompiling for some such thing or other which to be honest is a ball ache when I can flash CWM and they work fine. I can send you the reodex script if you want to see what I mean. It's beyond my skill to get them working.

As for OS like I said ADB works fine when booted into android, in CWM and also with my other devices.

ADB DEVICES doesn't see anything when in TWRP. Not sure why, even when I try to use ADB push mode it still doesn't even register a beep on either of my pcs. Probably a driver issue somewhere but just haven't got round to figuring it out. I'm using windows 7 primarily. I should have a crack on linux but I use CWM to do most of my work when building as scripts work and then switch back to TWRP to test flashes as it is much faster than CWM especially for backing up and restoring. I do like TWRP but this freezing issue has me scratching my head.
 

_that

Recognized Developer / Inactive RC
Oct 2, 2012
4,821
4,211
Already spoke to OP about scripts and he has confirmed why they won't work. They need recompiling for some such thing or other which to be honest is a ball ache when I can flash CWM and they work fine. I can send you the reodex script if you want to see what I mean.

Sounds confusing. :) Send me what you are using and tell me how exactly the scripts don't work and I'll have a look.

ADB DEVICES doesn't see anything when in TWRP.

Funny - as written before, I see a device with serial number 0123456789ABCDEF and it works fine. But I'm using Linux.

I do like TWRP but this freezing issue has me scratching my head.

I am still on 2.3.1 after reading all the warnings about later versions, but maybe you can find out why it freezes.
 

fiidim

Member
Dec 17, 2011
38
9
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Is using GooManager method to install TWRP over an existing CWM installation good? I'm using CROMI v3.2.2. Not sure if replacing a recovery is the same method as installing a brand new one. Any advice would be appreciated ed.




Sent from my ASUS Transformer Pad TF700T using xda app-developers app
 

okantomi

Senior Member
Feb 20, 2011
3,020
709
Boston, MA
Is using GooManager method to install TWRP over an existing CWM installation good? I'm using CROMI v3.2.2. Not sure if replacing a recovery is the same method as installing a brand new one. Any advice would be appreciated ed.




Sent from my ASUS Transformer Pad TF700T using xda app-developers app
It's agreat method to install TWRP. Just make sure to let it run until you see a message that it's been installed. if it doesn/t reboot to recovery on its own, use the TWRP menu to reboot to recovery. You should see the blue curtains...then you know you've got it.
 
  • Like
Reactions: fiidim

dengom

Member
May 14, 2011
9
0
TWRP Image larger than screen

With every version of TWRP versions 2.4.x down to 2.2.1.4 the screen image appears to be zoomed with the right half of the image missing (off the screen). This makes the recovery unusable because necessary options are cut off as well as the ability to go back to previous screens. Any suggestions would be appreciated.

TF700T, JB 10.4.4.25, unlocked.
 

xpakage

Senior Member
Oct 23, 2010
2,094
685
Oklahoma
Every time I have used 2.4.2.0 today, it has said I lost root and will fix it. Once was a CROMI update, the next four times was after installing different colored themes for CROMI. It is possible to lose root that often or is the script being cautious?
 

maframan

Senior Member
Jun 19, 2006
71
2
Hi,

I have installed ClockWorkMod Recovery , is it possibile to replace this with TWRP?
If true, please send me the procedure for replacement

BR
maframan
 
Last edited:

Tylorw1

Senior Member
Feb 10, 2013
1,850
1,128
Ohio
tylorhost.me
Upgrading to newest version

I have TWRP 2.4.1, would it be wise to keep TWRP up to date of should I just leave it alone for now? Also, updating the recovery, would it wipe any of the rom settings of Cromi 3.4?
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

Every time I have used 2.4.2.0 today, it has said I lost root and will fix it. Once was a CROMI update, the next four times was after installing different colored themes for CROMI. It is possible to lose root that often or is the script being cautious?

Try TWRP 2.3.1 or 2.3.3 and see if you have the same problem. Some people have issues with TWRP 3.4.x

Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
 

Top Liked Posts

  • There are no posts matching your filters.
  • 77
    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:

    -Backups will now include adopted storage keys (Dees_Troy)
    -Fixed an adb restore issue (bigbiff)
    -Fixed rebooting when no OS is present (Dees_Troy)
    -Fixed line wrapping in the GUI terminal (_that)
    -Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)


    CHANGELOG for 3.1.0-0:

    -vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
    -adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
    -tweak MTP startup routines (mdmower)
    -support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
    -support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
    -better indicate to users that internal storage is not backed up (Dees_Troy)
    -improve automatic determination of TW_THEME (mdmower)
    -minimal getcap and setcap support (_that)
    -try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
    -shut off backlight with power key (mdmower)
    -timeout during FDE decrypt (Dees_Troy and nkk71)
    -support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
    -boot slot support (Dees_Troy)
    -TWRP app install prompt during reboot (Dees_Troy)
    -support for AB OTA zips (Dees_Troy)
    -support new Android 7.x log command (Dees_Troy)
    -update recovery sources to AOSP 7.1 (Dees_Troy)
    -numerous bugfixes and improvements by too many people to mention

    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!

    DOWNLOAD:
    1) Install the TWRP app from the Play Store or grab the apk from our website
    2) Open the app, agree to the terms, and enable root access
    3) Select TWRP Flash
    4) Search for your device and select the version you wish to download
    5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
    OR:
    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 from our website on your device
    2) Reboot to TWRP
    3) Hit Install and tap the "Images..." 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
    OR:
    You can find more information and download links on our website.

    BUGS:
    If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.
    14
    Sorry guys, GooManager should be fixed to find 2.3.0.0 now. When you're updating 40+ devices it's easy to miss one somewhere.
    11
    Official 2.7 is now available on the TWRP web site. http://teamw.in/project/twrp2

    If you format /data with this version and it appears to hang, give it 1-2 hours, it is erasing unused blocks on the eMMC (trim/discard). At least that was the case with my unofficial version.
    8
    The staging error is non critical -- doesn't mean anything bad. It will be fixed in the next release.
    8
    Updated to 2.2.1.1 with a full screen theme / layout.