yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Chromium:
Info

This is Team Win Recovery Project (TWRP) 2.7.1.0 recovery for the HTC Desire (bravo). For more info read here.

Working

Flashing zips

Wiping

Nandroid backup/restore

USB Mass Storage

Charging

ADB (including adb sideload)

All other basic stuff

Not Working

LED while connected to USB/power

Downloads

Version 2.7.1.0

ZIP (flash via custom recovery)

- Download

- md5 checksum: 0a9c4f4de72de5907163a1245afc265f

IMG (flash via fastboot)

- Download

- md5 checksum: 5a07ce1a1f165a8fa82c6e2d1a79a1ce

Version 2.7.0.0

WARNING: 2.7.0.0 has some problems. If you value stability use 2.6.3.0.

ZIP (flash via custom recovery)

- Download

- md5 checksum: cdfdee4710ee88414d3f458fec9a5933

IMG (flash via fastboot)

- Download

- md5 checksum: 63ea82ce92186db9ebcbcf3f14f03f61

Version 2.6.3.0

ZIP (flash via custom recovery)

- Download

- md5 checksum: 5271f8b30edf095a69456cee74df5c59

IMG (flash via fastboot)

- Download

- md5 checksum: d775b6deb5044c8939a303df442de9df

Instructions for ZIP

1. Download the zip of the version of your choice above. Check that the md5 sum of the zip is correct.

2. Reboot into recovery.

3. Flash the zip.

Instructions for IMG

1. Setup fastboot and install these drivers.

2. Download the provided img of the version of your choice and put it on your desktop. Check that the md5 checksum of the img is correct.

3. Turn your phone off. Boot it into fastboot using back button + power button, then plug it into your computer. On your phone it should now say "FASTBOOT USB".

4. Open command prompt and enter the following commands:

fastboot devices

If your phone (serial number) shows up continue. If not, it means that your drivers aren't installed correctly and your computer cannot recognize the phone. Do not continue until you are able to get fastboot devices to return the serial number of your phone.

cd Desktop

fastboot flash recovery FilenameOfRecovery.img

After the installation is finished, proceed to the next step. (it should only take a few seconds to install)

5. Unplug the phone, and go back into the bootloader. From there you can scroll down to RECOVERY, and boot into it.

Sources

github.com/TeamWin/Team-Win-Recovery-Project

github.com/Evervolv/android_kernel_htc_qsd8k

github.com/Chromium-/bs_android_device_htc_bravo

Thanks

- Dees_Troy and the others who contribute to TWRP

- Evervolv for the device tree and kernel

- [MENTION=4346614]abaaaabbbb63[/MENTION] for testing

- [MENTION=5154992]tommypacker[/MENTION] for stealing my reserved spot
[Desire Android Development] tommypacker:
Yeeeeaaaahhhh!!!
[Desire Android Development] Chromium:
Reserved

...

Edit:
[Desire Android Development] ze7zez:
Very, very much!

.

The long awaited version finally on our Bravo.

.

There is no better recovery.

.

What version of the kernel is used in this recovery?.

.

I cordially greet.

.
[Desire Android Development] Chromium:
2.6.38
[Desire Android Development] abaaaabbbb63:
Haha!! You weren't quick enough :P
[Desire Android Development] ze7zez:
Knock, knock, knock! Mr.Mefisto!

.

Did you notice the existence of TWRP and you add the HTC Desire (Bravo) Index?

.
[Desire Android Development] zinconnu:
Thanks for this recovery!

Does it have features that 4ext doen't?
[Desire Android Development] ze7zez:
TWRP has full access to the busybox command line.

Other Recovery have only what propose icons.

.

TWRP is the most powerful tool for advanced users.

Users less advanced receives the same icons with functions like any other recovery.

.

Useful Links:

teamw.in/project/twrp2

teamw.in/twrpfaq
[Desire Android Development] zinconnu:
Thanks for your explanations! I will give it a try so.

