yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] tereg:
Flash successful HBOOT v 1.49.0000 S-ON

Radio 2.42.00.04.12
[Droid Eris Android Development] thenestor:
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).

I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
[Droid Eris Android Development] TopazAaron:
but this may give us the ablitly to regain further updates, instead of verizon not giving us leakers no mo updates :(
[Droid Eris Android Development] conflipper:
feel free to spread the word, and get this out there. Spread the word, I am sure people will want the "Official" file.
[Droid Eris Android Development] TopazAaron:
i keep on getting error about connectiviy to the phone which i have it connected and idk,

also ever other time i try it gives me your battery is less than 30% which its at 68% so idk about that either.

i couldnt get it to work. im gonna give it another redownload and see
[Droid Eris Android Development] jearl75:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
[Droid Eris Android Development] tenzomonk:
i think he meant he was already running leak 3... and not rooted.
[Droid Eris Android Development] SasoriSoren:
Does this bring all the 2.1 Sense UI features to the Eris like friendstream etc?
[Droid Eris Android Development] bftb0:
LOL

Perhaps folks should try re-reading what thenestor reported up above in this very thread:

[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].

Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.

bftb0
[Droid Eris Android Development] bftb0:
All the leaks (excepting the 2nd chronological leak, the "root-ROM") were shipped with release-keys.

The root-ROM was the only one that reported "test-keys".

bftb0
[Droid Eris Android Development] jearl75:
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
[Droid Eris Android Development] bftb0:
What?

If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?

I'm wondering, what do people think "Identical" means?

Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.

Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.

Oh well, more power to them... or less, as the case may be.

bftb0
[Droid Eris Android Development] jearl75:
First of all I said "those on a leak", didn't say leak v3. Just to bring you up to speed there are 2 leak versions before v3, hence the v3. It would be more official because this one WAS released by Verizon, whereas the leaks were not, which is why they were leaks. It is identical yes, but the build number is different, which would differentiate between leak v3 and this OFFICIAL release should you need to return your phone. Just because the support people might not be able to tell, someone can believe me. I know people who have returned there leak and been charged for a new phone because they had unofficial software on there phone, never even mentioning it. This was a month or more later, just showed up right there on there bill.

So, people who feel better having an official release (whether your on leak v1, v2, or v3) can flash this, it's official. If someone who has root can't read where it says this is for people on the leaks, if you have or ever want root don't update. Then that's their problem, not much you can do about that....
[Droid Eris Android Development] bftb0:
jearl75,

I'm not trying to start a pi$$ing match, really.

As for bringing me up to speed, I'll refer you to my comments right up above there (which you quoted) in this very thread where I mentioned all the leaks and their chronology:

..Or perhaps this XDA thread where I apparently was blissfully unaware of the chronology of leaks from HTC/VZW. :D

How could you install IDENTICAL software and have it report a different build number? How does that work? Again, there's that "identical" thing rearing it's ugly head again. :)

I think you missed the point entirely - and so did Topaz_Aron, I guess. The RUU utility initially unpacks a bunch of files, and one of them is called "rom.zip". It contains all the stuff which the RUU eventually flashes to the phone: the bootloader, the radio, the NVRAM, boot, system, data, recovery - everything! Despite it being named "rom.zip", it is a file in exactly the same format (including a mystery crypto sig) used with the PB00IMG.ZIP method. And in fact, if you take that file, put it on the root of the SD card, and re-name it to PB00IMG.ZIP, you can apply it using the phone's HBOOT method.

Now, what "thenestor" did, was run the RUU to the point that the files are unpacked, find that "rom.zip" file, and then check the md5sum signature of that "rom.zip" file, and.... guess what, he found out that it is identical to the md5sum signature of the Leak-V3 PB00IMG.ZIP file:

1c0b0182356242a9d673a661e7458587 rom.zip

