Root help save a brick

[13kyl]

Well, it looked like it was all going to work like the v3 RUU did...I think this message came-up after it asked me if I wanted to proceed (but I'm not 100% sure)...

I just tried it again...

1. Main splash screen (i.e., "Welcome to the ROM Update Utility...")
2. Second screen ("Follow the instructions below to prepare the phone for the update:")
3. Current information about your Android phone: Image version 2.36.605.1, select "Update" (clicked "Update" button) to update the current ROM version
4. Fourth screen: "Verify that you want to update the ROM version:" (from Image version 2.36.605.1 to 2.19.605.1)...hit the "Next" button
5. Fifth screen: "You are now ready to update your ROM image..."...hit Next button...
6. Rebooting to Bootloader...Sending....
7. Finally comes back with the "ERROR [140]: BOOTLOADER VERSION ERROR"

Gotta run...be back in 2-ish hours... Good luck!

My version numbers are different. I don't know if this makes a difference but I thought I would point it out.

I get:
From:
Image version:
2.37.605.4

To:
Image version:
2.36.605.1

 

[scotty85]

My version numbers are different. I don't know if this makes a difference but I thought I would point it out.

I get:
From:
Image version:
2.37.605.4

To:
Image version:
2.36.605.1

the 2.19.605.1 number in scarys post is because hes trying to get it to install the root rom.

in another note,i wonder if scary was able to hboot the v3 leak back to his phone because his phone updated to the 2.41.605.6 march 2011 firmware? maybe it doesnt check so diligently for such things as the older fimwares?

i have installed the v3 leak and the root rom overtop of the "flashback" rom several times,but alwasy just assumed it had been modified to make that possible.

 

[scotty85]

OK, Here's what I am thinking (scary will probably reply to my Q before I finish typing this).

If the "SoSicWitIt" (RUU/replace the rom.zip with the ROOT PB00IMG.zip) trick does not work, there really is only one more long shot available - the "tereg double race condition exploit".

Yeah, I know - scary and scotty are rolling their eyes right now

That's because it is tedious, and only about one in five people who attempted it could get it to work - I tried for days and never succeeded. (That's the nature of race conditions - they are statistically improbable).

Before anybody goes down that route, though, I guess we should be absolutely convinced that

- the HBOOT (ROOT) PB00IMG.zip install fails without installing even the S-OFF bootloader
- the SoSicWitIt ("rom.zip" file replacement) can't be coerced into working
- fastboot can not be used to get the phone into RUU mode ("oem-78") before the RUU utility is started.

scary, I can't find my notes - if you run the fastboot command "fastboot oem ?" with the phone in fastboot mode, what output does the 1.49.0000 bootloader produce?

eu1

eu1,i have my phone in fastboot mode,and tiped "fastboot oem" and just "oem" and it gives me:

'oem' is not recognized as an internal or external command,
operable program or batch file.

what do i need to type in fastboot?

 

[scotty85]

oops,did adb shell,then fastboot oem and got this:

C:\Users\Scott>fastboot oem
finished. total time: 1310329033.038s

do i need to now look for a file or image on the sd card to tell you what you want to know?

 

[erisuser1]

Sorry. Got interrupted by a intruder^H^H^H^H^H^H^H^H neighbor.

Reading through the replies now.

eu1

 

[erisuser1]

oops,did adb shell,then fastboot oem and got this:

C:\Users\Scott>fastboot oem
finished. total time: 1310329033.038s

do i need to now look for a file or image on the sd card to tell you what you want to know?

should be "fastboot oem ?"

I was asking scary to do this because he put the 1.49.0000 S-ON bootloader on his phone - you have 1.49.2000, no? (13kyl could try it).

I'm not expecting many oem commands to be available (because it is a S-ON bootloader). With the S-OFF (1.49.2000) bootloader, the command

fastboot oem rebootRUU

