yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] aerdely:
So if it works on leak v3 did you try switching to rooted when swapping. If you do and downturn work my assumption would be after it loads the leak v3 and after you swap cards and press track ball it might verify to make sure its same file its flash that went through verification process. Just my assumption. Or the other would be when it loads the zip file it only does it partially but after swapping it either can't recognize where to start from when it updates and loads rest of zip file then restarts hboot again. I could be wrong though and hope I am.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] hoovnick:
When I say I switched the sdcards, I mean that I switched to the card with the rooted rom. I've tried switching before you press the trackball, immediately after you press the trackball, and during the update process. All of these have not succeeded in achieving root.

-------------------------------------

Sent from my Eris
[Droid Eris Android Development] aerdely:
Ok, now I was wondering if you got v3 to flash, I don't know if there is yet but if there was root version of v3 I wonder if that might work. If it won't work on 1.5 to 2.1 root pb00img it could work if there were a root pb00img of v3. If there already is and tried then damn. It's always good you got it to reflash though, might be able to work with that.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] hoovnick:
Well, if I understand correctly, the PB00IMG method is a total flash process. My current theory on this method is that when it goes through the steps of loading, checking and parsing the zip file, it somehow creates some kind of ghost image on the phone to load the rom from. So despite me switching the sd cards, it still wants to load the first zip. Anyone know if I'm totally off track here?

-------------------------------------

Sent from my Eris
[Droid Eris Android Development] Dc_striker:
Maybe we can use the ruu

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] Realm:
It'll be awesome if their was an actual software that forces to wipe out the OS + Bootloader and replaces it with a different one
[Droid Eris Android Development] Resun:
Umm, I wasn't talking about the SD card, or the bootloader. I was saying, with the Incredible root process, adbd on the phone is running in Recovery. I realize that the race condition for adb on the computer is necessary for adb to acknowledge it. What I was saying, if you could force adb to push the file, would the phone receive it in recovery mode. Basically cracking the adb file to ignore the device not found and push the file to the SD card, similar to the second race condition on the Incredible.
[Droid Eris Android Development] homewmt:
My touch 3G slide rooted
[Droid Eris Android Development] hoovnick:
Well, after restoring my phone twice today (great learning experience), I've come up with another idea.

I've come to my own conclusion that during the PB00IMG.zip method, the zip loads once, declaring what bootloader is present. This is the point at which, it doesn't really matter if you switch the sd card to one with the root PB00IMG.zip. It has already put some sort of ghost image of the bootloader actually on the phone itself. Then, after you press the trackball to tell it to start the update, it loads and checks the zip a second time. During this load and check, the entire contents of the PB00IMG.zip are actually loaded onto the phone. At this point, the list of items that is under where it says "Parsing" no longer includes "BOOTLOADER" as something that it will load. If you tell it to proceed with the update, you can take the sd card out and replace at will. Nothing will interrupt the update process except for a battery pull, at which point you have to actually flash leak v3 again to have a functional phone again.

All that being said, I believe that the only way to trick the phone in the bootloader state is possibly through ADB. If you could push the root PB00IMG.zip onto the sdcard during the first load and check without it failing the verification, then I think we could get somewhere. Anyone want to brainstorm on that with me?
[Droid Eris Android Development] Realm:
I guess we need an advanced user in ADB to figure this out
[Droid Eris Android Development] bftb0:
The reason that it does not appear the second time the zip appears to be unpacked is because the bootloader has already been flashed. That's exactly what happens in the 0.25 seconds after you press the trackball - watch the screen carefully. And as you've pointed out, it is no longer the contents of the SD card that matters at that point.

The bootloader is a tiny program: 512 kB of code and data. That means that HBOOT has 500+ MB of ram space to unpack things into (and plenty of space in /cache too, if non-volatile space is needed).

adbd is a linux-like binary, requiring a booted Unix kernel and the services a kernel provides to support it. The bootloader is not an operating system, nor a linux kernel, so adbd is never running simultaneously with the bootloader.

Hopefully that will save you some time.
[Droid Eris Android Development] nindoja:
hoovnick, your findings agree with what we found out a while ago, but I don't remember if it was ever posted on the forums or not. I'm glad you were able to replicate our results though.

