yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Babyhustle:
TWRP 2.8.5.0 not usable

Hi, I tried to use TWRP manager to flash TWRP 2.8.5.0 . After it shows success in flashing, it rebooted to the recovery and shows unresponsive, after 10s it rebooted to system itself

I tried TWRP 2.8.4.1, it didn't show these problems

Can somebody help me? :)

Your help is much appreciated :)

==================================================================================

The problem has been resolved

===================================================================================
[ONE Original Android Development] L10nH34Rt:
Latest TWRP is 2.8.5.1 AFAIK. Maybe you should try that version instead.
[ONE Original Android Development] donalgodon:
Is there a flashable zip of the latest version that I can flash via CWM?
[ONE Original Android Development] Heisenberg:
If you need to flash it from your phone you can just use Flashify.

Transmitted via Bacon
[ONE Original Android Development] clone217:
Zip

http://rg.to/file/6cc5813ab89648878684504bcfb41226/2-20-15-unofficial_twrp_2.8.5.1-bacon.zip.html
[ONE Original Android Development] Fabioo123:
for me mtp works only on TWRP 2.8.3, no on recent version. it's possible to fix this?
[ONE Original Android Development] donalgodon:
I have the latest version installed, but when I use the CMUpdater, the device doesn't automatically install and reboot. I have to do it manually.

Anybody know why and how I can fix it?
[ONE Original Android Development] LeroViten:
It's a common and known issue. There's a new version of twrp 2.8.6.0 available here:

http://dl.twrp.me/bacon/twrp-2.8.6.0-bacon.img

~• Posted via Baconed Tapatalk •~
[ONE Original Android Development] Donald Nice:
Same Problem, also with 2.8.6.0. Still corrupt zip. Flashing the zip file manually works great but no install from internal updater possible.﻿
[ONE Original Android Development] :
Yeah, now it's working for me!!!!!! First time ever with my bacon ?
[ONE Original Android Development] Fabioo123:
mtp still does not work for me even in 2.8.6.0. I go back to 2.8.3.0
[ONE Original Android Development] bombadier:
Then there must be a problem with the drivers that you have installed as it does work,have you contacted the developers to see if they can troubleshoot why its not working for you ?
[ONE Original Android Development] Fabioo123:
No, I have just written here. I thought you could even report errors here. Now I try to contact them
[ONE Original Android Development] Donald Nice:
MTP works for me.... TWRP 2.8.6.0 with cm12
[ONE Original Android Development] :
Aroma Installer doesnt work in this new build. Last working build is 2.8.4.0.
[ONE Original Android Development] LeroViten:
This is really strange because it doesn't work for me. And I'm not the only one with this issue. And what is more I can no longer use my beloved "material theme" as the "swipe to install" slider isn't visible due to latest changes. Hope theme designer will update the theme.

By the way, do you use custom theme?

~• Posted via Baconed Tapatalk •~
[ONE Original Android Development] bombadier:
If you are using z31s1g awesome theme you will have to wait till later before it gets updated check his thread

http://xdaforums.com/showpost.php?p=59690824&postcount=1552
[ONE Original Android Development] Heisenberg:
I think [MENTION=2714876]bombadier[/MENTION] is right, I've never had an issue with MTP on any build of TWRP, neither have many others, so it does work. There must be some other variable at play, like drivers. For all you guys having issues with MTP, exactly which drivers do you have installed?

Transmitted via Bacon
[ONE Original Android Development] Fabioo123:
I do not know I did not touch anything in the drivers. Mtp works with phone ON and TWRP 2.8.3.0, not with later versions. I also tried to change the computer.
[ONE Original Android Development] mabmed:
Please zip file for latest version. Can't find it via twrp Manager ..
[ONE Original Android Development] Nburnes:
Download it onto your device.

Reboot to recovery.

Press Install.

Press Images in lower right-hand corner.

Find twrp.xxx.xxx.img.

Select Recovery.

Swipe to confirm flash.
[ONE Original Android Development] nsmart:
Can someone check if twrp 2.8.6.0 works with cm12 and device encryption enabled ? Is it able to decrypt data partition ?
[ONE Original Android Development] mabmed:
Thanks

Thank you man.
[ONE Original Android Development] glockman4519:
The downloads packages are only 4.0kb to 9.0kb big. I don't think the download links are fully functional yet. TWRP manager doesn't give me an options for the latest update either. It shows latest as 2.8.5.1

