Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,779,457 Members 51,577 Now Online
XDA Developers Android and Mobile Development Forum

Problem: does not boot and does not recovery

Tip us?
 
Ammar-y
Old
(Last edited by Ammar-y; 17th November 2011 at 11:41 AM.)
#1  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
Exclamation Problem: does not boot and does not recovery

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





Not ClockworkMod recovery






RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver




Please help me
Attached Thumbnails
Click image for larger version

Name:	1.jpg
Views:	488
Size:	55.4 KB
ID:	774846   Click image for larger version

Name:	2.jpg
Views:	488
Size:	56.7 KB
ID:	774847   Click image for larger version

Name:	3.jpg
Views:	481
Size:	81.7 KB
ID:	774848   Click image for larger version

Name:	4.jpg
Views:	477
Size:	72.4 KB
ID:	774849   Click image for larger version

Name:	5.jpg
Views:	469
Size:	57.9 KB
ID:	776082  

 
Stonent
Old
(Last edited by Stonent; 8th November 2011 at 04:26 AM.)
#2  
Stonent's Avatar
Senior Member
Thanks Meter 28
Posts: 454
Join Date: Apr 2010
I think I'd go back to stock and start with a clean slate and go from there.

Second, under no circumstances use clockwork on an Eris. Use Amon_Ra. There's a big warning on the top of the page about how it can brick (or pretty close) your phone.

Also this may be of help:

http://forum.xda-developers.com/show....php?t=1137321
The Following User Says Thank You to Stonent For This Useful Post: [ Click to Expand ]
 
Ammar-y
Old
#3  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
Quote:
Originally Posted by Stonent View Post
I think I'd go back to stock and start with a clean slate and go from there.

Second, under no circumstances use clockwork on an Eris. Use Amon_Ra. There's a big warning on the top of the page about how it can brick (or pretty close) your phone.

Also this may be of help:

http://forum.xda-developers.com/show....php?t=1137321
Thanks for the reply
But the problem still exists
 
doogald
Old
#4  
Senior Member
Thanks Meter 312
Posts: 1,298
Join Date: May 2010
I agree that this thread is probably the best solution: http://forum.xda-developers.com/show...2#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-th...ml#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.
The Following User Says Thank You to doogald For This Useful Post: [ Click to Expand ]
 
Ammar-y
Old
#5  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
Quote:
Originally Posted by doogald View Post
I agree that this thread is probably the best solution: http://forum.xda-developers.com/show...2#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-th...ml#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.
Thank you very much
I'm working
 
Ammar-y
Old
(Last edited by Ammar-y; 13th November 2011 at 06:22 PM.)
#6  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
The problem is there


After pressing the power key, the following happens:


Then connect the USB cable to get the following:


Remove the cable when the show the following:


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>fastboot getvar boot-mode
boot-mode: RUU

E:\DroidEris\temp>fastboot getvar battery-status
battery-status: good

E:\DroidEris\temp>fastboot erase cache
erasing 'cache'... OKAY

E:\DroidEris\temp>fastboot flash zip PB00IMG36.zip
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[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again)

E:\DroidEris\temp>fastboot flash zip PB00IMG36.zip
< 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[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,42
INFO[RUU]UZ,boot,85
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[radio] 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
INFO[RUU]UZ,radio,100
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
INFO[RUU]WP,radio,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,41
INFO[RUU]UZ,recovery,82
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,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
INFO[RUU]UZ,system,76
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
INFO[RUU]WP,system,52
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
FAILED (remote: 51 partition update fail)

E:\DroidEris\temp>
This was the result:


Remove the cable when the show the following:


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
Attached Thumbnails
Click image for larger version

Name:	IMAG0103.jpg
Views:	441
Size:	45.4 KB
ID:	781460   Click image for larger version

Name:	IMAG0104.jpg
Views:	167
Size:	43.2 KB
ID:	781461   Click image for larger version

Name:	IMAG0105.jpg
Views:	169
Size:	96.5 KB
ID:	781462   Click image for larger version

Name:	IMAG0106.jpg
Views:	165
Size:	42.5 KB
ID:	781463   Click image for larger version

Name:	IMAG0107.jpg
Views:	170
Size:	54.5 KB
ID:	781465  

 
scary alien
Old
#7  
Recognized Developer
Thanks Meter 88
Posts: 261
Join Date: Jun 2010
Location: 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...
The Following User Says Thank You to scary alien For This Useful Post: [ Click to Expand ]
 
Ammar-y
Old
(Last edited by Ammar-y; 14th November 2011 at 07:27 AM.)
#8  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
Quote:
Originally Posted by scary alien View Post
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...
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
 
Ammar-y
Old
#9  
Ammar-y's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 20
Join Date: Nov 2011
Location: Taiz
Can anyone solve my problem please
 
bftb0
Old
#10  
Senior Member
Thanks Meter 796
Posts: 2,122
Join Date: Feb 2010
Quote:
Originally Posted by Ammar-y View Post
Can anyone solve my problem please
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

The Following User Says Thank You to bftb0 For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes