Homebrew postLoader4

[masterjakeway]

mine is the dual sub 2.0 +3.0

 

[stfour]

The one I found is just usb 2.0.

Please install this priibootergui (2.5c)

http://code.google.c...5c.zip&can=2&q=

It will create a file named priibooter.log on sd. Paste it to me.

Thank you

 

[masterjakeway]

Same as b version.
Hope all you did was enable logging. Anyways:

devices_Mount [devmode = 0, tout = 15]
USBDevice_Init: begin
USBDevice_Init: device initialization ok
USBDevice_Init: storage->readSectors(mbr) = 0
USBDevice_Init: partcount 0, parttyp = 0
USBDevice_Init: partcount 0, parttyp = 0
USBDevice_Init: partcount 0, parttyp = 0
USBDevice_Init: partcount 0, parttyp = 0

and then again after loading postloader from the forwarding channel

devices_Mount [devmode = 0, tout = 15]
USBDevice_Init: begin
USBDevice_Init: device initialization ok
USBDevice_Init: storage->readSectors(mbr) = 1
USBDevice_Init: partcount 0, parttyp = 12
USBDevice_Init: storage->readSectors(BootSector) = 1
USBDevice_Init: fat->updating slot 1
USBDevice_Init: partcount 1, parttyp = 0
USBDevice_Init: partcount 1, parttyp = 0
USBDevice_Init: partcount 1, parttyp = 0

Thanks again for all the effort!

 

[stfour]

Hope all you did was enable logging. Anyways:

Yes, just logging

The result is interesting. On the firs run device is ready but reading of mbr sector fails.

 

[stfour]

Please give a try to 2.5d

http://code.google.com/p/postloader/downloads/detail?name=priibooter.2.5d.zip&can=2&q=

Paste priibooter.log

 

[MassiveRican]

Do you think a good ol' checkdisk with fix errors might do the trick?

 

[stfour]

Do you think a good ol' checkdisk with fix errors might do the trick?

It seems to me that the drive report ready but it isn't really ready, so the "readSectors" fails. Or something like that. I have 5 usb drive and I never experienced this problem (but they are all native usb2). Checkdisk doesn't help as priibooter in this phase is reading a precise sector on disc, it isn't accessing the filesystem.

 

[masterjakeway]

Well, it booted to the main intro screen.
Counted down usb mount to 0, then counted backwards. I let it go to -200 before I gave up and unplugged the Wii.

There was no log file...

I then rebooted to priiloader waited like 10 seconds and booted installed file. And it worked fine like that again...

Wish I could help more then just testing...
I am trying to be as thorough as possible with the reports, lol!

 

[stfour]

Sorry, I can't test this version by myself as I never fall in your situation.

priiboter 2.5e should fix the countdown and I've added a storage->shutdown() when readsector fails

http://code.google.com/p/postloader/downloads/detail?name=priibooter.2.5e.zip&can=2&q=

if also this not work, I'm out of ideas. Maybe we can add an ios reload if it fails before retrying again.

 

[masterjakeway]

devices_Mount [devmode = 0, tout = 15]
USBDevice_Init: begin
USBDevice_Init: device initialization ok
USBDevice_Init: storage->readSectors(mbr) = 0
USBDevice_Init: begin
USBDevice_Init: device initialization failed (timeout)

 

[stfour]

Really the last one

http://code.google.com/p/postloader/downloads/detail?name=priibooter.2.5f.zip&can=2&q=

 

[obcd]

It might not be related to your issues, but in my case, I notice the following behavour:

If I launch a homebrew emulator with a channel forwarder from my usb drive, than that emulator is unable to remount my usb drive.

If I reload the running ios, it can initialise the usb drive fine.

If the emulator is loaded from the sd card, it works without reloading the ios as well.
Team Twizzers also had other problems with the homebrew channel if they didn't reload the ios to keek ahbprot.
For that reason, they changed the behavour in the latest hbc, so that it always reloads the ios before launching the homebrew.

