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!
download: https://www.mediafire.com/folder/w9nh7oyabwvww/tate
fastboot -i 0x1949 flash recovery tate_recovery_xxxxxxxx.img
restore old recovery:fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img
Flashed the img fine from twrp install menu, seems to work great. Marshmallow logo might not make complete sense, but there's no more graphical error when loading, so overall big improvement. :good:
r3t3ch said:
Flashed the img fine from twrp install menu, seems to work great. Marshmallow logo might not make complete sense, but there's no more graphical error when loading, so overall big improvement. :good:
Click to expand...
Click to collapse
Are you talking about the giant Marshmallow logo before going into TWRP? Too big imho
xWolf13 said:
Are you talking about the giant Marshmallow logo before going into TWRP? Too big imho
Click to expand...
Click to collapse
Yeah I admit it's a little too large but I do like it in general for MM roms. But for twrp, despite AOSP 6 base, a user could be using a non-MM rom and the logo could seem out of place. I also liked the blue kindle logo with twrp so I could differentiate between booting into recovery or system.
Either way, I suppose you should direct aesthetic complaints to @monster1612 as he pushed the new logo.
r3t3ch said:
Yeah I admit it's a little too large but I do like it in general for MM roms. But for twrp, despite AOSP 6 base, a user could be using a non-MM rom and the logo could seem out of place. I also liked the blue kindle logo with twrp so I could differentiate between booting into recovery or system.
Either way, I suppose you should direct aesthetic complaints to @monster1612 as he pushed the new logo.
Click to expand...
Click to collapse
Suggestions noted. I'll work on reducing the size of the logo (it was one of my first bootloader logo mods, so I wouldn't know for sure how it looked on a physical screen ). Also, I'll work on making a TWRP logo so one can easily identify what mode the kindle's booting into.
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
transi1 said:
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
Click to expand...
Click to collapse
This is over my head. I'll sit back and learn on this one.
transi1 said:
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
Click to expand...
Click to collapse
I just noticed I can't boot into recovery by holding either of the volume buttons. Previous builds of twrp allowed booting directly into recovery by holding the volume up button. Is it possible to add this?
r3t3ch said:
I just noticed I can't boot into recovery by holding either of the volume buttons. Previous builds of twrp allowed booting directly into recovery by holding the volume up button. Is it possible to add this?
Click to expand...
Click to collapse
use old build or fastboot .... reboot oem recovery.
seems trouble with new CM-environment
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Maromi said:
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Click to expand...
Click to collapse
You could also just flash the img from twrp 2.8.7.0 the same way you flash a zip.
Maromi said:
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Click to expand...
Click to collapse
Thanks! I'll give it a try. :good:
build (3.0.1) 160403: http://www.mediafire.com/download/b286zg2cs0go0i8/tate_recovery_160403.img
transi1 said:
build (3.0.1) 160403: http://www.mediafire.com/download/b286zg2cs0go0i8/tate_recovery_160403.img
Click to expand...
Click to collapse
Seems like something is wrong with this build. After flashing the img directly from last twrp 3.0.0 build 160312, rebooting to recovery causes the screen to go black. TWRP is technically running since MTP mount seems to still work, but nothing is being displayed on the tablet screen. Had to flash back old recovery from fastboot.
r3t3ch said:
Seems like something is wrong with this build. After flashing the img directly from last twrp 3.0.0 build 160312, rebooting to recovery causes the screen to go black. TWRP is technically running since MTP mount seems to still work, but nothing is being displayed on the tablet screen. Had to flash back old recovery from fastboot.
Click to expand...
Click to collapse
I installed the img by using fastboot flash and didnt see any issue.
Can you even flash an .img file?
Hey, I take it back. You are right If you do a reboot to recovery from within Android it goes black....
Ive been doing reboots and holding the volume key to get into recovery.
mikeataol said:
I installed the img by using fastboot flash and didnt see any issue.
Can you even flash an .img file?
Hey, I take it back. You are right If you do a reboot to recovery from within Android it goes black....
Ive been doing reboots and holding the volume key to get into recovery.
Click to expand...
Click to collapse
Yes, for awhile now in twrp you can flash an img file to either the boot or recovery partitions by pressing the img button in bottom right corner of the same file browser you use to flash a zip file.
Holding the volume key during boot isn't supported in these builds. If you need it you'll have to go back to 2.8.7.0.
r3t3ch said:
Yes, for awhile now in twrp you can flash an img file to either the boot or recovery partitions by pressing the img button in bottom right corner of the same file browser you use to flash a zip file.
Holding the volume key during boot isn't supported in these builds. If you need it you'll have to go back to 2.8.7.0.
Click to expand...
Click to collapse
from power off holding the (left)volume key with volume at top works... just did it....I just start holding at the orange splash screen
mikeataol said:
from power off holding the (left)volume key with volume at top works... just did it....I just start holding at the orange splash screen
Click to expand...
Click to collapse
Ah you're right. Not sure what I was doing wrong before then; maybe I was just holding them both or something.
@transi1
I appreciate all that you do, just a head's up.
Thank you for the great roms & twrp. (Save the last twrp build. ?)
tate_recovery_160403 only gives me a black screen. At one point I had the twrp background as a shadow border to my fastboot screen.
(That looked kinda neat!)
Back running tate_recovery_160312.
Sent from my Amazon Tate using Tapatalk
Both newer build of rr & twrp seem to be running fine on my jem.
Is Twrp 3.0.1. Stable? If not I will flash 3.0.0 and hope for the best, as I am well know for bricking kindles. I have like, 2 that are bricked that I can't fix, and another one with no recovery or os.
Related
The HTC One XL is now officially supported by ROM Manager. ClockworkMod recovery can be downloaded from within the ROM Manager application, or from clockworkmod.com/rommanager.
Official ClockworkMod Builds
Download ClockworkMod 6.0.2.8 Official
This is the stock ClockworkMod recovery. Navigation is done through volume-up/down and power to select.
Download ClockworkMod Touch 6.0.2.8 Official
This is the touch driven ClockworkMod recovery. Navigation is done through a touch interface.
Automated Installers
Automated installation will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Official ClockworkMod builds: ROM Manager
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery recovery-clockwork-6.0.2.8-evita.img
where the filename should be replaced with that of the version you downloaded. When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start ClockworkMod recovery.
Additional Information:
Credits:
mdmower for doing all the recovery work for the HTC MSM8960s
gweedo767 (@unstableapps on twitter) for the gesture enabled modifications to CWM
KemoNine for building assistance
Shaaan for his CWM building guide
Koush for writing ClockworkMod and officially supporting this device
CyanogenMod for way too many reasons
Known issues / Workarounds / To Do
In the stock version, there is no support for the capacitive back/home/recent buttons on the phone.
The charging status LED does not turn on when the phone is charging, though charging does work.
If the phone is powered off while plugged into USB, it will temporarily reboot into CWM then shut down 20-30sec later
Source
The device tree is at github.com/CyanogenMod/android_device_htc_evita.
Note: This is for evita, not endeavoru.
If anyone is interested, I also offer a gesture enabled version: CWMR Touch, based on gweedo767's work. Navigation is done through swiping up/down/left/right on the classic CWM interface.
CWMR Touch 6.0.3.7
nice!
Too accustomed to TWRP now :silly:
Re: [RECOVERY][2/14] ClockworkMod Recovery Touch v6.0.2.8
Nice to have choices!
Re: [RECOVERY][2/14] ClockworkMod Recovery Touch v6.0.2.8
Better late than never, choice is always good. Thanks!
Re: [RECOVERY][2/14] ClockworkMod Recovery Touch v6.0.2.8
Very nice...awesome stuff
My blazingly fast as f*#k One XL fueled with CM10.1
Re: [RECOVERY][2/14] ClockworkMod Recovery Touch v6.0.2.8
Very nice work. Now when noobs post about cwm and icj we have to ask more questions instead of telling them they have a brick!
Sent from my HTC One XL
954wrecker said:
Very nice work. Now when noobs post about cwm and icj we have to ask more questions instead of telling them they have a brick!
Sent from my HTC One XL
Click to expand...
Click to collapse
Heh, yeah. Good to have choices and perhaps competition, I suppose. Sticking with TWRP, though.
Awsome I love cwm can't wait for it to go offical.
Nice! Thanks for posting this! How is it working for everyone so far?
mirGantrophy said:
nice!
Too accustomed to TWRP now :silly:
Click to expand...
Click to collapse
Yeaaaah.
After all this time, it's like that girl you lusted after in high school who wouldn't give you time of day, then when you meet her at your 10-year reunion and she wants to hook up, you've been married for five years already.
(This actually happened to me, but nevermind.)
anyone know if our build of cwm lack any features that other phones have? i see you can't format boot in our version unless that is normal for all cwm 6.x.x.x.
DvineLord said:
anyone know if our build of cwm lack any features that other phones have? i see you can't format boot in our version unless that is normal for all cwm 6.x.x.x.
Click to expand...
Click to collapse
I just checked on my Nexus 7 with CWM 6.0.1.9, and didn't see an option to format boot either
DvineLord said:
anyone know if our build of cwm lack any features that other phones have? i see you can't format boot in our version unless that is normal for all cwm 6.x.x.x.
Click to expand...
Click to collapse
Are you able to format boot in TWRP? I would think this is related to HTCDev Unlock only allowing writes to the boot partition through fastboot, and not through recovery.
mdmower said:
Are you able to format boot in TWRP? I would think this is related to HTCDev Unlock only allowing writes to the boot partition through fastboot, and not through recovery.
Click to expand...
Click to collapse
Didn't see anything. Under the wipe menu, there's buttons for system, cache, dalvik cache, factory reset, external storage, and android secure. I'm on TWRP 2.3.3.0 if that means anything
Mosch26 said:
Didn't see anything. Under the wipe menu, there's buttons for system, cache, dalvik cache, factory reset, external storage, and android secure. I'm on TWRP 2.3.3.0 if that means anything
Click to expand...
Click to collapse
Then I do think the reason /boot format is not permitted has to do with HTCDev unlock. S-OFF users should see the option (in both TWRP and CWM).
i have s-off and format /boot is not implemented.
flashed this recovery and seems to be working well. also touch doesn't seemed to be working inspite of the name? thanks
mrjayviper said:
flashed this recovery and seems to be working well. also touch doesn't seemed to be working inspite of the name? thanks
Click to expand...
Click to collapse
touch worked fine for me. only issue i had is the one stated in op where usb mount doesn't work.
New image uploaded by mdmower with USB Mount fixed!
Check the OP for the image link
Normal install instructions, fastboot flash recovery recovery.img
Go thank mdmower for his hard work on this!
Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
dengom said:
Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
Click to expand...
Click to collapse
How about try to reflash the 4.2.1 bootloader and twrp using one package zip file? http://forum.xda-developers.com/showthread.php?t=2223492
Thanks for the reply.
That is exactly what I did first with the results mentioned in OP. Will give it another try,
that's why it is a little baffling.
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
dengom said:
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
Click to expand...
Click to collapse
Yeah, it's a good idea, flash back stock firmware to get back stock recovery, root the device then download goomanager from the market then try to install twrp again. I think your recovery bootloader maybe messup(reflash recovery from stock rom should address this issue).
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
dengom said:
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
Click to expand...
Click to collapse
That's incremental update. You want a full upgrade.
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
dengom said:
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
Click to expand...
Click to collapse
Alternative Firmware update Method: download full firmware from Asus web site.
1. Unzip the downloaded file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button twice
9. Wait patiently for 10 minutes or so and Done.
Thanks, will give it a try after work.
Also, I should preview my posts b4 submitting for spelling.
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
dengom said:
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
Click to expand...
Click to collapse
I suggest you should reflash the full Asus firmware which included the rom and bootloader. Just make sure you download the right version for your tf700 and the correct SKU and you are sure that you have the tf700 right? not the tf300!!
Yes it is definitely a TF700. I will try the re-flash of official 4.2.
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Bump?
riclin54 said:
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Click to expand...
Click to collapse
No-one able to help here??
Would really appreciate some guidance before I blow the tablet away completely!
riclin54 said:
Bump?
Click to expand...
Click to collapse
riclin54 said:
Would really appreciate some guidance before I blow the tablet away completely!
Click to expand...
Click to collapse
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
f69m said:
First of all go to the bootloader screen by holding power and vol-down.
Double-check the Asus version of your bootloader at the top of the bootloader screen and pick the right TWRP version for it:
For Asus v10.4.*: any TWRP *-jb.blob
For Asus v10.6.1.8.*: only TWRP 2.4.4.0-4.2.blob
For Asus v10.6.1.15.*: any TWRP *-4.2.blob
Hope this is clear enough!
Click to expand...
Click to collapse
Thanks for your suggestion Rhian. However I've not yet sorted this. Perhaps a little more info from me will help you help me
The device is running 'Android cardhu-user bootloader <1.0.0 e> released by "WW_epad-10.6.2.3-20130402" A03'. It was unlocked with Asus Unlock_v7 whilst still running ICS and has had Superuser-3.2-RC3-arm-signed.zip installed.
Currently, on initial power up, the device boots straight into TWRP v2.5.0.0 Recovery. I can execute TWRP commands - however there seems to be an issue with access to partitions. Although I can mount the System partition - Cache & Data as well as Micro SDcard and SD-Ext are unmountable (neither can I see block devices in /dev that relate to these). I am however able to access a shell via adb. Further, both volume toggles appear to be operating as they should.
Rebooting from TWRP alerts that "Root permissions appear to be lost". I have attempted to reinstall Superuser but this has not resolved the matter.
"adb reboot boot-loader" will reboot the device into fastboot mode with the boot screen noting "Key driver not found .. Booting OS" and the version info above. From here, I have attempted to use adb to replace TWRP 2.5.0.0 with version 2.4.4.0. Although the adb commands complete without error, the new recovery is not written and the existing 2.5.0.0 remains in place.
From the Fastboot screen on the device, it can be forced to boot Android where everything seems to operate normally and with all partitions and filesystems appearing to be accessible.
All this suggests to me that there is either a problem with the bootloader itself, or less probably, that there is an issue with one or more of the partitions which is interfering with the boot process. There is however a better than even chance that I'm wrong.
I'm considering reformating and replacing the partitions one by one - however this seems rather extreme and in any case, I've not been able to locate an ASUS source of the partitions images yet.
Doing my head in here Rhian - any suggestions?
Thanks,
Richard
Rhian said:
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
Click to expand...
Click to collapse
Recovery issue
Hi, i have the latest 10.6.1.15.3 rom. I've installed twrp 5.0.0, 4.2 recovery. Now, i can enter to recovery, but if i want to make something, do nothing. It seems, twrp don't see the sd card. Any idea?
Thanks
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy
The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4
New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)
I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to
New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)
Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk
Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.
It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk
reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.
hello everyone, today i tried to flash twrp on my phone (rooted with magisk and running stock samsung rom), the flash was successful and i was able to boot into twrp but i coudnt access my storage or anything else, so i saw a guide saying to change the filesystem to ext2 then ext4, after i did that i could access most of the other folders but not the storage foldier as it still showed 0mb. i thought i just need to reboot my device to fix the issue but now im stuck on a bootloop. i cant poweroff the device since no button combination is currently working. is there anything i can do to power it off or do i have to wait a few days till the battery drains to 0?
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)
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...
forum.xda-developers.com
this is the link i used to flash twrp except i didnt follow the wipe instructions because i dont want to use a custom os.
and if nothing else works and i have to wait a few days till it drains to 0, will i be able to boot back into samsung's recovery mode or is this device hard bricked?
help will be greatly appreciated.
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
sandsofmyst said:
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
Click to expand...
Click to collapse
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
floppen22 said:
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
Click to expand...
Click to collapse
yeah so it seems like the issue isnt with changing the file system or anything because i installed twrp again and tried rebooting and i got the same bootloop issue, but if i flash a rom then ill lose twrp like it happened last time so i dont understand what im supposed to do
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
beanbean50 said:
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
Click to expand...
Click to collapse
wipe>format data>type yes>reboot to recovery. i did that and still cant reboot to system bootloop issue persists
yes you did it correctly this time, is there anyway to undo your 'filesystem to ext2 then ext4'?
or maybe you have to flash the custom kernel to get it all up and running again
beanbean50 said:
or maybe you have to flash the custom kernel to get it all up and running again
Click to expand...
Click to collapse
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
floppen22 said:
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
Click to expand...
Click to collapse
it's a zip file so it should flash in twrp
beanbean50 said:
it's a zip file so it should flash in twrp
Click to expand...
Click to collapse
yes i was able to boot into my phone after flashing the kernel. thank you so much.
Try a different version of TWRP I remember this happened to me before and I installed a different version and it was fine