will put the phone into RUU mode. It is worth a shot trying this on 13kyl's phone (and then attempting the RUU+"rom.zip" replacement w/ ROOT PB00IMG.zip trick).

eu1

still reviewing prior posts...

 

[erisuser1]

Yes the rest of the recovery menu does appear.

Edit:

Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition

13kyl,

I suspect you tried the "Wipe cache partition" and "Wipe data/factory reset" menu options of the recovery, yes?

If so, did you try a reboot? Did it simply hang on the three skating droids?

eu1

 

[13kyl]

13kyl,

I suspect you tried the "Wipe cache partition" and "Wipe data/factory reset" menu options of the recovery, yes?

If so, did you try a reboot? Did it simply hang on the three skating droids?

eu1

Yes, I did try both "Wipe data/factory reset" and "Wipe cache partition". It does end up hanging on the three skating droids

edit:
-after reboot it hangs on the splash screen of the three droids

 

[scotty85]

doh! smacks foread... i forgot the ?

with the s-off i get all this:

C:\Users\Scott>fastboot oem ?
...
(bootloader) command list
(bootloader) mb
(bootloader) mh
(bootloader) mw
(bootloader) ew
(bootloader) eh
(bootloader) eb
(bootloader) mmu
(bootloader) ram_test
(bootloader) jump
(bootloader) test
(bootloader) sdtest
(bootloader) eraseconfig
(bootloader) writeconfig
(bootloader) readconfig
(bootloader) writesku
(bootloader) readsku
(bootloader) rflash
(bootloader) tflash
(bootloader) block_test
(bootloader) erasesd
(bootloader) btrouter
(bootloader) tick
(bootloader) heaptable
(bootloader) emapi
(bootloader) emapiTest
(bootloader) emapiCountryID
(bootloader) emapiWlanMac
(bootloader) emapiSetDefCal
(bootloader) emapiReadCal
(bootloader) lr
(bootloader) imgcrc
(bootloader) resetautoimage
(bootloader) resetRUUflag
(bootloader) writeserialno
(bootloader) readserialno
(bootloader) battcheck
(bootloader) gotofastboot
(bootloader) writemid
(bootloader) usbtestmode
(bootloader) eraseWifiFlash
(bootloader) powertest
(bootloader) erase
(bootloader) readmbserialno
(bootloader) listpartition
(bootloader) erasebcid
(bootloader) writebcid
(bootloader) readbcid
(bootloader) fmrouter
(bootloader) resetuP
(bootloader) bdaddress
(bootloader) wMfgTp
(bootloader) rMfgTp
(bootloader) saveprt2sd
(bootloader) savemem2sd
(bootloader) changeCid
(bootloader) lnb
(bootloader) gpiow
(bootloader) gpior
(bootloader) mddiw
(bootloader) mddir
(bootloader) clock
(bootloader) i2cr
(bootloader) i2cw
(bootloader) ulpi
(bootloader) bma150
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) enableqxdm
(bootloader) rtask
(bootloader) task
OKAY [  0.079s]
finished. total time: 0.079s

C:\Users\Scott>

and i now have my phone in ruu mode via fastboot oem rebootRUU

would it be helpful if i flash the v3 PB00IMG so i can try some things for you?

 

[erisuser1]

i dont think there exist full rom RUUs or hboot files for the 4th 2010 OTA,or march 2011 OTAs,since they were just partial updates. if they did exist,flashing them would be next option.

That's correct - there are no RUUs corresponding to the March 2011 OTA (=2.41.605.1), or the July 2010 OTA (= 2.37.605.1) - the last one released into the wild was the same as Leak-V3 (= 2.36.605.1).

Unfortunately, the OTAs (which I published links to in this XDA thread) are all incremental patches, rather than full installs. If the things that 13kyl did with the "unlockr" instructions munged the /system paritition, there is no way that applying the updates would do anything useful.

eu1

 

[erisuser1]