Thank you all for the update.

"Chance Favors the Prepared"
[ONE Original Android Development] donalgodon:
The latest version 2.8.6 doesn't even boot for me.
[ONE Original Android Development] archer100:
I have the same problem while accessing the download link on the phone. Although it can be downloaded on the computer, the download link is exactly the same as the web page providing the link. The new website must be setup to do something too smart for the Android stock browser.
[ONE Original Android Development] Heisenberg:
You must have installed drivers on your PC at some point in order to unlock the bootloader. How do you not know which drivers you have installed?

Transmitted via Bacon
[ONE Original Android Development] Fabioo123:
The commands adb and fastboot work perfectly, the drivers installed them in September to unlock the bootloaeder recovery and change, I do not remember that I followed guide
[ONE Original Android Development] DjDiabolik:
On newest mirror no md5 file it's present... I have download this:

twrp-2.8.6.0-bacon.img

Whit this md5:

f69fa503419644851822d883c2388bb8

It's correct?
[ONE Original Android Development] :
I have successfully flashed 2.8.6.0, so no worries for others. I usually had to wait for a newer build, because of some problems, but this one was good from the start.
[ONE Original Android Development] ZeppeMan:
Mine is stuck on the 1+ logo, it just stays there with 2.8.6.0.

2.8.5.1 works fine.
[ONE Original Android Development] Formhault:
No such problems here.

Maybe you should try to reflash the recovery? I know mine didn't stick on the first try... fastboot flash recovery, reboot, reboot to recovery -> Cyanogen recovery :silly: . Flashed it second time and all was good.
[ONE Original Android Development] Heisenberg:
I'm always dumbfounded when I see someone say they don't know which drivers they have installed. I don't understand how people don't make sure they remember what they've done when they modify their phone. Anyway, troubleshooting your problem is impossible without that information.

Transmitted via Bacon
[ONE Original Android Development] Lanchon:
too bad flashify doesnt work anymore...
[ONE Original Android Development] z31s1g:
https://plus.google.com/+ChristianGollner/posts/jdstEpySDpo
[ONE Original Android Development] Lanchon:
thanks!! xda is quicker than the play store :)
[ONE Original Android Development] JoeF2:
No, it still can not decrypt the data partition.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333
[ONE Original Android Development] Heisenberg:
You can flash images directly from TWRP now.

Transmitted via Bacon
[ONE Original Android Development] Lanchon:
thanks, i know! but downloading them is a drag :)
[ONE Original Android Development] Fabioo123:
this is the driver:

http://d-h.st/sF2V

I tried to uninstall the drivers and reinstall them but nothing.

adb, fastboot and mtp with device on work well, but mtp in recovery no.
[ONE Original Android Development] Heisenberg:
Try these drivers instead:

http://www.koushikdutta.com/post/universal-adb-driver

So uninstall current drivers, reboot PC, install new drivers, reboot PC, connect phone.
[ONE Original Android Development] Fabioo123:
Also tested these drivers but mtp in recovery is still not working for me. I also tried to install the drivers in another PC but equal. Win7 64bit
[ONE Original Android Development] Thuneau:
Sorry if this was answered before but search did not show any results.

I'm on TWRP 2.8.3 and trying to update to the latest using TWRP Manager app.

It downloads the latest 2.8.5.1 but then prompts me for location to install.

It asks if /dev/block/platform/msm_sdcc.1/by-name/recovery is the correct partition?

Well, is it? How would I go about verifying this?

[IMG="screen shot"]http://i.imgur.com/YQLJBMk.png[/IMG]
[ONE Original Android Development] Thuneau:
"download the image of 2.8.6. from twrp's website and "flash" it via twrp. "

I'm on 2.8.3. The ability to update the twrp image is not there. I believe that started in 2.8.4.

I guess I will have to do it from adb, or if someone confirms the directory for me from the twrp manager app.
[ONE Original Android Development] Lanchon:
yes it is correct. and yes, you can flash it manually in many different ways. but i recommend getting the flashify app instead, it seems to be the best for this.
[ONE Original Android Development] Thuneau:
Thank you. I went ahead and let it do its thing, and it went through with no problem.

I then manually upgraded TWRP to 2.8.6 using TWRP itself. Next time I flash the CM nightly, I hope it will be a fully automated process with no errors or warnings.
[ONE Original Android Development] Lanchon:
it will, if u use flashify
[ONE Original Android Development] pbergonzi:
concur