EDIT: Unfortunately it is not compatible with ClockWork/4eXT backups.
[Desire Android Development] ze7zez:
.

There is no need to TWRP recovered backup from other Recovery.

Since there are system applications, such as "Nandroid Manager", "OBackup - Nandroid backup", and more.

.
[Desire Android Development] weslyr:
Thank you Chromium_ for this release! Your effort to keep this device along the top is much appreciated.

I was already wondering whether a newer version of TWRP was possible on our device so this release comes with great timing.

Also I was having trouble flashing the zip-file through recovery TWRP 2.6.0 ("not able to open ZIP").

Instead I used the alternative (and IMO much easier) method of flashing the image file:

In terminal as root, issue the following command: flash_image recovery openrecovery-twrp-2.6.3.0-bravo.img

Worked like a charm. Thanks again!
[Desire Android Development] abaaaabbbb63:
Weird.. The zip flashed just fine from 4ext.
[Desire Android Development] 2012katas:
Thanks

Thanks [MENTION=4883664]Chromium_[/MENTION] ......I sincerely hope u keep updating TWRP whenever new versions are available.......cheers :cowboy:
[Desire Android Development] jukyO:
Difference between this one and one from nikez.nu site?
[Desire Android Development] paolo-red1:
http://teamw.in/project/twrp2 see What's new in 2.6.1.0 and What's new in 2.6.3.0:
[Desire Android Development] jukyO:
Great! Any chance to have support of charging in recovery?
[Desire Android Development] Chromium:
I plan to. Right now I believe this is the latest version (2.6.3.0). I've merged all of the open commits from their github and gerrit. Although you may see other devices seem to have newer versions (ie: 2.6.3.4), i think those version increments are device specific fixes.

Newer version. And I've also compiled this with a newer fstab found in more recent commits on evervolv's github, which may fix some stuff.

I'll look into it.

Edit: After talking to Dees_Troy, I realized that it is actually charging. The "+" icon shown beside the battery percentage (as shown in the screenshot attached) shows that its being charged. And I also tested it just to confirm, and the charge definitely is increasing. The only slight issue is that the LED light that usually comes on to indicate charging is not coming on, but dont worry...it is being charged.
[Desire Android Development] ze7zez:
What's new in 2.3.0.0:

Added charging indicator while in recovery (only updates once every 60 seconds)
[Desire Android Development] jukyO:
Thanks [MENTION=4883664]Chromium_[/MENTION] for elaborating.
[Desire Android Development] paolo-red1:
Do you have any idea why I have 'updater binary error' flashing twrp 2.6.3.0 from 2.6.0.0 recovery (install zip).

I can't use zip method in bootloader beacuse of up volume broken and I can't use fastboot use in windows 8 or in vitualbox.

EDIT: solved, I use updater script from evervolv, changing in twrp zip.
[Desire Android Development] Chromium:
Updater binary is what i think you meant.
[Desire Android Development] paolo-red1:
yes sorry, it was a typo
[Desire Android Development] kostelo:
2.7.0.0 update?

Hi there Chromium, would it be possible to compile 2.7.0.0 update of TWRP for desire? Thanks in advance.
[Desire Android Development] Chromium:
Im attempting it now ;) This is from their site:

Edit: So it built the image, then realized it was too big and deleted it. lol: http://i.imgur.com/FPJJdJy.png

I have no idea about recovery stuff, but im currently on twrp irc trying to find a solution.
[Desire Android Development] 2012katas:
[MENTION=4883664]Chromium_[/MENTION] is indian Priyesh..... :cowboy:
[Desire Android Development] Chromium:
Yeah.

So it was easier than I anticipated:
[Desire Android Development] Chromium:
Added download links for 2.7.0.0. I haven't thoroughly tested this so be aware of that. However with that being said, I believe most things should be working just as they were in my previous build. Feedback is appreciated. Thanks.
[Desire Android Development] djfirefy:
I tried both of the possibilities, .zip and .img, but no luck! I followed all the recomended steps. Is it possible to be something wrong with the downloaded files? I appreciate your work! Thanks a lot!
[Desire Android Development] Chromium:
What specifically is the problem?
[Desire Android Development] djfirefy:
E: Error executing updater binary in zip /sdcard

