Nand read error

Предлагаю сегодня несколько углубиться в тему SSD накопителей, вернее, в работу NAND памяти как таковой. Не секрет, что в процессе ее функционирования возникают ошибки, которые необходимо предотвращать или корректировать таким образом, чтобы не нарушить целостность данных и обеспечить работоспособность устройства в целом. Давайте поговорим про ошибки NAND памяти и методы борьбы с ними, какие бывают, что является причиной возникновений, как с ними борется контроллер.

Классификация ошибок

Принято делить ошибки на два основных вида – постоянные (некорректируемые) и временные (корректируемые). К первым относится главным образом износ ячеек по причине исчерпания их ресурса. Серьезные производители часто указывают гарантированный ресурс накопителя, т. е. максимальный объем данных, который можно записать без возникновения ошибок.

Как часто бывает, эти значения чаще всего имеют мало общего с реальностью, и количество данных, которые действительно можно отправить на тот или иной SSD, существенно больше, чем нам гарантирует производитель. Узнать это можно, если провести тестирование интересующего накопителя. Процесс этот небыстрый, но результаты порой бывают интересными.

Так, на момент написания этой статьи у меня тестируются два накопителя – Crucial BX500 с памятью TLC и A-data SU635, в котором установлены чипы NAND типа QLC, способные хранить 4 бита в одной ячейке.

Но вернемся к сегодняшней теме. Второй класс ошибок (временные) можно подразделить на несколько типов, с которыми предлагаю познакомиться немного подробнее.

Read Disturb Error – ошибки чтения

Как следует из названия, эти ошибки никак не связаны с циклами записи/стирания (P/E) ячеек, а причиной возникновения является операция чтения. Почему? Давайте разберемся.

Кратко напомню, что представляет собой NAND память. В качестве запоминающего элемента ячейки используется транзистор. На данный момент применяется технология изготовления транзисторов с плавающим затвором, который (собственно затвор), и является хранителем заряда, величина коего позволяет определить, какая комбинация бит хранится в ячейке.

Особенностью именно NAND памяти, в отличие от NOR, является организация поблочного доступа к данным, т. е. оперировать отдельными битами/байтами нельзя, можно только считать сразу целый блок данных, произвести там изменения (если требуется) и вернуть этот блок обратно на накопитель.

Для того чтобы определить, какое значение хранится в ячейке, надо измерить уровень заряда, хранящийся в ней. Это пороговое значение напряжения позволит идентифицировать комбинацию бит, которая тут записана. Чтобы выполнить это, на затвор транзистора подается референсное напряжение, что затем позволит измерить пороговое напряжение ячейки.

Напряжение считывания (V_READ) изначально выше максимально возможного порогового напряжения, но оно гораздо ниже напряжения, которое необходимо для перепрограммирования ячейки или ее стирания. Казалось бы, в чем может быть проблема?

А проблема в организации NAND памяти. Т. к. мы оперируем не отдельными битами, а блоками данных, то и считывающее напряжение подается на весь блок, из которого потом другим сигналом выбирается нужная нам страница данных. Что при этом происходит?

После считывания нужной порции данных сигнал чтения снимается, и… ничего не происходит? Почти. Проблема в том, что референсное (опорное) напряжение пусть немного, но влияет на ячейки данных, из которых не производилась выборка, но которые «попали под раздачу» по причине того, что находились в том же блоке, что и интересовавшая нас страница. Уровень порогового напряжения изменяется, пусть и на мизерную величину.

Это проблема? После одного чтения нет, и после десяти тоже, и даже после тысячи скорее всего нет. Но все же изменение напряжения в неактивных ячейках неуклонно повышается. Следует отметить, что речь именно о неактивных ячейках на тех страницах, на которые подано опорное напряжение, а чтение из них не производится.

Можно найти результаты исследований, в которых приводится такая цифра – происходит искажение одного бита на каждые 10⁵-10⁶ чтений страницы для NAND памяти типа MLC, изготовленной с использованием 16-нм техпроцесса. Следует помнить, что увеличение разрядности ячеек (TLC, QLC) и дальнейшее утончение техпроцесса увеличивают частоту возникновения Read Disturb Error. Оказывает свое влияние и постепенный износ ячеек.

Кстати, на использовании этого эффекта нежелательного изменения значений в ячейках основана хакерская атака на накопитель, цель которой – заставить его выполнять большое количество операций чтения из одних и тех же блоков данных. Это может привести к искажению информации в блоке именно из-за возникновения ошибки Read Disturb.

Как защититься

Как избавиться от ошибки? Есть как минимум два способа. Первый – ошибка будет исправлена «на лету» при помощи используемых алгоритмов коррекции ошибок ECC. Второй — переписать данные, в которых обнаружена ошибка, в другой блок, а исходный очистить и приготовить к повторному использованию. По сути, выполнить операцию «уборка мусора» в сочетании с механизмом выравнивания износа.

Правда, тут есть своя тонкость. Ресурс ячеек отнюдь не бесконечен. Мало того, довольно скромен. Для NAND TLC принято считать, что нормальное значение — 3 000 циклов записи/стирания, для QLC это значение вообще находится на уровне 1 000. Поэтому часто гонять данные туда-сюда не получится, ибо ячейки будут активно изнашиваться.

В то же время и с ошибками Read Disturb мириться нельзя. Часто контроллеры имеют некое заранее заданное количество операций чтения из одного и того же блока, по достижении которого весь блок принудительно переписывается на новое место с последующей очисткой ранее использовавшегося блока данных. В сочетании с системой коррекции ошибок это позволяет избавиться от возникшей ошибки, и обеспечить равномерное расходование ресурса ячеек NAND.

Program Disturb Error – ошибка при программировании ячейки

Следующая ошибка, которая поддается исправлению — Program Disturb Error, т. е. ошибка, возникающая при программировании ячейки. Выше было упомянуто, что для записи/стирания используется напряжение, заметно большее, чем при чтении. И опять суть проблемы в чем-то схожа с рассмотренной выше.

Отличие лишь в том, что при обновлении информации в ячейке NAND повышенное напряжение за счет имеющихся паразитных емкостных связей между элементами воздействует и на соседние ячейки, что опять-таки может привести к изменению порогового напряжения в них и, как следствие, несанкционированному изменению хранящейся информации.

В данном случае такому нежелательному воздействию подвержены как ячейки из блоков, которые не участвуют в перепрограммировании, так и ячейки, которые располагаются в блоке, выбранном для изменения.

Этот эффект проявляется тем сильнее, чем тоньше техпроцесс, который использовался для изготовления NAND.

Как защититься

Панацеей от этого типа ошибок вновь выступает перенос блока, в котором содержатся поврежденные, но поддающиеся исправлению данные, в другой блок.

Over-Programming Error – ошибка перепрограммирования

Еще один тип корректируемой ошибки – перепрограммирование. Такая ситуация может возникнуть в случае, если при программировании страниц пороговое напряжение в ячейках соседних, находящихся в том же блоке, но не участвующих в операции изменения страниц становится слишком высоким, не соответствующим исходным заданным значениям и не позволяющим провести операцию чтения.

Чаще всего это случается с ячейками, в которых по тем или иным причинам после операции стирания в плавающем затворе транзистора сохраняется слишком высокое исходное напряжение. Такое нередко случается с ячейками, ресурс которых уже почти выработан.

Как защититься

На помощь вновь приходит механизм переноса блока данных в новое место, благо ошибка поддается корректировке силами контроллера.

Retention Error – ошибка удержания заряда

Хранящиеся в накопителе данные склонны к повреждению с течением времени. Связано это с падением уровня напряжения в ячейке, точнее, в плавающем затворе транзистора. Хотя он окружен изолирующим оксидным слоем, все же постепенная утечка электронов через этот слой имеет место.

Чем более изношена ячейка, тем активнее идет утечка заряда через изолирующий слой, который постепенно теряет свои физические свойства. Ускорить процесс искажения записанных в NAND память данных могут продолжительное нахождение ячеек в отключенном состоянии, повышенная температура, тип ячеек (MCL, TLC, QLC), использованный для производства чипа техпроцесс, толщина изолирующего оксидного слоя и т. п.

По поводу четырехбитовых ячеек должен сказать, что я провожу эксперимент с имеющимся у меня накопителем Crucial P1, в котором как раз QLC NAND. Он сейчас заполнен наполовину объема файлами, и теперь он просто лежит в коробочке, где проведет не менее полугода (как минимум до сентября этого года), что позволит проверить, случится ли что-то с информацией на накопителе, который длительное время не включался.

Способность держать заряд – одна из важных характеристик любого накопителя. Хотя предполагается, что большинство из них если и обесточивается, то на сравнительно короткое время (часы, максимум несколько дней), все же хочется быть уверенным в том, что спустя более продолжительный период все данные останутся целыми и невредимыми.

Как защититься

Универсальное решение для корректируемых ошибок – регулярная перезапись данных из одного блока в другой. Этой работой занимается контроллер, и он же следит за ресурсом ячеек.

Механизмы мониторинга и обработки ошибок NAND

Раз возможны ошибки, надо как-то следить за их возникновением и исправлять. Для этого используются несколько технологий и методов.

Error Correction Codes (ECC)

Технология выявления и исправления ошибок в устройствах памяти ECC применяется давно. Используется она, в частности, в модулях RAM, устанавливаемых в сервера, т. е. там, где требования к надежности работы и отсутствию ошибок очень жесткие.

Суть метода заключается в добавлении дополнительных бит к битам данных, что позволяет обнаруживать и корректировать ошибку. Так, к m-битам блока данных добавляется k-бит дополнительной информации, в результате чего блок данных становится равным m+k. Количество дополнительных бит зависит от используемого алгоритма ЕСС.

Такой алгоритм кодирует m+k таким образом, что из всех доступных комбинаций 2⁽^m+^k) только минимальное количество комбинаций соответствует корректным данным. Если изменится бит в данных, то это сразу станет видно, и ошибка может быть исправлена.

Количество дополнительных бит варьируется не только в зависимости от применяемого алгоритма ECC, но и от типа NAND памяти, используемой в накопителе. Так, для SLC требуется меньшего всего дополнительных бит, чем для TLC, и тем более для QLC. Количество также зависит от количества циклов P/E, т. к. ячейки постепенно изнашиваются и вероятность появления ошибки становится выше.

Производители запоминающих устройств, в частности, контроллеров для них, могут использовать различные алгоритмы ECC. Наиболее распространение получили алгоритмы на базе кода Хэмминга, кода Рида-Соломона, низкоплотностный код (Low Density Parity Codes — LDPC) и ряд других.

Например, код Хэмминга способен определять ошибки в двух битах и корректировать один бит, что делает его пригодным для использования с SLC NAND, где потребуется всего один дополнительный проверочный бит.

Wear Leveling – выравнивание износа ячеек

Операции записи в NAND память не проходя бесследно и являются основной причиной износа ячеек. Для того, чтоб максимально продлить жизнь памяти, используется механизм выравнивания износа. Его смысл в том, чтобы не допускать ситуации, когда в одних блоках NAND содержатся редко изменяемые данные, а в других блоках обновление информации происходит часто.

Wear Leveling и призвана обеспечить равномерное использование всего объема памяти. Контроллер следит за количеством циклов записи в ячейки и стремится, чтобы количество циклов записи/стирания (P/E) было примерно одинаковым у всех блоков. Различают два метода выравнивания износа:

Динамический – для равномерного распределения циклов P/E используется весь доступный свободный объем накопителя, не затрагиваются «холодные» данные, т. е. те, которые не обновляются.
Статический – выравнивание износа производится на всем объеме накопителя, включая неизменяемые данные.

Второй метод обеспечивает более равномерный износ и, как следствие, большую продолжительность жизни накопителя, но требует больших вычислительных ресурсов и затрачивает больше времени на манипулирование блоками данных внутри накопителя.

Bad-Block Management

Назначение этого механизма знакомо по обычным жестким дискам, где также ведется мониторинг состояния поверхности пластин и вышедшие из строя дорожки отправляются в «плохие» (Bad) и заменяются новыми из резервной области.

В SSD принцип действия тот же. Недопустима ситуация, когда целостность данных нарушается из-за того, что информация была записана в блок, который уже не в состоянии обеспечить полноценную работу. Для этого ведется мониторинг состояния блоков данных, и при получении ошибки, не позволяющей в дальнейшем использовать этот блок, он помечается плохим и прописывается в таблице плохих блоков.

Эта таблица присутствует всегда, т. к. уже на этапе производства или тестирования чипа могут появится плохие блоки. Причем, тестирование на заводе производится в более жестких условиях, чем при обычной работе. Вполне возможна ситуация, когда изначально помеченный как плохой, блок может вполне проходить проверки при повседневном использовании накопителя. Тем не менее, следует избегать использования таких блоков.

Прежде, чем записывать информацию в блок, необходимо проверить, что он отсутствует в таблице плохих блоков. Количество поврежденных блоков растет по мере использования накопителя из-за износа ячеек. Если в ответ на выполнение операции стирания или программирования страницы получено сообщение об ошибке, то блок должен быть помечен как плохой и занесен в соответствующую таблицу.