That's a, "Yes" to Flashify--the newest version--the one that you need--is on their website--NOT at the play store. Link in this thread.

Correction--it is on the play store at this link: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

Thanks [MENTION=4141005]Lanchon[/MENTION]
[ONE Original Android Development] Lanchon:
yes it is on the play store! has been for days
[ONE Original Android Development] donalgodon:
2.8.6 STILL does not work with CMUpdater correctly.

OTA updates require a manual flash and reboot.

Any idea what's breaking the OTA updater flash process?
[ONE Original Android Development] Zach1928:
Is there a timeframe for when 2.8.6.1 will be included in the TWRP manager install list?
[ONE Original Android Development] NoSpamDan:
I too have Win7 x64. Here is what I would do:

Make a new System Restore point just in case.

Make sure your device is disconnected from your computer.

Open a Command Prompt window As administrator

Enter each of the commands below, followed by the Enter key:

Set devmgr_show_nonpresent_devices=1
Devmgmt.msc

Device Manager will open. You can close the Command Prompt window.

In the View menu, select "Show hidden devices" and uninstall any grayed out, device related "ghost" mobile devices under:

Disk drives

Other devices

Portable Devices

Phone

Etc.

*** If prompted, delete the drivers/software for grayed-out "ghost" mobile devices.

Be careful not to remove any Microsoft or computer components. If in doubt, drill into the item and closely review the properties.

When done, close the Device Manager

Uninstall your current drivers and reboot.

Install these drivers and reboot.

Try plugging the device in again...

Profit?!
[ONE Original Android Development] theCroh:
You'll need to ask that from the developer of the TWRP manager.

Lähetetty Nexus seiska 2013:sta Tapatalkilla
[ONE Original Android Development] Zach1928:
Oh I figured it was the same group of devs.. anyway flashing it through recovery worked fine. viva la devs
[ONE Original Android Development] ek69:
It's way more reliable than that twrp manager app that's made by some random person who has nothing to do with twrp AFAIK ... Even flashify works well.

I've had and seen nothing but trouble with that twrp manager app so get rid of it is my advice ;)
[ONE Original Android Development] Zach1928:
Yeah I flashed through TWRP and all is well. However- I could swear I saw a "2.8.6.1" build floating around for the 1+1... am I crazy or not?
[ONE Original Android Development] Rafase282:
No only is the cm12 updates not flashing, but the time for the US easter timezone is nto working. It is one or two hours behind depending on daylight savings settings. Anyone else experiencing this?
[ONE Original Android Development] Heisenberg:
The time has been incorrect on TWRP for as long as I can remember.

Transmitted via Bacon
[ONE Original Android Development] DrNinjaa:
Oxygen OS released....

https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
[ONE Original Android Development] jgcaap:
Anyone having issues after flashing a rom or kernel with twrp, where the hour changes? Is quite annoying...
[ONE Original Android Development] DerRomtester:
Yep +1 for this. But i think it is not related to twrp.
[ONE Original Android Development] Formhault:
I don't think we should care. It's rubbish, anyway.
[ONE Original Android Development] IrisNebula:
Recent versions of TWRP have an issue with anything AROMA based. I don't know if this is bacon specific or a generic problem since I cannot test a new TWRP release on another phone.

This has been reported before but not with much information:

http://xdaforums.com/showpost.php?p=58815813&postcount=841

http://xdaforums.com/showpost.php?p=59693165&postcount=927

The problem is rendering related and seeing some changes on this part in 2.8.5 changelog makes me think that that may have helped :P

