Problem: does not boot and does not recovery

Search This thread
By:
Advanced…
Ammar-y

Ammar-y

Member
Nov 7, 2011
20
3
39
Taiz
The problem is not the system does not boot and no recovery

My phone: HTC Droid Eris

I've downloaded and installed
PB00IMG.zip
MainVer: 2.36.605.1

This version I have installed several times successfully

Then install the
kaosgingerbread-v8
By ClockworkMod recovery > Update form ZIP

But the disaster was

No system
attachment.php


attachment.php



Not ClockworkMod recovery
attachment.php


attachment.php




RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver

attachment.php



Please help me
​
 

Attachments

  • 1.jpg
    1.jpg
    55.4 KB · Views: 537
  • 2.jpg
    2.jpg
    56.7 KB · Views: 540
  • 3.jpg
    3.jpg
    81.7 KB · Views: 532
  • 4.jpg
    4.jpg
    72.4 KB · Views: 526
  • 5.jpg
    5.jpg
    57.9 KB · Views: 515
Last edited:
D

doogald

Senior Member
May 27, 2010
1,387
337
I agree that this thread is probably the best solution: http://xdaforums.com/showthread.php?p=11651122#post11651122

Over on AndroidForums, we've seen quite a few of these that have been solved using this method. At this point, it's the best bet. Scary_Alien put the steps together in one post here, for somebody who had a similar issue (though not quite the same, in this case; his ROM actually runs, he just cannot start Recovery, and cannot replace what's there with Amon_RA):

http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263


At least for the Eris, the best thing in my opinion:

- stay away from Clockwork as the default Recovery. You can still run Clockwork from ROM Manager if you are using Amon_RA, but almost every one of these phones that has ended up in this state did so with Clockwork as the default Recovery

- stay away from KaosGingerbread. Punk.kaos seems to have abandoned this, it never ran well anyway for a day-to-day ROM, and lots of people have problems with it. There are a number of up-to-date GB builds, such as GSB, CondemnedSoul, Tazz's ROMs, Evervolv, etc.

I think that the problem is that people who search for rooting the Eris stumble upon blog posts that describe how to root with Clockwork Recovery and also mention how great KGB is; I'm not sure that was ever true, though it surely was cool that our phone had a GB build early on in the game.
 
  • Like
Reactions: Ammar-y
Ammar-y

Ammar-y

Member
Nov 7, 2011
20
3
39
Taiz
doogald said:
I agree that this thread is probably the best solution: http://xdaforums.com/showthread.php?p=11651122#post11651122

Over on AndroidForums, we've seen quite a few of these that have been solved using this method. At this point, it's the best bet. Scary_Alien put the steps together in one post here, for somebody who had a similar issue (though not quite the same, in this case; his ROM actually runs, he just cannot start Recovery, and cannot replace what's there with Amon_RA):

http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263


At least for the Eris, the best thing in my opinion:

- stay away from Clockwork as the default Recovery. You can still run Clockwork from ROM Manager if you are using Amon_RA, but almost every one of these phones that has ended up in this state did so with Clockwork as the default Recovery

- stay away from KaosGingerbread. Punk.kaos seems to have abandoned this, it never ran well anyway for a day-to-day ROM, and lots of people have problems with it. There are a number of up-to-date GB builds, such as GSB, CondemnedSoul, Tazz's ROMs, Evervolv, etc.

I think that the problem is that people who search for rooting the Eris stumble upon blog posts that describe how to root with Clockwork Recovery and also mention how great KGB is; I'm not sure that was ever true, though it surely was cool that our phone had a GB build early on in the game.
Click to expand...
Click to collapse

Thank you very much
I'm working
 
Ammar-y

Ammar-y

Member
Nov 7, 2011
20
3
39
Taiz
The problem is there


After pressing the power key, the following happens:
attachment.php


Then connect the USB cable to get the following:
attachment.php


Remove the cable when the show the following:
attachment.php


I then turned to install 2.36 as follows:
Code: 
E:\DroidEris\temp>cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

E:\DroidEris\temp>[COLOR="Blue"]fastboot getvar boot-mode[/COLOR]
[COLOR="Green"]boot-mode: RUU[/COLOR]

E:\DroidEris\temp>[COLOR="Blue"]fastboot getvar battery-status[/COLOR]
[COLOR="Green"]battery-status: good[/COLOR]

E:\DroidEris\temp>[COLOR="Blue"]fastboot erase cache[/COLOR]
[COLOR="Green"]erasing 'cache'... OKAY[/COLOR]

E:\DroidEris\temp>[COLOR="Blue"]fastboot flash zip PB00IMG36.zip[/COLOR]
sending 'zip' (107369 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[[COLOR="DarkOrange"]hboot[/COLOR]] unzipping for pre-update check...
INFOstart image[[COLOR="DarkOrange"]hboot[/COLOR]] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
[COLOR="red"]FAILED (remote: 90 hboot pre-update! please flush image again)
[/COLOR]
E:\DroidEris\temp>[COLOR="Blue"]fastboot flash zip PB00IMG36.zip[/COLOR]
< waiting for device >
sending 'zip' (107369 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[[COLOR="DarkOrange"]boot[/COLOR]] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,42
INFO[RUU]UZ,boot,85
[COLOR="Green"]INFO[RUU]UZ,boot,100[/COLOR]
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,40
INFO[RUU]WP,boot,81
[COLOR="Green"]INFO[RUU]WP,boot,100[/COLOR]
INFOstart image[[COLOR="DarkOrange"]radio[/COLOR]] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,19
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,31
INFO[RUU]UZ,radio,37
INFO[RUU]UZ,radio,44
INFO[RUU]UZ,radio,50
INFO[RUU]UZ,radio,56
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,68
INFO[RUU]UZ,radio,75
INFO[RUU]UZ,radio,81
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,93
[COLOR="Green"]INFO[RUU]UZ,radio,100[/COLOR]
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,25
INFO[RUU]WP,radio,32
INFO[RUU]WP,radio,38
INFO[RUU]WP,radio,45
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,58
INFO[RUU]WP,radio,64
INFO[RUU]WP,radio,80
[COLOR="Green"]INFO[RUU]WP,radio,100[/COLOR]
INFOstart image[[COLOR="DarkOrange"]recovery[/COLOR]] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,41
INFO[RUU]UZ,recovery,82
[COLOR="Green"]INFO[RUU]UZ,recovery,100[/COLOR]
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,41
INFO[RUU]WP,recovery,82
[COLOR="Green"]INFO[RUU]WP,recovery,100[/COLOR]
INFOstart image[[COLOR="DarkOrange"]system[/COLOR]] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,4
INFO[RUU]UZ,system,9
INFO[RUU]UZ,system,14
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,23
INFO[RUU]UZ,system,28
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,38
INFO[RUU]UZ,system,43
INFO[RUU]UZ,system,47
INFO[RUU]UZ,system,52
INFO[RUU]UZ,system,57
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,67
INFO[RUU]UZ,system,72
[COLOR="Red"]INFO[RUU]UZ,system,76[/COLOR]
INFO[RUU]WP,system,0
INFO[RUU]WP,system,4
INFO[RUU]WP,system,9
INFO[RUU]WP,system,14
INFO[RUU]WP,system,19
INFO[RUU]WP,system,23
INFO[RUU]WP,system,28
INFO[RUU]WP,system,33
INFO[RUU]WP,system,38
INFO[RUU]WP,system,43
INFO[RUU]WP,system,47
[COLOR="red"]INFO[RUU]WP,system,52[/COLOR]
INFOstart image[[COLOR="DarkOrange"]userdata[/COLOR]] unzipping & flushing...
INFO[RUU]UZ,userdata,0
[COLOR="Green"]INFO[RUU]UZ,userdata,100[/COLOR]
INFO[RUU]WP,userdata,0
[COLOR="Green"]INFO[RUU]WP,userdata,100[/COLOR]
[COLOR="Red"]FAILED (remote: 51 partition update fail)[/COLOR]

E:\DroidEris\temp>
This was the result:
attachment.php


Remove the cable when the show the following:
attachment.php


Of the information I can not use any of the commands adb.exe

And I can not use some of the orders fastboot
For example :

fastboot flash recovery recovery-RA-eris-v1.6.2.img
.
.
fastboot boot recovery-RA-eris-v1.6.2.img
.
.
fastboot erase system
.
.


Because of the signature is not valid and S=On

I am waiting for any help
Thanks for all the work and help
 

Attachments

  • IMAG0103.jpg
    IMAG0103.jpg
    45.4 KB · Views: 490
  • IMAG0104.jpg
    IMAG0104.jpg
    43.2 KB · Views: 176
  • IMAG0105.jpg
    IMAG0105.jpg
    96.5 KB · Views: 178
  • IMAG0106.jpg
    IMAG0106.jpg
    42.5 KB · Views: 173
  • IMAG0107.jpg
    IMAG0107.jpg
    54.5 KB · Views: 178
Last edited:
S

scary alien

Inactive Recognized Developer
Jun 27, 2010
276
107
Indy
What is the PB00IMG36.zip file that you are trying to flash and where did you get it from?

I am unfamiliar with that .zip file...
 
  • Like
Reactions: Ammar-y
Ammar-y

Ammar-y

Member
Nov 7, 2011
20
3
39
Taiz
scary alien said:
What is the PB00IMG36.zip file that you are trying to flash and where did you get it from?

I am unfamiliar with that .zip file...
Click to expand...
Click to collapse

I have group of flash files
So rename PB00IMG to PB00IMG36
In order to distinguish them only
This version is 2.36.605.1
I install it several times before successfully

Now can not install this version or any other version

The cause of the problem is the following:
Install Rom kaosgingerbread-v8 incorrectly
How?
I had the power root in the past and not now
1- Recovery
2- Flash zip from sdcard (kaosgingerbread-v8.zip)
3- Reboot system

The result no system
no system of Genuine (2.36.605.1)
no system kaosgingerbread-v8

Then I knew the way with Rom correctly, namely:

1- Recovery
2- wipe data/factory reset
3- wipe dalvik cache
4- Flash zip from sdcard (kaosgingerbread-v8.zip)
5- Reboot system

But too late
 
Last edited:
B

bftb0

Senior Member
Feb 5, 2010
2,594
1,041
Ammar-y said:
Can anyone solve my problem please
Click to expand...
Click to collapse

Everything you indicated is completely consistent with some underlying problem in the /system partition - most likely due to many (NAND flash memory) pages being marked as bad.

This could be due to actual memory (hardware) fault conditions; however, if the problem occurred during a flashing operation, the more likely culprit is a low-level (kernel) bug/race condition that causes NAND flash memory pages to be marked as bad. (We've seen it on several-to-many phones; sometimes the use of a ClockwordMod recovery was implicated, but there really is no clear understanding of what causes it)

The only solution that I am aware of is to run the ErisMTDNuke_v0.9 zip (from a root-privileged recovery boot). So, (obviously) to do this you need a custom recovery running.

Because you are (for the moment) precluded from successfully writing the /system partition, you don't have any hope of installing a recovery via a booted & rooted OS. The only way you are going to get a rooted recovery running is through an installation of the S-OFF bootloader, and follow that up with a fastboot (boot or flash) installation of Amon_RA's recovery (or one of the Trackball-free/optional versions).

Because of version checking by the HBOOT/PB00IMG.zip installation process, the only hope of getting the S-OFF bootloader installed is via SoSicWitiT's trick of replacing the "rom.zip" file with one of the RUU installers.

It worked for a couple phones; for your phone, I think it is your last and best hope.

Steps (this is an outline, you need to fill in the gaps, all the info is in one of the XDA Eris forums):

1) Flash ROOT PB00IMG.zip file using SoSicWiTit's RUU/"rom.zip" replacement trick

Note: the system partition flash will (also) fail here - but the HBOOT flash to S-OFF might succeed. (If you can't get S-OFF, then stop. No joy.)

2) Get ErisMTDNuke_v0.9.zip onto your SD card, and a decent Eris ROM. (verify checksums)

3) boot (or flash) a custom recovery from your PC using fastboot

4) Flash the MTDNuke.zip file in recovery.

5) Shut phone off, cold boot into recovery, Flash your ROM, and be happy.


bftb0
 
  • Like
Reactions: Ammar-y
Ammar-y

Ammar-y

Member
Nov 7, 2011
20
3
39
Taiz
bftb0 said:
Everything you indicated is completely consistent with some underlying problem in the /system partition - most likely due to many (NAND flash memory) pages being marked as bad.

This could be due to actual memory (hardware) fault conditions; however, if the problem occurred during a flashing operation, the more likely culprit is a low-level (kernel) bug/race condition that causes NAND flash memory pages to be marked as bad. (We've seen it on several-to-many phones; sometimes the use of a ClockwordMod recovery was implicated, but there really is no clear understanding of what causes it)

The only solution that I am aware of is to run the ErisMTDNuke_v0.9 zip (from a root-privileged recovery boot). So, (obviously) to do this you need a custom recovery running.

Because you are (for the moment) precluded from successfully writing the /system partition, you don't have any hope of installing a recovery via a booted & rooted OS. The only way you are going to get a rooted recovery running is through an installation of the S-OFF bootloader, and follow that up with a fastboot (boot or flash) installation of Amon_RA's recovery (or one of the Trackball-free/optional versions).

Because of version checking by the HBOOT/PB00IMG.zip installation process, the only hope of getting the S-OFF bootloader installed is via SoSicWitiT's trick of replacing the "rom.zip" file with one of the RUU installers.

It worked for a couple phones; for your phone, I think it is your last and best hope.

Steps (this is an outline, you need to fill in the gaps, all the info is in one of the XDA Eris forums):

1) Flash ROOT PB00IMG.zip file using SoSicWiTit's RUU/"rom.zip" replacement trick

Note: the system partition flash will (also) fail here - but the HBOOT flash to S-OFF might succeed. (If you can't get S-OFF, then stop. No joy.)

2) Get ErisMTDNuke_v0.9.zip onto your SD card, and a decent Eris ROM. (verify checksums)

3) boot (or flash) a custom recovery from your PC using fastboot