Выход из строя одной страницы блока не означает, что другие страницы также проблемные, но тем не менее, весь блок идет «в утиль». После занесения блока в таблицу плохих блоков он больше не используется.

Источник

Diman4eg
Пользователь

Регистрация:

05.05.2015

Сообщения:

90

Симпатии:

4

Всем привет, пытаюсь считать NAND консоли Xbox 360 S, плата Corona v3
Читаю программатором Matrix SPI Nand Flasher
Программу использую J-Runner v0.3 Beta (7)
Проблема в том, что при считывании нанда всегда выводятся ошибки чтения одних и тех же блоков памяти. Сама консоль включается и функционирует
В чём может быть проблема? Провода от программатора укоротил как смог, эти ошибки прям сильно напрягают, и использовать такие дампы нанда я немножко ссу…
Прикладываю логи J-Runner’a

===================================================
5 сентября 2018 г. 15:00:53

J-Runner v0.3 Beta (7) Started

WARNING! — Your selected working directory already contains files!
You can view these files by using ‘Show Working Folder’ Button

Connection Error
Checking Files
Connection Error
Version: 01
Flash Config: 0x00043000
00043000
Corona
CB Version: 13181
Corona
Reading Nand to C:UsersAdminDesktopJ-Runnernanddump1.bin
Reading Nand
Error: 25C reading block 35
Error: 250 reading block AD
Error: 250 reading block B4
Error: 250 reading block 2F8
Error: 250 reading block 3CB
Done!
in 6:39 min:sec

Initializing nanddump1.bin..
Reading Nand to C:UsersAdminDesktopJ-Runnernanddump2.bin
Corona
Reading Nand
Glitch2 Selected
Nand Initialization Finished
Error: 25C reading block 35
Error: 250 reading block AD
Error: 250 reading block B4
Error: 250 reading block 2F8
Error: 250 reading block 3CB
Done!
in 6:41 min:sec

Comparing…
Bad Block ID 0035 Found @ 0x03FF [Offset: 0x107BE00]
Bad Block ID 00AD Found @ 0x03FE [Offset: 0x1077C00]
Bad Block ID 00B4 Found @ 0x03FD [Offset: 0x1073A00]
Bad Block ID 02F8 Found @ 0x03FC [Offset: 0x106F800]
Bad Block ID 03CB Found @ 0x03FB [Offset: 0x106B600]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0035 [Offset: 0xDAA00]
Block ID 03FE [Offset: 0x1077C00] remapped to Block ID 00AD [Offset: 0x2C9A00]
Block ID 03FD [Offset: 0x1073A00] remapped to Block ID 00B4 [Offset: 0x2E6800]
Block ID 03FC [Offset: 0x106F800] remapped to Block ID 02F8 [Offset: 0xC3F000]
Block ID 03FB [Offset: 0x106B600] remapped to Block ID 03CB [Offset: 0xFA5600]
Bad Blocks Remapped
Bad Block ID 0035 Found @ 0x03FF [Offset: 0x107BE00]
Bad Block ID 00AD Found @ 0x03FE [Offset: 0x1077C00]
Bad Block ID 00B4 Found @ 0x03FD [Offset: 0x1073A00]
Bad Block ID 02F8 Found @ 0x03FC [Offset: 0x106F800]
Bad Block ID 03CB Found @ 0x03FB [Offset: 0x106B600]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0035 [Offset: 0xDAA00]
Block ID 03FE [Offset: 0x1077C00] remapped to Block ID 00AD [Offset: 0x2C9A00]
Block ID 03FD [Offset: 0x1073A00] remapped to Block ID 00B4 [Offset: 0x2E6800]
Block ID 03FC [Offset: 0x106F800] remapped to Block ID 02F8 [Offset: 0xC3F000]
Block ID 03FB [Offset: 0x106B600] remapped to Block ID 03CB [Offset: 0xFA5600]
Bad Blocks Remapped
Nands are the same

Вроде, он ремапит повреждённые участки, но изменения в файлы не записываются.
При повторном сравнении он снова находит ошибки и ремапит. Не знаю уже, что делать.
voldemaro
Пользователь

Регистрация:

28.05.2011

Сообщения:

2.545

Симпатии:

370

Все норм,продолжай дальше

Отправлено с моего m2 note через Tapatalk
Lapa
Пользователь

Регистрация:

22.12.2015

Сообщения:

580

Симпатии:

99

Всё ок. Он их заремапит, когда ты создашь фрибутный нанд и зашьешь
Diman4eg
Пользователь

Регистрация:

05.05.2015

Сообщения:

90

Симпатии:

4

Окей, но появилась еще проблема — в консоль не заливается ECC.
В лог пишет следующее:

ECC created
Version: 01
Flash Config: 0x00043000
Writing Nand
image_00000000.ecc
Failed to write 0x0 block
Failed to write 0x1 block
Failed to write 0x2 block
Failed to write 0x3 block
Failed to write 0x4 block
Failed to write 0x5 block
Failed to write 0x6 block
Failed to write 0x7 block
Failed to write 0x8 block
Failed to write 0x9 block
Failed to write 0xA block
Failed to write 0xB block
Failed to write 0xC block
Failed to write 0xD block
Failed to write 0xE block
Failed to write 0xF block
Failed to write 0x10 block
Failed to write 0x11 block
Failed to write 0x12 block
Failed to write 0x13 block
Failed to write 0x14 block
Failed to write 0x15 block
Failed to write 0x16 block
Failed to write 0x17 block
Failed to write 0x18 block
Failed to write 0x19 block
Failed to write 0x1A block
Failed to write 0x1B block
Failed to write 0x1C block
Failed to write 0x1D block
Failed to write 0x1E block
Failed to write 0x1F block
Failed to write 0x20 block
Failed to write 0x21 block
Failed to write 0x22 block
Failed to write 0x23 block
Failed to write 0x24 block
Failed to write 0x25 block
Failed to write 0x26 block
Failed to write 0x27 block
Failed to write 0x28 block
Failed to write 0x29 block
Failed to write 0x2A block
Failed to write 0x2B block
Failed to write 0x2C block
Failed to write 0x2D block
Failed to write 0x2E block
Failed to write 0x2F block
Failed to write 0x30 block
Failed to write 0x31 block
Failed to write 0x32 block
Failed to write 0x33 block
Failed to write 0x34 block
Failed to write 0x35 block
Failed to write 0x36 block
Failed to write 0x37 block
Failed to write 0x38 block
Failed to write 0x39 block
Failed to write 0x3A block
Failed to write 0x3B block
Failed to write 0x3C block
Failed to write 0x3D block
Failed to write 0x3E block
Failed to write 0x3F block
Failed to write 0x40 block
Failed to write 0x41 block
Failed to write 0x42 block
Failed to write 0x43 block
Failed to write 0x44 block
Failed to write 0x45 block
Failed to write 0x46 block
Failed to write 0x47 block
Failed to write 0x48 block
Failed to write 0x49 block
Failed to write 0x4A block
Failed to write 0x4B block
Failed to write 0x4C block
Failed to write 0x4D block
Failed to write 0x4E block
Failed to write 0x4F block
Done!
in 0:33 min:sec

И после этого фейла плата определяется как Trinity… (Пишет, что версия CB 9188 )
Гуглением ничего не нашёл… Не подскажете, что делать?
З.Ы. при считывании памяти консоли, теперь пишется Header is wrong.
Нанд считывает, но ЕСС создавать теперь отказывается…

Последнее редактирование: 05.09.2018
DDD
Пользователь

Регистрация:

30.10.2012

Сообщения:

3.355

Симпатии:

522

Ты себе на пустом месте создаёшь глупые проблемы.
1)программатор в логе всегда будет выдавать failed, это нормально, продолжай шить.
2)не надо считывать нанд, в который ты залил ecc, он в любом случае будет ругаться header is wrong и показывать, что мамка Тринити.
3)не стоит преждевременно переживать из-за бэд блоков, вот когда не будет грузиться xell, тогда можешь паниковать )) И то, напаял новый нанд, залил туда образ и всё работает.
Тебе нужно сейчас залить оригинальный дамп и сразу же залить есс. Далее включай хбокс и снимай ключ.
Okas43

Регистрация:

18.01.2017

Сообщения:

1.370

Симпатии:

134

использовал бы АвтоГГ — таких граблей бы небыло
timoncrew
Пользователь

Регистрация:

06.03.2017

Сообщения:

789

Симпатии:

179

Если бы сперва читал и поиском пользовался, не было бы таких вопросов. А чем пользоваться разницы нет, я например автоГГ не перевариваю и пользуюсь исключительно раннером.
Lapa
Пользователь

Регистрация:

22.12.2015

Сообщения:

580

Симпатии:

99

Солидарен. АвтоГГ вообще неприятенн
voldemaro
Пользователь

Регистрация:

28.05.2011

Сообщения:

2.545

Симпатии:

370

Ошибки из за матрикс програматора,в реале все заливается и читается

Отправлено с моего m2 note через Tapatalk

Поделиться этой страницей

Источник

Home
Forums
Gaming Platforms
Console Modding Support
Xbox 360 Modding Support and Help Questions

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Thread starter
relo999
Start date
Nov 25, 2017
Views
2,468

I can’t seem to read my nand, sometimes it get’s half way of reading the NAND once only after redoing everything but most of the time it’s just a long list of read errors. At first I though it might have been a soldering issue but even with multiple tries of cleaning the pads and resoldering (even though there seemed to be no short if I trust my multimeter).
The error I get is nearly often 618, if that helps.

Picture of my soldering. (point 2 and 4 aren’t touching, just perspective)

I can’t seem to read my nand, sometimes it get’s half way of reading the NAND once only after redoing everything but most of the time it’s just a long list of read errors. At first I though it might have been a soldering issue but even with multiple tries of cleaning the pads and resoldering (even though there seemed to be no short if I trust my multimeter).
The error I get is nearly often 618, if that helps.

Picture of my soldering. (point 2 and 4 aren’t touching, just perspective)

I’m not sure who told you those were the corresponding colors, but you have it all mixed up.

http://team-xecuter.com/nandx_pics/nandx_wires_phat.jpg

I know, this is my own connector (lost the original one).

Well then the only thing I can really suggest is to simply go through them one by one to see which one is causing the problem.

Well then the only thing I can really suggest is to simply go through them one by one to see which one is causing the problem.

All have solid connections.

color to connector goes blue = 1/mosi, green = 2/ss#, yellow = 3/sck, orange = 4/miso, red = 5/ground, brown = 6/eject, black = 7/xx

Update: Tried booting the 360 normally and it doesn’t power on…

Edit: added the log, also found my only seemingly good read of the NAND (other got saved over…)