(I didn't run this test myself - I trust "thenestor" after seeing his other posts - he is very careful and diligent.)

So, look - believe it or not, the phone does not "trust" the RUU utility. It checks the very same signatures on the "rom.zip" file that it does when you use an HBOOT procedure. If this were not the case, it would be a simple matter of cobbling together a custom "rom.zip" file and slapping it in to place just before the RUU starts transferring to the phone - and then root would have been had back in December.

That means that if it successfully installs, it had to come from HTC/VZW. And if it has the same checksum, it is IDENTICAL.

And as far as the channel that HTC uses to deliver MRx updates in an official manner - they have been using PCD phones - their distribution partner, not random "I've got your undocumented ROM right here" sites.

As far as we know, that file was merely cobbled together from freely available pieces on the internet, named in a way that looks reasonable, and had the .EXE portion stuffed full of viruses - after all, even if the data payload is signed, the .EXE is not.

Official? Probably it is; but it certainly isn't apparent looking at HTC site, or PCD's site, or VZW's site.... yet.

Sorry for the rant - I just want people to avoid Cargo Cult in their advocacy.

conflipper - if you are reading this, please consider adding a note to your OP that points out this is no different than Leak-V3.

bftb0
[Droid Eris Android Development] jearl75:
REALLY??? Could have fooled me..............
[Droid Eris Android Development] fox_dye:
Thanks for the info. Seeing as I am running leak v3 I don't have to bother with this. But I got a little hopeful that this might help so I could root. But I guess its back to the waiting game.
[Droid Eris Android Development] nesgodawg:
I am also hoping that this opens the door to rooting on leak v3.
[Droid Eris Android Development] char561:
Nope, You still have the same HBOOT version so all this does is give you a "official" release.
[Droid Eris Android Development] ncwildcat:
And THIS, my friends, is why developers don't want to continue to share their work and findings. They get completely blasted. Con has always been an reputable dev, going way back to alltel roms for win6.1 and possibly further. You, sir, are flammnig
[Droid Eris Android Development] lifyre:
Thanks Conflipper!

Does anyone know an easy way to migrate/reinstall all my programs when I upgrade from Leakv2 to the RUU? It is why I hadn't updated to v3 before now and would love to avoid having to find and install them all again.

-Lifyre
[Droid Eris Android Development] XC_eris:
HELPP!!!!

JUST WANTED TO SAY THANKS FOR MAKING THIS!! I thought I had seriously messed up my phone when I got some weird errors after trying to install with windows 7. But it worked fine in vista! OTA now :)

EDIT: Works now
[Droid Eris Android Development] :
Shoved off the fence....

So I was on root thanks to the great Dev's here, and now I'm on the "Official" release as it has "release-keys" instead of "test-keys". I wasn't sure if I wanted to keep root or go for the OTA, and then I saw the DL that Con left, and as I've had NO ISSUES with anything I've downloaded from him before I got off of the fence and went for it.

I was able to reload all of my info and applications, and after 24 hours I have noticed a significant difference in speed and NO "force closes" compared to the seemingly ever increasing "FC's" from the root... of course not nearly as many as when I was running it off the SD card of my FUZE.

To all the Developers I'd just like to give my eternal thanks, you guys have helped me educate myself and broaden my horizons and amaze and astonish my tech friends with what I've learned.

I'd donate if I didn't have 4 mouths to feed...and please DON'T let any of the trolls wreck your willingness to share as I'm sure I'm not the only "silent" member that's had many benefits from your generosity and willingness to teach and share.

Aaron
[Droid Eris Android Development] jfont25:
Just want to make sure I understand before I apply this. I am running Leak v3. Do I need to apply this RUU?
[Droid Eris Android Development] char561:
No you do not need to. The only reason to do this would be to make it the "official" version but leak v3 and ota are the same
[Droid Eris Android Development] bftb0:
For you - on Leak-V3, it will have exactly the same effect as doing a factory reset.

If you enjoy factory resets, go right ahead. When you are finished, you will have - wait for it - Leak V3.

bftb0

Edit: (6/7 00:18) To be technically precise, parts of the Factory Reset procedure initiated from the main O/S (in all the 2.1 releases - leak, root, or RUU) are performed by the recovery partition on the phone, including some NVRAM operations which clear the phone activation data. If you run the RUU utility to completion, the phone will be wiped to near-factory, but a *228 activation call will not occur during setup. Everything else on the phone will need to be set up from scratch, though.
[Droid Eris Android Development] bukada:
Well.. I tried this.. "RUU" Release..

