Develop Bugs

[Q] Boot partition problem, bad blocks

I bought my desire last week, besides no warranty as it is suppose to be sold here. Anyway, I am happy that I got a AMOLED one but when I get to the part flashing custom rom. It failed everytime when writing boot.img to the boot partition. Most rom give the following error message, where xxx is the line of the flash boot.img part in the update script.
E:Error finishing BOOT:
E:Failure at line xxx:
write_raw_image PACKAGE: boot.img BOOT:
Installation aborted
Click to expand...
Click to collapse
Some rom can boot up and the other can not and stuck reboot loop. I then have some search in XDA and modaco and find out that might be a problem in the boot partition, the internal flash memory got bad block. After trying to flash the boot.img in command line and confirmed with the following output
flash_image boot /sdcard/boot.img
mtd: read all-zero block at 0x00000000; skipping
mtd: read all-zero block at 0x00020000; skipping
mtd: read all-zero block at 0x00040000; skipping
mtd: read all-zero block at 0x00060000; skipping
mtd: read all-zero block at 0x00080000; skipping
mtd: read all-zero block at 0x000a0000; skipping
mtd: read all-zero block at 0x000c0000; skipping
mtd: read all-zero block at 0x000e0000; skipping
mtd: read all-zero block at 0x00100000; skipping
mtd: read all-zero block at 0x00120000; skipping
mtd: read all-zero block at 0x00140000; skipping
mtd: read all-zero block at 0x00160000; skipping
mtd: read all-zero block at 0x00180000; skipping
mtd: MEMGETBADBLOCK returned 1 at 0x001a0000 (errno=0)
mtd: read all-zero block at 0x001c0000; skipping
mtd: MEMGETBADBLOCK returned 1 at 0x001e0000 (errno=0)
mtd: read all-zero block at 0x00200000; skipping
mtd: read all-zero block at 0x00220000; skipping
mtd: read all-zero block at 0x00240000; skipping
mtd: read all-zero block at 0x00260000; skipping
mtd: not writing bad block at 0x001a0000
mtd: not writing bad block at 0x001e0000
error closing boot: No space left on device
Click to expand...
Click to collapse
While returning is not an option for me, it is just .
But I am not sure why I can use some rom and use RUU to flash it to stock. I am not confident with the custom rom as I am not sure why it work even when the boot.img is not flashed correctly. I stick to RUU for the moment, but lacking root really make it less fun with my desire. From the search in the forum I find some work arounds, like fastboot using boot.img in sdcard, flash boot.img in recovery(http://forum.xda-developers.com/showthread.php?t=731657). There are also people using custom mtd partition for their G1, don't know if that work for desire though(http://forum.xda-developers.com/showthread.php?t=717874). Has anyone got any luck with these methods?
I am wondering why some rom could work, it seems most rom have the flash boot.img part at last. Also if the boot partition have bad blocks, why does the RUU can work too. I do notice that I am stuck with the HTC first boot screen for all the rom, Is that just that boot screen not write successfully made the boot.img work for those custom rom ?
Last, any suggestion, and any others got the same problem and have a solution ?
Best Regards,
Kelvin

Seems this is a rare problem.................

Heard of this a few times, I managed to shrink the boot.img a little in my latest 1.9a build for y'all
Sent from my HTC Desire using XDA App

LeeDroid said:
Heard of this a few times, I managed to shrink the boot.img a little in my latest 1.9a build for y'all
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Very nice, downloading, will try it later.

HTC Desire - I have the same problem. Bad blocks? Solution?
Currently my Desire fails to install or boot any ROMs and I believe this is due bad blocks in boot partition preventing T-Mod rom installation using clockworkmod recovery.
I have throughly read and followed t-mod.org (full wipe of phone first, format of sd and other partions, including boot partiion etc) and the radio rom always flashes ok but installing any of the T-mod rom zips right near the end of the T-mod installation I get this:
Copying Boot Files...
Writing Boot..
E:Error finishing BOOT:
E:Failure at line XXX.
Understandably, different T-mod roms provide different XXX line numbers for the failure. I have googled this error and it seems reasonably common but I have found no solution. Some posters suggest the cause is due to bad blocks in the boot partition of some phones and suggest that a smaller boot.img be flashed in to get around the bad blocks.
Does anyone know how to do this or have any further ideas? Currently the phone is unserviceable (only boots to the clockworkmod recovery menu. My Nandroid restore fails and I can't return to use the RUU stock exe since it won't detect the phone etc etc.)
What to do? Thanks

Depends on what you want next. If you really need root, I suggest you try CM6 , because it has a smaller boot.img. It might give the same error, but in my case, CM6 can boot up.
If you are going back to RUU, then you have to check what is you LCD, SLCD or AMOLED. Both of them can use the H.boot downgrade (0.92 -> 0.80) method (in the dev forum tutorial) to return to 2.1 rom and then you can RUU flash the official rom. But you would be operating in the dark if you have SLCD, but there are post describe how to do that.

[Q] alpharev x issue - mtd: not writing bad block at 0x00020000

So a few of us wildfire users are trying to use Alpharev X to get S-off and are met with the following frustrating error:
Acquiring root (method 1)...
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press (almost) any key to exit.
This was pasted from another post, I'm sure the error I get is 0x00020000 rather than 0x00040000, but either way the issue is bad NAND and alpharev team are aware of this. My question is how many other users are experiencing this and has anyone had any success with getting past this? I dont think its very high on their to do list, but I'm sure if enough people are experiencing this they will take it more seriously.
I'm on a Telstra branded Wildfire (A3335) with HBoot 1.01.0002, so I wonder if its specific to this model or is it completely random (and simply bad luck)?
I've done a downgrade using the downgrade guide at http://forum.xda-developers.com/showthread.php?t=1132028
This got me HBoot 1.01.0001, but the problem persisted. It must have taken me 20 attempts to actually get this guide to work and I think the reason for this was also because of the bad NAND. during step 1 (gaining temp root) it would complain about not being able to write to the flash (sorry don’t have any exact error messages). The fact that it eventually worked makes me wonder if continuously running Alpharev X (and rebooting phone after every fail) would eventually work..
Would be good to hear suggestions and please reply if you are also getting this error or have managed to find a work around.

have you solved this issue yet ?? i got same problem but there is no way to solve it so far !

I have an HTC Evo 4g and I tried to root it using the Revolutionary tool and I got the same error message. My phone was upgraded to gingerbread OTA without my permission. Has there been a fix yet?

I am encountering the same problem and it's quite annoying
Tried both unrevoked and revolutionary methods without any success. Unrevoked comes back with: "Error: failed to get root. Is your firmware too new?" whilst revolutionary comes back with below:
C:\revolutionary-0.4pre4>revolutionary.exe runas administrator
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: HTC Wildfire (buzz-1.01.0001, Android: 2.2.1, ROM version: 2.
22.405.1)
This is a beta release and requires a beta release key.
Enter beta key [ serial: <###SERIAL HERE###> ]: ##KEY HERE##
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
Press (almost) any key to exit.
In order to get revolutionary to work, I also ended up downgrading my hboot to 1.01.0001 from 1.01.0002.
In case this helps, my phone is on the three network in the UK. Looking forward to a solution to this issue since quite a lot of people seem to be encountering it.

never root??...
Desire(A8181) Hboot 1.02.0001, firm 2.3.3 stock. Have a 100% same problem. NO root, no s-off.... i Killed my brain. Nothing helpe, absolute.
From Russia, sory for my english)

I have the same problem with Wildfire bought in Poland. :/
but there is also an official way to unlock bootloader.
has sb tried (with bad block issue) unlock bootloader via HTCdev?

maskim said:
I have the same problem with Wildfire bought in Poland. :/
but there is also an official way to unlock bootloader.
has sb tried (with bad block issue) unlock bootloader via HTCdev?
Click to expand...
Click to collapse
I don't think you will have any problems unlocking via HTCDev. I also think that there is a thread regarding this somewhere in the q&a section forum.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5

bad block problem by revolutionary ?is there way to avoid writing in bad block ?

Have problem
im trying to S-OFF & Recovery by Revolutionary
and it always give me
Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press (almost) any key to exit.
Click to expand...
Click to collapse
and my device Info. is
(bravo-1.02.0001, Android: 2.3.3, ROM version: 3.14.405.1)
and as shown in RootWiki
my device is officially supported
Revolutionary currently supports the following Android phones and HBOOT versions:
HTC Desire (bravo) 0.93.0001, 1.02.0001
Click to expand...
Click to collapse
im just asking is there way to avoid writing in bad sector ??
i contact with revolutionary (IRC)
and they told me your device is defective and i must get a new one

Ask in revolutionary irc channel.
SwiftKeyed from Oxygen with Transparent XDA App

I have EXACTLY the same problem
mtd: not writing bad block at 0x00040000
with desire with HTC's "official" gingerbread.
Can somebody give us any advice - is there any other way to write a different rom/S-OFF?
help

GreenToad said:
I have EXACTLY the same problem
mtd: not writing bad block at 0x00040000
with desire with HTC's "official" gingerbread.
Can somebody give us any advice - is there any other way to write a different rom/S-OFF?
help
Click to expand...
Click to collapse
go to htc care center and tell them i have internal memory problem and some apps goes away and brick, they should replace ur mother board with new one
thats what hapeend with me ,,

[A] - [Q] Trying to root Desire Bravo GSM - Got answer

]Hi all!
I have rooted my own Desire Bravo GSM, and trying to do this with
another phone.
It all went well on mine, but I get an error on this.
This is the RUU File (that gives you a bit info about the phone):
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
and the hboot is 93.00001 (Same as mine phone)
I run ubuntu on my laptop and used this One-Click from Unrevoked.
All went fine on my phone, but the error I get on this other is
Code:
"Backup CID is Missing"
and when I run revolutionary I get this:
Code:
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors (if any):-
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
Edit: Trying an older one-click from Unrevoked I get this in terminal (and still get Backup CID is Missing):
Code:
ERROR: n = -1, errno = 19 (no such device)
rawadb_open: remote closed the connection looking for target "reboot"
Edit: Answer in my last post if anybody else has the same problem.