Yes, I did try both "Wipe data/factory reset" and "Wipe cache partition". It does end up hanging on the three skating droids

edit:
-after reboot it hangs on the splash screen of the three droids

This is going to sound kind of strange, but humor me on this:

If you power down your phone, plug your phone into your laptop, and then attempt to boot it normally, do you hear any USB sounds (from the PC) about 8 to 12 seconds after you see the three skating droids?

eu1

 

[13kyl]

That's correct - there are no RUUs corresponding to the March 2011 OTA (=2.41.605.1), or the July 2010 OTA (= 2.37.605.1) - the last one released into the wild was the same as Leak-V3 (= 2.36.605.1).

Unfortunately, the OTAs (which I published links to in this XDA thread) are all incremental patches, rather than full installs. If the things that 13kyl did with the "unlockr" instructions munged the /system paritition, there is no way that applying the updates would do anything useful.

eu1

I downloaded 5th Eris OTA. I then renamed it update.zip. I tried to apply update.zip from the repair screen and it did not work.

Is there any hope left?

I tried to call Verizon and they said they do cannot do flash updates. All updates are done over the air.

 

[erisuser1]

doh! smacks foread... i forgot the ?

with the s-off i get all this:

...

and i now have my phone in ruu mode via fastboot oem rebootRUU

would it be helpful if i flash the v3 PB00IMG so i can try some things for you?

well, I expect that with S-OFF. It would be faster if 13kyl tries it (I think he has fastboot and the drivers installed, yes?).

You could try it if you like, but let's see if 13kyl can do it first:

Boot phone in FASTBOOT mode, then on the PC:

fastboot devices [COLOR=grey](should see your device ID if communication w/phone is working)[/COLOR]
fastboot oem rebootRUU

 

[13kyl]

This is going to sound kind of strange, but humor me on this:

If you power down your phone, plug your phone into your laptop, and then attempt to boot it normally, do you hear any USB sounds (from the PC) about 8 to 12 seconds after you see the three skating droids?

eu1

Yes, the laptop makes a sound like a USB device has been detected and a pop up bubble tells me:
"USB Mass Storage Device
Device driver software installed successfully."

Is this what you were looking for?

edit:
This is when trying to start the phone normally.

 

[erisuser1]

I downloaded 5th Eris OTA. I then renamed it update.zip. I tried to apply update.zip from the repair screen and it did not work.

I presume that you verified the MD5 sum first - what error message appeared when you tried this - something about an "assert()" error? Or something else? You should NOT have gotten a verification error if the MD5 of the update.zip was correct, but other forms of errors are possible if the unlockr method messed with /system

Is there any hope left?

Yes - that's why I am still asking you questions; I am trying to eliminate gaps in my understanding of your phone's condition to be sure that there are no other possibilities remaining.

eu1

 

[scotty85]

well, I expect that with S-OFF. It would be faster if 13kyl tries it (I think he has fastboot and the drivers installed, yes?).

You could try it if you like, but let's see if 13kyl can do it first:

Boot phone in FASTBOOT mode, then on the PC:

fastboot devices [COLOR=grey](should see your device ID if communication w/phone is working)[/COLOR]
fastboot oem rebootRUU

im installing the v3 leak now. if 13kyl doesnt have adb setup,ill let you know the output in a few minutes.

 

[13kyl]

The HTC Bootloader installs automatically with my phone in "FASTBOOT USB"
I do not know where I would enter the code.

I tried from the command line (Windows) and the command is not recognized.

How do I get to the proper prompt?

As a side note, I have PDANET installed on my laptop and it recognized my phone and asks me if I want to connect.

Note:
I had been using my desktop until you told me to plug into my laptop. I don't know if this was on purpose if you were assuming I was using my laptop earlier I was just trying to follow as closely (directions) as possible.

 

[scotty85]

13kyl,do you have adb set up and working on one of your computers? do you have any knowledge if using it?