The whole log can be summed up to first 2 read went fine, third crapped out after 200. After that point any attempt at a read either failed immediately or after 200 with error 618 and 650.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:01:26 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Done!
in 3:30 min:sec

Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Error: 650 reading block 201
Done!
in 3:30 min:sec

Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump3.bin
Comparing...
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Reading Nand
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
Nands are the same
Error: 650 reading block 201
Error: 604 reading block 24A
Error: 604 reading block 24B
Error: 604 reading block 24D
Error: 61C reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 618 reading block 251
Error: 618 reading block 252
Error: 61C reading block 253
Error: 618 reading block 254
Error: 618 reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 618 reading block 25A
Error: 61C reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 618 reading block 25E
Error: 610 reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 618 reading block 26E
Error: 618 reading block 26F
Error: 618 reading block 270
Error: 618 reading block 271
Error: 618 reading block 272
Error: 618 reading block 273
Error: 618 reading block 274
Error: 618 reading block 275
Error: 618 reading block 276
Error: 618 reading block 277
Error: 618 reading block 278
Error: 618 reading block 279
Error: 618 reading block 27A
Error: 618 reading block 27B
Error: 618 reading block 27C
Error: 618 reading block 27D
Error: 618 reading block 27E
Error: 618 reading block 27F
Error: 618 reading block 280
Error: 618 reading block 281
Error: 618 reading block 282
Error: 618 reading block 283
Error: 618 reading block 284
Error: 618 reading block 285
Error: 618 reading block 286
Error: 618 reading block 287
Error: 618 reading block 288
Error: 618 reading block 289
Error: 618 reading block 28A
Error: 618 reading block 28B
Error: 618 reading block 28C
Error: 618 reading block 28D
Error: 618 reading block 28E
Error: 618 reading block 28F
Error: 618 reading block 290
Error: 618 reading block 291
Error: 618 reading block 292
Error: 618 reading block 293
Error: 618 reading block 294
Error: 618 reading block 295
Error: 618 reading block 296
Error: 618 reading block 297
Error: 618 reading block 298
Error: 618 reading block 299
Error: 618 reading block 29A
Error: 618 reading block 29B
Error: 618 reading block 29C
Error: 618 reading block 29D
Error: 618 reading block 29E
Error: 618 reading block 29F
Error: 618 reading block 2A0
Error: 618 reading block 2A1
Error: 618 reading block 2A2
Error: 618 reading block 2A3
Error: 618 reading block 2A4
Error: 618 reading block 2A5
Error: 618 reading block 2A6
Error: 618 reading block 2A7
Error: 618 reading block 2A8
Error: 618 reading block 2A9
Error: 618 reading block 2AA
Error: 618 reading block 2AB
Error: 618 reading block 2AC
Error: 618 reading block 2AD
Error: 618 reading block 2AE
Error: 618 reading block 2AF
Error: 618 reading block 2B0
Error: 618 reading block 2B1
Error: 618 reading block 2B2
Error: 618 reading block 2B3
Error: 618 reading block 2B4
Error: 618 reading block 2B5
Error: 618 reading block 2B6
Error: 618 reading block 2B7
Error: 618 reading block 2B8
Error: 618 reading block 2B9
Error: 618 reading block 2BA
Error: 618 reading block 2BB
Error: 618 reading block 2BC
Error: 618 reading block 2BD
Error: 618 reading block 2BE
Error: 618 reading block 2BF
Error: 618 reading block 2C0
Error: 618 reading block 2C1
Error: 618 reading block 2C2
Error: 618 reading block 2C3
Error: 618 reading block 2C4
Error: 618 reading block 2C5
Error: 618 reading block 2C6
Error: 610 reading block 2C7
Error: 618 reading block 2C8
Error: 618 reading block 2C9
Error: 618 reading block 2CA
Error: 618 reading block 2CB
Error: 618 reading block 2CC
Error: 618 reading block 2CD
Error: 618 reading block 2CE
Error: 618 reading block 2CF
Error: 618 reading block 2D0
Error: 618 reading block 2D1
Error: 618 reading block 2D2
Error: 618 reading block 2D3
Error: 618 reading block 2D4
Error: 618 reading block 2D5
Error: 618 reading block 2D6
Error: 618 reading block 2D7
Error: 618 reading block 2D8
Error: 618 reading block 2D9
Error: 618 reading block 2DA
Error: 618 reading block 2DB
Error: 618 reading block 2DC
Error: 618 reading block 2DD
Error: 618 reading block 2DE
Error: 618 reading block 2DF
Error: 618 reading block 2E0
Error: 618 reading block 2E1
Error: 618 reading block 2E2
Error: 618 reading block 2E3
Error: 618 reading block 2E4
Error: 618 reading block 2E5
Error: 618 reading block 2E6
Error: 618 reading block 2E7
Error: 618 reading block 2E8
Error: 618 reading block 2E9
Error: 618 reading block 2EA
Error: 618 reading block 2EB
Error: 618 reading block 2EC
Error: 618 reading block 2ED
Error: 618 reading block 2EE
Error: 618 reading block 2EF
Error: 618 reading block 2F0
Error: 618 reading block 2F1
Error: 618 reading block 2F2
Error: 618 reading block 2F3
Error: 618 reading block 2F4
Error: 618 reading block 2F5
Error: 618 reading block 2F6
Error: 618 reading block 2F7
Error: 618 reading block 2F8
Error: 618 reading block 2F9
Error: 618 reading block 2FA
Error: 618 reading block 2FB
Error: 618 reading block 2FC
Error: 618 reading block 2FD
Error: 618 reading block 2FE
Error: 618 reading block 2FF
Error: 618 reading block 300
Error: 618 reading block 301
Error: 618 reading block 302
Error: 618 reading block 303
Error: 618 reading block 304
Error: 618 reading block 305
Error: 618 reading block 306
Error: 618 reading block 307
Error: 610 reading block 308
Error: 618 reading block 309
Error: 618 reading block 30A
Error: 618 reading block 30B
Error: 618 reading block 30C
Error: 618 reading block 30D
Error: 618 reading block 30E
Error: 618 reading block 30F
Error: 618 reading block 310
Error: 61C reading block 311
Error: 618 reading block 312
Error: 61C reading block 313
Error: 618 reading block 314
Error: 618 reading block 315
Error: 618 reading block 316
Error: 618 reading block 317
Error: 618 reading block 318
Error: 618 reading block 319
Error: 618 reading block 31A
Error: 61C reading block 31B
Error: 618 reading block 31C
Error: 618 reading block 31D
Error: 618 reading block 31E
Error: 618 reading block 31F
Error: 618 reading block 320
Error: 618 reading block 321
Error: 618 reading block 322
Error: 618 reading block 323
Error: 618 reading block 324
Error: 618 reading block 325
Error: 618 reading block 326
Error: 618 reading block 327
Error: 618 reading block 328
Error: 618 reading block 329
Error: 618 reading block 32A
Error: 610 reading block 32B
Error: 618 reading block 32C
Error: 618 reading block 32D
Error: 618 reading block 32E
Error: 618 reading block 32F
Error: 610 reading block 330
Error: 618 reading block 331
Error: 618 reading block 332
Error: 618 reading block 333
Error: 618 reading block 334
Error: 618 reading block 335
Error: 618 reading block 336
Error: 618 reading block 337
Error: 610 reading block 338
Error: 618 reading block 339
Error: 618 reading block 33A
Error: 618 reading block 33B
Error: 618 reading block 33C
Error: 618 reading block 33D
Error: 618 reading block 33E
Error: 618 reading block 33F
Error: 61C reading block 340
Error: 618 reading block 341
Error: 618 reading block 342
Error: 61C reading block 343
Error: 618 reading block 344
Error: 61C reading block 345
Error: 610 reading block 346
Error: 618 reading block 347
Error: 61C reading block 348
Error: 618 reading block 349
Error: 618 reading block 34A
Error: 61C reading block 34B
Error: 618 reading block 34C
Error: 618 reading block 34D
Error: 618 reading block 34E
Error: 618 reading block 34F
Error: 618 reading block 350
Error: 618 reading block 351
Error: 618 reading block 352
Error: 618 reading block 353
Error: 618 reading block 354
Error: 610 reading block 355
Error: 618 reading block 356
Error: 618 reading block 357
Error: 618 reading block 358
Error: 618 reading block 359
Error: 618 reading block 35A
Error: 618 reading block 35B
Error: 618 reading block 35C
Error: 610 reading block 35D
Error: 618 reading block 35E
Error: 618 reading block 35F
Error: 618 reading block 360
Error: 618 reading block 361
Error: 618 reading block 362
Error: 618 reading block 363
Error: 618 reading block 364
Error: 618 reading block 365
Error: 618 reading block 366
Error: 618 reading block 367
Error: 618 reading block 368
Error: 618 reading block 369
Error: 618 reading block 36A
Error: 618 reading block 36B
Error: 618 reading block 36C
Error: 618 reading block 36D
Error: 618 reading block 36E
Error: 618 reading block 36F
Error: 618 reading block 370
Error: 618 reading block 371
Error: 618 reading block 372
Error: 618 reading block 373
Error: 618 reading block 374
Error: 618 reading block 375
Error: 618 reading block 376
Error: 618 reading block 377
Error: 618 reading block 378
Error: 618 reading block 379
Error: 618 reading block 37A
Error: 618 reading block 37B
Error: 618 reading block 37C
Error: 618 reading block 37D
Error: 618 reading block 37E
Error: 618 reading block 37F
Error: 61C reading block 380
Error: 618 reading block 381
Error: 610 reading block 382
Error: 618 reading block 383
Error: 618 reading block 384
Error: 618 reading block 385
Error: 618 reading block 386
Error: 618 reading block 387
Error: 618 reading block 388
Error: 618 reading block 389
Error: 618 reading block 38A
Error: 618 reading block 38B
Error: 618 reading block 38C
Error: 618 reading block 38D
Error: 618 reading block 38E
Error: 618 reading block 38F
Error: 618 reading block 390
Error: 618 reading block 391
Error: 618 reading block 392
Error: 618 reading block 393
Error: 618 reading block 394
Error: 618 reading block 395
Error: 618 reading block 396
Error: 618 reading block 397
Error: 618 reading block 398
Error: 618 reading block 399
Error: 618 reading block 39A
Error: 618 reading block 39B
Error: 618 reading block 39C
Error: 618 reading block 39D
Error: 618 reading block 39E
Error: 618 reading block 39F
Error: 618 reading block 3A0
Error: 618 reading block 3A1
Error: 618 reading block 3A2
Error: 618 reading block 3A3
Error: 618 reading block 3A4
Error: 618 reading block 3A5
Error: 618 reading block 3A6
Error: 618 reading block 3A7
Error: 618 reading block 3A8
Error: 61C reading block 3A9
Error: 618 reading block 3AA
Error: 618 reading block 3AB
Error: 618 reading block 3AC
Error: 61C reading block 3AD
Error: 618 reading block 3AE
Error: 618 reading block 3AF
Error: 618 reading block 3B0
Error: 61C reading block 3B1
Error: 618 reading block 3B2
Error: 618 reading block 3B3
Error: 61C reading block 3B4
Error: 618 reading block 3B5
Error: 618 reading block 3B6
Error: 618 reading block 3B7
Error: 618 reading block 3B8
Error: 61C reading block 3B9
Error: 618 reading block 3BA
Error: 618 reading block 3BB
Error: 61C reading block 3BC
Error: 618 reading block 3BD
Error: 61C reading block 3BE
Error: 618 reading block 3BF
Error: 618 reading block 3C0
Error: 618 reading block 3C1
Error: 618 reading block 3C2
Error: 618 reading block 3C3
Error: 61C reading block 3C4
Error: 618 reading block 3C5
Error: 618 reading block 3C6
Error: 618 reading block 3C7
Error: 61C reading block 3C8
Error: 618 reading block 3C9
Error: 618 reading block 3CA
Error: 618 reading block 3CB
Error: 618 reading block 3CC
Error: 618 reading block 3CD
Error: 61C reading block 3CE
Error: 618 reading block 3CF
Error: 610 reading block 3D0
Error: 61C reading block 3D1
Error: 618 reading block 3D2
Error: 61C reading block 3D3
Error: 610 reading block 3D6
Error: 610 reading block 3D7
Error: 610 reading block 3D8
Error: 61C reading block 3D9
Error: 618 reading block 3DA
Error: 61C reading block 3DB
Error: 618 reading block 3DE
Error: 610 reading block 3DF
Error: 618 reading block 3F7
Error: 618 reading block 3FF
Done!
in 4:26 min:sec

