yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] :
I want to report a bug. I have flashed twrp 2.8.5.1 and since then, my aroma installer zip file doesnt load anymore. So I have to switch back to the last working version of twrp (2.8.4.0). I hope, that this will be fixed in one of the next versions. Thanks.
[ONE Original Android Development] Uqbar:
Why I hate IMG files

It's not just convenience.

It's more about reliability, safety and "universality".

With the ZIP (aka Update) format you also get:

protection against transmission corruption

protection against flashing for the wrong hw

ability to easily flash from non-TWRP recoveries

1.

In case your download is incomplete (If you can get a corrupted download then you are doomed!) either from the net or from PC to device the plain IMG will be flashed leaving you with a (semi-)bricked device. The ZIP needs to be intact in order to be uncompressed.

2.

The ZIP contains information that can be checked before flashing. Like correct hardware identification check. A plain IMG file doesn't allow (yet) for such checks.

3.

If you are coming from another recovery (with no straight IMG support) you need to attach a PC with tools and libraries or to install a specific app that requires root. The ZIP format is "universally"(tm) supported by recoveries, even stock ones. And you'll need to reboot your device anyway in order to check that the recovery is in place.

Then, if the Bacon TWRP port maintainer (Dees_Troy, I presume) is willing to go on with IMG files, then it's his/her choice.

With plain IMG file users won't get any extra value/feature/benefit when compared to ZIP, just more risks,

in my opinion

.
[ONE Original Android Development] Heisenberg:
1. All downloads' md5 should be checked anyway to verify the integrity. Even if it's a zip you still need to check it because a bad zip can just as easily brick a phone.

2. So just don't download something that isn't meant for the device. Easy. Anyone who downloads a recovery for a different device probably has no business flashing anyway.

3. Those tools should be setup and available anyway. Firstly, because that's how you unlock the bootloader. Secondly, because any modder should have a working fastboot environment (for many reasons).

You mention universality, there already is one universal format and method for flashing pretty much any partition; the image and via fastboot.

Transmitted via Bacon
[ONE Original Android Development] Uqbar:
Why I (still) hate IMG files

There has never been any official checksum in the official repository so far. So none could check them. How did you check it?

If you have multiple devices to flash, you download multiple images. If you can do it from your device, then it'll be less error prone, not error free. With the ZIP you are really error free 100% of times provided that the ZIP has been correctly packaged.

Mistakes are here just behind the corner. Bypassing the ZIP device check just adds more risks.

Partially true. I used those things just the first time. Everything else can be done from the device itself. This is really more convenient.

True if you have a PC. False if you are on your own with your device.

I can easily be proved to be wrong, but I would say that you need a PC with USB cable, drivers and tools to unlock (just once) or to unbrick (I hope never) your devices.

For anything else you have Masterc^H^H^H^H^H^H^Hthe update ZIP format.

It's 15 seconds work to go from ZIP to IMG. It's not that trivial and easy the other way around.

One more thought. If you decided not to go the Google Play way, you won't be able to install Flashify (unless you download it from unofficial sources). TWRP manager is also available as an official download, but this could break the Google policies and could lead to it to be kicked out of Google Play. It'll not be a problem, thogh.