Tried with a different PC?

bortak said:
Tried with a different PC?
Click to expand...
Click to collapse
Yeah. He tried on his own (Win pc) and I tried on my own (ubuntu).
Gave same error, Backup CID is Missing

Try Revolutionary:
http://revolutionary.io/

MatDrOiD said:
Try Revolutionary:
http://revolutionary.io/
Click to expand...
Click to collapse
That I did, the code under "and when I run revolutionary I get this:"
is the error I get when I run revolutionary

LarsChristian said:
That I did, the code under "and when I run revolutionary I get this:"
is the error I get when I run revolutionary
Click to expand...
Click to collapse
My bad. Did not read it. I recommend to ask in IRC-Channel of Revolutionary.

MatDrOiD said:
My bad. Did not read it. I recommend to ask in IRC-Channel of Revolutionary.
Click to expand...
Click to collapse
Have tried, no answer yet.

Got the answer from Revolutionary's irc channel:
Code:
badblocks is If you get "Not writing bad block at 0xXXXXXXX
errors while running Revolutionary, you have a hardware error on your NAND.
We have no workaround for that at the moment, sorry.
Nothing to do, can't be fixed. Damn.

I'm looking for Unobtanium.... Stock Gingerbread

Htc Desire/Bravo.... I have the factory Froyo 2.2 installed on my Desire right now but would like to upgrade to the ROM released by HTC on their developers site. The site seem to be down or buggy. Has anyone got this file hidden away somewhere? I cruised through a lot of sites including this one looking for this file but all I found were custom roms or links to the HTC site that doesnt seem to work. I am not against using custom roms but I havent had luck with this in the past and am not real excited about traveling down that path again. Thanks for any help pointing me in the right direction....