Error flashing zip /sdcard/openrecovery-twrp-2.7.0.0
[Desire Android Development] Chromium:
I just redownloaded the zip and flashed it, and it worked fine. Your issue is probably that your current recovery is too old
[Desire Android Development] ckpv5:
I have the same problem when flashing it with your previous recovery TWRP 2.6.3.0

I tried to fastboot flash it, error too

View attachment 2625126

I maybe wrong as I don't know much about recovery. I guess the recovery size is the problem as your recovery size of 4660 KB is maybe bit bigger than the size of recovery partition which is around 4608 KB.

So I rebuild your recovery to make it smaller by removing all the Superuser files and the size now reduced to 4600 KB.

And successfully flash the rebuild one.
[Desire Android Development] Chromium:
Actually I had that issue at the beginning due to the recovery being too big. Then I removed the Superuser.apk as you said and rebuilt, and that time it worked successfully. Like I said, I flashed both the img and zip and they both worked fine. Maybe the recovery partition varies in size from device to device?

Was anyone else able to flash it successfully?
[Desire Android Development] kakofonija:
uff, i can't flash it either...
[Desire Android Development] Chromium:
Very weird. How did it flash on mine?

Did it work for anyone else? Its got about 45 downloads...
[Desire Android Development] kakofonija:
you have a special one, for developers :D
[Desire Android Development] djfirefy:
My current recovery is not too old! I just flashed TWRP 2.6.3.0 using 4Ext.
[Desire Android Development] Chromium:
Alright I guess the image is indeed to close to the max size allowed on the recovery partition. Im just confused by the fact that it worked fine on mine. Anyways, Ill try reducing the size a bit more. Should be done soon.
[Desire Android Development] martinsgo:
For me is working nice..... Thks
[Desire Android Development] Chromium:
Ok so I just talked to the lead developer of TWRP, Dees_Troy, about this issue. His explanation is that MTD devices (such as the Desire), tend to have many bad blocks on the nand. Therefore on some devices you have less space than on others depending on how many bad blocks you have in the recovery partition.

So essentially, those who had issues flashing have a greater amount of bad blocks on their phone, while those who flashed the image fine without problems have healthier phones (with less bad blocks). Good news for me and [MENTION=548059]martinsgo[/MENTION]. For everyone else...death is coming soon to your phone. :p

I'm currently trying to reduce the size of the image a bit more so that it'll work on your unhealthy devices too. :)
[Desire Android Development] ckpv5:
Hahaha ... what to expect with a 3 yrs and 6 months old device :D

http://xdaforums.com/showpost.php?p=20531773&postcount=170

Anyway, you have a very nice working recovery... thanks for that.
[Desire Android Development] kakofonija:
bad blocks, "shmad" blocks... give it to us :fingers-crossed:
[Desire Android Development] Chromium:
Lol ok. Someone with bad blocks (who got an error flashing my first image) who can fastboot flash the img PM me. Ive got a new img that i need to test.
[Desire Android Development] djfirefy:
I just reflashed 4Ext and after that I succesfuly reflashed TWRP 2.7.0.0! No luck to flash from TWRP 2.6.3.0!
[Desire Android Development] Chromium:
Has anyone tried using Flashify or Recovery Tools to flash a recovery.img on the desire?
[Desire Android Development] kakofonija:
hmmm... pm recovery failed, ill try original one with one of above tools, thanks
[Desire Android Development] kostelo:
Flashed it like a charm here through fastboot.
[Desire Android Development] djfirefy:
Which are the former recovery?
[Desire Android Development] Chromium:
Guys like I said, the problem is the recovery is very close to the size of the desires recovery partition. Im trying to slim it down a bit more.

