Related
Q&A for [RECOVERY][mint] TWRP 2.8.4.0 touch recovery [2015-01-13]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][mint] TWRP 2.8.4.0 touch recovery [2015-01-13]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
dzadzev said:
@Dees_Troy the last working recovery was 2.8.0.1
Click to expand...
Click to collapse
It still is the latest working version of TWRP for our device Xperia T (mint).
I tried 2.8.1.0, 2.8.3.0 and 2.8.4.0 when flashed these versions I can't boot into recovery and it keeps bootlooping the recovery.
I can boot into system without problem, the only solution to get into recovery again is by flashing the latest working 2.8.0.1 again into the FOTA kernel.
Already contact teamwin to let them know that there is something wrong with building TWRP from 2.8.0.1 and further, but still no luck on a reply.
it doesn't work on my xperia t
i have root permission and unloacked bootloader but it doesn't work
it downloads the recovery and install it but when it's reboot it doesn't work.
i have already install other recovery but nothing (
if i flash a cwm with flashtool works only recovery and none the os.
please help me, now i ave 4.1 kitkat, i'm italian
i try help also my italian community in "androidiani forum"
spartanhack said:
i have root permission and unloacked bootloader but it doesn't work
it downloads the recovery and install it but when it's reboot it doesn't work.
i have already install other recovery but nothing (
if i flash a cwm with flashtool works only recovery and none the os.
please help me, now i ave 4.1 kitkat, i'm italian
i try help also my italian community in "androidiani forum"
Click to expand...
Click to collapse
Like you can see in my previous comment you need to download the TWRP version 2.8.0.1 because that is the only version that is working for now.
You can do this easily with installing the app: TWRP Manager (ROOT) findable in play store and then use a theme for TWRP and you have a splendid recovery.
Theme is findable: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
TWRP is the best recovery I've tested so far, except the latest version wont work for the moment on our Xperia T.
ziggyke said:
It still is the latest working version of TWRP for our device Xperia T (mint).
I tried 2.8.1.0, 2.8.3.0 and 2.8.4.0 when flashed these versions I can't boot into recovery and it keeps bootlooping the recovery.
I can boot into system without problem, the only solution to get into recovery again is by flashing the latest working 2.8.0.1 again into the FOTA kernel.
Already contact teamwin to let them know that there is something wrong with building TWRP from 2.8.0.1 and further, but still no luck on a reply.
Click to expand...
Click to collapse
TeamWin for the WIN! The new version 2.8.5.0 that yesterday made available for our Xperia T is working without a problem! I just flashed the new .img on my FOTA kernel and could boot into recovery.
I updated the old zip to the latest version and attached it to my post.
problem flashing gapps 5
i flashed CM12 on my xperia T using the recovery mod that came in the boot.img inside the cm12 build, and then the GApps 5
everything was fine except for a small bug in which some apps couldn't detect the sd
i decided to do a clean install, but this time i installed TWRP and performed the data wipe/factory reset and flash using it
i got the TWRP manager, and installed the version 2.8.5.0
i booted into recovery, wiped data, flashed cm12, reboot into system, reboot into recovery, flashed gapps, wipe dalvik/cache, reboot into system and the GApps keep crashing all the time.
I tried all the GApps available, the 5 packages of PA GApps, and all the basket team GApps 5 i could find and all crash
i decided to flash cm11 and GApps 4 and it works perfectly, and if i flash CM12 itself the system works, it's the gapps that have problems
it must be a recovery mod problem then
Why i can't install any lollipop rom on mint
my recovery is Twrp 2.8.5..0
Hello to everyone, can anyone tell me how to install the twrp, I'm new with xperia and Idon'thave any idea of how is it going, I had samusng and motorola and was so easy. But there I heard "adb shell", "FOTAKernel", thing that make me confused.. On samusng there is a Odin tool, and on XPERIA -Flashtool? The phone is XPERIA T (LT30P), is rooted with bootloader unlocked.
Enviado desde mi E6653 mediante Tapatalk
With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
SuperSU
After flashing the latest SuperSU from TWRP and rebooted, the device just hangs on the boot logo and does not pass.
Using the much older SuperSU 2.63 works without a problem.
Question: Is there any solution to get the latest SuperSU installed?
gotling said:
With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
Click to expand...
Click to collapse
Mate, I installed the unofficial TWRP from the post below, it worked fine in my moto X (XT1058). Try flash the TWRP 3.0.2 via fastboot (using computer).
https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449
Try to verify the downloaded archives, because they may contain errors and a re download is needed.
(I'm not permitted to post in the developers forum, i.e. roms, kernels, recoveries, etc., so I'm posting this here).
My original post can be found here in the Blu Development Group on Google+. (Forgive me if this is considered redundant):
https://plus.google.com/u/0/106948556420593597970/posts/Lp8cCUR8AZq
TWRP v3.0.3 BLU VIVO XL V0030UU - MT6753 for Android 6.0 (kernel 3.18.19) by lopestom
(And TWRP v3.0.2-1 Materialized)
Special thanks for +lopestom for compiling these custom recoveries and for all his instruction and help.
Instructions for minimal ADB installaion:
https://forum.xda-developers.com/showthread.php?t=2317790
Instructions for TWRP boot load:
- Turn on developer options
- Turn on USB debugging
- Turn on OEM unlocking in developer options. Using fastboot oem unlock doesn't matter, I believe, but I did it anyway. It doesn't cause a boot loop on Android 6.0, but using fastboot oem unlock on my android 5.1 version did cause a boot loop for me.
- ADB reboot bootloader
- Fastboot boot <twrp_recovery_file.img>
- Wait about 1-2 minutes
THIS IS IMPORTANT. I had no luck flashing the twrp recoveries using the conventional means of either SP flash tool or Fastboot flash of the recovery. The device would always boot loop at least once and revert back to the stock recovery. However, I did have success using "fastboot boot recovery recovery.img" in the bootloader. TWRP would take a while to load, but it did. This was the first TWRP recovery I personally was able to load on Android 6.0 of the Blu Vivo XL. If you are successful in permanently flashing the TWRP, please share your method
TWRP download files:
5 - recoveryTWRPv3.0.3 BLU VIVO XL V0030UU - by lopestom
https://drive.google.com/open?id=0B3FJHUCtGU9sc0dQT2Q5TUpuMG8
OR
4 - recoveryTWRPv3.0.2-1 Materialized BLU VIVO XL V0030UU - by lopestom
https://drive.google.com/open?id=0B3FJHUCtGU9sNnVEWTVfOTZfUzQ
You can try both of the above. I was able to successfully root the device using v3.0.3, but both would load.
The prior STOCK ROMs (Android 5.1 V07 and Android 5.1 V10) for Blu Vivo XL are on the repository by +William Smith. Please note that no stock rom for the Blu Vivo XL on Android 6.0 has been released by Blu. You must upgrade to Android 6.0 through the OTA update.
I used this to root (not sure who to credit, my apologies):
https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNGdP_Scd5jn9Dgri61Yz-mhA1B7zQ
*I shall not be held responsible for any errors/issues caused using this custom recovery.
(Please see below for the images of the TWRPs that loaded)
Shoot, I meant to post this in the guides section. Newbie mistake. Are there any moderators that can move this thread? Thanks.
don't work , tryed on SPlus on 3.18.19 , both recovery got blackscreen and reboot
IacobIonut-DW said:
don't work , tryed on SPlus on 3.18.19 , both recovery got blackscreen and reboot
Click to expand...
Click to collapse
Thanks for letting us know. Do you currently have another custom recovery on there?
It's important to wait for it to load for about 1 to 3 minutes. Or did the phone go back to system booting on its own? During that time the "screen" may go into sleep mode. Just tap power button to wake it up and see if TWRP is there. Also, is your bootloader unlocked? I believe that may be required on the Gionee elife S Plus, where you actually have to go through the process of "fastboot oem unlock", and let it reboot. BEWARE: this will wipe your device.
In any case, I didn't test this recovery on the Gionee elife S Plus, as I don't have that device. Although they're the same phone, maybe there are slight differences in the booting process?
Likewise, for instance, this TWRP from Hovatec below for the Gionee e life S plus didn't work on my Blu VIVO XL. I believe others may have had luck booting to recovery using it on the VIVO XL, however. Not positive. But for me, I had no luck.
https://forum.hovatek.com/thread-15270.html
I read somewhere the Gionee S Plus has Android 6.0.1. Is that correct? The VIVO XL still has Android 6.0 (same kernel), but I'm not sure that would make a difference.
can you provide me a TUT on how to replace the recovery using ADB just the way you flashed Your Phone.. Please
Same as the 3rd floor. Black screen and then bootloop
Hello guys.
I've seen this device development for custom rom and custom recovery are slow (they did it in privat currently, invited user or someone who want to join). The unofficial twrp having issue with encrypted device (asking for password). So internal storage in twrp isnt accesible and need to format data to make it works. Of course ROOTING with TWRP is still POSSIBLE by placing magisk to extSdcard anyway.
And this guide is a SECOND chance for you who wants to ROOT your phone WITHOUT TWRP. But, need a PC. The root method here are from magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 .
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
- Know how to use minimal adb and fastboot.
Again this method does not need root, and also does not require a custom recovery. boot.img & UBL is a must.
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
8. Voila!
I've done this method with my Redmi 5 Plus and not having any issue. Technically, bootloop risk are very low. Because magisk disable dm-verity.
I dont know someone already make a guide about this here. But its not detailed. So, ill keep this thread on. For root with custom recovery TWRP here.
GueztStar said:
I dont know someone already make a guide about this here. But its not detailed. So, ill keep this thread on. For root with custom recovery TWRP here.
Click to expand...
Click to collapse
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
---------- Post added at 04:55 AM ---------- Previous post was at 04:51 AM ----------
reynold30 said:
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
Click to expand...
Click to collapse
The credit mainly goes to @Peaktogoo
reynold30 said:
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
---------- Post added at 04:55 AM ---------- Previous post was at 04:51 AM ----------
The credit mainly goes to @Peaktogoo
Click to expand...
Click to collapse
In general people didnt know that like i am. But, im glad to hear that. My friend have this phone and think about doing these kind of.
GueztStar said:
In general people didnt know that like i am. But, im glad to hear that. My friend have this phone and think about doing these kind of.
Click to expand...
Click to collapse
Am glad to help you
Why this phone don't have custom rom? What am I missing?
This method actually works for my S2. Thanks for sharing.
Download twrp redmi s2 by peak
Fastboot boot twrp.img
Press Cancel
Flash magisk zip
Reboot
Done
Please give latest mi magisk patched boot image .
Please ..
Thanks a lot, Gueztar!
Your method has worked on my Redmi S2.
Hi all,
I flashed a (now, very old) version of Epic ROM (v7.5.4) on my MIX shortly after its release. I used it as my daily for about 2 years and never had the desire to update beyond that, as it included everything I needed.
Soon, my MIX is no longer going to be my daily, so I figured I'd explore what newer ROMs were available. The highest usable version of TWRP on my device is 3.0.2-0 (MrRaines) and any attempt to flash anything remotely modern to my device either reports an 'Error Code 7' or reads [This package is intended for "lithium" devices, your device is type " "].
I've attempted to update my TWRP (via the Official TWRP App) to a newer version, and that renders the recovery useless, as it has no touch screen functionality; so I have to revert to 3.0.2.
What do I have to do to get my device recognized as type "lithium," so that I can go about flashing newer stuff, and how do I go about resolving the touchscreen issue?
Thanks
Mr. Raines TWRP will not let you flash a newer TWRP.
You have to fastboot flash a new TWRP from a Windows computer.
After that you should have no problem.
Official TWRP is dead, you should use the latest updated one by Blunden-Raupe
Flashing is not the issue
I can flash any TWRP (including the one you mentioned) just fine using the app or using the fastboot method. It doesn't matter - the touch screen doesn't work on any newer [than 3.0.2-0] versions of TWRP.
I understand that I need a newer recovery to flash newer stuff and I know how to flash a new recovery. My issue is that I cannot get from the old recovery to a new WORKING recovery because of touchscreen support.
Do I need to go find the stock version of MIUI that came with the phone, revert to that, and then use upgrade to a newer OEM Xiaomi ROM to achieve "lithium" status (the lack of which is what I'm assuming is causing touch issues with newer TWRP versions)?
You probably have to do something like that, so the TWRP matches the firmware to get touch working.
It has been such a long time since I had these problems so I don't remember exactly.
Now yshalsager has made firmwares available without having to flash an entire rom, you could try that.
https://forum.xda-developers.com/android/software-hacking/devices-xiaomi-firmware-updater-t3741446
Addendum:
I would either fastboot flash the latest official rom, and then flash the latest TWRP, or -
try flashing via TWRP the latest TWRP and firmware zip file at the same time.
---------- Post added at 04:58 PM ---------- Previous post was at 04:09 PM ----------
At the end of the official TWRP thread someone has just posted a modified TWRP with working decryption.
https://forum.xda-developers.com/mi...y-official-twrp-xiaomi-mi-mix-t3498960/page67
A link to Blunden-Raupes most recent TWRP is on a previous page in that thread.
The official TWRP is not supported, does not work.