This one is stock, just some updated apps, no a2sd, no nothing, but it's rooted...
http://www.fileswap.com/dl/rzzpsUX22Y/nlooooo_stock.zip.html
flash it like a custom rom. If you'd like the official RUU someone else is going to have to jump in... ;-)
Sent from my HTC Desire using Tapatalk

This is the unrooted stock RUU I got from HTC's website, I've also included the addons (wallpapers, flashlight.apk, etc).
http://dl.dropbox.com/u/32128487/Android 2.3 Stock.zip

Thanks guys!!
I really appreciate the response.... I will be trying these out as soon as possible.

http://forum.xda-developers.com/showthread.php?t=695667
Sent from my HTC Desire

Wtf
I have now tried several different Roms but all have failed as has rooting. The Revolutionary root tool and factory ruu update both failed part way through and the Rev. shows some sort of failure to write to certain memory blocks. I will have to go through them all again to get the specifics. Anyone else ever have these issues with so many methods of making changes to their phone? The phone works fine on the present software so Im not sure why I'm having these issues....

my80chevette said:
I have now tried several different Roms but all have failed as has rooting. The Revolutionary root tool and factory ruu update both failed part way through and the Rev. shows some sort of failure to write to certain memory blocks. I will have to go through them all again to get the specifics. Anyone else ever have these issues with so many methods of making changes to their phone? The phone works fine on the present software so Im not sure why I'm having these issues....
Click to expand...
Click to collapse
Revolutionary.io method worked after all methods, unrevoked etc failed for me......so better give it a retry....
Regards
Sent from my HTC Desire using xda app-developers app