Comparing...
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
0x0249
0x024A
0x024B
0x024D
0x024E
0x024F
0x0250
0x0251
0x0252
0x0253
0x0254
0x0255
0x0256
0x0257
0x0258
0x0259
0x025A
0x025B
0x025C
0x025D
0x025E
0x026A
0x026B
0x026C
0x026D
0x026E
0x026F
0x0270
0x0271
0x0272
0x0273
0x0274
0x0275
0x0276
0x0277
0x0278
0x0279
0x027A
0x027B
0x027C
0x027D
0x027E
0x027F
0x0280
0x0281
0x0282
0x0283
0x0284
0x0285
0x0286
0x0287
0x0288
0x0289
0x028A
0x028B
0x028C
0x028D
0x028E
0x028F
0x0290
0x0291
0x0292
0x0293
0x0294
0x0295
0x0296
0x0297
0x0298
0x0299
0x029A
0x029B
0x029C
0x029D
0x029E
0x029F
0x02A0
0x02A1
0x02A2
0x02A3
0x02A4
0x02A5
0x02A6
0x02A7
0x02A8
0x02A9
0x02AA
0x02AB
0x02AC
0x02AD
0x02AE
0x02AF
0x02B0
0x02B1
0x02B2
0x02B3
0x02B4
0x02B5
0x02B6
0x02B7
0x02B8
0x02B9
0x02BA
0x02BB
0x02BC
0x02BD
0x02BE
0x02BF
0x02C0
0x02C1
0x02C2
0x02C3
0x02C4
0x02C5
0x02C6
0x02C7
0x02C8
0x02C9
0x02CA
0x02CB
0x02CC
0x02CD
0x02CE
Could not find a part of the path.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:17:06 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:18:14 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Version: 10

Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:19:34 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:22:12 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Falcon Manually Selected

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:27:19 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 604 reading block 22D
Error: 604 reading block 233
Error: 604 reading block 239
Error: 604 reading block 243
Error: 618 reading block 247
Error: 618 reading block 248
Error: 618 reading block 249
Error: 618 reading block 24A
Error: 618 reading block 24B
Error: 618 reading block 24C
Error: 61C reading block 24D
Error: 618 reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 618 reading block 251
Error: 618 reading block 252
Error: 61C reading block 253
Error: 618 reading block 254
Error: 618 reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 618 reading block 25A
Error: 61C reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 618 reading block 25E
Error: 618 reading block 25F
Error: 618 reading block 260
Error: 618 reading block 261
Error: 618 reading block 262
Error: 610 reading block 263
Error: 618 reading block 264
Error: 618 reading block 265
Error: 618 reading block 266
Error: 618 reading block 267
Error: 618 reading block 268
Error: 618 reading block 269
Error: 618 reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 618 reading block 26E
Error: 618 reading block 26F
Error: 618 reading block 270
Error: 618 reading block 271
Error: 618 reading block 272
Error: 618 reading block 273
Error: 618 reading block 274
Error: 618 reading block 275
Error: 618 reading block 276
Error: 618 reading block 277
Error: 618 reading block 278
Error: 618 reading block 279
Error: 618 reading block 27A
Error: 610 reading block 27B
Error: 618 reading block 27C
Error: 618 reading block 27D
Error: 618 reading block 27E
Error: 618 reading block 27F
Error: 618 reading block 280
Error: 618 reading block 281
Error: 618 reading block 282
Error: 618 reading block 283
Error: 618 reading block 284
Error: 618 reading block 285
Error: 618 reading block 286
Error: 618 reading block 287
Error: 618 reading block 288
Error: 618 reading block 289
Error: 618 reading block 28A
Error: 618 reading block 28B
Error: 618 reading block 28C
Error: 618 reading block 28D
Error: 618 reading block 28E
Error: 618 reading block 28F
Error: 618 reading block 290
Error: 618 reading block 291
Error: 618 reading bloc
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:32:55 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Falcon Manually Selected
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:38:49 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 604 reading block 210
Error: 61C reading block 211
Error: 61C reading block 212
Error: 618 reading block 213
Error: 618 reading block 214
Error: 610 reading block 215
Error: 618 reading block 216
Error: 618 reading block 217
Error: 61C reading block 218
Error: 618 reading block 219
Error: 618 reading block 21A
Error: 618 reading block 21B
Error: 618 reading block 21C
Error: 618 reading block 21D
Error: 618 reading block 21E
Error: 618 reading block 21F
Error: 618 reading block 220
Error: 618 reading block 221
Error: 618 reading block 222
Error: 618 reading block 223
Error: 610 reading block 22A
Error: 61C reading block 22E
Error: 610 reading block 22F
Error: 618 reading block 230
Error: 618 reading block 231
Error: 604 reading block 240
Error: 618 reading block 241
Error: 618 reading block 242
Error: 61C reading block 243
Error: 610 reading block 244
Error: 61C reading block 245
Error: 618 reading block 246
Error: 618 reading block 247
Error: 618 reading block 248
Error: 61C reading block 249
Error: 618 reading block 24A
Error: 618 reading block 24B
Error: 618 reading block 24C
Error: 61C reading block 24D
Error: 618 reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 618 reading block 251
Error: 61C reading block 252
Error: 61C reading block 253
Error: 618 reading block 254
Error: 618 reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 618 reading block 25A
Error: 61C reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 618 reading block 25E
Error: 618 reading block 25F
Error: 618 reading block 260
Error: 618 reading block 261
Error: 618 reading block 262
Error: 610 reading block 263
Error: 618 reading block 264
Error: 618 reading block 265
Error: 618 reading block 266
Error: 618 reading block 267
Error: 618 reading block 268
Error: 61C reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 618 reading block 26E
Error: 618 reading block 26F
Error: 618 reading block 270
Error: 618 reading block 271
Error: 618 reading block 272
Error: 618 reading block 273
Error: 618 reading block 274
Error: 618 reading block 275
Error: 618 reading block 276
Error: 618 reading block 277
Error: 618 reading block 278
Error: 618 reading block 279
Error: 618 reading block 27A
Error: 618 reading block 27B
Error: 618 reading block 27C
Error: 618 reading block 27D
Error: 618 reading block 27E
Error: 618 reading block 27F
Error: 610 reading block 280
Error: 618 reading block 281
Error: 618 reading block 282
Error: 618 reading block 283
Error: 618 reading block 284
Error: 618 reading block 285
Error: 618 reading block 286
Error: 618 reading block 287
Error: 618 reading block 288
Error: 618 reading block 289
Error: 618 reading block 28A
Error: 618 reading block 28B
Error: 618 reading block 28C
Error: 618 reading block 28D
Error: 618 reading block 28E
Error: 618 reading block 28F
Error: 618 reading block 290
Error: 618 reading block 291
Error: 618 reading block 292
Error: 618 reading block 293
Error: 610 reading block 294
Error: 618 reading block 295
Error: 618 reading block 296
Error: 618 reading block 297
Error: 618 reading block 298
Error: 618 reading block 299
Error: 618 reading block 29A
Error: 618 reading block 29B
Error: 610 reading block 29C
Error: 618 reading block 29D
Error: 618 reading block 29E
Error: 618 reading block 29F
Error: 61C reading block 2A0
Error: 618 reading block 2A1
Error: 618 reading block 2A2
Error: 618 reading block 2A3
Error: 618 reading block 2A4
Error: 618 reading block 2A5
Error: 618 reading block 2A6
Error: 618 reading block 2A7
Error: 618 reading block 2A8
Error: 610 reading block 2A9
Error: 618 reading block 2AA
Error: 618 reading block 2AB
Error: 618 reading block 2AC
Error: 618 reading block 2AD
Error: 618 reading block 2AE
Error: 618 reading block 2AF
Error: 618 reading block 2B0
Error: 610 reading block 2B1
Error: 618 reading block 2B2
Error: 618 reading block 2B3
Error: 618 reading block 2B4
Error: 618 reading block 2B5
Error: 618 reading block 2B6
Error: 618 reading block 2B7
Error: 618 reading block 2B8
Error: 618 reading block 2B9
Error: 618 reading block 2BA
Error: 618 reading block 2BB
Error: 618 reading block 2BC
Error: 618 reading block 2BD
Error: 618 reading block 2BE
Error: 618 reading block 2BF
Error: 618 reading block 2C0
Error: 618 reading block 2C1
Error: 618 reading block 2C2
Error: 618 reading block 2C3
Error: 618 reading block 2C4
Error: 618 reading block 2C5
Error: 618 reading block 2C6
Error: 610 reading block 2C7
Error: 610 reading block 2C8
Error: 618 reading block 2C9
Error: 618 reading block 2CA
Error: 618 reading block 2CB
Error: 618 reading block 2CC
Error: 618 reading block 2CD
Error: 618 reading block 2CE
Error: 618 reading block 2CF
Error: 618 reading block 2D0
Error: 618 reading block 2D1
Error: 618 reading block 2D2
Error: 618 reading block 2D3
Error: 618 reading block 2D4
Error: 618 reading block 2D5
Error: 618 reading block 2D6
Error: 618 reading block 2D7
Error: 618 reading block 2D8
Error: 618 reading block 2D9
Error: 618 reading block 2DA
Error: 618 reading block 2DB
Error: 618 reading block 2DC
Error: 618 reading block 2DD
Error: 618 reading block 2DE
Error: 618 reading block 2DF
Error: 618 reading block 2E0
Error: 618 reading block 2E1
Error: 618 reading block 2E2
Error: 618 reading block 2E3
Error: 618 reading block 2E4
Error: 618 reading block 2E5
Error: 618 reading block 2E6
Error: 618 reading block 2E7
Error: 618 reading block 2E8
Error: 618 reading block 2E9
Error: 618 reading block 2EA
Error: 618 reading block 2EB
Error: 618 reading block 2EC
Error: 618 reading block 2ED
Error: 618 reading block 2EE
Error: 618 reading block 2EF
Error: 618 reading block 2F0
Error: 618 reading block 2F1
Error: 618 reading block 2F2
Error: 618 reading block 2F3
Error: 618 reading block 2F4
Error: 618 reading block 2F5
Error: 618 reading block 2F6
Error: 618 reading block 2F7
Error: 618 reading block 2F8
Error: 618 reading block 2F9
Error: 618 reading block 2FA
Error: 000 reading block 2FB
Error: 000 reading block 2FC
Error: 610 reading block 2FD
Error: 618 reading block 2FE
Error: 618 reading block 2FF
Error: 610 reading block 300
Error: 618 reading block 301
Done!
in 5:49 min:sec

Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump2.bin
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:47:28 AM

J-Runner v0.3 Beta (5) Started


Version: 10
Flash Config: 0x00000000
Can not Continue

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 7:48:24 AM

