Hey all,
My phone was acting up and had a lot of clutter so I ODIN'ed to stock WITH root and e3. I downloaded Rom manager and flashed recovery. Seemed to work. I did the double install deal. Loaded green recovery: great. Reboot the phone. Turn it off to boot back into recovery. As i do the two volume plus power button combo, phone boots and i come to the blue and yellow install screen for recovery. Happens everytime.
I even tried going back to entirely stock. No root or anything. I then rooted, added e3, and flashed. Same deal.
Whats going on?!
I'm flashing a rom right now to see if that fixes anything.
It can't be normal to have to reinstall the package everytime i reboot into recovery.
And it only boots into green. Not blue or red.
Help!
Just finished flashing Zeus and went into recovery. Booted right into red. I guess problem solved?
galaxy s phones and the infuse don't conform to the android standard. they use a kernel with initramfs for boot in place of a boot.img partition. the initramfs can't be modded short of compiling a kernel and flashing it to the phone. the behavior you described is absolutely normal for high end Samsung phones. there isn't really any other safe or easy way to do it. the green recovery is the one designed for the i9000 with the stock kernel. the red/blue versions are themed and modded version that are baked into the kernel. once you flash a rom with a custom kernel you will have red unless it is cm7 or miui which will have blue.
Thanks for the explanation! Makes sense now.
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.
Hey,
so I tried to flash Xposed Frameworks on my S6 6.0.1 with TWRP, sadly now after the Samsung Logo the Screen Stay Black and the blue Light keeps on, I cant shutdown the PHone just reboot it.
Is there anyway to fix this? I think I might overread the Part that TWRP need a different Kernel. If so, would be nice, if someone can show me a Kernel I can use.
Did you install the version specifically for the S6? In that thread, there's an uninstall zip you can flash from TWRP.
Sent from my SM-G920W8 using Tapatalk
Hello,
i tried to root my Mate 7 (MT7-TL10) B560
when i installed the custom recovery TWRP and even the stock recovery.
i can't do anything!
the touch dosen't work , volume buttons , only the power button ! and it lock the screen.
tried 2 diffrent versions of the TWRP 2.8.7.0 and the 3.0.2,
and both versions show that i have a problem with partition or something!
"Unmodified System Partition"
and i don't know what to do.
i really want to install custom roms start using it
* i replaced the entire screen because the last one broke. anything to do with my issue?
Simple default splash without annoying useless note about unlocked bootloader.
Also Pie firmware include splash with incorrect proportions, it's vertically stretched. But this is with normal dimensions. Made by this utility.
UPD: reulploaded, fixed missing fastboot logo (mi-bunny).
Just flash attached ZIP via custom recovery. Remember, that installing MIUI update or new firmware may overwrite bootlogo.
Also attached default logo if you want to revert.
BTW check stylised "Redmi Note 5" logo
thx for sharing