PDA

View Full Version : Nearly a brick-Kaiser


sbolt986
18th July 2008, 01:24 PM
I have a new (to me) Kaiser, which i tried to upgrade last night with a cooked ROM,( Duttys non Cube, Non-Lite from 4-29-08) going through the soft SPL, Hard SPL, and ROM upgrade painstakingly. Once done, the device powered up, buzzed the AT&T screen, and just continues to cycle from dark to the the AT&T screen- until i yank the battery. When i press camera button and the reset button i get the tri-color screen with: " KAIS1*0 MFG SPL-1.0.01iPof CPLD-8.
i figured the ROM ( copied from a known good source to a thumb drive to my desktop) might have been somehow corrupted, and formatted a micro SD card, downloaded the ROM from this site, renamed it KAISIMG.nbh, pressed the camera button and...the screen goes to tri-color, briefly flashes No Image Found, and then reverts to the tri-color. The AT&T screen cycle persists. Frustrated, but not yet panic-stricken; i read more here and do the MTTY exercise from Pof and get the following output: "Cmd>boot
InitDisplay: Display_Chip=1

Fill RSVD information for block 288 to 309
Storage start sector=0x9E00, total sector=0x114C0
Storage start block=653, total block=1107
Total Bad Block in CE: 1

Erase physical block from 942 to 2032

formatstorage Bad block found: 1933
si backup: Erase physical block from 2032 to 2048

No card inserted

OSSIPreLoad ++

FMD_ReadSector+, bad block no=0x4F40, status:0x0"
so, now i am at a complete loss. the unit persists with the AT&T screen cycle, on buzz, partial AT&T display, then dark- and pressing the camera button/reset still gives the same tri-color screen as before.
So, i've managed to take an otherwise fine device and taught it to be as stupid as it's owner. I really need this thing to function for my work, and beg for sage advice. Thanks in advance.

monx®
18th July 2008, 01:35 PM
omg, i'm sorry mate. my post is useless for u. just wondering why u didnt flash it via ur pc. it was a nightmare but i'm pretty sure some experts can help u.

sbolt986
18th July 2008, 01:42 PM
original flash was via PC, after i got stuck, activesync cannot see the device, so i resorted to the micro SD to try; hopefully someone with a bigger brainstem than mine can pitch in

monx®
18th July 2008, 01:48 PM
actually if u can see tricolor screen, activesync is not needed to flash using CustomRUU. have u tried flashing original shipped rom? just an idea because i also failed to flash so many times long time ago :o

tomasz
18th July 2008, 03:06 PM
Tried to go to tri-color screen, connect USB so 'USB' is displayed instead of 'serial' and then flash from CustomRUU utility?

That worked for me when my pc bsod'd during an update.

jommo
19th July 2008, 05:51 AM
Have you found a fix for this? I have a similar problem... See my problem (http://forum.xda-developers.com/showthread.php?p=2423564&posted=1#post2423564).

At your point, I would also recommend flashing back to an original ROM, which can be done from the tri-color screen. To my best understanding, all you need to do is have the Hard SPL loaded, which you do have.

Please update if you find a fix. Hopefully it can help me as well.