Was ROOTED..

Now I have lost root...

Tried the steps to regain root...

FAILED! :mad:

No more ROMS for me.. this Effen sucks!
[Droid Eris Android Development] char561:
I could have told you that would happen... did you lose the recovery partition?
[Droid Eris Android Development] bukada:
Yup.. :(

I am shi* out of luck!

Why oh why did I try this one..

not very happy with myself
[Droid Eris Android Development] char561:
Well, it does say that it is the OTA RUU (not root) and its only for people on leak (hboot 1.49) so you shoulda known better but oh well, **** happens
[Droid Eris Android Development] bukada:
Will try and get an "exchange" via Verizon tomorrow..

Oh well.. if not.. time to buy another phone..

Lesson learned..
[Droid Eris Android Development] char561:
Yep, you'll know to ask first before flashing something that could unroot your phone
[Droid Eris Android Development] tenzomonk:
OUCH! sorry!
[Droid Eris Android Development] bftb0:
This type of thing was exactly the reason I tried to encourage conflipper to put something in his OP as a warning. For that, I got called a "flammer" (sic) after explaining what the facts of the matter were.

LOL. I used to wonder why jcase gets testy from time to time. Not any more.

It's as if we learned nothing from the whole leak episode. At least the original leak episode was a little more understandable, because the first one was an upgrade from 1.5 to 2.1, and root had not yet been uh, "obtained" yet. But after -V2, and again -V3, you would think folks might catch on.

bftb0
[Droid Eris Android Development] bukada:
My own ignorance caused my loss of root! If I had read JCase's 3rd post...

So.. I blame no one but myself..

It's not the end of the world.. it's just a cell phone lol :D
[Droid Eris Android Development] umarz:
Has anyone else tried this with Windows 7? It looks like XC_eris had some problems with that.
[Droid Eris Android Development] TopazAaron:
I got it to work on windows 7, just i didnt have any drivers installed no SDK or anything, it was like a clean install of windows pretty much, and ran the .exe and it worked
[Droid Eris Android Development] hallstevenson:
:D :D :D ... just sit back and watch
[Droid Eris Android Development] bukada:
Great news.. Just got a new Eris issued to me from Verizon.. ;)

It had 1.5 on it..

Am now back in business with ROOT!!! :D

Will read thoroughly next time around before I Flash ANY ROM!
[Droid Eris Android Development] roirraW "edor" ehT:
I just wanted to say thanks to conflipper even though I don't need this for myself (I'm rooted), to help make up for those who don't appreciate it. I understand that more information is better, but I'm a smartphone, Android, and Eris NOOB (only have had it for one month) and I knew well enough to read, read, read before jumping on anything. Heck, I'm picky before I jump to another ROM and nothing in the first post would lead me to believe that this is the latest and the greatest new ROM. If I may put my smart*** hat on for a sec, gee, no screenshots, hardly any description, being an EXECUTABLE!? So many red flags to indicate that this isn't your usual custom ROM.

BTW, this isn't aimed at bukada at all, you seem cool. You understandably got miffed, but you didn't blame conflipper, you kept it in perspective and you "fixed" it yourself by replacing it.

bftb0, you should be more careful how you go about trying to do good. Your intentions were good, I'm sure, but the way you went about it just caused some ruffled feathers. So it's not what you wanted to achieve was the problem, but the way you tried to achieve it. The anonymity and impersonalness (is that a word - LOL) of the internet only makes it easier for people to be misunderstood and taken out of context. Forgive me, this is just my two cents and I'm not here to lecture you. Please take it the way it is meant.

Back to your regularly scheduled program...
[Droid Eris Android Development] jcase:
bwhahahahahahahahahahahahahhahahahahahahahahahahahaha

heh