If TWRP needs to gain money from the TWRP manager with ads (I've tried it just once, long ago), then make it clear. It's not a sin, it's the business: openness is a great value nowadays. And they can still use ZIPs just like CyanogenMod Update does to play it safer.
[ONE Original Android Development] Lanchon:
IMHO this is a ridiculous answer where it is not plainly mistaken. i will not waste time telling where is which or why; non-prejudiced readers should be able to tell. Uqbar, thanks for reasonably arguing the benefits of zips.
[ONE Original Android Development] Uqbar:
You are welcome ... and thanked too.:D
[ONE Original Android Development] Heisenberg:
Yes there are, there always has been, on every single download link, once you open the link.

You can still make the error of downloading the wrong recovery to your device, for the exact same reason that you could do it from your PC. It all relies on human accuracy. And no, you're not error free 100% of the time, I'd bet that the amount of times a bad zip has bricked a device is higher than the amount of times a fastboot flash has bricked a device. Bad zips happen, bad flashes happen.

Every single modder needs a working fastboot environment. Every. Single. One. Just look at every q&a section for every single device on XDA. They're full of thousands of threads of people who can only use fastboot to save their device from whatever stupid mistake they made. You seem to be passionate about mitigating risk, then you should always have a working fastboot environment, because you'll be crying on the day that you need it and don't have it.

This is all irrelevant to the debate.

The most powerful argument is this: look at the OEM's, all of their stock tools, look at every recovery for every device, look at anything partition related that needs to be flashed to Android. They're all images. There's a reason for that.

Transmitted via Bacon
[ONE Original Android Development] :
2.8.5.0/1: Fix handling of mapped zip files for OTA updates (CM12 updater)

Unfortunately it doesn't work for me with today's cm nightly for bacon. Am I the only one??
[ONE Original Android Development] Heisenberg:
I was hoping when I received a quote notification that you might have something constructive to add to the conversation, do you or not? I'm merely pointing out some things to the other gent, in a respectful manner, in order to discuss the matter. Your post only seems to be aggressive for the sake of it.

Transmitted via Bacon
[ONE Original Android Development] Uqbar:
My mistake. I beg for your forgiveness.:o

With the ZIP you cannot flash the wrong file! No way.

Bad zip happens to the packager. One person's fault none can protect you from. Bad flashes happen to hundreds of persons. The ZIP is to protect against those mistakes.

A recovery is a very delicate and sensible piece of software. I would ensure as many protections as possible. Not fewer and asking/scaring people.

Why?

Which reason? For sure they almost all still put ZIP file support in recoveries and distribute stuff as ZIPs because of some safety reasoning.

And, anyway, before doing what the others do, I prefer to try to understand, think and maybe challenge it.

Look at this very thread (as well as almost all other TWRP threads). At every release there is someone as stupid as I am asking for the ZIP.

Either this thread is full of fools, or maybe there is something missing or highly requested. Again, in my opinion.
[ONE Original Android Development] tobitege:
Ideally, device-specific flashable ZIP's have a device assert at top of their updater-script to prevent errors, such as

assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" || getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + "."););
[ONE Original Android Development] Uqbar:
That's what I am talking about.

I still don't get the point in making error prone manual checks when there are reasonably safe automatic ones. W H Y ???

Accordingly to timmaaa's answer, there is some reason for OEMs to go the IMG way. I'll wait to know more about that.

In the meantime, I think that a recovery upgrade is nothing different from any other upgrade.

Thousands of ROMs all get distributed as ZIPs. Millions of mods all get distributed as ZIPs. Other recoveries get distributed as ZIPs.

And all recoveries support ZIP flashing. Also TWRP.

Someone could say that a recovery can be seen as something more important than a ROM or a mod and needs more care, more attention.

But more care and more attention implies, in my opinion, more reliability, more checks, not fewer.
[ONE Original Android Development] thepaperescape:
Stop arguing and help people... bump: http://xdaforums.com/showpost.php?p=58813182&postcount=839
[ONE Original Android Development] L10nH34Rt:
Check your device drivers. You should have ADB

Composite

blah blah interface installed, not the non composite one.

You should be able to copy paste it via MTP.
[ONE Original Android Development] Uqbar:
I think this could help you next time you'll flash TWRP, though...:p
[ONE Original Android Development] bombadier:
to rule out problems with the latest recovery can you downgrade to 2.8.3.0 and see if that works ? I am also having problems with the latest and MTP not working, although adb and fastboot both work and windows can see the bacon, just not in recovery

UPDATE I just downgraded to 2.8.3.0 and MTP in recovery is working fine windows can see it and I can copy stuff to/from
[ONE Original Android Development] Lanchon:
no, you don't need to check checksums of zips. and fyi, even fastboot directly handles zips. posting bare img files on the internet is dangerous and braindead. anyone doing that ignores the realities of the internet. absolutely no serious entity would do it, just as google and samsung of course don't. there is no reason to post a bare img file except laziness, and if you can't be bothered to make a flashable zip, at least wrap it in a plain vanilla zip.

there, something constructive, hope you like it. the problem is, i don't want to enter into this argument. you are defending the indefensible, even after someone took the trouble of explaining why. it seems you are arguing from an emotional position and i wont be trolled into it. i just wanted to reassure Uqbar and remind him that a vocal minority is not consensus, and that his point was well argued and probably accepted by almost anyone who read it.

if you consider aggressive that im not ready to argue with you, it's not: it's just that you didn't present reasonable arguments that i would feel compelled to counter, again IMHO. let's agree to disagree and be done with it.
[ONE Original Android Development] bombadier:
After fiddling about with things this afternoon it seems like my MTP problems were somehow connected to the driver seem to have fixed my problems as I can now access the device in recovery and when booted into the rom
[ONE Original Android Development] z31s1g:
Who is willing to go the extra mile?

IMO there's no point in argueing about the usefulnes of flashable zips. They are.

But do we really NEED them for TWRP? And if so, who SHOULD provide them?

TWRP developers most likely have an automated build process for the recoveries.

Once the image is built, they have something they can distribute, and users already have different options for installing the images.

Wrapping the images in flashable zips would add a step to the process, and if one takes into account the sheer number of devices that TWRP is provided for, no one can be asked to do that manually. So someone knowledgeable has to come up with a way to automatically build the "more fail safe" zips, maybe then the TWRP guys would add this step to their build process.

But calling them irresponsible for providing "just" images seems plain ungrateful to me.

And regarding Bacon, as far as I can tell you guys have [MENTION=3306843]kantjer[/MENTION] who's providing the zip for your device minutes after a new version becomes available.

In this thread, everyones preferences are being catered for. So you guys just really like to argue, don't you? ;)
[ONE Original Android Development] Uqbar:
No way to justify IMG files so far

The same who compiles/packages/distributes the IMG?

It's automated! Then you add the extra step (I presume it takes less than 5 minutes to run) to the original process and you magically get the ZIP.

Do you really think that the ZIP wrapping is done manually? Seriously? Let's ask the CyanogenMod guys how do they automatically wrap hundreds of IMG files!

Came on! I cannot believe what I am reading here! It's the 21st century since some time now!

If I am not wrong none called irresponsible anyone. Maybe "lazy".

No, I definitely don't.

I am trying to challenge this unjustified risk of delivering IMG files.

Scattering the process between two steps will just add delays and error opportunities.
[ONE Original Android Development] z31s1g:
Mate, all I was trying to say is that endlessly discussing this matter in this thread will not change the way TWRP devs are distrbuting their work.

If you don't want it to change, then it's an argument for the sake of having an argument. If you want it to change, head over to

the IRC channel , that's where the lazy guys hang out.
[ONE Original Android Development] Uqbar:
Ah!

I wouldn't count 6 or 7 messages as "endless discussion", do you?

I don't accept non-technical answers to technical questions, this is why I have been "challenging" timmaaa's reasoning.

As a recognized contributor seems to have no technical answer (I won't count "because there is some reason" as an answer), then I will go serach it somewhere else as you suggested.
[ONE Original Android Development] jejehtc:
MTP works well for me on the TWRP 2.8.5.1 .The flash custom rom for no worries either
[ONE Original Android Development] xanthrax:
[MENTION=1966251]Uqbar[/MENTION]

I understand your point, apparently for sake of safety, right ?

Well, creating a zip involves far more variables, you can try to do it yourself without using a zip template, just do it like a boss and you'll see how many things you should take care off to make it work and safe

The img format requires only one time your full attention to download it and little knowledge to flash it

Please do not involve the recognize contributor title in here, it's absolutely not relevant and somehow offensive

Don't blame someone when you can't understand or accept facts which are beyond your principles

Sent from my Darkside of 1+1
[ONE Original Android Development] Dees_Troy:
The main reason we provide image files instead of zips is because:

make recoveryimage

spits out an image file.

Making a zip after that requires more work that yes, can be scripted eventually. In a few cases, namely with loki images, I do produce zips. Still it's more work. Further, you cannot flash those zips on devices that are running stock recovery. Noobs are incredibly noobish and I guarantee you I would get support emails from noobs saying "zip signature verification failed" from people trying to flash the zip in the stock recovery.

But really, it boils down to what's the least amount of work for me. Supporting recovery is a LOT of work, especially when you're supporting 60 to 80 devices. Don't claim to know what's best or debate how it should be done until you're doing it yourself at a large scale.
[ONE Original Android Development] xanthrax:
Thanks Dees! This is more than a "technical" answer!

Sent from my Darkside of 1+1
[ONE Original Android Development] Heisenberg:
There you go, [MENTION=1966251]Uqbar[/MENTION], there's your technical reasoning. Sorry I couldn't provide it myself, I've been far too busy with my responsibilities here on XDA to continue debating it.
[ONE Original Android Development] LeroViten:
Yes, doesn't work for me either. [emoji6]

~• Posted via Bacon Flavoured Tapatalk •~
[ONE Original Android Development] Crash:
+1

Thanks in advance

Edit. Don't worry already read about why aroma won't work.
[ONE Original Android Development] Lanchon:
lol
[ONE Original Android Development] major_daz:
+1

I can also confirm, cm12 nightly unable to automatically update on 2.8.5.1

I can manually flash though, could it be a bug with cm12?
[ONE Original Android Development] xanthrax:
I haven't checked your "+1" meaning but I assume you're not happy with twrp manager update, well, do it manually, isn't related to cm12 or something, the app just doesn't work properly
[ONE Original Android Development] bL33d:
Is any recovery working with auto update cm12?
[ONE Original Android Development] xanthrax:
What do you mean?
[ONE Original Android Development] bL33d:
I have to manually install cmudater zip because when it boots into twrp it does nothing. Does clockwork recovery auto run updater ?
[ONE Original Android Development] knuspertante:
I remember in the first cm12 nightly announcment I would read cm12 nightly doesn't support openrecovery script at the moment, ...
[ONE Original Android Development] Nos_20:
Guys,

Just wondering if anyone could help me out. I got my One Plus One last week. [emoji3] I unlocked it and flashed 2.8.5.1 recovery on it. I an using SlimSaber and AK kernel. [emoji41]

I am trying to change the splash screen via the recovery. It says everything has worked but the splash screen doesn't change.

It appears that the recovery isn't saving the custom_splash_twrp.img file to the storage. It is like it doesn't have write access it something?

Thanks in advance for any help. [emoji106][emoji106]
[ONE Original Android Development] Wolfman017:
Hi,

The techerrata.com web site seems to be down. Is there a mirror where I can download the latest version of TWRP ? (img)
[ONE Original Android Development] bombadier:
[MENTION=779471]Wolfman017[/MENTION] PM sent
[ONE Original Android Development] tobitege:
Look in One forums, there are custom builds by [MENTION=3814731]katinatez[/MENTION]
[ONE Original Android Development] NuLLV01D:
Newest Unofficial Build by [MENTION=3814731]katinatez[/MENTION]

https://www.androidfilehost.com/?fid=95916177934527894
[ONE Original Android Development] Natakranta:
Did you flash

UPDATE-AIK.Mobile.Installer.v1.7-ALL.zip prior to it?

Which method are you choosing, theme one or twrp built in one?

Is your custom splash jpg in correct size? 1080x1920 pixels portrait?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] Nos_20:
It was a bad download of the twrp IMG file. I redownloaded it on my laptop and all is well!
[ONE Original Android Development] Lanchon:
this kind of thing is why twrp should be distributed in a zip. even if it's a regular non-flashable zip. he was lucky nothing bad happened.
[ONE Original Android Development] Heisenberg:
Both images and zips can be corrupted during a download, zips aren't immune to that.

Transmitted via Bacon
[ONE Original Android Development] Lanchon:
they have CRCs, they won't unzip so you wont flash.
[ONE Original Android Development] Heisenberg:
Fair point. But the dev has clearly explained that TWRP won't be distributed in zip form, and why, so I'm not sure why you guys are still flogging this dead horse.
[ONE Original Android Development] nsmart:
TWRP seems to have problems decrypting data partition with cm12 nightlies. I never tried it with aosp Lollipop. Details can be found in issue #333 on TWRP Github https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333
[ONE Original Android Development] burnski:
has anyone else found that since daylight savings time, TWRP has been shifting the time by an hour in the wrong direction? example. its 1:50pm EST w/ DST. TWRP thinks its 11:50am. Ive set the time zone, and the DST flag but after a reboot the time is still out by 2hrs.
[ONE Original Android Development] mnhs1010:
My 1+1 getting too much hot in recovery during backup and do doing any other activity
[ONE Original Android Development] Heisenberg:
That's normal, it's using a lot of resources when doing a backup/restore.

Transmitted via Bacon
[ONE Original Android Development] PeterGuru:
Time Zone issue here, too ...

I have the same issue. Now TWRP is 2 hours behind actual time.

Peter
[ONE Original Android Development] srynoname:
Forgive me if this was previously asked, but there are too many answers to check them.

My OnePlus One is encrypted. If I now take a backup using TWRP, is it stored on the /data partition? Will it be encrypted when it is written to the data partition? (actually I am not sure if the partition itself is encrypted or if there is only file level encryption, meaning TWRP would have to actively encrypt the file before writing it).

Thanks for any hint on this!
[ONE Original Android Development] sgreene59:
Numeric pattern

Not working on my install. Entering from numeric keyboard.

Steve
[ONE Original Android Development] apfo:
I can't update CM12 wiith this recovery. There is an error that says that the zip file is corrupt when I update from settings, about phone. The phone restarts to the twrp recovery but always says that the zip is corrupt and when I try to install manually it works but the phones freezes when it's finishing to update apps. Can anyone help me? Thanks in advance
[ONE Original Android Development] Heisenberg:
Are you checking the md5 of the zip to verify its integrity before attempting to flash it?
[ONE Original Android Development] strategist99:
[MENTION=4153349]timmaaa[/MENTION], dear mate are you using the latest version 2.8.5.1?

could u help me with mtp mode??

facing issues of mtp not connecting while in recovery and the bloody 2.8.3.0 version has lot of bugs, keeps restarting and may or may not flash..

so..

kindly help..

regards
[ONE Original Android Development] Heisenberg:
Just flashed 2.8.5.1 to test for you, MTP working fine for me. Try going into the mount menu in TWRP and toggling MTP off and on again while disconnected, then connect to your PC again.
[ONE Original Android Development] strategist99:
well brother, I have already tested with all the later versions higher than 2.8.3.0 the way you have mentioned.

enabled-disabled MTP and also rebooted recovery, etc..

but to no avail..

anything to do with drivers??

but then again how can the drivers function on 2.8.3.0 version , then??

maybe just my bad luck.

i must say this 2.8.3.0 version is irritatingly frustrating..

thanks for ur time and help though

regards
[ONE Original Android Development] Heisenberg:
Which drivers are you using? You could test by uninstalling them and installing again (with reboots of the PC between each uninstall/install.
[ONE Original Android Development] Fabioo123:
Even for me Mtp from recovery not working. Tried 3 different computers. A month ago worked fine. I also tried to put an older version of TWRP but nothing.

I have not changed in any way drivers
[ONE Original Android Development] apfo:
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------

No. How can I do it? I saw an option in the recovery but I'm not sure. Thanks.
[ONE Original Android Development] apfo:
This is the error that I always get in the recovery when I update from settings, about phone.
[ONE Original Android Development] :
For me the same problem with bacon and manta; mako and grouper are working/updating fine. All have the latest twrp versions installed.
[ONE Original Android Development] Heisenberg:
Notice how on the download page for CM each nightly has an md5 listed? Once you've downloaded the file you need to use an md5 checking app to make sure the md5 of the downloaded file matches the md5 listed on the CM site.

Transmitted via Bacon
[ONE Original Android Development] jgcaap:
Isn't twrp giving problems to you? Thanks
[ONE Original Android Development] Heisenberg:
Nah it never has.

Transmitted via Bacon
[ONE Original Android Development] apfo:
I hace checkedmd5 and it's correct ?