• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Eris gets official booloader unlock support (*yawn*)

scary,thats nice of you... i couldnt take your lil buddy tho. methinks ill scour craiglist for one thats got a broken screen or some flaw for cheap that can be scarificed :D

i really would like to play with this,and help eu1 figure out a way to get rid of it in case its a pain to deal with,and people get tripped up with it.
 
hi guys,

I flashed it to my scratch Eris phone using fastboot, e.g.

Starting with the 1.49.2000 S-OFF bootloader already installed on the phone:

Code: 
# [color=blue]fastboot flash hboot hboot_7501a_1.51.0000_111229.nb0[/color]
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY

Here's the good news - so long as you have the misc partition flashed with the jcase "Flash any RUU" hack (which resets the "MainVer" recorded in the misc partition back to 1.12.605.1), you are free to use a HBOOT+PB00IMG.zip rollback process to restore a different bootloader, e.g. the S-OFF bootloader**.

I installed the 1.51.0000 bootloader using fastboot as shown above, fooled with it long enough to get some screen images, and then rolled it back using the Root PB00IMG.zip ROM (which has the 1.49.2000 S-OFF bootloader)

I'll show some screenshots later - time for bed now.


** A couple caveats apply.

(1)
For this testing I did not apply any unlock codes from HTC, nor did I install this (1.51.0000 bootloader) using a HBOOT+PB00IMG.zip method. The "android-info.txt" file (in the "rom.zip" container) is different enough looking from all prior ones we've seen from HTC that I didn't want to go that route - I wanted to make sure that the misc partition would still have an old MainVer # in it immediately after installing the 1.51.0000 bootloader. It may not have mattered, but...

I suppose it is possible that once the phone is unlocked, the bootloader could behave differently, for instance simply ignoring PB00IMG.zip files, or not having a RUU mode, etc. But I am guessing we will find that so long as you don't get the phone into a wedged state where you can no longer get a root shell running - so that you can flash an old "MainVer" number into the misc partition - we will be able to use PB00IMG.zip-style installs to perform bootloader rollbacks.

I suppose it is also possible that those odd-looking changes in the "android-info.txt" file could cause some unanticipated behavior change; I haven't test that (yet).

(2) Don't forget that the Root PB00IMG.zip ROM flashes an old radio - if you are experimenting and bouncing back and forth between bootloaders, it might be a good idea to flash to a current radio after the Root PB00IMG.zip install and before you install the 1.51.0000 bootloader, just in case you "get stuck there".

(3) I haven't tried an hboot install via a recovery package with 1.51.0000 installed on the phone. Dragons might lurk there.

eu1
 
thats great news,eu1. :cool: i hope that when the hboot is installed via htcs RUU,or via htc on a replacement that it still behaves this way,and still behaves this way even when unlocked.

on the incredible a user picked up a phone with gingerbread and the htcdev support locked 1.02.0000 hboot,and tried to roll it back by changing the misc image to froyo,where he could run unrevokeds program to achieve s-off. his downgrade was successful,but with 1.02.0000 remaining,instead of the 0.92.0000 that would come with froyo builds. :eek: when he tried to run the newest unrevoked(version 3.32) it failed repeatedly with a "unable to nand unlock" error.

at that point several things were tried,and the bootloader was unlocked and relocked several times as well. we RUUed forward back to gingerbread,and downgraded to froyo a couple times, and finanlly all the way back to eclair. in all cases the hboot did not change. it remained locked or relocked every time the rom was changed. :eek: running unrevoked 3.32 on eclair still failed.

finally,an older version(3.22- wich must work differently,as it also successfully rooted GB,where 3.32 fails) was able to nand unlock and set the secure flag off.

i hope when you do further testing that you do not find a similar situation when you install the hboot more "conventionally" ;) and unlock it.

for what its worth,i can still install PxxxIMG files on my htcdev unlocked rezound. i can install full signed RUUs with the hboot relocked(all normal rules apply) and i can install "mini-ruus" with the hboot unlocked that contain ONLY system,boot,or recovery images.