J-Runner v0.3 Beta (5) Started


Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 604 reading block 20E
Error: 604 reading block 213
Error: 608 reading block 214
Error: 618 reading block 215
Error: 618 reading block 216
Error: 618 reading block 217
Error: 618 reading block 218
Error: 618 reading block 219
Error: 618 reading block 21A
Error: 618 reading block 21B
Error: 618 reading block 21C
Error: 614 reading block 21D
Error: 618 reading block 21E
Error: 618 reading block 21F
Error: 618 reading block 220
Error: 618 reading block 221
Error: 618 reading block 222
Error: 61C reading block 223
Error: 618 reading block 224
Error: 610 reading block 225
Error: 618 reading block 226
Error: 618 reading block 227
Error: 618 reading block 228
Error: 618 reading block 229
Error: 618 reading block 22A
Error: 618 reading block 22B
Error: 618 reading block 22C
Error: 618 reading block 22D
Error: 618 reading block 22E
Error: 610 reading block 22F
Error: 618 reading block 230
Error: 618 reading block 231
Error: 618 reading block 232
Error: 618 reading block 233
Error: 618 reading block 234
Error: 618 reading block 235
Error: 61C reading block 236
Error: 618 reading block 237
Error: 618 reading block 238
Error: 618 reading block 239
Error: 618 reading block 23A
Error: 61C reading block 23B
Error: 618 reading block 23C
Error: 618 reading block 23D
Error: 618 reading block 23E
Error: 618 reading block 23F
Error: 618 reading block 240
Error: 618 reading block 241
Error: 618 reading block 242
Error: 610 reading block 243
Error: 618 reading block 244
Error: 618 reading block 245
Error: 618 reading block 246
Error: 610 reading block 247
Error: 618 reading block 248
Error: 618 reading block 249
Error: 618 reading block 24A
Error: 61C reading block 24B
Error: 618 reading block 24C
Error: 61C reading block 24D
Error: 618 reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 61C reading block 251
Error: 618 reading block 252
Error: 614 reading block 253
Error: 610 reading block 254
Error: 618 reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 610 reading block 25A
Error: 618 reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 618 reading block 25E
Error: 618 reading block 25F
Error: 618 reading block 260
Error: 618 reading block 261
Error: 610 reading block 262
Error: 618 reading block 263
Error: 618 reading block 264
Error: 618 reading block 265
Error: 618 reading block 266
Error: 618 reading block 267
Error: 618 reading block 268
Error: 618 reading block 269
Error: 618 reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 610 reading block 26E
Error: 618 reading block 26F
Error: 618 reading block 270
Error: 618 reading block 271
Error: 618 reading block 272
Error: 618 reading block 273
Error: 618 reading block 274
Error: 618 reading block 275
Error: 618 reading block 276
Error: 618 reading block 277
Error: 618 reading block 278
Error: 618 reading block 279
Error: 618 reading block 27A
Error: 618 reading block 27B
Error: 618 reading block 27C
Error: 618 reading block 27D
Error: 618 reading block 27E
Error: 618 reading block 27F
Error: 618 reading block 280
Error: 610 reading block 281
Error: 618 reading block 282
Error: 618 reading block 283
Error: 618 reading block 284
Error: 618 reading block 285
Error: 618 reading block 286
Error: 618 reading block 287
Error: 618 reading block 288
Error: 618 reading block 289
Error: 618 reading block 28A
Error: 618 reading block 28B
Error: 618 reading block 28C
Error: 618 reading block 28D
Error: 610 reading block 28E
Error: 618 reading block 28F
Error: 618 reading block 290
Error: 618 reading block 291
Error: 618 reading block 292
Error: 618 reading block 293
Error: 618 reading block 294
Error: 618 reading block 295
Error: 610 reading block 296
Error: 618 reading block 297
Error: 618 reading block 298
Error: 618 reading block 299
Error: 618 reading block 29A
Error: 618 reading block 29B
Error: 618 reading block 29C
Error: 618 reading block 29D
Error: 610 reading block 29E
Error: 618 reading block 29F
Error: 618 reading block 2A0
Error: 618 reading block 2A1
Error: 618 reading block 2A2
Error: 610 reading block 2A3
Error: 618 reading block 2A4
Error: 618 reading block 2A5
Error: 618 reading block 2A6
Error: 618 reading block 2A7
Error: 618 reading block 2A8
Error: 618 reading block 2A9
Error: 618 reading block 2AA
Error: 618 reading block 2AB
Error: 618 reading block 2AC
Error: 618 reading block 2AD
Error: 618 reading block 2AE
Error: 610 reading block 2AF
Error: 618 reading block 2B0
Error: 618 reading block 2B1
Error: 618 reading block 2B2
Error: 618 reading block 2B3
Error: 618 reading block 2B4
Error: 618 reading block 2B5
Error: 618 reading block 2B6
Error: 610 reading block 2B7
Error: 618 reading block 2B8
Error: 618 reading block 2B9
Error: 618 reading block 2BA
Error: 618 reading block 2BB
Error: 618 reading block 2BC
Error: 618 reading block 2BD
Error: 618 reading block 2BE
Error: 610 reading block 2BF
Error: 610 reading block 2C0
Error: 618 reading block 2C1
Error: 618 reading block 2C2
Error: 618 reading block 2C3
Error: 618 reading block 2C4
Error: 618 reading block 2C5
Error: 618 reading block 2C6
Error: 618 reading block 2C7
Error: 618 reading block 2C8
Error: 610 reading block 2C9
Error: 610 reading block 2CA
Error: 618 reading block 2CB
Error: 618 reading block 2CC
Error: 610 reading block 2CD
Error: 618 reading block 2CE
Error: 618 reading block 2CF
Error: 618 reading block 2D0
Error: 610 reading block 2D1
Error: 610 reading block 2D2
Error: 618 reading block 2D3
Error: 618 reading block 2D4
Error: 610 reading block 2D5
Error: 618 reading block 2D6
Error: 618 reading block 2D7
Error: 618 reading block 2D8
Error: 610 reading block 2D9
Error: 610 reading block 2DA
Error: 618 reading block 2DB
Error: 618 reading block 2DC
Error: 610 reading block 2DD
Error: 618 reading block 2DE
Error: 618 reading block 2DF
Error: 618 reading block 2E0
Error: 618 reading block 2E1
Error: 618 reading block 2E2
Error: 610 reading block 2E3
Error: 618 reading block 2E4
Error: 610 reading block 2E5
Error: 618 reading block 2E6
Error: 618 reading block 2E7
Error: 618 reading block 2E8
Error: 618 reading block 2E9
Error: 618 reading block 2EA
Error: 618 reading block 2EB
Error: 618 reading block 2EC
Error: 618 reading block 2ED
Error: 618 reading block 2EE
Error: 618 reading block 2EF
Error: 618 reading block 2F0
Error: 618 reading block 2F1
Error: 618 reading block 2F2
Error: 618 reading block 2F3
Error: 618 reading block 2F4
Error: 618 reading block 2F5
Error: 618 reading block 2F6
Error: 618 reading block 2F7
Error: 618 reading block 2F8
Error: 618 reading block 2F9
Error: 618 reading block 2FA
Error: 618 reading block 2FB
Error: 618 reading block 2FC
Error: 618 reading block 2FD
Error: 618 reading block 2FE
Error: 618 reading block 2FF
Error: 618 reading block 300
Error: 610 reading block 301
Error: 618 reading block 302
Error: 618 reading block 303
Error: 618 reading block 304
Error: 618 reading block 305
Error: 618 reading block 306
Error: 618 reading block 307
Error: 618 reading block 308
Error: 618 reading block 309
Error: 618 reading block 30A
Error: 618 reading block 30B
Error: 610 reading block 30C
Error: 618 reading block 30D
Error: 618 reading block 30E
Error: 610 reading block 30F
Error: 618 reading block 310
Error: 618 reading block 311
Error: 618 reading block 312
Error: 618 reading block 313
Error: 610 reading block 314
Error: 618 reading block 315
Error: 618 reading block 316
Error: 610 reading block 317
Error: 618 reading block 318
Error: 618 reading block 319
Error: 618 reading block 31A
Error: 618 reading block 31B
Error: 610 reading block 31C
Error: 618 reading block 31D
Error: 618 reading block 31E
Error: 610 reading block 31F
Error: 618 reading block 320
Error: 618 reading block 321
Error: 618 reading block 322
Error: 618 reading block 323
Error: 618 reading block 324
Error: 618 reading block 325
Error: 618 reading block 326
Error: 618 reading block 327
Error: 618 reading block 328
Error: 618 reading block 329
Error: 618 reading block 32A
Error: 618 reading block 32B
Error: 618 reading block 32C
Error: 618 reading block 32D
Error: 618 reading block 32E
Error: 61C reading block 32F
Error: 618 reading block 330
Error: 618 reading block 331
Error: 618 reading block 332
Error: 618 reading block 333
Error: 618 reading block 334
Error: 618 reading block 335
Error: 618 reading block 336
Error: 61C reading block 337
Error: 618 reading block 338
Error: 618 reading block 339
Error: 618 reading block 33A
Error: 618 reading block 33B
Error: 618 reading block 33C
Error: 618 reading block 33D
Error: 618 reading block 33E
Error: 61C reading block 33F
Error: 618 reading block 340
Error: 618 reading block 341
Error: 618 reading block 342
Error: 61C reading block 343
Error: 618 reading block 344
Error: 618 reading block 345
Error: 618 reading block 346
Error: 618 reading block 347
Error: 618 reading block 348
Error: 610 reading block 349
Error: 618 reading block 34A
Error: 618 reading block 34B
Error: 618 reading block 34C
Error: 618 reading block 34D
Error: 618 reading block 34E
Error: 618 reading block 34F
Error: 618 reading block 350
Error: 610 reading block 351
Error: 618 reading block 352
Error: 618 reading block 353
Error: 618 reading block 354
Error: 618 reading block 355
Error: 618 reading block 356
Error: 618 reading block 357
Error: 618 reading block 358
Error: 610 reading block 359
Error: 618 reading block 35A
Error: 618 reading block 35B
Error: 618 reading block 35C
Error: 618 reading block 35D
Error: 618 reading block 35E
Error: 618 reading block 35F
Error: 618 reading block 360
Error: 618 reading block 361
Error: 618 reading block 362
Error: 618 reading block 363
Error: 618 reading block 364
Error: 618 reading block 365
Error: 618 reading block 366
Error: 618 reading block 367
Error: 618 reading block 368
Error: 618 reading block 369
Error: 618 reading block 36A
Error: 618 reading block 36B
Error: 618 reading block 36C
Error: 618 reading block 36D
Error: 618 reading block 36E
Error: 618 reading block 36F
Error: 618 reading block 370
Error: 618 reading block 371
Error: 618 reading block 372
Error: 618 reading block 373
Error: 618 reading block 374
Error: 618 reading block 375
Error: 618 reading block 376
Error: 618 reading block 377
Error: 618 reading block 378
Error: 618 reading block 379
Error: 618 reading block 37A
Error: 618 reading block 37B
Error: 618 reading block 37C
Error: 618 reading block 37D
Error: 618 reading block 37E
Error: 618 reading block 37F
Error: 61C reading block 380
Error: 618 reading block 381
Error: 618 reading block 382
Error: 618 reading block 383
Error: 618 reading block 384
Error: 618 reading block 385
Error: 618 reading block 386
Error: 618 reading block 387
Error: 618 reading block 388
Error: 618 reading block 389
Error: 610 reading block 38A
Error: 618 reading block 38B
Error: 618 reading block 38C
Error: 618 reading block 38D
Error: 618 reading block 38E
Error: 618 reading block 38F
Error: 618 reading block 390
Error: 618 reading block 391
Error: 610 reading block 392
Error: 618 reading block 393
Error: 618 reading block 394
Error: 618 reading block 395
Error: 618 reading block 396
Error: 618 reading block 397
Error: 618 reading block 398
Error: 618 reading block 399
Error: 610 reading block 39A
Error: 618 reading block 39B
Error: 618 reading block 39C
Error: 618 reading block 39D
Error: 618 reading block 39E
Error: 618 reading block 39F
Error: 618 reading block 3A0
Error: 618 reading block 3A1
Error: 618 reading block 3A2
Error: 618 reading block 3A3
Error: 618 reading block 3A4
Error: 618 reading block 3A5
Done!
in 9:00 min:sec

Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump2.bin
Initializing nanddump1.bin..
Device Not Found.
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
IoTimedOut

IoTimedOut:No more bytes!
01198030
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
IoTimedOut
IoTimedOut:No more bytes!
Version: 10
Flash Config: 0xFFFFFFFF
Error: 615 reading block 0
Error: 618 reading block 1
Error: 711 reading block 2
Error: 311 reading block 3
FFFFFFFF
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x01198030
Error: 615 reading block 0
Error: 619 reading block 1
Error: 619 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Retail Selected
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 792 reading block 2
Error: 30A reading block 3
01198030
CB Version: 0
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 8:16:04 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: E1B reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Jtag Selected
Retail Selected
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0

Bootloader Attached
Bootloader Version: 1.0.5

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 8:25:41 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 8:26:54 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Falcon Manually Selected

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 8:27:34 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 8:50:05 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: .............................................................................................................
Done!
Verifying Flash: .............................................................................................................
 Write Verified!
Restarting Device ...
Finished!

