Author Topic: Rawflash v4  (Read 39895 times)

Offline tuxuser

  • Member of Free60
  • Administrator
  • User
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 299
    • http://www.libxenon.org
  • Linux Distribution: Debian Squeeze - Backports
  • XeLL Build: XeLL-Reloaded - git~HEAD
Rawflash v4
« on: Oct 21, 2011, 20:48:33 »
A little tool that cOz made. Let's you flash full raw images (16 or 64MB) to your NAND. Started, as usual, via XeLL.

Quote
place "nandflash.bin" on the root of a usb device
start 2stage xell and shut off when prompted (replug power if you changed SMC)
- by default it checks blocks before writing, and will NOT overwrite or erase any block with ecc/other issues (perfect for *** images with auto remaps)

small change to libxenon was required to silence non-error messages

tested on falcon, trinity and jasper 256

v4: fix page offsets for bad block checks on big blocks (fixes problems when nandmu is present)
v3: re-re-refix bad block skipping so it skips it in both the dump and flash instead of just in the dump
v2: add big block support
v1: initial version
« Last Edit: Dec 12, 2011, 15:38:44 by tuxuser »
I have no idea what I am doing but atleast I am trying

nitram

  • Guest
Re: Rawflash v2
« Reply #1 on: Oct 21, 2011, 21:01:01 »
Thanks tux.

spandaman

  • Guest
Rawflash v2
« Reply #2 on: Oct 22, 2011, 09:57:50 »
Sweet, thanks :)


Sent from my iPhone using Tapatalk

Offline mjet

  • User
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 2
Re: Rawflash v2
« Reply #3 on: Oct 22, 2011, 15:17:47 »
hi!
I have a Slim Model (Trinity)
I used this tool, but i got following info:
---------------------------------------------------
block 0xc1 seems bad, status 0x0000210
block 0x1bf seems bad, status 0x0000210
---------------------------------------------------

After this, fans stayed very noises...dashboard is not loading, but xell loaded no problems.
Please, help me!
P.s. I dumped my original nand few times and all was very well - nandpro not indicated any bads or others errors.
Also I write this original nand in my console via NandPro - works great! No errors...
« Last Edit: Oct 22, 2011, 15:20:04 by mjet »

chapas

  • Guest
Re: Rawflash v2
« Reply #4 on: Oct 24, 2011, 16:44:57 »
Hi,
putted the .elf file on a Fat32 formatted USB pen, but xell didn't find it, so i tried a CD-RW and it started rawflash from CD, but then nothing happens and stay's stuck on screen like this:



I'm with on a SLIM 4GB, any suggestion?

Thanks in advance,
Chapas

rikimaer

  • Guest
Re: Rawflash v2
« Reply #5 on: Oct 26, 2011, 00:29:18 »
Hi,
putted the .elf file on a Fat32 formatted USB pen, but xell didn't find it, so i tried a CD-RW and it started rawflash from CD, but then nothing happens and stay's stuck on screen like this:



I'm with on a SLIM 4GB, any suggestion?

Thanks in advance,
Chapas

Same oribken gere aso with Slim mobo , but on Falcon mobo worked like a charm!!

Offline Razkar

  • Team
  • User
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 2
  • Posts: 16
Re: Rawflash v3
« Reply #6 on: Oct 26, 2011, 13:30:17 »
V3 is out :)
First port updated ;)

glaze83

  • Guest
Re: Rawflash v3
« Reply #7 on: Nov 01, 2011, 04:01:11 »
There's an issue with samsung nands it would appear -- it fails on everyblock.

Tried with two 512 jaspers.

Was successful on a 512 jasper with a hynix nand

Offline k0mpresd

  • User
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 1
Re: Rawflash v3
« Reply #8 on: Nov 04, 2011, 04:57:41 »
There's an issue with samsung nands it would appear -- it fails on everyblock.

Tried with two 512 jaspers.

Was successful on a 512 jasper with a hynix nand

i had the opposite problem. i went to flash a *** image on to a hynix big block and the program said error on every block. reflashing now with nandpro.
edit: tried again on the same console and it flashed ok. must just be a bug.
« Last Edit: Nov 04, 2011, 05:32:06 by k0mpresd »

Valerie

  • Guest
Re: Rawflash v3
« Reply #9 on: Nov 17, 2011, 23:49:12 »
I am also getting the black screen on a program that I'm working on. I'm thinking that there must be a bug somewhere, but I have not been able to locate it. Has anyone been able to locate the issue? At first I thought that maybe it was just an issue with my xbox, and actually came really close to running down to hhgregg to see if I could pick up a new one. Fortunately I didn't do that since it seems that I am not the only one having this issue. I will appreciate any help I can get with this, thank you.
« Last Edit: Nov 26, 2011, 01:48:37 by Valerie »

Offline tuxuser

  • Member of Free60
  • Administrator
  • User
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 299
    • http://www.libxenon.org
  • Linux Distribution: Debian Squeeze - Backports
  • XeLL Build: XeLL-Reloaded - git~HEAD
Re: Rawflash v4
« Reply #10 on: Dec 12, 2011, 15:39:36 »
Updated first post with rawflash v4, eliminates the bug with big block consoles (Internal NAND MemoryUnit)
I have no idea what I am doing but atleast I am trying

Offline c01eman.360

  • User
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 9
Re: Rawflash v4
« Reply #11 on: Dec 12, 2011, 16:14:29 »
 Y Thanks

turnerl

  • Guest
Re: Rawflash v4
« Reply #12 on: Dec 13, 2011, 00:21:01 »
Amazing tux !!! thanks my current JTAG has bad blocks remapped was a biatch injecting the bad blocks back into flash every update, now being able to flash diectly to my badblock nand and have it not touch the bad blocks is a dream come true !

Thanks Again !


turnerl

  • Guest
Re: Rawflash v4
« Reply #13 on: Dec 13, 2011, 00:41:40 »
sorry tux or anyone quick question I'm running an original JTAG with normal xell reloaded, can I use this or does it only run on that Xell '2Stages'?

Thanks in advance

Offline tuxuser

  • Member of Free60
  • Administrator
  • User
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 299
    • http://www.libxenon.org
  • Linux Distribution: Debian Squeeze - Backports
  • XeLL Build: XeLL-Reloaded - git~HEAD
Rawflash v4
« Reply #14 on: Dec 13, 2011, 00:50:01 »
runs from every XeLL, no idea why xbox-scene is spreading such false info...
I have no idea what I am doing but atleast I am trying