72 replies to this topic

[PaulOBrien]

Uploaded 1.2 with the script fixes.

What should happen...

- the device should reboot (adb shell reboot oem-78)
- the device should boot the superboot image (fastboot boot tattoo.superboot.img) and appear to boot normally, adding su and superuser.apk

If the main image doesn't work, i'd expect the alternate image posted above to!

Hmm...

P

[PaulOBrien]

Not sure if this will work, but booting normally, could you post the output of:

'adb shell cat /etc/fstab'

and

'adb shell mount'

You may need to enable USB debugging.

Cheers!

P

[PaulOBrien]

The reason for the request above is i'm assuming that, like the Hero, /system is actually /dev/block/mtdblock3, unless anyone knows differently?

P

[mainfram3]

1.2 hangs in the same spot.
It never reaches the fastboot reboot command.

C:\1.2-tattoo-superboot>fastboot-windows boot tattoo.superboot.img
< waiting for device >
downloading 'boot.img'... OKAY
booting...

I'll post the output of those adb commands shortly.

[mainfram3]

Here you go, Paul.

C:\1.2-tattoo-superboot>adb-windows.exe shell
$ cat /etc/fstab
cat /etc/fstab
/etc/fstab: No such file or directory
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0

[PaulOBrien]

The final fastboot reboot is erroneous, and not required for the Tattoo fastboot.

When it boots and hangs, do you get the splash screen? Is the device visible to adb?

P

[PaulOBrien]

Thanks mainfram3, I am trying to mount the right partition then. Hmmm...

P

[chusen]

mainfram3, on Jan 13 2010, 14:41, said:

1.2 hangs in the same spot.
It never reaches the fastboot reboot command.

C:\1.2-tattoo-superboot>fastboot-windows boot tattoo.superboot.img
< waiting for device >
downloading 'boot.img'... OKAY
booting...

I'll post the output of those adb commands shortly.

I have the same problem....some solution? thanks for all

[PaulOBrien]

Could someone confirm they have also tried my alternate boot image from here?

http://loadbalancing...p7dl1ff9adx2f63

- adb shell reboot oem-78
- fastboot boot tattoo.superboot.1.1.alternate.img

Thanks!

P

[despod]

chusen, on Jan 13 2010, 15:00, said:

I have the same problem....some solution? thanks for all

Same here.

If I pull the USB cable I get a spalscreen with 3 android chaps.

[mainfram3]

That link is not wget frendly
Either way, same result as the others, hangs on "booting...".

No change in the phone screen, still display htc logo, on black background.
Disconnecting USB shows the 3 skating androids, with RUU on top.

[PaulOBrien]

Gah, very strange!

Not sure what more I can do until I get a Tattoo...

P

[chusen]

Same problem

[unofficialitguy]

Paul, on Jan 13 2010, 10:02, said:

Could someone confirm they have also tried my alternate boot image from here?

Attempted to use both standard and alt boot img files. Hangs in the same place. Modified the install-superboot-mac.sh file to this (chmod the two other files prior to running this script):

./adb-mac shell reboot oem-78
echo Waiting 10 seconds for reboot...
sleep 10
echo Booting superboot...
./fastboot-mac boot tattoo.superboot.1.1.alternate.img
./fastboot-mac reboot
echo Done!

[seremoth]

calkar, on Jan 13 2010, 15:31, said:

same results with both images either with script or manually   (

always hangs in booting !

How long should be this step when it succeed ?

I have tried manually with boot standard and alternate image and I also hangs at booting
(tried on winXP SP2)

downloading 'boot.img'... OKAY
booting...

[PaulOBrien]

I fear it's doing some sort of signature checking, hence not booting...

P

[mainfram3]

Does this method work on other phones (adb shell reboot oem-78 and fastboot boot) ?
To me, it seems that the tattoo is silently ignoring the boot command, while in RUU mode.
I've tried other combinations, like fastboot oem boot tatto.superboot.img, but I never got any satisfying result.

Is there some debug console(?) or method to check what the Tattoo is answering to the fastboot boot command ?

[chusen]

Great job Paul though it does not work

[chusen]

Paul please continues trying it!!

[unofficialitguy]

Any chance that this could be used via Goldcard method to flash the rom?