Bootloader Removed.
Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 604 reading block 23A
Error: 604 reading block 23B
Error: 618 reading block 23C
Error: 61C reading block 23D
Error: 618 reading block 23E
Error: 61C reading block 23F
Error: 618 reading block 240
Error: 618 reading block 241
Error: 61C reading block 242
Error: 604 reading block 245
Error: 604 reading block 246
Error: 618 reading block 247
Error: 604 reading block 248
Error: 618 reading block 249
Error: 618 reading block 24A
Error: 61C reading block 24B
Error: 614 reading block 24C
Error: 61C reading block 24D
Error: 618 reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 618 reading block 251
Error: 618 reading block 252
Error: 61C reading block 253
Error: 618 reading block 254
Error: 61C reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 61C reading block 25A
Error: 61C reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 61C reading block 25E
Error: 618 reading block 25F
Error: 618 reading block 260
Error: 618 reading block 261
Error: 618 reading block 262
Error: 610 reading block 263
Error: 618 reading block 264
Error: 618 reading block 265
Error: 618 reading block 266
Error: 618 reading block 267
Error: 618 reading block 268
Error: 618 reading block 269
Error: 618 reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 618 reading block 26E
Error: 618 reading block 26F
Error: 618 reading block 270
Error: 618 reading block 271
Error: 618 reading block 272
Error: 618 reading block 273
Error: 618 reading block 274
Error: 618 reading block 275
Error: 618 reading block 276
Error: 618 reading block 277
Error: 618 reading block 278
Error: 618 reading block 279
Error: E1B reading block 27A
Error: E3A reading block 27B
Error: E1B reading block 27C
Error: 618 reading block 27D
Error: 61C reading block 27E
Error: 618 reading block 27F
Error: 618 reading block 280
Error: 618 reading block 281
Error: 618 reading block 282
Error: F3A reading block 283
Error: F3A reading block 284
Error: F3B reading block 285
Error: F3B reading block 286
Error: 73A reading block 287
Error: F9B reading block 288
Error: E1B reading block 289
Error: 718 reading block 28A
Error: F3A reading block 28B
Error: F1A reading block 28C
Error: E1B reading block 28D
Error: E3A reading block 28E
Error: F1B reading block 28F
Error: 718 reading block 290
Error: 791 reading block 291
Error: F13 reading block 292
Error: 691 reading block 293
Error: F13 reading block 294
Error: F93 reading block 295
Error: 300 reading block 296
Error: 300 reading block 297
Error: 300 reading block 298
Error: 300 reading block 299
Error: 702 reading block 29A
Error: 702 reading block 29B
Error: 300 reading block 29C
Error: 300 reading block 29D
Error: 703 reading block 29E
Error: 300 reading block 29F
Error: 703 reading block 2A0
Error: 300 reading block 2A1
Error: 703 reading block 2A2
Error: 703 reading block 2A3
Error: 702 reading block 2A4
Error: 700 reading block 2A5
Error: 300 reading block 2A6
Error: 300 reading block 2A7
Error: 300 reading block 2A8
Error: 300 reading block 2A9
Error: 340 reading block 2AA
Error: 742 reading block 2AB
Error: 340 reading block 2AC
Error: 740 reading block 2AD
Error: 340 reading block 2AE
Error: 340 reading block 2AF
Error: 340 reading block 2B0
Error: 340 reading block 2B1
Error: 340 reading block 2B2
Error: 340 reading block 2B3
Error: 340 reading block 2B4
Error: 340 reading block 2B5
Error: 340 reading block 2B6
Error: 340 reading block 2B7
Error: 340 reading block 2B8
Error: 340 reading block 2B9
Error: 340 reading block 2BA
Error: 340 reading block 2BB
Error: 340 reading block 2BC
Error: 340 reading block 2BD
Error: 340 reading block 2BE
Error: 340 reading block 2BF
Error: 340 reading block 2C0
Error: 340 reading block 2C1
Error: 340 reading block 2C2
Error: 340 reading block 2C3
Error: 340 reading block 2C4
Error: 340 reading block 2C5
Error: 340 reading block 2C6
Error: 340 reading block 2C7
Error: 340 reading block 2C8
Error: 340 reading block 2C9
Error: 340 reading block 2CA
Error: 340 reading block 2CB
Error: 340 reading block 2CC
Error: 340 reading block 2CD
Error: 340 reading block 2CE
Error: 340 reading block 2CF
Error: 340 reading block 2D0
Error: 340 reading block 2D1
Error: 340 reading block 2D2
Error: 340 reading block 2D3
Error: 340 reading block 2D4
Error: 340 reading block 2D5
Error: 300 reading block 2D6
Error: 340 reading block 2D7
Error: 340 reading block 2D8
Error: 340 reading block 2D9
Error: 340 reading block 2DA
Error: 340 reading block 2DB
Error: 340 reading block 2DC
Error: 340 reading block 2DD
Error: 340 reading block 2DE
Error: 340 reading block 2DF
Error: 340 reading block 2E0
Error: 340 reading block 2E1
Error: 340 reading block 2E2
Error: 340 reading block 2E3
Error: 300 reading block 2E4
Error: 300 reading block 2E5
Error: 300 reading block 2E6
Error: 300 reading block 2E7
Error: 300 reading block 2E8
Error: 300 reading block 2E9
Error: 300 reading block 2EA
Error: 300 reading block 2EB
Error: 300 reading block 2EC
Error: 300 reading block 2ED
Error: 300 reading block 2EE
Error: 300 reading block 2EF
Error: 300 reading block 2F0
Error: 340 reading block 2F1
Error: 300 reading block 2F2
Error: 300 reading block 2F3
Error: 300 reading block 2F4
Error: 300 reading block 2F5
Error: 300 reading block 2F6
Error: 300 reading block 2F7
Error: 300 reading block 2F8
Error: 300 reading block 2F9
Error: 300 reading block 2FA
Error: 300 reading block 2FB
Error: 300 reading block 2FC
Error: 300 reading block 2FD
Error: 340 reading block 2FE
Error: 300 reading block 2FF
Error: 702 reading block 300
Error: 702 reading block 301
Error: 000 reading block 302
Error: 000 reading block 303
Error: 000 reading block 304
Error: 000 reading block 305
Error: 000 reading block 306
Error: 783 reading block 307
Error: 702 reading block 308
Error: 702 reading block 309
Error: 702 reading block 30A
Error: 340 reading block 30B
Error: 340 reading block 30C
Error: 702 reading block 30D
Error: 742 reading block 30E
Error: F83 reading block 30F
Error: 000 reading block 310
Error: 702 reading block 312
Error: 201 reading block 313
Error: 613 reading block 314
Error: 772 reading block 315
Error: 77A reading block 316
Error: 71A reading block 317
Error: 7FB reading block 318
Error: 632 reading block 319
Error: 6BB reading block 31A
Error: 210 reading block 31B
Error: 73A reading block 31C
Error: 700 reading block 31D
Error: 340 reading block 31E
Error: 783 reading block 31F
Error: E82 reading block 320
Error: 300 reading block 321
Error: 300 reading block 322
Error: 300 reading block 323
Error: 380 reading block 324
Error: 700 reading block 325
Error: F00 reading block 326
Error: 700 reading block 327
Error: 680 reading block 328
Error: 300 reading block 329
Error: 000 reading block 32A
Error: 000 reading block 32B
Error: 700 reading block 32C
Error: 602 reading block 32D
Error: 000 reading block 32E
Error: 000 reading block 32F
Error: 611 reading block 332
Error: 300 reading block 333
Error: 300 reading block 334
Error: 780 reading block 335
Error: 680 reading block 336
Error: 300 reading block 337
Error: 73A reading block 338
Error: 311 reading block 339
Error: 7D0 reading block 33A
Error: 711 reading block 33B
Error: 000 reading block 33D
Error: 000 reading block 33E
Error: 000 reading block 33F
Error: 000 reading block 340
Error: 000 reading block 341
Error: 000 reading block 342
Error: 000 reading block 344
Error: 000 reading block 345
Error: 000 reading block 346
Error: 000 reading block 347
Error: 000 reading block 348
Error: 680 reading block 349
Error: 680 reading block 34A
Error: 011 reading block 34B
Error: 680 reading block 34C
Error: 000 reading block 34D
Error: 300 reading block 34E
Error: 700 reading block 34F
Error: 700 reading block 350
Error: 700 reading block 351
Error: 700 reading block 352
Error: 300 reading block 353
Error: 300 reading block 354
Error: 300 reading block 355
Error: 300 reading block 356
Error: 602 reading block 357
Error: 000 reading block 358
Error: 000 reading block 359
Error: 680 reading block 35A
Error: 300 reading block 35B
Error: 000 reading block 35C
Error: 000 reading block 35D
Error: 680 reading block 35E
Error: 000 reading block 35F
Error: 000 reading block 360
Error: 300 reading block 361
Error: 300 reading block 362
Error: 380 reading block 363
Error: 691 reading block 364
Error: 781 reading block 365
Error: 711 reading block 366
Error: 700 reading block 367
Error: 300 reading block 368
Error: 000 reading block 369
Error: 000 reading block 36A
Error: 000 reading block 36B
Error: 000 reading block 36C
Error: 000 reading block 36D
Error: 000 reading block 36E
Error: 000 reading block 370
Error: 000 reading block 371
Error: 000 reading block 372
Error: 680 reading block 373
Error: 611 reading block 374
Error: 000 reading block 375
Error: 000 reading block 376
Error: 000 reading block 377
Error: 011 reading block 378
Error: 000 reading block 379
Error: 000 reading block 37A
Error: 000 reading block 37B
Error: 680 reading block 37C
Error: 000 reading block 37D
Error: 680 reading block 37E
Error: 680 reading block 37F
Error: 000 reading block 380
Error: 301 reading block 381
Error: 300 reading block 382
Error: 000 reading block 383
Error: 300 reading block 384
Error: 391 reading block 385
Error: 011 reading block 386
Error: 000 reading block 387
Error: 000 reading block 388
Error: 000 reading block 389
Error: 000 reading block 38A
Error: 340 reading block 38B
Error: 340 reading block 38C
Error: 300 reading block 38D
Error: 311 reading block 38E
Error: 000 reading block 390
Error: 311 reading block 391
Error: 300 reading block 392
Error: 000 reading block 393
Error: 000 reading block 394
Error: 340 reading block 395
Error: 000 reading block 396
Error: 000 reading block 397
Error: 300 reading block 398
Error: 000 reading block 399
Error: 000 reading block 39A
Error: 300 reading block 39B
Error: 703 reading block 39C
Error: 000 reading block 39D
Error: 300 reading block 39E
Error: 340 reading block 39F
Error: 000 reading block 3A0
Error: 000 reading block 3A1
Error: 680 reading block 3A2
Error: 680 reading block 3A3
Error: 000 reading block 3A4
Error: 000 reading block 3A5
Error: 000 reading block 3A6
Error: 680 reading block 3A7
Error: 711 reading block 3A8
Error: 300 reading block 3A9
Error: 680 reading block 3AB
Error: 680 reading block 3AC
Error: 680 reading block 3AD
Error: 680 reading block 3AE
Error: 300 reading block 3AF
Error: 791 reading block 3B0
Error: 300 reading block 3B1
Error: 780 reading block 3B2
Error: 680 reading block 3B3
Error: 700 reading block 3B4
Error: 780 reading block 3B5
Error: 000 reading block 3B6
Error: 300 reading block 3B7
Error: 300 reading block 3B8
Error: 300 reading block 3B9
Error: 311 reading block 3BA
Error: 300 reading block 3BB
Error: 300 reading block 3BC
Error: 300 reading block 3BD
Error: 380 reading block 3BE
Error: 300 reading block 3BF
Error: 300 reading block 3C0
Error: 300 reading block 3C1
Error: 300 reading block 3C2
Error: 780 reading block 3C3
Error: 000 reading block 3C4
Error: 000 reading block 3C5
Error: 000 reading block 3C6
Error: 000 reading block 3C7
Error: 000 reading block 3C8
Error: 000 reading block 3C9
Error: 000 reading block 3CA
Error: 000 reading block 3CB
Error: 000 reading block 3CC
Error: 601 reading block 3CD
Error: 700 reading block 3D0
Error: 301 reading block 3D1
Error: 301 reading block 3D2
Error: 300 reading block 3D3
Error: 300 reading block 3D4
Error: 780 reading block 3D5
Error: 680 reading block 3D6
Error: 680 reading block 3D7
Error: 680 reading block 3D8
Error: 781 reading block 3D9
Error: 300 reading block 3DA
Error: 000 reading block 3DB
Error: 000 reading block 3DC
Error: 000 reading block 3DD
Error: 000 reading block 3DE
Error: 000 reading block 3DF
Error: 000 reading block 3E0
Error: 000 reading block 3E1
Error: 000 reading block 3E2
Error: 000 reading block 3E3
Error: 000 reading block 3E4
Error: 380 reading block 3E5
Error: 300 reading block 3E6
Error: 702 reading block 3E7
Error: 703 reading block 3E8
Error: F1F reading block 3E9
Error: 702 reading block 3EA
Error: 782 reading block 3EB
Error: 300 reading block 3EC
Error: 281 reading block 3EF
Error: 602 reading block 3F0
Error: 601 reading block 3F4
Error: 603 reading block 3FC
Error: 201 reading block 3FE
Done!
in 9:41 min:sec

Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump2.bin
Initializing nanddump1.bin..
Can not Continue
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Version: 10
Flash Config: 0x01198030
Error: 700 reading block 1
Error: 611 reading block 2
Error: 011 reading block 3
01198030
CB Version: 0
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
Error: 611 reading block 3
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 000 reading block 0
Error: 000 reading block 6
Error: 611 reading block 7
Error: E02 reading block C
Error: 680 reading block 13
Error: 300 reading block 15
Error: 601 reading block 16
Error: 700 reading block 30
Error: E02 reading block 5C
Error: E03 reading block 6F
Error: E02 reading block 73
Error: E02 reading block 76
Error: F02 reading block 77
Error: 700 reading block 78
Error: 700 reading block 79
Error: E02 reading block 7C
Error: F02 reading block 7D
Error: E02 reading block 7E
Error: E02 reading block 7F
Error: E7F reading block 80
Error: 702 reading block 82
Error: 000 reading block 83
Error: 000 reading block 84
Error: 000 reading block 85
Error: 000 reading block 86
Error: 700 reading block 87
Error: 611 reading block 88
Error: 000 reading block 89

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:11:33 AM

J-Runner v0.3 Beta (5) Started


Version: 10
Flash Config: 0x01198030
Error: E00 reading block 0
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: E02 reading block 10
Error: E02 reading block 12
Error: E02 reading block 13
Error: 601 reading block 14
Error: E02 reading block 15
Error: E02 reading block 18
Error: 000 reading block 19
Error: 000 reading block 1D
Error: 000 reading block 1E

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:12:47 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x7FFFFFF8
Error: 602 reading block 3
7FFFFFF8

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:13:04 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: E02 reading block 9
Error: E00 reading block D
Error: 601 reading block 1D
Error: 601 reading block 27
Error: E03 reading block 5E
Error: E02 reading block 5F
Error: E02 reading block 62
Error: F93 reading block 64
Error: 000 reading block 65
IoTimedOut
IoTimedOut:No
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:14:08 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x01198030
Error: E03 reading block 1
Error: 000 reading block 2
Error: 000 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
Error: 000 reading block 0
Error: 300 reading block 1
Error: 300 reading block 2
Error: 300 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 602 reading block 2
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 680 reading block 3
Error: 700 reading block B
Erro
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:21:36 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Version: 10

Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 601 reading block 212
Error: E03 reading block 213
Error: 601 reading block 215
Error: 601 reading block 216
Error: E02 reading block 217
Error: E0A reading block 218
Error: E05 reading block 219
Error: 618 reading block 21A
Error: 618 reading block 21B
Error: E3A reading block 21C
Error: E33 reading block 21D
Error: 618 reading block 21E
Error: E3B reading block 21F
Error: E1B reading block 220
Error: C32 reading block 221
Error: E1A reading block 222
Error: C32 reading block 223
Error: E3B reading block 224
Error: E30 reading block 225
Error: 000 reading block 226
Error: 618 reading block 227
Error: 011 reading block 228
Error: 000 reading block 229
Error: 611 reading block 22A
Error: 000 reading block 22B
Error: 000 reading block 22C
Error: 000 reading block 22D
Error: 000 reading block 22E
Error: 000 reading block 22F
Error: 000 reading block 230
Error: 601 reading block 231
Error: 000 reading block 232
Error: 000 reading block 233
Error: 000 reading block 234
Error: 000 reading block 235
Error: 000 reading block 236
Error: 781 reading block 237
Error: 000 reading block 238
Error: 000 reading block 239
Error: 000 reading block 23A
Error: 380 reading block 23B
Error: 300 reading block 23C
Error: 380 reading block 23D
IoTimedOut
IoTimedOut:No more bytes!
Version: 10
Flash Config: 0xFFFFFFFF
IoTimedOut

IoTimedOut:No more bytes!
FFFFFFFF
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:26:49 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
IoTimedOut
IoTimedOut:No more bytes!
Version: 10
Flash Config: 0x01FFFFFE
Error: 340 reading block 0
Error: 000 reading block 3
01FFFFFE
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x01198030
Error: 000 reading block 0
Error: 000 reading block 2
01198030
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0xFFFFFFFF
IoTimedOut