If you are getting the error when flashing in fastboot, PM so that you can test my slimmed builds.
[Desire Android Development] kostelo:
I was on 4ext touch recovery previously.
[Desire Android Development] Chromium:
Did they work?
[Desire Android Development] kakofonija:
it seems something is wrong with TWRP recovery flashing, like mr. djfirefy I managed to flash original TWRP 2.7.0.0 (3362f40f2672195a160cd54982775b5a) only from 4ext touch, every try to upgrade from old 2.6.3.0 failed, tried again to reflash it from TWRP 2.7.0.0 and it failed also
[Desire Android Development] Chromium:
But the issue with the size not fitting into the recovery partition is also valid, since some users couldnt even flash using fastboot.
[Desire Android Development] kakofonija:
It seems that is not my case, I manage to flash original (3362f40f2672195a160cd54982775b5a) but only from 4ext touch, flashing from 2.6.3.0 (5271f8b30edf095a69456cee74df5c59), 2.7.0.0 (3362f40f2672195a160cd54982775b5a) and flashify failed... I failed to flash pm version also from 2.6.3.0, didnt tried that version from 4ext...
[Desire Android Development] Chromium:
Yeah I undestand. So basically theres 2 problems:

1. The recovery image was too close to the size of the recovery partition on the desire. If your phone had a larger amount bad blocks, it probably wouldnt flash since it couldnt fit.

2. My TWRP builds apparently cannot flash recoveries.

So if you flashed via fastboot and it still failed, it essentially means that your problem was definitely #1.
[Desire Android Development] djfirefy:
I think the issue still remaines! And bad luck...For everyone else...death is coming soon to your phone.
[Desire Android Development] kakofonija:
correct, but i tried via flashify and it also failed, hmmm :eek:
[Desire Android Development] Chromium:
That could be cause the Flashify doesnt support the Desire. Did you try the other app I linked? (Recovery Tools)
[Desire Android Development] kakofonija:
didnt, it is enough flashing for me today or ill get bad sectors in my brain :eek:
[Desire Android Development] kostelo:
Try flashing using the utility I attach, don't know if it has already been mentioned. It has never failed me neither in hboot nor recovery flashing and stuff. Simply unzip, double clik the .exe, click what you want to flash (recovery here), select the .img, wait for the phone to reboot and you 're done.
[Desire Android Development] Chromium:
I just uploaded the new img and zip with reduced sizes. These should work for more people. If it still isnt working for you, this is all I can say...
[Desire Android Development] zarac:
I remember from my early Desire days that there are a few variants of our phones. Some of the most recent ones (PVT4) had their MTD erase block size at 40000, as opposed to 20000 on all previous variants. Even some early PVT4 models have 20000, including mine. Apparently, those models have different NAND chips which use a bigger pagesize and changed partition offsets.﻿

A friend of mine once came to me with his Desire for a custom rom installation. I unlocked it, rooted, and created the same partition layout as mine, fastbooting the same hboot img. I was quite surprised when a rom that fit perfectly on my phone with 500kb free space on system wouldn't fit on his phone. After some googling I found out that my friends' phone was the "40000" variant and after I created a slightly larger system partition using Thalamus' custom partition tool everything was fine and dandy.

For those having problems installing the original 2.7.0.0 download, test if that might be the problem. In terminal emulator or adb shell just type "cat /proc/mtd", if "erasesize" for the partitions says 40000, that's probably it.
[Desire Android Development] Chromium:
Thanks for the info. Mine's also PVT4 with 20000 erase size.
[Desire Android Development] kakofonija:
ill try when needed, cant push thanks, i exceeded thanks button for today and I have lots to thanks for...
[Desire Android Development] djfirefy:
It is possible to be only an explanation, not the entire solution!

After I used terminal emulator, I found that.
[Desire Android Development] zarac:
Of course it only *could be* an explanation. It could mean those "erasesize 40000" devices actually have less space on each partition so images that are very close to the partition sizes might not fit.

If this actually is the case, the only solution is making the recovery smaller, because I'm not familiar with any way of resizing the recovery partition.

Wait a sec! So you're facing this issue on an "erasesize 20000" device?

In that case, disregard everything I said :(
[Desire Android Development] djfirefy:
My HTC Desire is 3 years and 8 month old. And, yes, I am facing issue on an "erasesize 20000" device! See my posts nr. 29, 45 and 57.
[Desire Android Development] zarac:
Well, unfortunately that kills my suspicion about MTD erasesize difference causing this problem. It must be something else - bad sectors or god knows what.

Sorry for false alarm. Nothing to see here, move along...
[Desire Android Development] Chromium:
Im pretty sure this is the problem.
[Desire Android Development] paolo-red1:
I confirm that 1st version of 2.7 released failed but last version in OP is fine. I flashed with fastboot.
[Desire Android Development] Dodgexander:
I get this when trying to install the INT2EXTV2+ zip. I think it might fail because int2extv2+ usually asks in recovery if you want to install swap2int as well, but for some reason you don't get asked with this recovery. I think 4ext recovery worked okay.

'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/CronMod-INT2EXTV2+_signed.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/CronMod-INT2EXTV2+_signed.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
E:Error executing updater binary in zip '/sdcard/CronMod-INT2EXTV2+_signed.zip'
Error flashing zip '/sdcard/CronMod-INT2EXTV2+_signed.zip'

Tried installing zip of 2.7 in op and git same error. Will try fastboot.

Fastboot allowed me to install 2.7, but the problem with i INT2EXTV2+ still exists.

I even tried to install INT2EXT4+. Same problem.
[Desire Android Development] jukyO:
Problem is int2ext.

It uses possibly old update-binary file.

So replace that one with the one from e.g. Chromium beanstalk rom.

Also it might be script in zip needs to be modified.

Edit:

Here a link to update-binary mentioned:

https://www.dropbox.com/s/uw6dwftmbf07wwp/update-binary

So try that 1st.
[Desire Android Development] Dodgexander:
I can't test it right now, but are you sure this is right?

If so, the update script in version 2.7 of this recovery here also is old, as that gives me the same error when trying to update.
[Desire Android Development] jukyO:
Some guy in int2ext thread made some mods which might help:

http://xdaforums.com/showthread.php?p=51219537

He did some mods in the script in order to work with TWRP 2.7.

BtW, installed Chromium latest beanstalk with twrp 2.7.
[Desire Android Development] Dodgexander:
Try flashing the 2.7 version if twrp from the op here, I get the same error. So either the script in that zip needs updating too, or the problem lays with twrp.

I am sticking with ext4 for now, as that works fine.
[Desire Android Development] ze7zez:
twrp 2.7.0.0, 2014-03-11

Install TWRP 2.3.1.1 by by island3r ZIP works fine when the previous TWRP is 2.3.1.1

Install TWRP 2.6.0.3 by by Chromium ZIP works fine when the previous TWRP is 2.3.1.1

Install TWRP 2.7.0.0 by by Chromium ZIP works fine when the previous TWRP is 2.3.1.1

Install TWRP 2.3.1.1 by ZIP not work ( Failed ) when a previous TWRP 2.6.0.3 or 2.7.0.0

Install TWRP 2.6.0.3 by ZIP not work ( Failed ) when a previous TWRP 2.6.0.3 or 2.7.0.0

Install TWRP 2.7.0.0 by ZIP not work ( Failed ) when a previous TWRP 2.6.0.3 or 2.7.0.0

Executing busybox command in the terminal TWRP 2.3.1.1 is working properly and lists the commands.

Executing busybox command in the terminal TWRP 2.6.0.3 is working properly and lists the commands.

Executing busybox command in the terminal TWRP 2.7.0.0 resets TWRP.
[Desire Android Development] ausi:
Version 2.7.0.0

ZIP (flash via custom recovery)

- Download

- md5 checksum: cdfdee4710ee88414d3f458fec9a5933

Can someone please tell me if this version (& previous) of TWRP is the same for all phones (not phone dependant) or there is a specific version for my N7100 phone??
[Desire Android Development] Chromium:
Recoveries are device specific. Don't flash this unless you have an HTC desire, or you will brick your phone.
[Desire Android Development] proadi96:
Can i partition my SD Card with TWRP? :)
[Desire Android Development] Chromium:
Yes.
[Desire Android Development] ltGuillaume:
Does partitioning with this recovery align the partitions correctly, like 4ext does?
[Desire Android Development] Dodgexander:
Hi Chromium, any idea if the error we're getting when installing zips can be fixed?