edit: looks like "no" from the above post

 

[13kyl]

13kyl,do you have adb set up and working on one of your computers? do you have any knowledge if using it?

I cannot tell you with certainty that I have adb set up on my laptop. I can tell you that when I go into device manager the first entry is "ADB Interface" If I expand it it contains "HTC Bootloader" I assume this means I have adb set up.

I do NOT have any knowledge of ADB or how to use it.

 

[erisuser1]

Yes, the laptop makes a sound like a USB device has been detected and a pop up bubble tells me:
"USB Mass Storage Device
Device driver software installed successfully."

Is this what you were looking for?

edit:
This is when trying to start the phone normally.

Maybe.

Here is what I am digging at. The linux/Android kernel takes 8-10 seconds to get its legs underneath itself. It is possible (again, "possible") that even if the /system partition was screwed up, so that the rest of Android didn't boot up, the kernel would be alive, and maybe - just maybe - the "adbd" daemon has been started up - it lives inside the boot partition, rather than the /system partition.

The thing that makes your answer a little confusing is that even the Eris bootloader will produce an apparent USB Mass Storage interface - so I don't know if you are seeing something that comes from the bootloader or a kernel which is booted. Normally, you would see something like "ADB composite interface" if adbd was running on the phone, but one component of that "composite" is (yes, you guessed it - ) a Mass Storage Interface.

Have you ever used the "adb" program from the command line on your PC?

Is this result you mention using your laptop or your desktop computer (their software & driver installs are still different, yes?)?

eu1

 

[scotty85]

might want to watch this video:

YouTube - ‪ANDROID SDK Tools (How-To Install)‬‏

might want to go ahead and get it downloaded and set up. i have a feeling you may need it

 

[13kyl]

My desktop has the full version of HTC Sync installed. It has been what I have been using for the past 24 hours.

My laptop has HTC Sync uninstalled (but I believe still contains the actual drivers)

I am sorry to create confusion. I will stick with one or the other. If you have a preference.

Right now the phone is plugged into the laptop. I opened cmd.exe and typed "fastboot devices" I received the error 'fastboot' is not recognized as an internal or external command, operable program or batch file.

Note:
Laptop: Asus Aspire (netbook), Windows 7 starter
Desktop: Home build, Windows 7 Ultimate

 

[erisuser1]

I cannot tell you with certainty that I have adb set up on my laptop. I can tell you that when I go into device manager the first entry is "ADB Interface" If I expand it it contains "HTC Bootloader" I assume this means I have adb set up.

I do NOT have any knowledge of ADB or how to use it.

Both "adb" and "fastboot" are command-line tools.

If you want to try the fastboot tool first (easiest), you can download the (Windows) version of fastboot directly from this HTC developer page. It sounds like you already have drivers installed, so using this is as simple as downloading the "fastboot.exe" binary (for Windows), opening up a "command window", doing a

cd \whatever-folder-you-dropped-the-fastboot.exe-program-into

and then trying the fastboot commands (with the phone plugged in and in FASTBOOT mode).

eu1

 

[scotty85]

with the s-on 1.49.0000 all i get is this:

C:\Users\Scott>fastboot oem ?
...
(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) enableqxdm
(bootloader) rtask
(bootloader) task
OKAY [  0.014s]
finished. total time: 0.015s

hope that helps some.

 

[erisuser1]

with the s-on 1.49.0000 all i get is this:

C:\Users\Scott>fastboot oem ?
...
(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) enableqxdm
(bootloader) rtask
(bootloader) task
OKAY [  0.014s]
finished. total time: 0.015s

hope that helps some.

PERFECT!

Let's see if 13kyl can first force his phone into RUU mode and then attempt the RUU (2.36.605.1) + "rom.zip" replacement.

fastboot devices [COLOR=grey](should see your device ID reported)[/COLOR]
fastboot eom rebootRUU