IoTimedOut:No more bytes!
FFFFFFFF
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:52:56 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:53:25 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x7FFFFFFE
Error: 359 reading block 0
Error: 358 reading block 1
Error: 351 reading block 2
7FFFFFFE
Device Not Found
Device Not Found
Device Not Found

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:54:21 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Device Not Found
Device Not Found
Device Not Found

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:55:30 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Device Not Found

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:55:53 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Device Not Found
Device Not Found
Device Not Found
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 610 reading block E
Error: 300 reading block F
Error: 340 reading block 10
Error: 300 reading block 11
Error: 340 reading block 12
Error: 300 reading block 13
Error: 000
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 9:57:19 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x00000000
Can not Continue

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:04:57 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 650 reading block 201
Error: 604 reading block 242
Error: 604 reading block 244
Error: 61C reading block 245
Error: 618 reading block 246
Error: 610 reading block 247
Error: 618 reading block 248
Error: 618 reading block 249
Error: 610 reading block 24A
Error: 608 reading block 24B
Error: 61C reading block 24C
Error: 61C reading block 24D
Error: 618 reading block 24E
Error: 618 reading block 24F
Error: 618 reading block 250
Error: 618 reading block 251
Error: 618 reading block 252
Error: 618 reading block 253
Error: 618 reading block 254
Error: 618 reading block 255
Error: 618 reading block 256
Error: 618 reading block 257
Error: 618 reading block 258
Error: 618 reading block 259
Error: 610 reading block 25A
Error: 618 reading block 25B
Error: 618 reading block 25C
Error: 618 reading block 25D
Error: 618 reading block 25E
Error: 618 reading block 25F
Error: 618 reading block 260
Error: 618 reading block 261
Error: 618 reading block 262
Error: 618 reading block 263
Error: 618 reading block 264
Error: 618 reading block 265
Error: 618 reading block 266
Error: 618 reading block 267
Error: 618 reading block 268
Error: 618 reading block 269
Error: 618 reading block 26A
Error: 618 reading block 26B
Error: 618 reading block 26C
Error: 618 reading block 26D
Error: 618 reading block 26E
Error: 618 reading block 26F

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:08:03 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
RGH2 Selected
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 604 reading block 36
Error: 604 reading block 3E
Error: 608 reading block 40
Error: 604 reading block 4D
Error: 610 reading block 51
Error: 618 reading block 52
Error: 618 reading block 53
Error: 610 reading block 54
Error: 618 reading block 55
Error: 618 reading block 56
Error: 618 reading block 57
Error: 618 reading block 58
Error: 618 reading block 59
Error: 618 reading block 5A
Error: 618 reading block 5B
Error: 610 reading block 5C
Error: 618 reading block 5D
Error: 618 reading block 5E
Error: 618 reading block 5F
Error: 618 reading block 60
Error: 618 reading block 61
Error: 618 reading block 62
Error: 610 reading block 63
Error: 618 reading block 64
Error: 618 reading block 65
Error: 618 reading block 66
Error: 618 reading block 67
Error: 618 reading block 68
Error: 618 reading block 69
Error: 618 reading block 6A
Error: 618 reading block 6B
Error: 618 reading block 6C
Error: 618 reading block 6D
Error: 618 reading block 6E
Error: 61C reading block 6F
Error: 618 reading block 70
Error: 618 reading block 71
Error: 618 reading block 72
Error: 618 reading block 73
Error: 618 reading block 74
Error: 618 reading block 75
Error: 618 reading block 76
Error: 61C reading block 77
Error: 618 reading block 78
Error: 618 reading block 79
Error: 618 reading block 7A
Error: 618 reading block 7B
Error: 618 reading block 7C
Error: 618 reading block 7D
Error: 618 reading block 7E
Error: 61C reading block 7F
Error: 610 reading block 80
Error: 618 reading block 81
Error: 618 reading block 82
Error: 618 reading block 83
Error: 61C reading block 84
E
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:24:47 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:25:02 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:25:36 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:25:56 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 614 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:28:21 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:28:46 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
Version: 10
You can view these files by using 'Show Working Folder' Button

Flash Config: 0x01198000
01198000
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 610 reading block E8
Error: 618 reading block E9
Error: 618 reading block EA
Error: 618 reading block EB
Error: 618 reading block EC
Error: 618 reading block ED
Error: 618 reading block EE
Error: 61C reading block EF
Error: 618 reading block F0
Error: 618 reading block F1
Error: 618 reading block F2
Error: 61C reading block F3
Error: 618 reading block F4
Error: 618 reading block F5
Error: 618 reading block F6
Error: 61C reading block F7
Error: 618 reading block F8
Error: 618 reading block F9
Error: 618 reading block FA
Error: 618 reading block FB
Error: 618 reading block FC

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:30:08 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 618 reading block 0
Error: 658 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:30:27 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Device Not Found
Device Not Found

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: .............................................................................................................
Done!
Verifying Flash: ...............................................XxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXBootloader Removed.
xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXx
 Write Verified!
Restarting Device ...
Failed
Finished!


Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.
Device Not Found

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: ...............................................xxxxxxxxxxWrite Failed
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: .............................................................................................................
Done!
Verifying Flash: .............................................................................................................
 Write Verified!
Restarting Device ...
Finished!

Bootloader Removed.
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01FFFFFE
Error: 000 reading block 0
Error: 000 reading block 1
Error: 000 reading block 2
Error: 000 reading block 3
01FFFFFE
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198000
Error: 658 reading block 0
Error: 618 reading block 1
Error: 658 reading block 2
Error: 658 reading block 3
01198000
Version: 10
Flash Config: 0x01198010
Error: 65C reading block 0
Error: 658 reading block 1
Error: 658 reading block 2
Error: 658 reading block 3
01198010
Xenon, Zephyr, Opus, Falcon
Version: 10
Flash Config: 0x01198010
Error: 658 reading block 0
Error: 658 reading block 1
Error: 658 reading block 2
Error: 658 reading block 3
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 0

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:58:01 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Version: 10

Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Falcon Manually Selected
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:59:15 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Bootloader Attached
Bootloader Version: 1.0.5
Bootloader Removed.
Device Not Found

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: xxxxxxxxxxWrite Failed
Bootloader Removed.

Bootloader Attached
Bootloader Version: 1.0.5

Erasing Flash ...
Writing Flash: .............................................................................................................
Done!
Verifying Flash: .............................................................................................................
 Write Verified!
Restarting Device ...
Finished!

Bootloader Removed.
Version: 10
Flash Config: 0x01198030
Error: 658 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:52:56 PM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
01198030
CB Version: 5774
Falcon/Opus
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 61C reading block F
Error: 618 reading block 10
Error: 618 reading block 11
Error: 618 reading block 12
Error: 618 reading block 13
Error: 618 reading block 14
Error: 618 reading block 15
Error: 618 reading block 16
Error: 618 reading block 17
Error: 618 reading block 18
Error: 618 reading block 19
Error: 618 reading block 1A
Error: 618 reading block 1B
Error: 618 reading block 1C
Error: 618 reading block 1D
Error: 618 reading block 1E
Error: 618 reading block 1F
Error: 618 reading block 20
Error: 618 reading block 21
Error: 618 reading block 22
Error: 618 reading block 23
Error: 618 reading block 24
Error: 618 reading block
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 10:54:09 PM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198010
Error: 618 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 0
Version: 10
Flash Config: 0x01198010
Error: 610 reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 0
Version: 10
Flash Config: 0x01198000
Error: 658 reading block 0
Error: 658 reading block 1
Error: 658 reading block 2
Error: 658 reading block 3
01198000
CB Version: 0
Falcon Manually Selected
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Reading Nand
Error: 658 reading block 0
Error: 658 reading block 1
Error: 618 reading block 2
Error: 618 reading bloc
No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Sunday, November 26, 2017 11:10:29 PM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198000
Error: 658 reading block 0
Error: 658 reading block 1
Error: 658 reading block 2
Error: 658 reading block 3
01198000
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 61C reading block 0
Error: 618 reading block 1
Error: 618 reading block 2
Error: 618 reading block 3
01198030
CB Version: 0
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Monday, November 27, 2017 2:50:22 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Version: 10

Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Falcon Manually Selected
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Monday, November 27, 2017 3:07:15 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x00000000
Can not Continue

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Monday, November 27, 2017 3:10:22 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Version: 10
Flash Config: 0x01198030
Error: 658 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Falcon Manually Selected
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled
Jtag Selected
Version: 10
Flash Config: 0x01198030
Error: 650 reading block 0
Error: 650 reading block 1
Error: 650 reading block 2
Error: 650 reading block 3
01198030
Reading Nand to C:Documents and SettingsAdminDesktopJ-Runner v3 (5) Core Packoutputnanddump1.bin
Cancelled

No internet connection found (RasInstalled), so can't check integrity of files. Use at your own risk
===================================================
Monday, November 27, 2017 3:11:37 AM

J-Runner v0.3 Beta (5) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Initializing nanddump2.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Comparing...
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
Bad Block ID  0201 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0201 [Offset: 0x844200]
Bad Blocks Remapped
0x0249
0x024A
0x024B
0x024D
0x024E
0x024F
0x0250
0x0251
0x0252
0x0253
0x0254
0x0255
0x0256
0x0257
0x0258
0x0259
0x025A
0x025B
0x025C
0x025D
0x025E
0x026A
0x026B
0x026C
0x026D
0x026E
0x026F
0x0270
0x0271
0x0272
0x0273
0x0274
0x0275
0x0276
0x0277
0x0278
0x0279
0x027A
0x027B
0x027C
0x027D
0x027E
0x027F
0x0280
0x0281
0x0282
0x0283
0x0284
0x0285
0x0286
0x0287
0x0288
0x0289
0x028A
0x028B
0x028C
0x028D
0x028E
0x028F
0x0290
0x0291
0x0292
0x0293
0x0294
0x0295
0x0296
0x0297
0x0298
0x0299
0x029A
0x029B
0x029C
0x029D
0x029E
0x029F
0x02A0
0x02A1
0x02A2
0x02A3
0x02A4
0x02A5
0x02A6
0x02A7
0x02A8
0x02A9
0x02AA
0x02AB
0x02AC

Last edited: Nov 26, 2017

Update: Tried it again just now after leaving it be for 2 days. One decent read compared to most reads (6 errors) after that it was back to it’s non reading tricks.

Could it be something needs to discharge or something? If so, how can one discharge the 360 mobo and JR programmer?

Edit: Also, before that good-ish read the red and green LED’s flickered a lot when just connected to the 360, but didn’t anymore after. Could it be that both of my power supplies don’t give enough voltage when idling?

Last edited: Nov 28, 2017

Update: Tried it again just now after leaving it be for 2 days. One decent read compared to most reads (6 errors) after that it was back to it’s non reading tricks.

Could it be something needs to discharge or something? If so, how can one discharge the 360 mobo and JR programmer?

Edit: Also, before that good-ish read the red and green LED’s flickered a lot when just connected to the 360, but didn’t anymore after. Could it be that both of my power supplies don’t give enough voltage when idling?

What Color Is Your Power Brick LED?

Did You Try And Solder The Chip?

What Color Is Your Power Brick LED?

Did You Try And Solder The Chip?

The color on the power brick is yellow, nothing out of the ordinary for a off 360 as far as I know.

I havent tried soldering the chip (i assume you mean the jr programmer), multimeter says the connection is fine so havent even thought of doing that.

The color on the power brick is yellow, nothing out of the ordinary for a off 360 as far as I know.

I havent tried soldering the chip (i assume you mean the jr programmer), multimeter says the connection is fine so havent even thought of doing that.

Have You Tried To Unsolder The J-R Programmer And Power Console On?

Have You Tried To Unsolder The J-R Programmer And Power Console On?

Yes, but no boot with that either. Although that was straight after trying to read the NAND and getting loads of errors.

Can You Unsolder The Nand Wires And Take A Picture Of Everywhere That You Soldered On.

Can You Unsolder The Nand Wires And Take A Picture Of Everywhere That You Soldered On.

I will as soon as I get home

The wires are unsoldered and it looks like this.

Also tried booting again after it sitting for more than 2 days doing nothing, it actually turned on but got an error E79 (probably due to a failed write attempt)

Update: tried to write the known good read on it again on a hunch. Worked perfectly somehow, after that tried to reread the NAND again which worked largely error free but all with minor errors in different places (so no 2 equal nand reads). After 5 of such Nand reads it went back to how it all started (loads of errors after 201).
That said, it now does boot fine again in stock mode.

From my electronics knowledge this error seems to fit in the category «depends on the stars alignment».

Update 2: The issue seems to have resolved itself as now it reads and writes fine.

Similar threads

Home
Forums
Gaming Platforms
Console Modding Support
Xbox 360 Modding Support and Help Questions

Источник

General

In today’s systems, having a Nor flash (protected) bios supporting system boot from USB or SATA/IDE drives, SD cards and CF cards is now the choice for design, and these devices are typically industrial NAND flash based. Nor flash (protected) is part of the design to help in managing errors in NAND flash.

NAND flash comes in different technologies:

SLC (Single Level Cell)
MLC (2 Level Cell – which can be used as Pseudo SLC)
TLC (Triple Level Cell)
3D – (X-Y-Z axis grid array)

All these technologies are great and have a long service life, details noted in Flash Endurance. They require sophisticated interfacing, both hardware and firmware, to operate properly. Raw bit error rates in MLC/TLC are quite high and require heavy duty ECC algorithms for error detection and correction. > 96 bit detection/correction is about the average for MLC/TLC.

Source of Errors

NAND flash, by its nature (charge based cells), is inherently prone to errors. Here is a list of prominent error possibilities:

Cell Charge Loss or Gain
Read Disturbs
Program Disturbs
Excessive Program/Erase cycles

The use of a sophisticated, well designed NAND controller can make or break a storage product. The controller should have a properly designed Flash Translation Layer (FTL) in its hardware/ firmware to minimize error occurrence.

FTL