4) Flash the MTDNuke.zip file in recovery.

5) Shut phone off, cold boot into recovery, Flash your ROM, and be happy.


bftb0
Click to expand...
Click to collapse

Thank you bftb0 for help me
I have three notes

1 - When he used the root rom my Eris gives me a MESSAGE
The Old Version
And nothing happens
HBOOT remains as it is:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (0010000)

Becuase main Version 2.36.605.1 installed

I need root rom with main Version 2.36.605.1 or better

2 - Eris mode are available :
RUU mode = yes
Normal mode = no
HBOOT mode = no
FastBoot mode = no
Recovery mode = no
BootLoader mode = no

3- My english is bad

Thank you bftb0 for help me again
 
D

doogald

Senior Member
May 27, 2010
1,387
337
As far as I know, nobody ever released an RUU with updated software. I think that you are out of luck.
 
  • Like
Reactions: Ammar-y
You must log in or register to reply here.

Similar threads

P
Gmail 2.3 APK Download (when Market install fails)
Replies
29
Views
184K
D
doogald
bigslanki
How to flash_image Amon RA's recovery
Replies
26
Views
27K
D
doogald
composerdude
How Does HTC Sign Their Roms
Replies
21
Views
8K
H
har0ld
K
[Q] non-rooted eris stuck on boot screen
Replies
36
Views
13K
C
Cap'nO
S
[Q] Halo Boot Animation
Replies
19
Views
12K
fashoughing
fashoughing

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    Ammar-y
    Ammar-y
    doogald said:
    There may be a solution: see this thread: http://xdaforums.com/showthread.php?p=22725909#post22725909
    Click to expand...
    Click to collapse

    Thank you "doogald" .
    Thank you "bftb0" .
    Thank you "scotty" .
    Thank you "scary alien" .
    Thank you "erisuser1" .
    Thank you "Stonent" .
    And thanks for all.

    My problem fixed with 5 steps:

    1- Flash hboot version 1.51.0000.

    2- Unlocked hboot.

    3- Create zip file (recovery.img + android-info.txt ) with zip program default in windows 7 not with winrar, rename file for example recovery.zip .
    recovery.img = recovery-RA-eris-v1.6.2.img
    android-info.txt =
    Code: 
    CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12
    Then flash this new file (recovery.zip) in RUU mode.
    Code: 
    fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip [COLOR="DarkGreen"]recovery.zip[/COLOR]