i can partially "roll back" by flashing the system,boot,and recovery images from older firmware,but i CANNOT change the hboot or radio,the hboot and radio work together and are doing more checks that make it literally impossible to roll back fully on newer phones. :(

my greatest fear with this 1.51 hboot for the little eris is that it will start preventing the boot image from being written from recovery when its unlocked or locked,making the way folks flash new roms and restore backups different from simply doing it all in recovery. (i hAVE to flash the boot image via fasboot anytime i do something that needs a different kernel).

i hope it does not come to this,as its cause a GREAT deal of confusion to new rooters,since most are not adb/fastboot savy,and installing via PxxxIMG files is touchy becasue of s-on and the android info document.

anyway,if we find that the 1.51 does not change how users are able to restore and flash roms,and that its removable,it may be good for folks to update to it.

the s-on does its checks,making it nearly impossible to bork the bootloader,yet it does allow fastboot boot and fastboot flash (and maybe some other commands i dont realize),thus making it possible to still resurect bricked eris by soft booting the recovery. :cool: sort of the best of both s-on/s-off worlds,lol.

last and not least, here is the stff on the android info document that eu1 was refering to:


CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12

i dont understand whats going on here,either. i know the mainver number will change the phone to that,but im alittle unsure what the capital CIDNUM number is :confused: the lowercase cidnum i assume is checking to make sure the phone is a verizon,or the "UTSI_001" version.

again,looking fwd to hearing your thots and seeing what further testing reveals,eu1 :D
 
some other thots i was having... ive noticed the eris does look for a DIAG file in hboot. i know such file will have to be signed by htc to work,but it makes me wonder... do you think there is some way we can turn off the radio secure flag? unrevokeds forever patch does work on the cdma hero,wich also uses hboot 1.47 and a radio that works on the eris(2.42.01.04.27 IIRC) at one point id tried flashing it with clockwork,with that radio installed,and the install aborted for reasons i cannot remember currently :o

if we could develop a procedure for that,then in a worse case scenario maybe it would work to s-off the radio with a 1.51 hboot in place.

public:forever [RootWiki]
 
Whoa... I've been out of the loop too long. Is that a scary alien in mod red?

It's amazing to see lil' ol' EOL'd Eris still getting some love after all this time. That R2-D2 special edition should have gone to this little guy for being the little droid that does. From 2011 to present my coworker has gone through a Samsung Reality and a Fascinate, and an iPhone 4 and a 4S (possibly a 2nd 4S now) while my little buddy I affectionately call Twiki is still chugging along. The only hiccups I've ever had were user error, which thanks to the wonderful support community was easily fixed.

Good luck and many thanks to everyone still supporting Eris development and the Eris community.
 
erisuser1 said:
(2) Don't forget that the Root PB00IMG.zip ROM flashes an old radio - if you are experimenting and bouncing back and forth between bootloaders, it might be a good idea to flash to a current radio after the Root PB00IMG.zip install and before you install the 1.51.0000 bootloader, just in case you "get stuck there".
Click to expand...

I did forget this - thanks!

One other thing that I did try was to start from the leak RUU and wait for an OTA to the latest release, but an OTA never came and software update said that there was nothing. However, I never tried to apply OTAs manually. I am wondering if it's possible that having the jcase misc image flashed was the thing that prevented the new hboot RUU from installing. I did look at the RUU log and it doesn't say anything about that as the reason for not installing. I wouldn't be all that upset if my Eris gets in a state that prevents it from being rooted, as I am not using it all anyway.
 
Couple o' additional comments:

Last night when I did this testing, I used CWM to restore a nandroid backup with the 1.51.0000 while it was in a "locked" state, and there were no problems flashing any of the usual partitions involved in CWM (v2.50.7) nandroid restores: boot, system, userdata, cache & (sdcard) .android_secure. I haven't tried doing any fastboot flashes to confirm they are denied with the bootloader locked.

One of the subtleties that I rediscovered last night which should be of some concern is that when you perform a PB00IMG.zip install when the pre-existing bootloader is the S-OFF 1.49.20000, MainVer checking is surpressed initially, but enforced during the second phase of flashing if the new bootloader is of the S-ON type. When this happens, only the S-OFF bootloader gets replaced by a S-ON, but the rest of the PB00IMG.zip contents fail to install. (This occurs only if the misc partition MainVer value < PB00IMG.zip/android-info.txt MainVer value)

I don't think this is related to doog's experience with the RUU install, but I have to re-read his posts carefully (I'm not quite awake yet). It did clear up for me that there probably are no internally stored version numbers coded into the bootloaders which affect the version checking during PB00IMG.zip installs - the only two things that seem to matter are the MainVer values stored in the misc partition and the value in the android-info.txt file in the PB00IMG.zip file.

I'll run some more tests; stay tuned.

eu1
 
erisuser1 said:
FYI, the appropriate &quot;get_identifier_token&quot; command to fastboot had underscores in it, as in:

Code: 
fastboot oem get_identifier_token
Click to expand...


You're right... I forgot them earlier. :o

IIRC,the unlock.code has one also:
fasboot flash unlock_code.bin
 
OK, this is very odd.

(initial phone state: 1.51.0000 on the phone in a locked state - installed by fastboot flash hboot hboot-image-file.img when the 1.49.2000 S-OFF bootloader was on the phone)

- Got my device token
- registered with HTCdev.com
- downloaded the RUU (but didn't use it)
- waded/skipped through the 8 pages of instructions to get to the part where you submit your device token
- got my unlock code in an e-mail
- did a

Code: 
[color=green]fastboot flash unlocktoken Unlock_code.bin[/color]
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully

The phone gives you a screen where you have to select yes, unlock (with a Vol button), and then press End to do the unlocking. Then the phone reboots (normal boot to whatever ROM is on the phone).

Here's the odd part:

Despite now showing an "*** UNLOCKED ***" banner in the fastboot screen, it refuses to allow you to "fastboot flash" either the recovery, boot or misc partitions!. (They upload to the phone successfully and then give you the standard S-ON message "Remote: not allow")

[size=+2]WTF?[/size]

I also note there is a new string in the misc partition: "HTCU". This process did not seem to alter the MainVer value in the misc partition, though.***

I was able to flash recovery, boot, and misc partition images to the phone from within the Amon_RA recovery (using "flash_image <partition-name> <image-file>"), so there appears to be no "NAND hardware locking" taking place.

Here's what I'm left thinking about this: [size=+2]WTF, HTC?[/size]

I suppose I could try doing fastboot flashes of the system or data partitions, but flashing of "system" images never worked in prior Eris bootloaders (due to space issues, I think - the upload would fail after more than 100 MB), so I don't know why I would start doing it now.

I'll check to make sure I can still get this POS off the phone.

eu1


*** :eek: :D :D LOL, when you replace the misc image (because this "HTCU" string disappears from the misc partition??), the bootloader reverts back to a locked state.


PS I am (successfully) rolling back to the Root PB00IMG.zip ROM right now.


After all of this, the 1.51.0000 bootloader seems like nothing but an accident waiting to happen for unsuspecting owners.


.
 
Could you guys (that haven't had this 1.51.000 bootloader on your Eris) check something for me?

I don't know if this is residue from my experimentation, or if the 1.49.2000 S-OFF bootloader has always behaved this way, but if I try to flash the misc partition using fastboot now (using the 1.49.2000 S-OFF bootloader), I get this odd message:

Code: 
# [color=green]fastboot flash misc misc.img[/color]
sending 'misc' (640 KB)... OKAY
writing 'misc'... [color=red]FAILED (remote: partition is not allowed to be flushed!)[/color]

I honestly don't know whether I've tried flashing misc from fastboot before (maybe I always did it from within the custom recovery). I don't remember seeing that error message before - note the "flushed" mis-spelling. As I said - maybe I never tried it before, but it seems odd that I wouldn't have tried it during one of my many rollback experiments early on.

( BTW, the (jcase hack) misc.img that I have has a MD5 of 0ba96497afc6e124e465f3b1c7a99481 )

eu1



PS for others lurking on this thread up to this point - be aware that flashing the "misc" partition with jcase's image can cause problems if you have a phone "flashed" to a different carrier than VZW, as the CID is recorded in the misc partition. You still can use this technique, but you have to capture and hand-patch your own "misc.img" file with a hex editor to reset the "MainVer" number back to something ancient such as 1.12.605.1. Sounds complicated, but the MainVer string is easily located in the misc image file ; use "dump_image" with Amon_RA recovery running to capture your current misc partition, hex-edit the image file, and then flash the edited copy back with the "flash_image" command running under Amon_RA.
 
doogald said:
Thanks for this. It would be nice if an unlocked bootloader was unlocked period, and not sort of unlocked.
Click to expand...

I guess HTC's conceptual usage model is that only /system and /data will be replaced - so, no overclocking, :eek: new kernel features, or even custom recoveries.

But, as you pointed out, because all of the factory Eris (1.5 & 2.1) ROMs are so easily rooted now, and managed from the point of view of backup/restore in CWM recovery, it is hard to imagine why anybody would want to operate that way.

eu1
 
erisuser1 said:
Could you guys (that haven't had this 1.51.000 bootloader on your Eris) check something for me?

I don't know if this is residue from my experimentation, or if the 1.49.2000 S-OFF bootloader has always behaved this way, but if I try to flash the misc partition using fastboot now (using the 1.49.2000 S-OFF bootloader), I get this odd message:

Code: 
# [color=green]fastboot flash misc misc.img[/color]
sending 'misc' (640 KB)... OKAY
writing 'misc'... [color=red]FAILED (remote: partition is not allowed to be flushed!)[/color]

I honestly don't know whether I've tried flashing misc from fastboot before (maybe I always did it from within the custom recovery). I don't remember seeing that error message before - note the "flushed" mis-spelling. As I said - maybe I never tried it before, but it seems odd that I wouldn't have tried it during one of my many rollback experiments early on.

( BTW, the (jcase hack) misc.img that I have has a MD5 of 0ba96497afc6e124e465f3b1c7a99481 )

eu1
Click to expand...

eu1,

Same deal on my 1.49.2000 Eris:

C:\temp>dir misc*
Volume in drive C is Windows
Volume Serial Number is A0C6-44C7

Directory of C:\temp

07/15/2010 11:50 PM 655,360 misc.img
02/18/2012 06:44 PM 995 misc.img.zip
2 File(s) 656,355 bytes
0 Dir(s) 177,386,729,472 bytes free

C:\temp>md5sum misc.img
0ba96497afc6e124e465f3b1c7a99481 *misc.img

C:\temp>fastboot devices
HT9AKHG04952 fastboot

C:\temp>fastboot flash misc misc.img
sending 'misc' (640 KB)... OKAY
writing 'misc'... FAILED (remote: partition is not allowed to be flushed!)

C:\temp>
 
scary, doog

Thanks for that.

For what it is worth I just went through a different cycle of installation / test / removal. Not much new except for one quirk.

- Flashed LeakV3 (2.36.605.1)

- Recovery update.zip with OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip (2.37.605.4)
- Recovery update.zip with ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip (2.41.605.6)
- Performed a Factory Reset
- Installed the 1.51.0000 bootloader as a PB00IMG.zip install (the rom.zip file from the RUU)
- Booted phone and let it settle
- Rooted manually (Using Dummies root_part1.sh, reboot, root_part2.sh)
- Booted Amon_Ra recovery, and flashed jcase "misc.img" (MainVer = 1.12.605.1)
- Booted to Fasboot Mode and applied the device token via
Code: 
fastboot flash unlocktoken Unlock_code.bin

The unlocking worked correctly despite my diddling with the misc partition; fastboot flash recovery recovery.img still fails (as expected).

Here is where the quirk is - I next attempted to roll back using the Root PB00IMG.zip ROM - with the bootloader in the *** UNLOCKED *** state, it unpacked the PB00IMG.zip file, and then (silently) returned back to its' menu.

I then used
Code: 
fastboot oem lock
. This caused the bootloader to now show a *** RELOCKED *** banner - slightly different than how it appears immediately after installation. Fortunately, in this state it was happy to accept and install the (Root) PB00IMG.zip file. (I had checked it's MD5 after copying it to the root of the SD card, and the second pass at it (with the bootloader now "relocked") succeeded, so I am sure this wasn't an issue of a corrupted file

So there you go - in addition to lack of other useful features, having the 1.51.0000 bootloader in the **** UNLOCKED **** state means that ignores PB00IMG.zip installs, even when the MainVer value recorded in the misc partition should allow things to proceed.

I guess there's only one more pass at this needed - actually getting it to be installed from the RUU - to verify that it can be removed under those circumstances, as long as a rootable OS is installed or a custom recovery is still bootable.

Other than the quirk mentioned here, it's behavior is starting to look mostly undifferentiated from any other S-ON Eris bootloader.

I suppose I should check to see whether or not the system and data partitions can be flashed - it occurs to me now that if that works, the 1.51 bootloader could be used to rescue folks that have 1.49.0000 S-ON bricks (as a result of loss of a bootable OS and recovery).

eu1
 
erisuser1 said:
I guess there's only one more pass at this needed - actually getting it to be installed from the RUU - to verify that it can be removed under those circumstances, as long as a rootable OS is installed or a custom recovery is still bootable.
Click to expand...

As I said earlier, I'm away next week, but I will have loads of down time during the day Tuesday and Wednesday. I'll give another stab at installing from RUU, but I'll try a new procedure, similar to what you did: flash the 2.1v3 leak, the two OTA update zips, and then see if I can get the RUU to install.
 
thanks so much for all this testing eu1 :cool: im glad that it appears to be overwritable. as such,maybe i will do some of my own testing now :D

its really wierd that fastboot flash doesnt work with it unlocked... thats contradictory to its behavior on all other devices that ive messed with it.

did you try to fastboot boot a recovery? if that works,then this couldd well still be a good rescue tool for 1.49.0000 s-on bricks,as in theory one could install the bootloader,unlock,then softboot recovery all without a functional,booting OS.

so just to make sure i understand everything correctly:
1)users are still able to root maunally with the 1.51 in either a locked or unlocked state
2)users are able to flash roms and restore backups with it locked,or unlocked... it has not started protecting the boot.img

i.e., tho it has some wierd quirks for being "unlocked" :rolleyes: it functions to the normal rooter/eris user the same as any of the s-on hboots,with a couple of potential benefits(softbooting a recovery,and possibly installing unsigned boot/recovery/system images)

in one of your next tests,you should be able to make up a "mini-ruu" containing a recovery,system,boot image,and with a properly modified android info document flash it in hboot via the unlocked hboot.

ill fire mine up,and see what happens as well :)
 
scotty85 said:
did you try to fastboot boot a recovery?
Click to expand...

It occurred to me last night that I hadn't done that, so I re-did everything this morning (full stock phone), including generating a new token and getting a new unlock code from HTCdev.

No joy. :(

I thought that perhaps the token-generating process was somehow bound to radio firmware or something I changed which causes a bug of some sort, but in this latest go-around I didn't even twiddle the misc partition as a safety valve - and yet it still seems to behave no differently than any other S-ON bootloader (other than that strange bit about ignoring PB00IMG.zip files in the UNLOCKED state).

BTW, the token generating process apparently uses some entropy-collection process or timestamp - sequential passes of token generation generate new token values, even if nothing has changed on the phone. I'm glad they made installation of a non-functional unlockable bootloader so secure :rolleyes:

scotty85 said:
in one of your next tests,you should be able to make up a "mini-ruu" containing a recovery,system,boot image,and with a properly modified android info document flash it in hboot via the unlocked hboot.
Click to expand...

Hmmmm. I suppose that I did not try flashing a unsigned PB00IMG.zip file to see if would be accepted in either the unlocked or relocked state. When you construct yours, do you just omit the 256-byte HTC crypto blob at the front of the zip archives you create, or do something else?

I might try an RUU install first though - maybe that produces different results. :confused:

eu1
 
first let me say i was not successful at installing the RUU either. i tried baskically same as doogald:
-install 2.36.605.1,sans hboot(to keep s-off)
-install 2.37.605.4 via stock recovery
-install 2.41.605.6 via stock recovery

-ran ruu starting from booted phone,no go(cannot connect to your android phone)
-ran ruu with phone in RUU mode,no go(same error doog got,despite being on the fimrware it says to be on)

at this point i said eff-it,and installed in fastboot.

got identifier,flashed unlock token,reboot. back to fastboot:
Code: 
c:\mini-adb_eris>[COLOR="Red"]fastboot flash recovery recovery-scotty-and-dexters-lab.img[/COLOR]
  sending 'recovery' (3848 KB)... OKAY [  0.869s]
            writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.871s

c:\mini-adb_eris>[COLOR="red"]fastboot boot recovery-scotty-and-dexters-lab.img[/COLOR]
        downloading 'boot.img'... OKAY [  0.874s]
                       booting... FAILED (remote: not allow)
finished. total time: 0.876s

failed! :mad:

so tried installing as an RUU,with modified android info document:
Code: 
c:\mini-adb_eris>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.025s]
finished. total time: 0.026s

c:\mini-adb_eris>[COLOR="red"]fastboot flash zip scotty-recovery.zip[/COLOR]
       sending 'zip' (3831 KB)... OKAY [  0.852s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,20
INFO[RUU]UZ,recovery,40
INFO[RUU]UZ,recovery,60
INFO[RUU]UZ,recovery,80
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,23
INFO[RUU]WP,recovery,43
INFO[RUU]WP,recovery,63
INFO[RUU]WP,recovery,83
INFO[RUU]WP,recovery,100
OKAY [  3.423s]
finished. total time: 4.276s
wich worked fine,so i asume PB00IMG install would be fine as well. verified i have scarys special scotty/dexters lab recovery :D

last and not least,i tried installing a "mini RUU" containing boot,system,and recovery fromthe root rom,again with properly modified android info:
Code: 
c:\mini-adb_eris>[COLOR="Red"]fastboot erase cache[/COLOR]
               erasing 'cache'... FAILED (remote: not allow) [COLOR="Blue"]<- wtf?![/COLOR]
finished. total time: 0.001s

c:\mini-adb_eris>fastboot oem rebootRUU
                              ... OKAY [  0.025s]
finished. total time: 0.026s

c:\mini-adb_eris>[COLOR="Red"]fastboot flash zip PB00IMG-2.19.605.1-mini.zip[/COLOR]
      sending 'zip' (98148 KB)... OKAY [ 13.959s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,43
INFO[RUU]UZ,boot,84
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,40
INFO[RUU]WP,boot,81
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,99
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,41
INFO[RUU]WP,recovery,82
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,10
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,21
INFO[RUU]UZ,system,26
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,38
INFO[RUU]UZ,system,43
INFO[RUU]UZ,system,49
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,60
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,87
INFO[RUU]WP,system,0
INFO[RUU]WP,system,5
INFO[RUU]WP,system,10
INFO[RUU]WP,system,16
INFO[RUU]WP,system,21
INFO[RUU]WP,system,26
INFO[RUU]WP,system,33
INFO[RUU]WP,system,38
INFO[RUU]WP,system,43
INFO[RUU]WP,system,49
INFO[RUU]WP,system,54
INFO[RUU]WP,system,60
INFO[RUU]WP,system,66
INFO[RUU]WP,system,71
INFO[RUU]WP,system,76
INFO[RUU]WP,system,82
INFO[RUU]WP,system,87
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,90
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,92
INFO[RUU]UZ,system,92
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,99
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,87
INFO[RUU]WP,system,87
INFO[RUU]WP,system,88
INFO[RUU]WP,system,89
INFO[RUU]WP,system,89
INFO[RUU]WP,system,90
INFO[RUU]WP,system,91
INFO[RUU]WP,system,92
INFO[RUU]WP,system,92
INFO[RUU]WP,system,93
INFO[RUU]WP,system,94
INFO[RUU]WP,system,95
INFO[RUU]WP,system,95
INFO[RUU]WP,system,96
INFO[RUU]WP,system,97
INFO[RUU]WP,system,98
INFO[RUU]WP,system,98
INFO[RUU]WP,system,99
INFO[RUU]WP,system,100
OKAY [ 65.158s]
finished. total time: 79.118s

c:\mini-adb_eris>[COLOR="Red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.023s

what? i cant erase cache? :confused: but it did flsh the system,boot,recovey images. verified in about phone,so again,PB00IMG should work fine.

so im pretty bummed out that neither fastboot boot nor fastboot flash seem to be working. :(

i dont know...maybe it does have some merrit,since recovery,system,and boot can be installed as RUUs or PB00IMG files. maybe that would still get someone out of a pinch,since a big prollem is no signed RUU or PB00IMG for 2.37.605.4,or 2.41.605.6

maybe we can find someone with a bricked eris that we couldnt help before and have them try it :D
 
erisuser1 said:
Hmmmm. I suppose that I did not try flashing a unsigned PB00IMG.zip file to see if would be accepted in either the unlocked or relocked state. When you construct yours, do you just omit the 256-byte HTC crypto blob at the front of the zip archives you create, or do something else?
eu1
Click to expand...

all i did was take the root rom,unzip,and elimiate everything but the boot,recovery,and system images. then i edited the mainversion number to match the 2.41.605.6. saved it,and rezipped the whole thing.

im not sure why you have to relock to run RUUs. but for what its worth,my s-on unlocked rezound is the same way. :rolleyes:

edit:
as an afterthot,i verified the main version is still 2.41.605.6 after flashing the older system image:
Code: 
c:\mini-adb_eris>fastboot getvar mainver
mainver: 2.41.605.6
finished. total time: 0.002s

where does the misc image live? apparently not within system ;) wonder if we can somehow flash that as a PB00IMG or an RUU?
 
scotty85 said:
so tried installing as an RUU,with modified android info document:

[...snip...]

wich worked fine,so i asume PB00IMG install would be fine as well. verified i have scarys special scotty/dexters lab recovery :D
Click to expand...

I think I like you. :cool: :)

That does appear to be something for folks with bricks.

How do I know if a "android-info.txt" is properly constructed? You take an existing one from one of the prior HTC PB00IMG.zip files, and assign a larger MainVer value?

Are you using a Unix or windows zip program to re-pack the archives ?

eu1

.
 
erisuser1 said:
I think I like you. :cool: :)
Click to expand...
hooray :D

erisuser1 said:
That does appear to be something for folks with bricks.

How do I know if a "android-info.txt" is properly constructed? You take an existing one from one of the prior HTC PB00IMG.zip files, and assign a larger MainVer value?
Click to expand...
yup.. thats all i did. unzipped the root rom with 7 zip. opend the android info text document that came with the the root rom,changed the mainver number,then saved it. closed it,then reopend it to make sure it had changed.

erisuser1 said:
Are you using a Unix or windows zip program to re-pack the archives ?

eu1

.
Click to expand...

windows. just highlight the images,and the txt document. then:
/right click/send to/compressed(zipped)folder

then rename it so ill know what it is later :)
 
scotty85 said:
where does the misc image live? apparently not within system ;) wonder if we can somehow flash that as a PB00IMG or an RUU?
Click to expand...

It's just another partition in the Eris' NAND chip. The Eris actually has something like 12 or 13 partitions - do a

Code: 
fastboot oem listpartition

with the S-OFF bootloader installed and you will see them. I put up a thread on XDA a long time ago documenting them, and have a bootable version of Amon_RA that will allow you access to all of them**

My guess is that if the engineering (S-OFF) bootloader won't let you flash misc using fastboot, probably it will also throw an error with PB00IMG.zip installs, but that's just a guess.

eu1

** methinks the stock Eris kernel or perhaps hardware prevents access to certain MTD address ranges - for instance "dump_image" can't seem to grab the radio image, but it can dump other stuff e.g. "hboot", "mfg", "misc3" (I think this is a backup partition of misc), "sp1" etc.

.
 
scotty85 said:
first let me say i was not successful at installing the RUU either. i tried baskically same as doogald:
-install 2.36.605.1,sans hboot(to keep s-off)
-install 2.37.605.4 via stock recovery
-install 2.41.605.6 via stock recovery
Click to expand...

Ok, so I guess I can skip that next week. I may still do it while allowing the 1.49.0000 S-ON bootloader to be flashed, just to see if that's another thing that's being checked. I doubt it, though.

I'm thinking that there's little reason to let HTCDev know that this RUU fails. I think that anybody who wants to play around with root is much better off with the S-OFF bootloader, and we can continue to point people that way.

I should also say that part of my frustration the other night is that I had a really hard time trying to find jcase's erisengspl.zip with the megaupload shutdown issue. I finally found it attached to a forum message somewhere, and was happy when the MD5 matched. Whew! It's now on my Dropbox, for anybody who needs it. This sure has taught me to download stuff I may need someday *now* rather than wait until I might need it, though.
 
You must log in or register to reply here.
Back
Top Bottom