You can repeat the error just by trying to flash one of your .zip files listed in this thread.
[Desire Android Development] Bobbi lim:
Can I use this kernel to flash 2.2 or 2.3 sense based rom?

Is it stable for charging as I'm using CWM and my phone seems to take longer to charge
[Desire Android Development] Chromium:
I only briefly tested 2.7 and installing a few zips worked fine. As I said, my testing with 2.7 wasnt very thorough, however I did in fact test 2.6.3.0 for a relatively long amount of time and can confirm that its quite stable. I didnt have any problems with it.

I think it should work fine for gingerbread roms too. Charging works fine in both versions, though I would definitely recommend using 2.6.3.0 as it is more stable and consistent than 2.7.
[Desire Android Development] ltGuillaume:
Ouch, this is ugly! I added a password to my backups, but now I can't restore ANY of my backups, since it says the password is incorrect (which is absolutely not the case).

I tried with 2.6.3.0, too, but this one 1) says the password failed, too and 2) new backups with 2.6.3.0 don't even HAVE password protection even if I specify one.
[Desire Android Development] ltGuillaume:
Anyone experiencing the same thing?
[Desire Android Development] ze7zez:
slider Brightness

.

Is it possible to add to the Screen Settings slider "Brightness"?

This option exists in TWRP 2.6.3.0 for Samsung Galaxy S Plus.

It is very useful to be able to and out the screen brightness.

On amoled screen for too long to display image-intensive lightening can see it forever.

Thank You!

.
[Desire Android Development] ze7zez:
.

I confirm. This particular TWRP 2.7.0.0 in this release is defective. Were written about this before in the thread.

.
[Desire Android Development] ltGuillaume:
Really? I searched through this thread, didn't find it, must've used the wrong search term then or so. I see 2.7.0.4 going around, but no changelog, perhaps it fixed the issue?
[Desire Android Development] ze7zez:
It was released TWRP 2.7.1.0
[Desire Android Development] kostelo:
Dear [MENTION=4883664]Chromium[/MENTION], maybe you could try compiling 2.7.1.0 update for us? Thanks in advance. :fingers-crossed:
[Desire Android Development] ltGuillaume:
+1 :)
[Desire Android Development] Chromium:
Yep, my last exam is on Monday, so once thats out of the way I'll build the newer one.
[Desire Android Development] dado023:
ot: btw, what do you study?
[Desire Android Development] Chromium:
I'm currently in high school so I'm not studying anything specifically, but next year once I start university I'll be doing computer engineering.
[Desire Android Development] dado023:
it will suit you well, i think you will excel in it :good:
[Desire Android Development] ze7zez:
After your accomplishments here, I see that you have a chance to become an engineer. A good engineer!:good:

.
[Desire Android Development] Chromium:
Thanks for the kind words. I've just compiled 2.7.1.0 and it seems to be functioning properly so far. I'll upload the img and zip files in a bit.
[Desire Android Development] ze7zez:
Versions 2.6.3 and 2.7.0 does not support the old rom. I have to go back to 2.3.1 to get them to flash.
[Desire Android Development] ltGuillaume:
Could you test if password protected backups can be restored with this new version?