Wanna point out that bftb0 is always dead on.
[Droid Eris Android Development] jeffyo:
helps to read the posts in the thread and see what other people say before going for it.
[Droid Eris Android Development] ferrocene:
posting non-rooted roms on this forum shouldn't be allowed, specifically because of what happened, lol. :p
[Droid Eris Android Development] AcidRoot:
Or people could just read and then ask question if they have problems instead of doing something then asking questions and then reading lmao.
[Droid Eris Android Development] jcase:
I disagree, this kind of stuff does need to be posted. There was fair warning on the first page.
[Droid Eris Android Development] hallstevenson:
Absolutely. This sub-forum is for topics related to rooting phones or topics dealing with already rooted phones. Do we want non-rooted users asking everyday questions here ? I realize jcase warned people quickly, but that's not the point. Fact is, some people read that 1st post and ran with it. Being in this sub-forum, why wouldn't someone think it was just another ROM ?
[Droid Eris Android Development] :
because something that has release_signed in the name, is going to be an official ROM

So you should realize that by the thread name what it is.

Because people that need to send a device back to Verizon for warranty can not have a root anyways. So without something like that, its hard to send it back.

If you do not want me to post ROMS then that is not an issue. But the thing is these ROMS are needed to be posted. not everyone will enjoy it, but it is needed.
[Droid Eris Android Development] hallstevenson:
This forum isn't for "official" ROMs
[Droid Eris Android Development] :
It is for Android Development

Where do you get carrier files? where do you get Verizon stuff?

You get all of this stuff from official ROMS, Test ROMS and any other kind of ROM.

If you look at any forum on XDA, any ROM Development forum. You will see Official ROMS inside there.

So to argue that this is not for official roms is not going to be a very good argument.
[Droid Eris Android Development] mortymouse:
Does anyone know how to get this to work with windows 7? I tried running as admin, running in comp mode, installing 64 drivers, etc. Everything I have found on the site has not allowed me to use this RUU. I get stuck at the bootloader every time. It just says HTC on my eris and will not move after that. If I unplug the USB cable, it shows the bootloader screen and shows the RUU, but its just locked. I restart the phone and all is well.

Anyone?

Found the fix. For anyone that may want to know, Sincidius helped me. Here is the post that took care of it perfect.
[Droid Eris Android Development] Sincidius:
This is a DEVELOPMENT FORUM. In development, bad things happen to those who do not know what they are doing. When those things happen, it is always good to have an option to start from the original spot (OEM Roms, OTAs, etc). Some people even experiment with these roms or just load them because the root ones weren't what they wanted after all. THE PROBLEM is that people shoot first and ask questions later. Before doing any firmware/OS changes to your phone, you should always read everything before you start & be prepared to suffer the consequences if it fails. I went through about 20 different roms on my HTC Wing before I found one I liked. A few times the loader would not work with my phone, so I had to load the OEM T-Mobile ROM to get things like Windows 6.5 to work & also to get back to 6.1 (Yeah, 6.5, no matter how pretty devs try to make it, its pretty much glitter on a turd). This isn't directed at anyone, just adding to the conversation and pulling this post off topic a few more inches.
[Droid Eris Android Development] umarz:
Thanks to TopazAaron and Sincidius for the info on running it from Windows 7. Mine went smooth with no Windows reboots needed.
[Droid Eris Android Development] hoovnick:
Crap, sorry guys, wrong thread....moved to correct thread.
[Droid Eris Android Development] mortymouse:
Agreed.

FYI to anyone that might care. Since I have flashed this over, I have noticed that my silent ring issue seems to have stopped? Also, some of the lag I was getting with the dialer in general.

After I did the flash, I did a factory wipe as well, then reset everything and I was solid. Nice to know that technically while there is no "difference" between Leak v3 and this OTA, it did seem to solve some isues for me?
[Droid Eris Android Development] cornbreadfarts:
is there a way to do this without having to have the phone connected to USB? that's my problem. my PC will not read my phone so I am having to go back to stock to return it.
[Droid Eris Android Development] bftb0:
Download the Leak-V3 PB00IMG.ZIP file directly to your phone, move it to your SD card root folder (with a file manager), and install it using HBOOT.