fastboot reboot-bootloader
    4- Install "ErisMTDNuke_v0.9.zip" from the recovery.
    Code: 
    1- Recovery 
2- wipe data/factory reset
3- wipe dalvik cache
4- Flash zip from sdcard ([COLOR="DarkGreen"]ErisMTDNuke_v0.9.zip[/COLOR])
5- Install any rom (goto 5 step)

    5- Install any rom for example "kaosgingerbread-v8.zip" from the recovery.
    Code: 
    1- Recovery 
2- wipe data/factory reset
3- wipe dalvik cache
4- Flash zip from sdcard ([COLOR="DarkGreen"]kaosgingerbread-v8.zip[/COLOR])
5- Reboot system
    View
    2
    D
    doogald
    There may be a solution: see this thread: http://xdaforums.com/showthread.php?p=22725909#post22725909
    View
    1
    D
    doogald
    Ammar-y said:
    Thank you "doogald" .
    Click to expand...
    Click to collapse

    Wow, that's great. Congrats.

    All of your thanks should be directed to bftb0, scotty1223 and ScaryAlien - they did all of the "heavy lifting" in that thread. I'm glad to have done my very small part.

    And thanks to you for reporting what worked for you. I'm glad that we finally have some tools for phones with the latest OTA that have this problem.
    View
    1
    D
    doogald
    I agree that this thread is probably the best solution: http://xdaforums.com/showthread.php?p=11651122#post11651122

    Over on AndroidForums, we've seen quite a few of these that have been solved using this method. At this point, it's the best bet. Scary_Alien put the steps together in one post here, for somebody who had a similar issue (though not quite the same, in this case; his ROM actually runs, he just cannot start Recovery, and cannot replace what's there with Amon_RA):

    http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263


    At least for the Eris, the best thing in my opinion:

    - stay away from Clockwork as the default Recovery. You can still run Clockwork from ROM Manager if you are using Amon_RA, but almost every one of these phones that has ended up in this state did so with Clockwork as the default Recovery

    - stay away from KaosGingerbread. Punk.kaos seems to have abandoned this, it never ran well anyway for a day-to-day ROM, and lots of people have problems with it. There are a number of up-to-date GB builds, such as GSB, CondemnedSoul, Tazz's ROMs, Evervolv, etc.

    I think that the problem is that people who search for rooting the Eris stumble upon blog posts that describe how to root with Clockwork Recovery and also mention how great KGB is; I'm not sure that was ever true, though it surely was cool that our phone had a GB build early on in the game.
    View
    1
    S
    scary alien
    What is the PB00IMG36.zip file that you are trying to flash and where did you get it from?

    I am unfamiliar with that .zip file...
    View

New posts