I'm still on vacation but hopefully will have some time when I get back to check into this race condition.
[Droid Eris Android Development] hoovnick:
Thanks for the mini school session on linux, well, pertaining specifically to the bootloader. I had just finished a little troubleshooting when I decided to check the forums again and saw your post that just confirms what I found out. The computer recognizes the phone in the device manager as "Android Phone" with "Android Bootloader Interface" as the driver listed. Despite that this is listed, the ADB doesn't recognize any devices attached. Recap, you are correct bftb0, as always.

ninjoda, glad to have replicated failed tests. Seriously, I'm learning a lot, even if it is just repeating things that devs have already tried. I hope that my posts aren't irritating to the devs that have already discovered what I'm just now learning. I just find it helpful to put my ideas in writing and use the forum as an idea board.
[Droid Eris Android Development] nindoja:
Glad to see you are learning, as this is a huge learning experience for most of us working on this.
[Droid Eris Android Development] stizzelblack:
ok so this isvthe first time i have ever posted anything on a thread or in general for that matter i have a question for real im on eris 1.49 s on the special phone ha ha but hear we go............. p.s. this may sound silly

HAS anybody here devs or anybody else been able to brick an eris on purppos or accidentilly? with out being able to pull battery and it flicker back to life and no this is not a im looking to get a new phone B.S question i have a broken screen and it works fine im serious same for my question

-------------------------------------

Sent from my Eris
[Droid Eris Android Development] tenzomonk:
phones have been bricked... just about 2 weeks ago, there was a post about a bricked phone from a failed radio flash. there are other stories too. so, definitely possible...
[Droid Eris Android Development] JTF2007:
First of all, thanks to all helping root the 2.1 leaked ROM. I'm currently on v1. I stuck with v1 just in case there was a slight chance that an exploit worked on v1 and not 2 or 3.

Regarding rooting this ROM.

If the SD card is partitioned and one partition has the leak PB00IMG.zip on it and the other has the root PB00IMG.zip on it, is there a way to switch which partition the bootloader (or whatever the process is) is reading from in once the signature checks have been satisfied?

Just trying to throw ideas out there. Thanks again for all of the dev work on this topic.

JTF2007
[Droid Eris Android Development] hoovnick:
I see where you're coming from there. However, I had another idea this morning that failed also. I had the sdcard loaded with the root PB00IMG.zip and went through the HBOOT method. It loaded the zip file, then right as it started doing the signature check, I switched to the sdcard with the v3 leak to see if it would pass the signature check. After it was done checking, it gave the 'main version is older.' This leads me to believe that the signature/version verification is based off of that initial loading of the zip file to the phone itself.

-------------------------------------
[Droid Eris Android Development] bftb0:
tenzomonk,

Could you post a link to that report?

While you see people claiming all the time, "you could brick your phone", actual reports of that happening seem extremely rare - especially when you consider that we observe folks attempting root that have no apparent computer skills.

Honestly I can't remember a single report of a bricking.

It is easy enough to make the OS unbootable, but I wouldn't consider a phone to be bricked so long as the S-OFF (root) bootloader still runs.

bftb0
[Droid Eris Android Development] g00gl3:
I heard of an Eris being bricked last week. No link since it wasn't a post, just talk in irc. I believe the cause was a bad boot animation attempt... Maybe he will share more details for you. ;)
[Droid Eris Android Development] homewmt:
I'm not a developer, or even experienced with phones, but it is even possible to root a phone by switching sd cards, or partitioning them, has any phone every been rooted this way?
[Droid Eris Android Development] stizzelblack:
ok cause i was on my old samsung omnia last night aka windows based and thought bout my blackberry storm 9530 that i bricked straight paper weight then i thought if you could brick a phone while its still connected to the computer and the comp still reconizes its still there aka (droid eris) it may be possible to run a modded ruu or some kind of adb gibber gabber to reload stock 1.5 firmware back to thus enabiling those leaked/ota to go back threw time and use orginal leaked out root pb00img.zip to root - ha ha sounds iffy i know just thinking out the box of hpboot and recovery methods

