flash70
-
Content Count
3 -
Joined
-
Last visited
Posts posted by flash70
-
-
Thanks for your answer.
As I mentioned, this is part of a bigger issue...
I got Lego Dimensions and wanted to use it with my console but it won't recognize the Toy Pad. I saw some discussions where people solved this by upgrading the kernel.
When I tried upgrading the kernel remotely using the updserver feature of DashLaunch, it got to the point of flashing the console and that happened:
------ flashing console ------ sending flash data to console... file sent OK, awaiting result...timeout waiting for data, 0 failed!
So I thought maybe a DashLaunch upgrade will solve this, but now I see it might be a HW problem. Is there a test I can do to verify it's a bad NAND problem?
BTW My console has a corona board and kernel v. 2.0.16747
-
Hi all,
The DashLaunch issue is part of a bigger story, but let's take it one at a time...
I have a slim 360 with RGH. The DashLaunch version is 3.12.
When I run the newest DashLaunch (3.18) from a USB drive it detects the older version and suggest an update, but if I press the update button everything freezes.
I don't know if it's related, but a while back I had a crash of the internal storage space, and it appears on the console as unformatted storage device (any attempt to format it simply fails). I had to re-create the player profiles and use part of the USB HDD as XBOX storage to keep save files, but it holds and the console is usable.
Any ideas what's causing the DashLaunch to freeze? Any other way to update the version?
- 1
DashLaunch 3.18 freezes when choosing "update"
in DashLaunch
Posted
That's weird...
I followed the guide to the letter including all changes required for 4G corona, flashed the nand, no errors, but after reboot the kernel version did not change like nothing happend.
What could be the problem?