Jump to content

Jakdaw

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jakdaw

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    Hero
  1. Jakdaw

    BUILD YOUR OWN CRIMINAL EMPIRE!

    It's huuuuuge!
  2. Did that - fastboot said it had sent reboot but the phone just sat there.
  3. This doesn't seem to work for me - when I run fastboot it seems to send over the boot.img but I never see the display change on the device & it doesn't seem to do anything. Any ideas?
  4. Jakdaw

    HTC launch the Desire HD (formerly known as the HTC Ace)

    So basically it's a physically bigger Desire with a smaller battery. What an anticlimax.
  5. Ah cool - thats all I need to know then... I can get going... Cheers
  6. It's ironic that the Android modding scene whom are so scathing (justifiably IMHO) about GPL violations by handset manufacturers are not squeaky clean themselves when it comes to their releases. "when I get a chance" is what we hear from HTC/Huawei & the rest whenever they release as product, and really isn't good enough. (Paul: I do seem to be Paul-bashing today - don't take this as meaning that I don't appreciate your efforts nor rights to either cover-costs or monetize MoDaCo!).
  7. Paul, Keep meaning to sort out a toolchain in order to build a kernel & tools to do USB tethering on the Pulse. Does your MCR kernel just use the source from http://forum.huawei.com/jive4/thread.jspa?...&orderStr=9 or have you updated bits of it, other than just the config? Teknologist has a nice GIT tree for the Hero sources - do you have something similar for the Pulse? Cheers!
  8. So, interestingly when I now boot the recovery image on the now-returned-to-T-Mobile-December-stock Pulse, it still can't perform a Nandroid backup: / # nandroid-mobile.sh -b nandroid-mobile v2.2.1 Using G1 keyboard, enter a prefix substring and then or just to accept default: Using - prefix to create a backup folder mounting system and data read-only, sdcard read-write checking free space on sdcard Dumping boot to /sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/boot.img...done mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No such file or directory Dumping recovery to /sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img. ..mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No space left on device md5sum: can't open '/sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img' : No such file or directory mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No space left on device md5sum: can't open '/sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img' : No such file or directory mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No space left on device md5sum: can't open '/sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img' : No such file or directory mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No space left on device md5sum: can't open '/sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img' : No such file or directory mtd: ECC errors (0 soft, 1 hard) at 0x00260000 error reading recovery: No space left on device md5sum: can't open '/sdcard/nandroid/mem=128M/BCDMRS-20091217-1057/recovery.img': No such file or directory Fatal error while trying to dump recovery, aborting. [/codebox]
  9. ... update from me... boot.img didn't help, just like Paul predicted, but applying the T-Mobile December update again did get it booting again.
  10. Thanks! Much appreciated!
  11. Nope - when you do a nandroid backup it'll create the following files: boot.img cache.img data.img misc.img recovery.img system.img I just want boot.img (and possibly recovery.img might be useful too) - neither of these contain any of your data (which is in data.img/cache.img... the apps etc are in system.img).
  12. You mean your repackaged zip file? Tried that... it sits in a reboot loop and I don't even see anything with "adb logcat". Can't go through the T-Mobile process with their .app file 'cos I need a working phone to do that on!
  13. Hmm.... I have this problem. I have two Pulse's here... one is mine.... the other belongs to a colleague (guess which one has a problem). He had performed the December T-Mobile update (which I'd not realised!). I installed boot, recovery and MCR 1.5 on my device no problems. His device isn't happy at all, it just sits in a reboot loop. I've tried to flash MCR 1.5 onto it, tried the stock Tmobile update zip, tried to restore a NANDROID backup from my working device onto it etc. Fastboot on the good device has a Build Date of "Sep 10 2009, 23:24:35". On the brick has "Nov 26 2009, 11:05:05". So I can boot into recovery and fiddle from there.. if I boot recovery, wipe data, install the MCR 1.5 and then reboot running "adb logcat" then it gets a good way through the boot sequence, gets as far as "Starting Audio Service" and then adb quits and the phone reboots. What I've noticed is interesting is that the recovery image can't do a nandroid backup, instead I get ECC errors: Dumping recovery to /sdcard/nandroid/mem=128M/BCDMRS-20091216-1701/recovery.img... mtd: ECC errors (0 soft, 1 hard) at 0x00260000 Running "nanroid-mobile.sh -b --norecovery" does succeed but that doesn't really help matters much. Is it possible the NAND is no longer partitioned in the same way? What else can I try? The "won't boot" problem started as soon as I installed Superboot - the first step! What would be really helpful is if someone with a vanilla (unrooted) that *has* the December update could: - Power on with VolDown, Red held to enter Fastboot. - Use "fastboot boot recovery-RA-pulse-v1.5.2.img" to boot the Amon-Ra recovery image (without flashing it!) - Perform a nandroid backup & send me boot.img
  14. ... I got a phone with that problem. Gets as far (in adb logcat) as: I/SystemServer( 1079): Starting Wallpaper Service I/SystemServer( 1079): Starting Audio Service [/codebox] ... then reboots. Presumably we can fastboot recovery and then adb shell and undo whatever it is that superboot has done?
×

Important Information

By using this site, you agree to our Terms of Use.