Author Topic: [solved] Can't Boot Into Single User Mode.  (Read 6135 times)

m_kylli

  • Newbie
  • *
  • Posts: 2
    • View Profile
[solved] Can't Boot Into Single User Mode.
« on: November 24, 2008, 04:07:17 pm »
After trying Angstrom with Opie on my SL-C3200, I decided to go back to cacko. I started by doing a nand restore with systc320.dbk.
I then tried to enter single user mode using the d+b trick only for nothing to happen, no SHARP screen, nothing.
I figure OK, lets try flashing cacko anyway. So i start it while holding OK, choose option number 4, choose SD and choose Y.
The screen turns black and nothing happens.

Does anyone have a solution? Could the systc320.dbk be corrupted and still go through the restore? Anything?
« Last Edit: November 25, 2008, 02:27:20 pm by m_kylli »

Capn_Fish

  • Hero Member
  • *****
  • Posts: 2342
    • View Profile
    • http://
[solved] Can't Boot Into Single User Mode.
« Reply #1 on: November 24, 2008, 09:24:42 pm »
I'd suggest you try redownloading all of the files (install, backup, everything) and then try the whole process over again. If I had to guess which file was the issue, I'd guess it was the updater.sh or tools.tar, but I don't know for sure.

You might also want to reformat your card (as FAT16) if it's feasible.

Hope that gets your Z back into a working state.
SL-C750- pdaXrom beta 1 (mostly unused)
Current distro: Gentoo

speculatrix

  • Administrator
  • Hero Member
  • *****
  • Posts: 3707
    • View Profile
[solved] Can't Boot Into Single User Mode.
« Reply #2 on: November 25, 2008, 06:27:22 pm »
note for others: there's also a D+M combination too. I think it's all in the wiki!
Gemini 4G/Wi-Fi owner, formerly zaurus C3100 and 860 owner; also owner of an HTC Doubleshot, a Zaurus-like phone.

m_kylli

  • Newbie
  • *
  • Posts: 2
    • View Profile
[solved] Can't Boot Into Single User Mode.
« Reply #3 on: November 25, 2008, 06:41:27 pm »
In this case it seems as if the systc320.dbk was at fault. The copy on the SD-card corrupt or something.
When I deleted it, added it again and reflashed it the problem was gone.

It seems that a corrupt nand backup can cause some really odd problems.