The FTL is responsible for translation of logical to physical mapping. Logical sectors (LBA) to physical sectors in the flash (Blocks- > Pages->Sectors). Mapping is the relatively easy part. Most controllers use either block-based mapping or page-based mapping. Both have advantages and disadvantages. One can find comprehensive information about FTL mapping with a simple internet search if interested in further researching that topic. The most difficult task of the FTL is error handling. As you can imagine, this gets more critical with MLC/TLC and very small die process geometries.

Wear Leveling

Wearing out of blocks happens after many P/E cycles. ORT Testing can help determine wear. The first consideration is avoiding prematurely wearing out blocks in the flash which have a life as low as 3000 P/E cycles in small process MLC/TLC devices. Wear Leveling makes sure that all blocks receive approximately the same number of P/E cycles. The best wear leveling is of the static type, whereby data blocks circulate, even if rarely written to (static data is moved).

A good FTL will keep an erase count on each active block, and trigger a wear level once a preset number of erases is reached. Therefore, wear leveling is the first basic step toward error handling.

Error Detection/Correction

This function is normally performed in hardware. Errors will occur when data is read from the flash, there is no escaping that. In the best FTL designs, a combination of ECC and CRC are used, preventing false detection and correction of data. There are different algorithms in use, but the most effective is the BCH algorithm. This requires 13 bits of overhead for each bit of correction desired.

The overhead detection corrections data is kept in the spare area of the flash, hence the amount of correction used is dependent on the available flash in the overhead area. Flash vendors are tuned into this, so a good FTL will keep track of how many bits needed correction on each read, even in cases where the data is corrected. There is a good reason for this as we shall see.

Read Disturb Errors

This phenomenon is commonly overlooked by many controller vendors, and it shouldn’t be. Read disturb errors account for many mysterious issues in the field.

Read disturb errors occur when too many reads (about 1M) are made to a page, without an intervening block erase. Static wear leveling helps to some degree, but it is not enough. Wear leveling is a protective mechanism for preventing too many program erase cycles on a block. What is needed is a count of the number of reads from a block/page. When a threshold is reached, the data needs to be moved to a freshly erased block, and then the block erased can be put back into service.

The issue with read disturbs is that they affect not just the page being read, but adjacent pages as well. This is dangerous because the errors that happen when reading the affected pages may not be correctable.

Program Disturb Errors

Program disturb errors occur normally when too many partial page programs are made and adjacent pages are disturbed. One way to avoid this is to limit the number of partial page programs. There is no defined limit as with read disturbs, and other mechanisms can be used to minimize this. It happens when an affected page is read and the error is detected. Sometimes this can be corrected, however, the block is still in trouble.

So, what can be done? One operation that helps is to keep track of the number of bits needing correction on each page read. When approaching a percentage of available correction capability, the block needs to be erased after moving the data to another good block, then the block can be returned to use.

Program/Erase Errors

When managing errors in NAND Flash, program errors are less common than erase errors. When a program error occurs, it is not always necessary to take the block out of service. Taking the block out of service would be inefficient and unnecessary. Simply pick another block, copy the data from the old block to the new block, and erase the block that caused the error. It is then ready to return to service.

In the case that the erase fails, the result is more severe. Erase errors require that the block be retired and replaced (Remapped).

Handling Bad Blocks – Bad Block Remapping

Flash devices come from the factory with marked bad blocks. Normally all good blocks have 0xFF in them. The manufacturer marks the bad blocks on the first few pages of the block with different data than 0xFF. The first order of business for any controller is to scan for these and build a defect table. These blocks will not be included in logical to physical mapping. Manufacturers typically specify that initial + transient occurring bad blocks won’t exceed a percentage of total blocks. Typically, 2% is stated. It is important to have a pool of spare blocks established to replace these blocks as more go bad, hence bad block remapping is essential.

Excessive Use of Copy Page (Copy Back)

NAND flash has a feature whereby data can be internally copied from one block to another. This can help the speed increase by roughly 20%. The data never leaves the flash device. However, the big drawback is there is no error correction. Do this enough times and bit errors accumulate. So, what can be done to help prevent this? Limit the amount of copy backs performed by using a counter. When the threshold is exceeded, read the data out of the controller to correct any errors. Then reset the counter. This turns out to be a good compromise between speed and reliability.

Reporting Errors to the Host Device

We now see that there are several ways errors are introduced when using NAND flash, and why managing errors in NAND flash is important. The methods mentioned above should all be used to minimize the chance of encountering errors.

However, errors will occur anyway. Let’s take read errors from the flash. Above, we already mentioned a method of keeping track of how many bits are corrected on each read. By watching this counter, we can tell if the block is degrading. When it reaches 75% of its correction ability, a block erase will help.

Even at that, let’s say the controller reads a page and gets an uncorrectable error. It doesn’t know if this is a hard or soft error, maybe from a read or program disturb that occurred in the past. So, the controller should read a few times in succession to see if a correction is achieved. If so, the block should be scheduled for a refresh, so it gets erased and the data moved to another block. If the erase fails, then it should be remapped.

If a correction is not achievable, a UNC error is returned to the host, with no data. This is a bad scenario that can be minimized if the techniques mentioned above are used. From a system level, any service affecting critical data should be kept in multiple places on the drive.

For write errors that involve flash program errors, the controller should move the existing data to a new block, program the new pages, and schedule the block for a refresh. If the block fails an erase, it must be remapped.

Recovery from Power Down During Drive Writes

If power is lost (Power Fail) during a write cycle, with any storage device, there is a good chance of data corruption and consideration for managing errors in NAND flash. From a controller/disk perspective, there is a limit to what can be done. What happens depends on how much data is in the sector buffers, and how much data is behind it overall.

If there is enough capacitance on the disk power supply rails, the controller can detect the power fail at the beginning, flush the sector buffers to the flash, and present a busy signal to the host interface. At the same time, write protect the flash and halt the CPU.

It is not always possible to implement this scenario. From a disk perspective, all that can be done is to minimize corruption, so, upon detection of power down, if the above steps are taken, at minimum the flash is write protected.

The power up recovery is usually where things are attempted to be fixed. Keep in mind that with any reasonable controller design, it writes new data to flash buffers, not touching the existing data. So, power up recovery involves reading these buffers, and if errors occur, replacing this data with the old data. This is not ideal, but it at least guarantees no corruption or nonsense data stored to the drive.

The host bears the brunt of the responsibility of recovering from a power failure. Upon detection of power loss, the host needs enough time to complete writing data that it started to write, and then halt. The host then needs to resolve data conflicts by reading back what was intended to be written and make any corrections if possible. This is not a trivial task, and it is recommended doing further research for additional insight on this process as part of the process in managing errors in NAND flash.

ORDER DELKIN INDUSTRIAL FLASH STORAGE TODAY through our distribution partner Newark.

For Europe Contact Our Partner Farnell

Источник

ProLiant Servers (ML,DL,SL)

- Forums
- - Advancing Life & Work
  - Alliances
  - Around the Storage Block
  - HPE Ezmeral: Uncut
  - OEM Solutions
  - Servers & Systems: The Right Compute
  - Tech Insights
  - The Cloud Experience Everywhere
  - HPE Blog, Austria, Germany & Switzerland
  - Blog HPE, France
  - HPE Blog, Italy
  - HPE Blog, Japan
  - HPE Blog, Latin America
  - HPE Blog, Poland
  - HPE Blog, Hungary
  - HPE Blog, UK, Ireland, Middle East & Africa
- Blogs
- Information
Forums

Blogs
- Advancing Life & Work
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Latin America
- HPE Blog, UK, Ireland, Middle East & Africa
- HPE Blog, Poland
- HPE Blog, Hungary
Information
English

19 REPLIES 19

Previous
- 1
- 2
Next

Источник

С этой ошибкой сталкиваются обладатели Android-смартфонов. Так как, данная ОС весьма проблемная, некоторые ее компоненты постепенно выходят из строя, и пользователь замечает вначале некорректную загрузку виджетов, а потом они и вовсе пропадают. Когда попытки сбросить систему до настроек по умолчанию и очистить кэш не увенчаются успехом, принимается решение перепрошить смартфон. Но и это не удается, потому что при подключении загрузочного носителя и запуске специальной программы, вдруг выскакивает сообщение: «Error: NAND flash was not detected». Почему оно возникает и как с ним бороться, вы узнаете далее.

Решение проблемы NAND Flash was not detected.

Что такое «Error: NAND flash was not detected»

Флэш-память смартфонов и планшетов поделена на две части: для самой ОС и исполняемых файлов и для хранения данных (наверное, вы знаете, что такой же подход практикуется и создателями компьютерных операционных систем). Так вот, NAND – это как раз и есть накопительная память, и сообщение об ошибке гласит, что она не обнаружена, словно ее и нет. Конечно, все дальнейшие действия становятся невозможными, и прошивка аннулируется.

Причины ошибки

Причин этому может быть несколько:

NAND-флэш повреждена – например, телефон падал, лежал на чем-то мокром, был обтянут пластиковым чехлом и подвергся воздействию конденсата и т.п.;
некачественная прошивка (не хватает важных элементов);
уже неактуальна версия утилиты, которой производится прошивка;
смартфон защищен от попыток замены ПО.

Как исправить ошибку Error: NAND flash was not detected

Сначала нужно уточнить, в чем именно причина ошибки «NAND flash was not detected», чтобы решить, что делать. Припомните все «несчастные случаи», происходившие с вашим смартфоном: падения, удары, попадание осадков и т. п. Если что-то такое было, то, скорее всего, придется покупать новый гаджет или идти в сервисный центр. Попробуйте приобрести/скачать другую прошивку, может быть, причина в ее несовместимости с устройством или отсутствии нужных разделов в Scatter-файле. Прочитайте также требования к условиям прошивки: из некоторых смартфонов перед процедурой нужно вынимать батарейку.

Начиная с «Android» 5.1, смартфоны защищены функцией Factory reset protection, которая исключает любые программные изменения. Она задумана как средство защиты от воров, но может создать немало проблем пользователю, забывшему пароль от аккаунта «Гугл» и попытавшемуся решить вопрос с помощью перепрошивки. Загрузчик в таких аппаратах заблокирован, и даже неофициальное «пиратское» ПО не поможет – будет либо выскакивать окошко с уведомлением о том, что память не найдена, либо смартфон настойчиво потребует залогиниться. Если вы не помните свои данные, под которыми регистрировались в Google, то лучше не пробуйте перепрошивать – по крайней мере, самостоятельно.

Проверьте также работоспособность утилиты для прошивки: не устарела ли текущая версия, взаимодействует ли она со смартфонами определенной фирмы. При необходимости обновите ее до последней модификации. Можно также попробовать другие программы той же тематики – вероятно, они будут эффективнее. Их мини-рейтинг выглядит примерно так:

SP FlashTool – примите во внимание, что для Windows и Linux существуют отдельные выпуски;
Adb RUN – имеет довольно сложную структуру и не русифицирована: любая ошибка может превратить телефон в абсолютно нефункциональный предмет;
BootLoader – для прошивки телефонов фирмы Sony и некоторых других понадобится дополнительное ПО — Adb Run;
KDZ Updater;
FastBoot;
Odin;
Sony PC Companion – только для фирменных смартфонов «Samsung».

Перед началом работы с любой из них прочтите инструкцию, чтобы знать, в какой последовательности выполнять все действия и не навредить смартфону. Никогда не прерывайте начавшийся процесс прошивки, иначе результат может быть непредсказуем.

Источник

Классификация ошибок

Read Disturb Error – ошибки чтения

Как защититься

Program Disturb Error – ошибка при программировании ячейки

Как защититься

Over-Programming Error – ошибка перепрограммирования

Как защититься

Retention Error – ошибка удержания заряда

Как защититься

Механизмы мониторинга и обработки ошибок NAND

Error Correction Codes (ECC)

Wear Leveling – выравнивание износа ячеек

Bad-Block Management

Diman4eg
Пользователь

voldemaro
Пользователь

Lapa
Пользователь

Diman4eg
Пользователь

DDD
Пользователь

Okas43

timoncrew
Пользователь

Lapa
Пользователь

voldemaro
Пользователь

Поделиться этой страницей

Similar threads

Что такое «Error: NAND flash was not detected»

Причины ошибки

Как исправить ошибку Error: NAND flash was not detected

Классификация ошибок

Read Disturb Error – ошибки чтения

Как защититься

Program Disturb Error – ошибка при программировании ячейки

Как защититься

Over-Programming Error – ошибка перепрограммирования

Как защититься

Retention Error – ошибка удержания заряда

Как защититься

Механизмы мониторинга и обработки ошибок NAND

Error Correction Codes (ECC)

Wear Leveling – выравнивание износа ячеек

Bad-Block Management

Lapa Пользователь

Diman4eg Пользователь

DDD Пользователь

Okas43

timoncrew Пользователь

Lapa Пользователь

voldemaro Пользователь

Поделиться этой страницей

Similar threads

Что такое «Error: NAND flash was not detected»

Причины ошибки

Как исправить ошибку Error: NAND flash was not detected

Lapa
Пользователь

Diman4eg
Пользователь

DDD
Пользователь

timoncrew
Пользователь

Lapa
Пользователь

voldemaro
Пользователь