heres what Revolutionary said
Well I ran through the process with the Rev io again and heres what it had to say
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PB99400 (bravoc-1.06.0000, Android: 2.2, ROM version: 2.11.57
3.5)
This is a beta release and requires a beta release key.
Please visit: Revolutionary.io for more information.
Enter beta key [ serial: HT11KHM02160 ]: ************* Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
Press (almost) any key to exit.
So any idea what the issue is folks.......?

my80chevette said:
Well I ran through the process with the Rev io again and heres what it had to say
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PB99400 (bravoc-1.06.0000, Android: 2.2, ROM version: 2.11.57
3.5)
This is a beta release and requires a beta release key.
Please visit: Revolutionary.io for more information.
Enter beta key [ serial: HT11KHM02160 ]: ************* Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
Press (almost) any key to exit.
So any idea what the issue is folks.......?
Click to expand...
Click to collapse
The biggest problem is that you have desire CDMA (bravoc with different hboot from bravo). Most desire roms are not compatible with CDMA just like classical RUUs.
Search a bit more, plus read instructions and device compatibility given on revolutionary site.
Sent from my HTC Desire via flashes and thunders

The stupid s-on won't change and I have read everything I can find on how to change it. I have considered the gold card method of doing this and trying to change the bootloader version but Im not sure I am willing to go through the headache. So this may be my indicator to get a different phone to play with.

my80chevette said:
The stupid s-on won't change and I have read everything I can find on how to change it. I have considered the gold card method of doing this and trying to change the bootloader version but Im not sure I am willing to go through the headache. So this may be my indicator to get a different phone to play with.
Click to expand...
Click to collapse
Mate, reconsider what I told you, you have Desire CDMA or codename Bravoc, it's quite different from regular desire and you need specific roms and RUUs, also official 2.3 RUU is not working on your device.
Look at your bootloader everything is written there.
Go here, Desire CDMA section and try roms that are specific for your device:
http://forum.xda-developers.com/showthread.php?t=809328
Sent from my HTC Desire using flashes and thunders

I'm not sure if this guy is joking with us...
Sent from my HTC Desire using flashes and thunders