When you flash something AROMA based (I used AROMA File Manager to test this) the console shows the text normally up until "(c) 2013 Aroma starting" or whatever and that is the moment AROMA should take over the screen. Well, it doesn't, it stays there with a frozen display but it's actually running, I was able to exit AROMA FM (as I know the positions of it's buttons and vibration also helps) and then TWRP continues normally.

So, AROMA based zips do work but they are unable to output anything on screen. Please take a look at this [MENTION=912474]Dees_Troy[/MENTION]

I'm available for any additional help/info you might need ;)
[ONE Original Android Development] jgcaap:
I've updated to 2.8.6.0 seems to have solved the issues... Have you tried it?

Edit : nvm this is the same... Just tested..

I've been very conservative on changing back to twrp since I had some problems in the past. But seems to be working fine now. No one having any type of problems? Everything seems stable on the flashing part?

Thank you
[ONE Original Android Development] clevebb:
Others are mentioning 2.8.6.1 and I haven't seen it everywhere. Many people are imagining it, don't worry.
[ONE Original Android Development] PeterGuru:
Time Zone Issue here, too ...

I have the same issue, and have been having the same issue for a long time.

Like you, I'm in the Eastern time zone; however, if I select this zone, and then check the Daylight Saving Time box, I am always one hour too early.

My only option has always been to select the Atlantic time zone with the Daylight Saving Time box checked. True, it's not the ideal solution, but TWRP will show the correct time.

Peter

---------- Post added at 03:32 PM ---------- Previous post was at 03:28 PM ----------

There are many things in this world that some people imagine, hence the quotation in my signature. ;) For instance, I often imagine that, one day, I will be filthy rich. Alas, my silly imaginings are simply a delusion. Thankfully, though, I'm well aware of my fictitious fantasies.

Peter
[ONE Original Android Development] clevebb:
Unless the physical part of the world we see is the imagined part... Science requires a mind open to possibilities, to rule out religion is, itself, unscientific.

Still haven't found 2.8.6.1 http://dl.twrp.me/bacon/

Edit: just because it's not found doesn't mean it doesn't exist ;)
[ONE Original Android Development] cobra698:
Hi,why don t flash?[emoji26]
[ONE Original Android Development] Vonnegut:
You must be rooted.

Open an ADB shell or install a terminal emulator like this one https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en

After that, write the following 3 commands:

su (press Return)

dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)

dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)

Backup files modemst1.bin and modemst2.bin will be created on the root your internal storage.
[ONE Original Android Development] DuckMcQUack:
Perfect! In case of corruption i just paste these in their original location?
[ONE Original Android Development] Vonnegut:
Move both files into your PC.

If needed, you can flash'em in fastboot mode:

fastboot flash modemst1 modemst1.bin

fastboot flash modemst2 modemst2.bin

P.S. Penso che metterò le istruzioni anche su Androidiani
[ONE Original Android Development] DuckMcQUack:
Call me stupid but when i connect my phone to my mac i can't see the files with android file transfer as well as in windows.

Any clue? They're actually there as i can see them with root browser.

G

PS: Ciao :)
[ONE Original Android Development] Vonnegut:
Weird. Maybe that's due to the MTP connection (not showing system/executable files?).

Anyway, just change their extension from .bin to .bak and they'll show up.

I chose the .bin extension but it doesn' really matter. You can name them whatever you want.
[ONE Original Android Development] bud77:
Happens to me sometimes, just move them to another folder, and they will show up (or rename as told above)
[ONE Original Android Development] PeterGuru:
Default ui.zip Theme file ...

Where can I get a copy of the default ui.zip theme file?

I'm using an "xda" theme; however, it does not have the option to turn off touch vibration, whereas, the default theme has it. I would like to merge this particular function from the default theme into my xda theme.

Thanks,

Peter
[ONE Original Android Development] DuckMcQUack:
Strange, i did move the files and rename them to .bak extension without success.

I just solved the issue uploading the files to my dropbox and pasting them on the HD of my Mac.

Now to flash roms ;)

:good::laugh: :highfive:
[ONE Original Android Development] bud77:
Using stock file manager ? If yes, try next time with the app "file manager" from playstore
[ONE Original Android Development] DuckMcQUack:
Cm file manager and root browser.

To be honest i paid for the stupid root browser and i have to admit that it is really an awful quality app. It happens sometimes that it fails to copy paste files and even that it makes operations, said being successfully completed, even if in reality they didn't succeed. No updates since months ago, too. Totally disappointed.

G
[ONE Original Android Development] DerRomtester:
Is this recovery supporting f2fs filesystem ?

If not can you add this pls ?
[ONE Original Android Development] dansou901:
You should be using ES File Explorer, it's free and much better than Root Explorer...
[ONE Original Android Development] DuckMcQUack:
Quote that.
[ONE Original Android Development] Vonnegut:
I wasn't aware how faulty can be an MTP connection. It wasn't a matter of file extension: MTP acts weird. Anyway, turning it off and on again seems to solve the problem.

As for dropbox..well, that was a bad idea, i fear. Transferring anything (disk to disk) on a cable is a very reliable way to copy files. On the other hand, transferring files via internet can be quite dangerous. I'm sure you have faced a corrupted download here and there...that's because little bits of code can be lost on the net.