The only occasion reloading an ios is not needed is when you are in neek2o environment.
It takes almost 9 seconds there to reload the ios, so it's better not to reload. Since usb access is handeled by arm code there, the
drive remains mounted when you switch from one application to another.

 

[stfour]

The big problem is that the drive is initialized, but the readSector fails. Very odd... then after a storage->shutdown it seems that the drive come up no more. So I've added another ios reload, that is called only if readSector fails.

 

[masterjakeway]

priibooter screen came up, counted down to -6 and "froze" there

rebooted wii without sd card
same thing but the screen saying can't find postbooter.dol came up then it went back to the priiloader screen with the timer down to -6


BTW: I just tested Wiiflow Mod and CFG USBloader in the priiloader installed file for a check
They both behave the exact same way.
i.e. First boot won't load right.
boot into priiloader and wait 10 seconds and they work fine
boot to system menu and they work fine.
as long as the Wii isn't turned off they continue to return as they should...
So, this isn't really your problem. Although I do appreciate all the effort and help!

 

[obcd]

So, do I understand it right:

Booting from system menu works fine
Booting into priiloader, waiting 10 seconds, and launching postloader trough priibooter works fine.
Powering down the wii, and launching priiloader -> priibooter without delay is giving you hard disk mounting problems.

So, the diiference with the delays in priibooter is probably that it attempts to mount the drive directly, and waits for x seconds when that fails.
Than it tries to mount the drive again....

Maybe, just a delay before starting to mount the drive might work. Maybe you can write a magic word in the area that don't get cleared between boots to find out if the wii was power cycled.

Just a couple of ideas. I don't need to tell stfour how to program. :-) Maybe it was tried that way already?

 

[stfour]

Maybe, just a delay before starting to mount the drive might work. Maybe you can write a magic word in the area that don't get cleared between boots to find out if the wii was power cycled.

I was thinking the same... I will prepare a version with 5 second delay before attempting to init the hdd. I think that priiloader init the usb when you press "reset" to enter in interactive mode, so it will not be the same. Maybe another way can be restart priibooter gui if the readsector fail, so both ios and libogc restart in a clean way. Or again, I can to reload in ios 249... maybe d2x can help

It is ok that 2.5f freeze with sd, as it is mounted before usb, and ios reload is in the wrong place. Anyway masterjakeway has tested without it so we know that ios reload doesn't help.

---

 

[stfour]

little update to priibootergui (2.6)

* better fade in
* added rotating icon during device init
* a little faster
* added homebrew icon (thx joostin)

@[member='masterjakeway']: > you can find a version that will wait about 10 second before init devices... give it a try

 

[masterjakeway]

same deal. waits and says can't find postloader.dol

devices_Mount [devmode = 0, tout = 15]
USBDevice_Init: begin(0)
USBDevice_Init: device initialization ok
USBDevice_Init: storage->readSectors(mbr) = 0

and with the regular 2.6

devices_Mount [devmode = 0, tout = 15]
USBDevice_Init: begin(0)
USBDevice_Init: device initialization ok
USBDevice_Init: storage->readSectors(mbr) = 0

it's the same?

edit: i was thinking...
I swear the readme said I could remove priibooter_gui from the card. Does it need to be in my apps folder at all? or, can it just be the installed file in priiloader?

 

[stfour]

Yes it is the same, but it was waiting 10 second before init.

Tonight the last test... I will prepare a special version that init usb, then spawn priibootergui, hoping that a full reinit of libogc will help.

 

[stfour]

Tonight the last test... I will prepare a special version that init usb, then spawn priibootergui, hoping that a full reinit of libogc will help.

this is the untested frwpriibooter.

http://code.google.c....6.zip&can=2&q=

I wil try it on my wii when I'm back from work... but if you have the time, you can try it.

edit: it doesn't works