Identical to the "Official RUU". Identical.
[Droid Eris Android Development] sk842018:
Anone thats on V3 or this or ota 2.1 can still root. There's been ways for leakers to root for a while now
[Droid Eris Android Development] Bradh024:
I'm having alot of problems getting the OTA update to work on my eris. I used it on my first eris to unroot with no problems, but on this eris, it doesnt want to work. I keep getting "ERROR [140]: Bootloader version error". I've tried running it about a dozen times, and still the same thing. I've tried other unroot methods, like the one posted a couple posts back, didnt work though. If I cant get this damn thing unrooted I'm screwed. I gotta have it sent back by tomorrow. So any help is greatly appreciated.
[Droid Eris Android Development] bftb0:
Are you talking about using the RUU or the OTA update?

The OTA updates have never checked the bootloader version. The build fingerprint, yes - but the bootloader version, no, never. The RUU utility does check bootloader versions.

Tell us the exact version of your bootloader (if it is a 1.49 bootloader, it will be either 1.49.0000 or 1.49.2000).

bftb0

[ Edit ]PS Try this manual technique and let us know what happens.
[Droid Eris Android Development] Bradh024:
Thanks for the reply, its the 1.49.000 bootloader and it was the ruu that was giving me the problems. Ill give the other method a shot and let you know how it goes. Once again I appreciate the help.
[Droid Eris Android Development] bftb0:
That's a little bit strange that the RUU would not work with the current S-ON (1.49.0000) bootloader.

If the PB00IMG.ZIP method also fails with a "Main Version is Older" error, you will need to perform Jcase's misc partition hack (steps 1-6) , making sure you are using the PB00IMG.ZIP file from the RUU ("rom.zip" renamed to PB00IMG.ZIP) in step #4 instead of the Root-ROM.

Note also that the "rom.zip" file inside the RUU is the same thing as the Leak V3 PB00IMG.ZIP - you can use either to restore back to "factory".

I'm going to be AFK the rest of the evening, so I can't be of further help.

Good Luck

bftb0
[Droid Eris Android Development] LexusBrian400:
Malwarebytes and Avira both went nuts when I clicked the link.
[Droid Eris Android Development] bftb0:
There are three or four different links on this page - megaupload, XDA, AndroidForums, which?

That's the trouble with Ad delivery networks. These days it's possible to get your machine drive-by Pwned by visiting almost any legitimate page on the internet.

I don't use anti-virus software - I browse the internet in a VM and blow it away periodically; to the extent possible I avoid using any browser in a native Windows install.

bftb0
[Droid Eris Android Development] tophunterz:
official

I recieved a new phone a couple of days ago and I am trying to get the old one back official.

I tried downloading SDK but cant seem to get it to work. It sounds like this thread I dont need SDK.

I tried to Download the PMBG but I cant seem to get it.

Mobile me asks for a password.

any help or guidance would be greatly appreciated!!!!
[Droid Eris Android Development] bftb0:
That's correct; you don't need the SDK for either the RUU method or the PB00IMG.ZIP method.

If you want some pictures of how to perform the PB00IMG.ZIP flashing, have a look at this post over on AF. Please make sure your phone is well charged (say, > 80%) before you begin.

If you are having trouble with downloading the PB00IMG.ZIP file directly to your phone, do it on your computer and transfer it to the root folder of your SD card via USB. After you copy the file from the PC, make sure to use the "Safely Remove Hardware" (or Drive "eject" in Win 7) control before you turn off "Disk Drive Mode" on the phone. That will avoid accidentally corrupting the copied file.

WTF is Mobile Me? Never mind, I think I don't want to know. :)

bftb0
[Droid Eris Android Development] tophunterz:
Awesome

Back to 1.49 s-on

and back to verizon

Thanks everybody

:p:p:p:p:p:p:p
[XPERIA X2 General] rsx19:
i want to change it to the power key,
[XPERIA X2 General] mtechfan:
You can try this if you want -> http://ae.inc.ru/aebplus.php

Otherwise you need to go into the registry yourself and make some changes. Something I don't want to mess with at this point (button mapping).

Post your results so we know.
[XPERIA X2 General] rsx19:
It does what the remapping does but it still also opens panels

unbinding it doesnt work either, i guess the only way to remap this one is through the registry
[G1 General] robuser007:
Is it possible to unlock for free ? Couldn't find an manual (only jtag).
[G1 General] robuser007:
should I risk to buy an locked phone?