I would never flash any sensible partiton with a downloaded file before checking its MD5 hash. Go figure an uploaded and then downloaded one!

Even a "one bit" corruption can be letal. So i warn you to not use'em.

I made a flashable edify script here http://www.androidiani.com/forum/mo...one-recovery-custom-e-root-5.html#post5951201 in order to backup each and every partition of the main block (179). It create a folder (named MyBackup) on the internal storage. It does include all of the blocks except the ones with an asterisk...but the bootloader (i like to have a backup of my unlocked bootloader for future uses).

P.S. Ti conviene rifare il backup completo e riprovare a copiarlo via MTP. Ciao!
[ONE Original Android Development] DuckMcQUack:
I know it is a bad idea but I did it all on wifi and just as a temporary solution as I keep the original files on the Sd of my phone anyways. I will try again to download them to my hard drive as soon as I will connect my phone to my computer next time...you know I'm lazy XD

Inviato dal mio One utilizzando Tapatalk
[ONE Original Android Development] pwnyu:
Anyone find it takes a long time to boot into the recovery?
[ONE Original Android Development] störte:
Yes agree on that. Longer than other Recoveries
[ONE Original Android Development] DARKCHYLDX101:
Try updating to latest with twrp manager found in play store. 2.7.1.1 is available. It's a little faster.
[ONE Original Android Development] pwnyu:
Did this via the twrp manager and it bricked the phone.. it was set up as "Bacon" and downloaded 2.7.1.1 and then once it installed and rebooted it wouldn't go into recovery. I got into android with no wifi/network/imei e.t.c, so it corrupted my EFS. booted into fastboot and flashed the fast boot twrp 2.7.1.1 img and got it back and running..
[ONE Original Android Development] playya:
How did you get it back up and running - via a nandroid or did you flash img files
[ONE Original Android Development] NuLLV01D:
You must be using the OxygenOS Firmware. Flash the latest CM nightly or flash the 21/03 firmware from [MENTION=4842497]MMWolverine[/MENTION] thread in the general section
[ONE Original Android Development] fireforhire:
So... MTP is still broken?
[ONE Original Android Development] dmarden:
Has always worked fine for me.
[ONE Original Android Development] anshumangoyal:
Official Page is still showing 2.8.5.1 release of TWRP, but the links here shows 2.8.6.0. Is there any reason why official page at: http://techerrata.com/browse/twrp2/bacon is not showing the latest release.

Or, 2.8.6.0 is the beta non-tested release?
[ONE Original Android Development] Heisenberg:
That's because techerrata.com isn't the official page, it's a mirror, and their official page says that techerrata might not be up to date. The link to the actual official page is in the second post.

Transmitted via Bacon
[ONE Original Android Development] anshumangoyal:
Jut to re-confirm is this the official page? http://twrp.me/

I don't want to screw my-self with wrong recovery image and get F*****
[ONE Original Android Development] Heisenberg:
I literally just said the link is in the second post, so if that's the link from the second post the answer to your question is yes.

Transmitted via Bacon
[ONE Original Android Development] shoman94:
Nevermind... Goodbye TWRP Manager Hello Flashify!
[ONE Original Android Development] sabrefresco:
Yep. Probably a scaling issue because I use a theme with TWRP (MultiROM) and it broke after the update. Slide bars appeared wrongly scaled. The dev of theme released an update for it and things were OK. I too noticed that AromaFM works as long as you know where the buttons are, it just doesn't show up. Let's hope this gets fixed. Tried searching for this on the Nexus 5 and Nexus 6 TWRP threads and found no results. I thought I'd have better luck with their sub's larger user base. :(

EDIT:

The beta version of AromaFM seems to be working [MENTION=2282431]twr[/MENTION]P 2.8.6.0. Exiting gives me a black screen though. I used the b7 from here.
[ONE Original Android Development] sam911x:
Where can i find .zip of the latest twrp?. I want to flash via recovery just want to avoid flashing through fastboot mode.
[ONE Original Android Development] CBpbxEcmecmBeH:
C'mon use flashify!!!! :)
[ONE Original Android Development] navinthomas:
Woah! So, by using that app I can basically flash the recovery.img from the phone itself without getting into fastboot, using a PC ....bla ...bla .... and all that cumbersome ****? :confused:
[ONE Original Android Development] DocteurN:
Yes exactly ! ;)