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.
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.
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):
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.
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):
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.
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
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):
New Mobile Operating System Jolla Sailfish‘s … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
Problem: does not boot and does not recovery
Print
Email
Problem: does not boot and does not recovery
View Profile
View Forum Posts
Visit Homepage
Linear Mode