-------------------------------------

Sent from my Eris
[Droid Eris Android Development] fox_dye:
Not sure but thats the glory of a new idea. Just because it hasn't been tried before doesn't mean it won't work . Best of luck to those of you trying new things. Wish I could do more to help.
[Droid Eris Android Development] fox_dye:
If that was possible then it might just be easier to just go ahead and load the root rom instead of messing around with the stock 1.5. Because the 2.1 ruu has the new boot loader on it and I don't think there is one for 1.5.
[Droid Eris Android Development] stizzelblack:
yeah thats a good point well hmmmmm im racking my brain thinking up how you would purposely brick ha ive try every obviouse way thats a no go ghost rider but theres got to be a way any ideas ?????? ill test any theroy or method twice lol

-------------------------------------

Sent from my Eris
[Droid Eris Android Development] ericFuels999:
Has anybody looked into replacing the rom.zip generated by the 2.1 RUU with the root rom renamed to "rom.zip". I'm not entirely sure if this possible, and I'm guessing it might fail a check somewhere, but it could be worth a shot.

Here's some related reading:

http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
[Droid Eris Android Development] Realm:
Does the RUU replaces the bootloader?
[Droid Eris Android Development] bftb0:
Has anyone tried?

[SIZE=+1]Yes[/SIZE].

On this very board.

In 2009.

5 weeks after the Eris was released.

Brings to mind that old quote, "Those that do not learn from history..."

bftb0
[Droid Eris Android Development] rycheme:
True, but that was on an older bootloader, no? Might be worth another shot - it can't hurt, anyway.
[Droid Eris Android Development] ericFuels999:
Yeah, that was also from Dec. 2009 - before the rooted 2.1 engineering rom was obtained. I'm guessing that attempt involved trying to flash an unsigned rom that had been hacked to grant root access.

I fail to see how that post is directly analogous to what I proposed, seeing as the tools we are dealing with now are different. If the 2.1 RUU can upgrade both the 1.47 HBoot of 1.5 and 1.49 HBoot of the leaks, then it doesn't seem like that aspect would fail if the 2.1 root rom were swapped in; however, what might fail is the fact that the 2.1 root rom has a lower version number than some of the leaks.

Again, worth a try for someone.
[Droid Eris Android Development] laxattack:
I was the one who bricked, but it was from a bad radio flash :-( oh well now im back on the rooting 2.1 bandwagon
[Droid Eris Android Development] aerdely:
I bricked one when I ran a cache clear program but forgot to install a busybox for it. Device froze so I shut it down by pulling battery and wouldn't boot into hboot or anything after that. If I remember correctly I was booting it continuously and shutting it back down by pulling the battery and eventually went to hboot and got it to recovery. I loaded the Rom back on the sdcard with another device and after getting to recovery again reflashed it but had constant problems with it freezing after that and having to pull battery and reflashing. It did run a little better after I cleared power cache after pulling battery so many times but eventually had to replace it because of freezing problem.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] bftb0:
.

Someone, but not you?

The phone does not "trust" the RUU, in the sense of giving the RUU special privileges to decide what can be put on the phone and what can not. The RUU is little more than a nice graphical wrapper around a very dumb program, namely "fastboot".

Note that the RUU utility on the PC does not interact with the the booted OS or the booted recovery to do anything other than start the bootloader in OEM-78 mode (aka RUU). That makes any OS changes irrelevant; and while a change in the bootloader conceivably could make a difference, because it is "in play", it isn't very likely that HTC changed the security policy of their bootloaders.

But you are right, the post that I referred to was not identical to what you suggested.

Good luck.
[Droid Eris Android Development] babybacon:
would it be possible to use the 2.1 bootloader hack that was used to root the incredible? I imagine someone has had to have tried.
[Droid Eris Android Development] bftb0:
Were you using fastboot to do the flashing? Do you remember exactly what transpired?

I'm thinking that a momentary slip-up, maybe a hurriedly typed command such as "fastboot flash hboot radio.img" might even run without an error - but with obvious deadly consequences.

I suppose a bad radio image could brick the phone ... it's just seems sort of counterintuitive that the bootloader would need the radio to be up and running.

bftb0
[Droid Eris Android Development] stizzelblack:
FASTBOOT findings

ok so i was messing around with ruu.exes and seeing if there was anything different between one to the other and then i stumbled upon this so when your in fast boot on leak/ota and you run the command

fastboot flash system update.zip

or any zip DUH...... ha ha it will say sending 'system' (size of .zip KB)... FAILED (remote: not allow)

BUTTTTTTTTTTTTTTT.....................

when you run a ruu i used modacos testruu.exe for the htc desire rooting method been tried i know but anyways but when it fails it gives you a message blah blah blah could not complete find the right ruu basically well your phone will still be in bootloader mode technically yes it is true till you exit out of the ruu app its self now we run the same command

fastboot flash system update.zip but now what you get is this

sending 'system' (size of .zip KB)... OKAY

writing 'system'... INFOsignature checking...

FAILED (remote: 12 signature verify fail)

so maybe we can get past the failed signiture some how and on to the next sep so on and so forth to temple of root LOL.................. this is just traning cause at the end of this all we will enjoi our root so much more then the rooters who bashed us for wanting the sneak peak when they were going to just late on the info HATTERS just playing

oh yeah P.S. i dont know if anybody had done this before me so my findings not over all findings ha there to anybody going to say something to that

lets get this done stay focused team
[Droid Eris Android Development] stizzelblack:
updated remote 12 signature is the error no matter what your trying to flash but now we can push sorta files to recovery partition thinking...................................?
[Droid Eris Android Development] Realm:
can the signature be replicated to make it look like as if its the same zip?
[Droid Eris Android Development] quic:
Your comments are hard to understand. Please speak english! thank you. haha i'm just kidding. But if i understand what you were saying about this error. we are kinda stuck at this point and have been. We can't fake a signature so this is a dead end.
[Droid Eris Android Development] stizzelblack:
well is there any zip that doesnt have a fake signiture?
[Droid Eris Android Development] stizzelblack:
well maybe

well what if we ran the ota ruu that we got from verizon and cause that may be able to make the phone think it has a signature for the zip that you want to flash i mean like -

1. open command prompt and ready the fastboot flash system (.zip) butt dont run it yet - also probably the closest one we have to ota root -

2. then run the ruu.exe and wait till it get to the sending part

3. command prompt enter

and maybe we can slip the root in there before the phone can finish the ruu.exe bassed of finding above
[Droid Eris Android Development] jvward:
Since the RUU is a windows app maybe it could be reengineered to not check for the Sig or check for a different one. Can anyone link it? Because isn't that essentially what they did for one of the Droid hacks
[Droid Eris Android Development] stizzelblack:
http://forum xda-developers com/showpost php?p=6702102&postcount=1

delete spaces and put . cause i cant post links ha ha but thats the official ruu for the leak ota for the droid eris
[Droid Eris Android Development] stizzelblack:
testing my own theroy and im sending the ruu and the official 0.8.1t2.zip and nether have failed yet of course its been sending for eta almost 7 minutes now ill let you know what happens
[Droid Eris Android Development] JTF2007:
Just thinking outside the box here, is there a way to rig a usb cable so that the phone can be connected to two separate computers and have two adb sessions open? That way we could time it so a root file can be pushed to the phone after the sig check is done.
[Droid Eris Android Development] stizzelblack:
maybe if you had a cable built that way kinda like a external hard drive with two prongs lol for sending data from one to the other threw the hard drive ummmmmmmmmm if you did some really good splicing and soughtering maybe !
[Droid Eris Android Development] jvward:
Hi,

Does anyone have a copy of 1.5 Rom with original Boot loader bundled with it?
[Droid Eris Android Development] hoovnick:
I have the MR1 RUU if that helps any.
[Droid Eris Android Development] stizzelblack:
DUDE can you post a link for that joint ive been trying to find that all day
[Droid Eris Android Development] stizzelblack:
OH yeah

just a little bit of data from earlyer

fastboot flash system eris_official_0.8.1t2.zip

sending 'system'(96533 KB)... INFOzip header checking...

INFOchecking model ID...

INFOchecking main verison...

INFOchecking image[hboot] flushing...

INFOchecking (status read failed (too many links)

- during updating rom portion -

---------------------------------------------------------

fastboot flash system eris.zip

sendind 'system'(96533 KB)... OKAY

writing 'system'... INFOsignature checking...

FAIL (unknown status code)

- during checking right befor sending portion -
[Droid Eris Android Development] hoovnick:
How do I post the MR1 RUU?
[Droid Eris Android Development] mdc4115:
http://www.technews.biz/gadgets/phones/htc/droid-eris/ErisMR1.zip
[Droid Eris Android Development] stizzelblack:
you will have to upload it in a attachment or on a different site such as mega upload or rapidshare but the manage attachment button witch is in additional options under advanced reply options then click then click choose and navigate to the item
[Droid Eris Android Development] stizzelblack:
or that works too ha ha sorry a little late there
[Droid Eris Android Development] hoovnick:
Ah, thanks mdc4115. I couldn't find that link that I got it from. I'm giving my brain a break for a few days from all this. Partly because I've got an MMA fight to run video for and a wedding to DJ. Good luck all, check back on Monday.
[Droid Eris Android Development] stizzelblack:
anybody running a os besides windows to trying things
[Droid Eris Android Development] akillys:
Would out be possible to splice the ruu and the rooted 2.1 together some how so that when we install the ruu it updates the hboot to the 1.49.2 hboot. Maybe this could be done on a computer then re zipped leaving the signature intact and updating our hboot to 1.49.2 allowing us to root. Not sure if this is a new idea or even if it's even slightly valid just thought I would post the idea for someone more tech savvy than I to contemplate.
[Droid Eris Android Development] Father_Vic:
Delete post.
[Droid Eris Android Development] bdt1995:
No. We cant touch the zip or the contents of it without breaking the signature. And since we cant sign them ourselves...

Man, i want this thing rooted, and im sure theres a way, but splicing the cables wont work either, The phone would recognize one connection and ignore the other.

Also, if any of the devs need a semi-educated tester, im pretty good with all the command prompt stuff, and ill be willing to do pretty much anything to get this thing rooted.
[Droid Eris Android Development] nesgodawg:
So... how would one go about breaking the trackball to get a replacement phone? haha
[Droid Eris Android Development] bdt1995:
That would be useless to do, because EVERY replacement phone has hboot 1.49 S-ON now, verizon "did us a favor" by pre upgrading all the phones to 2.1 through the RUU.

I think theyre on to us ;)
[Droid Eris Android Development] nesgodawg:
Those bastards! I think I missed that in another post. I really need to read this forum a few times a day now. haha
[Droid Eris Android Development] aerdely:
I don't know if anyone had this type of luck but, my Eris has a trackball issue. This is my 4 or 5 one with it so after complaining to Verizon for a week and a half they decided to allow me to switch to MOTO Droid for 289.00. Well I still kept calling them and local Verizon store checking on availability of them because there were no cpos in stock. After calling the Verizon dealer one more time on Friday they said they finally would do it for free, not an upgrade because I'm not due for one yet or anything else. Just a warranty exchange. I do like Eris but so many trackball issues ;) it comes in on Tuesday. This could be a special deal for problem devices that they're allowing to switch to MOTO Droid but I've called them repeatedly for days and they wanted me to pay 289.00 and finally on Friday they said a brand new in box for free. I think they got sick of me. Lol.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] Duffman3005:
I must be lucky, my leaked 2.1 eris stopped holding a charge, and I went to Verizon to exchange it. At first she thought they were out, but it turns out there were three left. Luckily it was still at 1.5, and I had it rooted (E.E. 3.0) in less then 24 hours.
[Droid Eris Android Development] aerdely:
Yes you are, I've got about 5 Eris' for trackball and all had 2.1 and 1.49 hboot. No luck here. Shouldn't have to worry about that now with MOTO Droid coming. I would have rooted it ASAP like you did but hopefully MOTO Droid isn't like the Eris.

-------------------------------------

Sent via the XDA Tapatalk App