Develop Bugs

rooting progress but still an issue

So I just successfully rooted my phone and now trying to unlock NAND. The issue im experiencing is when using adb in CMD to do this step "cat /sdcard/flash_image > /data/flash_image" I get cannot create /data/flash_image: permission denied.
Im not sure what to do now. Could someone please help.
Ive been using unlocker's rooting guide- which is the only one that has worked for me
Thanks in advance

Nevermind! fixed the issue. The tutorial says to put phone in "Charge only" mode, but you have to keep the phone in disk drive.
but now when i try the same command it says "no such file or directory

no u dont keep the phone in disk drive cause i think the phone cant read the sd card cause ur on the drive with the computer. try doing it with out it only on charger but im pretty sure if u check the 2nd post u'll see common error and how to fix them.

AWESOME! thanks so much! I guess I had to put it into disk mode to allow "super user" then put it back into charge only.
onto the next step. Thank you very much!
EDIT: No! run into the same problem as before.. says "main version is older"

wait what software version are u running on right now and if u do a quick search you'll should find that older version problem some where.

EPIC. WIN.
and toast, if you ever had a reason to sticky one of your own threads, I think this one is deserving.
Common Mistakes / Questions
Problem:
I can't download the files / They are corrupted / etc!!!!1!!!!1
How to fix:
Here's a mirror, thanks to lewi3069.
Originally Posted by lewi3069 View Post
http://cybermetricsystems.net/android/PC36IMG.zip
http://cybermetricsystems.net/android/flash_image.zip
http://cybermetricsystems.net/android/mtd-eng.zip
http://cybermetricsystems.net/android/recovery.img
----------------------------------------------------
Error:
Code:
adb shell
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat: can't open ' /sdcard/flash_image' : No such file or directory
How to fix:
Your sdcard isn't mounted properly. You can use ADB to push the files:
Code:
adb push /path/to/flash_image /sdcard/flash_image
adb push /path/to/mtd-eng.img /sdcard/mtd-eng.img
or try to mount the card: (*note, this command only works from recovery. If you are inside the android OS you have to use adb remount. This is also how you test system r/w access, which is what this whole process gives you
Code:
adb shell mount /sdcard
----------------------------------------------------
Error:
Code:
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
(note: probably a lot longer than that)
How to fix:
You are using the wrong PC36IMG.zip file. Its not the same one from part one. Download the file listed in Toast's post, above.
----------------------------------------------------
Error:
Something about "Main version is older" ...not sure of exact syntax
How to fix:
You need to redo the mtd-eng.img step. Check and make sure you didn't get the sdcard mounting error.
----------------------------------------------------
Question:
Can I delete these files from my sdcard, now that I have finished?
Answer:
Sure. Alternatively, you can just throw them into a folder named whatever you want (example folder name: "files for rooting") and leave them there in case you need the later! Totally up to you, but yes they are safe to remove.
----------------------------------------------------
Question:
Do I have to backup/restore my nandroid? Can't I just flash a new ROM?
Answer:
Yep. The advantage of restoring your nandroid is I believe you get your radio back. Maybe not. It takes like 3 seconds to restore your radio anyway. I just flashed my ROM back over clean and used Titanium Backup which I strongly recommend to restore all my apps.

Okay, ill try that. Ill use those files- that will then eliminate any possibility im using wrong files. Almost done d/ling PC36IMG

okay i need to know more info cause i see u posted on the thread can ur computer communicate with ur phone and sd card. then did u do any other roots like unrevoked or u tried simple root. what is ur software version check on the about phone in setting then software info.
my brother got his phone a week ago and i did the simple root on it and worked fine

Okay its working the listed files above!
Before this latest try, i did a factory default to make sure no attempts before caused issues.
im using 1.47.651.1

SWEET! I was using the wrong files or something.. Its updating now
Im running 1.47.651.1

great so u should b full nand unlocked now

Okay got NAND unlocked! Now my problem is what ROM to flash im deciding between Baked snack and fresh evo..
what do you guys think?

well its all up to u and to each there own but i personally like dc latest 2.1 but im on the newest ava froyo waiting for dc froyo to b released have fun dont forget to do a nand back up before hand

But like whats the pro's cons of those? which would be best for me to flash with my software and running 2.1.. just so confused with all the different ROMS
edit: also, how do i make a NAND backup??

nand back up is in recovery under restore and back up
now with the roms just read up on them and make sure ur up to date with the radios and wimax most of them give u links to the threads and show u how to do it. pretty easy to do install them under the zip install just like u were installing a rom.

Bad Blocks on Boot Partition

Anyone else with this problem? OTA won't install for me. Phone won't flash kernels larger than 2.2MB. How can I get Sprint or HTC to replace this phone?

i'm in the same boat buddy. question, what method(s) did you use to root/unlock?
i first did unrevoked (just for root), then (weeks later) the unrevoked 1.47 ota thing, then the three click method...

how did you find out what size kernel you can flash? Is therr some utility to check for bad blocks

i was flashing a ROM, and i got this (from the log)
"/data/firstboot.sh"
minzip: Extracted file "/data/local/resolv.conf"
calling command set_perm
calling command show_progress
calling command format
Formatting BOOT:...
mtd: not erasing bad block at 0x001e0000
mtd: not erasing bad block at 0x00260000
calling command write_raw_image
Writing BOOT:...
mtd: not writing bad block at 0x001e0000
mtd: not writing bad block at 0x00260000
E:Error finishing BOOT:
mtd: not writing bad block at 0x00260000
E:Failure at line 396:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/DamageControl-3.5-final.zip
ra-recovery and clockwork both just said "error writing boot image"

canteenboy said:
Anyone else with this problem? OTA won't install for me. Phone won't flash kernels larger than 2.2MB. How can I get Sprint or HTC to replace this phone?
Click to expand...
Click to collapse
you could accidentally drop it in the toilet or "lose" it

Microwave, 3 or 4 seconds...done. But, good luck getting a phone in under a few weeks.

Warm 2.2 RLS4 to Fresh 3.5.0.1 flashing Problems

Im having problems flashing Fresh 3.5.0.1. The phone currently has Warm 2.2 RLS4 on it, Ive never had a problem flashing roms before until now, Any help would be appreciated, Below is the Recovery log so that you can see what's going on. Thanks to anyone who can help me.
Starting recovery on Sat Dec 25 20:09:54 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
psfMod freeBuild
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
I:Running script:
I:
print "ROM Manager Version 3.0.0.2"
print "Preparing to install ROM..."
format CACHE:
format DATA:
format SDEXT:
install_zip SDCARD:/fresh-evo-3.5.0.1.zip
Parsed /tmp/extendedcommand
calling command print
ROM Manager Version 3.0.0.2
calling command print
Preparing to install ROM...
calling command format
Formatting CACHE:...
mtd: not erasing bad block at 0x05240000
mtd: not erasing bad block at 0x05840000
calling command format
Formatting DATA:...
mtd: not erasing bad block at 0x07120000
mtd: not erasing bad block at 0x0a780000
mtd: not erasing bad block at 0x199c0000
calling command format
Formatting SDEXT:...
No app2sd partition found. Skipping format of /sd-ext.
calling command install_zip
-- Installing: SDCARD:/fresh-evo-3.5.0.1.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/fresh-evo-3.5.0.1.zip
Opening update package...
I:Update file path: /sdcard/fresh-evo-3.5.0.1.zip
minzip: Missed a local header sig (at 942)
E:Can't open /sdcard/fresh-evo-3.5.0.1.zip
(bad)
Installation aborted.
Failure at line 6:
install_zip SDCARD:/fresh-evo-3.5.0.1.zip

It looks like the downloaded file is corrupted. Try downloading again. Also, make sure you wipe before installing Fresh or you might get stuck in a bootloop

113MB of bad blocks on /data...can i be helped???

Edit: summary of what ive tried and failed with.
Wipe all userdata from cwm and amon recovery ... no effect.
erase_image from cwm ... no effect.
fastboot erase ... no effect.
fastboot erase -w ... no effect.
RUU ... no effect.
cat zero to mtd ... no effect.
dd zero to mtd ... no effect.
flash_image (image edited with hex editor to contain only zero's) ... no effect.
fastboot oem task 28 ... no effect.
fastboot oem task 29 ... no effect.
fastboot flash hboot (different partition tables) ... no effect.
I'm out of ideas.
Original post:
Even after clearing all userdata from recovery and erasing userdata from fastboot i am missing over 100mb from /data, but there are no files there taking up the space.
How can i reclaim this space, is it corrupted??? How do i check for (and fix) a corrupt filesystem on android?
I'm thinking of flashing a new HBOOT, oxygen table, but if it's corrupt will it screw it up or fix it?
Below was done from recovery and fastboot and shows the problem, look at how much space is in use on data after wipe.
Code:
[email protected]:~$ sudo su
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.1M 93.9M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock5 197.6M 187.5M 10.2M 95% /data
/dev/block/mmcblk0p1 3.7G 3.4G 302.9M 92% /sdcard
[B]/ # #wipe all userdata from recovery (amonra 2.0.0)[/B]
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # reboot bootloader
[B][email protected]:/home/mercianary# fastboot erase userdata
erasing 'userdata'... OKAY[/B]
[email protected]:/home/mercianary# #into recovery again
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # ls /data
lost+found
/ # du /data
2 /data/lost+found
4 /data
I'm using
CM7
amonra recovery 2.0.0
N1 Boot table
Any help troubleshooting this would be great, thanks.

did you wipe the /data/ partition in mounts & storage in recovery? try that if not, also try flashing a stock ruu, it will revert and changes made to the MTD Partitions

that was the first thing i tried, no luck. it erased fine but space was still missing
I dont particularly want to flash a RUU or another HBOOT untill i know what's wrong because if there's 100mb of bad nand on my phone i can imagine flashing a RUU or HBOOT going very wrong and leaving me with a very pretty paperweight.

I tried flashing some different hboots, problem still there, it just moves round a bit....
on the original boot table the space is missing on system and data..about 10mb or 20mb on system, the rest on data.
on oxygen and n1 boot table its just missing on data.
I cant seem to reclaim this space
anyone know how to check the disk for errors?

thats bad news, sounds like you may have some corrupt blocks

AndroHero said:
thats bad news, sounds like you may have some corrupt blocks
Click to expand...
Click to collapse
just a few, only 897 of them the phone is still working, so i suppose i'm kinda lucky.
I think i may have screwed it up a few weeks ago when i was messing around with cat, dd, fastboot and flash_image. I remember when i finished messing around i tried to restore my nand backup back on it but it failed, looking back it must have been because it didnt fit anymore due to the bad blocks. This must have been when the corruption occured.
Is it normal to have this many bad blocks? i've never seen more than a few, i'm hoping they aren't actually bad and it just thinks they are because of something stupid i did, is there anything i can do to remove the bad block flag (if there is one???) and then try again?
Code:
/sdcard/badblock # flash_image userdata mtd5.img
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00020000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00040000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00060000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00080000 (errno=0)
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
...
edited because it put the post over the 30,000 character limit!
...
mtd: not writing bad block at 0x0c520000
mtd: not writing bad block at 0x0c540000
mtd: not writing bad block at 0x0c560000
mtd: not writing bad block at 0x0c580000
error writing userdata: No space left on device
/sdcard/badblock #

That's way too high. NAND blocks usually fail at once and in the same area but not that many at once unless it be software error or a major stressor placed on them. It may be faulty bad block management defuncting those cells. If you could somehow find a way to Secure Erase the NAND, it could help. NAND cells sometimes work fine after this and cell state becomes reset so all those marked bad will be recycled back in use to test. The reason why they can sometimes spring back to perfect retention after a SE is academically quite known.
------------------------------
- Sent via HTC Desire -

I guess that you should use an RUU as it should format nand. If it does not the update wikl fail which mesns that your bad block could never be recoverd. Keep in mind to use RUU and not a PB.img i believe it is safer as long as it comed to bricking the phone. I know that some pvt 1 boards had some bad blocks on nands but never so muny( if it is a pvt1) . Regards
Sent from my LeeDroided Desire HD

I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun

mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
mercianary said:
I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun
Click to expand...
Click to collapse

mariosraptor said:
mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
Click to expand...
Click to collapse
That's what I was planning to do but I decided against it for several reasons.
I'm not feeling lucky, I dont think I will get away with it this time.
With the nature of the problem I can imagine whoever gets their hands on it at HTC will look into what's happened and discover my warranty's void...paranoid I know.
It doesn't help that there is no RUU for orange UK branded desires, I have to use a dodgy method to unroot (restoring an old backup, removing superuser and su then updating OTA.)
I'm happy with the way it is at the moment, who knows, I might drop it under my car at some point in the near future

anyone know anything about performing a low level format or clearing the bad block map so i can start a fresh???
PS...turns out the stock orange rom doesn't even fit on /system because its missing 10MB of space...damn you orange bloatware...damn you to hell!!!
PPS...Bump.

Get in contact with a dev. I am sure they will help you out to access and do a secure wipe on your memory. Way beyond me for sure

Got this when flashing recovery via terminal..

Hi,
After typing this command:
Code:
flash_image recovery recovery.img
I got this:
Code:
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
So, what's this block? I mean is it some mount point or bootloader stuffs? According to feedback by terminal it seems like recovery's dead, but it successfully flashed it. How to fix?