To those that have phone with lower android version.
i also make root and flash your phone to the latest version.
contact me via email or fb page
Wednesday, May 8, 2013
Riff Box Services
Right now im working for selected phones only.
you can contact me via email or sms and facebook.
anything you can ask me on fb page or email me.
with phone condition is hardbrick.
dont send the phone with another problem because i only can jtag your phone.
if the condition not hardbrick i will send you back the money and phone.
but i will take charge for delivery only
you can contact me via email or sms and facebook.
anything you can ask me on fb page or email me.
with phone condition is hardbrick.
dont send the phone with another problem because i only can jtag your phone.
if the condition not hardbrick i will send you back the money and phone.
but i will take charge for delivery only
Riff Box Jtag Repair Hardbrick ( Currently Im Working On Samsung Phone )
Features
RIFF JTAG Features
by admin on Jul.05, 2010, under Features
RIFF JTAG firmware supports following features at the moment:
ARM7/ARM9/ARM11 PXA3xx, PXA270, Cortex-A8, OMAP850, Cortex-A9 Dual cores support;
Multiple devices on JTAG chain are supported, thus TAP number selection is available;
Any custom voltage level selection from range ~1.4V to 3.3V
TCK/Adaptive clocking selection
Halt core (NRST is not changed)
Reset core (NRST is applied before halt)
Direct Read memory (by 8/16/32-bit bytes/half-words/words)
Direct Write memory (by 8/16/32-bit bytes/half-words/words)
Access to the control registers of ARM core (coprocessor 15)
Program code breakpoints
Run core
Custom scripting and DCC loader support (trace32 compatible)
Custom GDB Server Available
I/O pins detection !Unique feature offered only by RIFF JTAG
This is result of six months hard work. And we just started -;)
Stay tuned for more !
This is list of supported memory controllers and chipsets and CPU cores using Direct Memory Access :
Currently supported memory controllers are:
OneNAND Memory (connected directly to the MCU’s address space);
CFI Compliant NOR Memory with CFI Command sets 0×0001, 0×0002, 0×0200 and 0×0003;
NAND Controller in MSM6250, MSM6250A;
NAND Controller in QSC6055, QSC6085, QSC6240, QSC6270;
NAND Controller in MDM6085, MDM6200, MDM6600;
NAND Controller in MSM6245, MSM6246, MSM6270, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6290, MSM6800A, MSM6801A;
NAND Controller and OneNAND Controller in MSM7225, MSM7227, MSM7625, MSM7627;
NAND Controller in MSM7200, MSM7200A, MSM7201A, MSM7500, MSM7500A, MSM7501A, MSM7600;
NAND Controller in QSD8250, QSD8650;
eMMC Controller #2 in MSM7230, MSM8255, MSM8255T;
eMMC Controller #0 in S5PV310;
Currently supported chipsets and cores for JTAG I/O operations:
Generic ARM Cores: ARM7, ARM9 (ARM920, ARM926, ARM946), ARM11, CORTEX-A8,CORTEX-A9;
Qualcomm QSC Family: QSC1100, QSC1110, QSC6010, QSC6020, QSC6030, QSC6055, QSC6085, QSC6240, QSC6270;
Qualcomm MSM Family: MSM6000, MSM6150, MSM6245, MSM6246, MSM6250, MSM6250A, MSM6260, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6800A, MSM6801A, MSM6290, MSM7225, MSM7227, MSM7625, MSM7627, MSM7230, MSM8255, MSM8255T, MSM8260;
Qualcomm QSD Family: QSD8250, QSD8650;
Qualcomm ESM Family: ESM7602A;
Qualcomm MDM Family: MDM6085 MDM6200, MDM6600;
OMAP Family: OMAP1710, OMAP3430, OMAP3630, OMAP4430;
NVIDIA Family: TEGRA2;
Marvell/XScale Family: PXA270, PXA271, PXA272, PXA310, PXA312, PXA320.
Samsung Processors: S5P6422, S5PV310.
This is the list of supported devices and operations, supported by RIFF JTAG Box:
Tablets :
Samsung GT-P7320 Galaxy Tab 8.9 LTE Unbrick, Repair, Read/Write eMMC memory
Samsung GT-P6810 Galaxy Tab 7.7 WiFi 16GB Unbrick, Repair, Read/Write eMMC memory
Samsung Galaxy TAB (Samsung P1000) Unbrick, Repair, Read/Write NAND Flash memory
Samsung Galaxy TAB (Samsung P1000N) Unbrick, Repair, Read/Write NAND Flash memory
Samsung Galaxy TAB (Samsung M180s) Unbrick, Repair, Read/Write NAND Flash memory
Samsung Galaxy TAB Wi-Fi (P1010) Unbrick, Repair, Read/Write NAND Flash memory
Samsung Galaxy Note (Samsung N7000) Unbrick, Repair, Read/Write eMMC memory
Samsung Galaxy Note (Samsung i9220) Unbrick, Repair, Read/Write eMMC memory
Samsung Galaxy Plus (GT-P6200) Unbrick, Repair, Read/Write eMMC memory
Samsung YP-G70EW Galaxy S WiFi 5.0 Unbrick, Repair, Read/Write eMMC memory
Samsung GT-P6800 Galaxy Tab 7.7 Unbrick, Repair, Read/Write eMMC memory
Samsung SGH-i717 Galaxy Note LTE Unbrick, Repair, Read/Write NAND Flash memory
Wednesday, June 20, 2012
Party Search Macro
IMPORTANT!
• You must have plugins for this to work. Read Bot Installation Guide (lowest part)
Macro for MASTER
• Go to control folder - macros.txt and paste this
#######################################
########FIND SLAVE#####################
#######################################
#slave is lost
automacro findSlave {
pm /x (.*) (.*) (.*)/
call {
$slavemap = $.lastMatch1
$slavemapx = $.lastMatch2
$slavemapy = $.lastMatch3
$mymap = $.map
if ($slavemap == $mymap) goto findslave
do pm "$.lastpm" x $.map $.pos
stop
:findslave
do pm "$.lastpm" x $.map $.pos
do move $slavemap $slavemapx $slavemapy
}
}
#when slave is found
automacro clear {
pm /clear/
call {
do eval AI::clear("move", "route");
}
}
Macro for Slave
• Go to control folder - macros.txt and paste this
################################
######FIND MASTER###############
################################
#find master
automacro findMaster {
timeout 3
console /^I lost my master/
call {
$master = @config (followTarget)
do pm "$master" x $.map $.pos
}
}
automacro findMaster2 {
timeout 3
console /^Calculating route to find master/
call {
$master = @config (followTarget)
do pm "$master" x $.map $.pos
}
}
#goto master
automacro gotoMaster {
pm /x (.*) (.*) (.*)/
call {
$pm = $.lastpm
if ($pm != $master) stop
do move $.lastMatch1 $.lastMatch2 $.lastMatch3
}
}
#when master is found
automacro foundMaster {
console /^Found my master!/
call {
do pm "$master" clear
}
}
Also adjust your MASTER/SLAVE's route_step
For Master: make it route_step 8
For Slave: make it route_step 18
HAPPY LEVELING!!
Disclaimer:
I do not own or Im not the one who made this macro, I just made it plain and simple for the newbies to understand it easily. Thank you!
• You must have plugins for this to work. Read Bot Installation Guide (lowest part)
Macro for MASTER
• Go to control folder - macros.txt and paste this
#######################################
########FIND SLAVE#####################
#######################################
#slave is lost
automacro findSlave {
pm /x (.*) (.*) (.*)/
call {
$slavemap = $.lastMatch1
$slavemapx = $.lastMatch2
$slavemapy = $.lastMatch3
$mymap = $.map
if ($slavemap == $mymap) goto findslave
do pm "$.lastpm" x $.map $.pos
stop
:findslave
do pm "$.lastpm" x $.map $.pos
do move $slavemap $slavemapx $slavemapy
}
}
#when slave is found
automacro clear {
pm /clear/
call {
do eval AI::clear("move", "route");
}
}
Macro for Slave
• Go to control folder - macros.txt and paste this
################################
######FIND MASTER###############
################################
#find master
automacro findMaster {
timeout 3
console /^I lost my master/
call {
$master = @config (followTarget)
do pm "$master" x $.map $.pos
}
}
automacro findMaster2 {
timeout 3
console /^Calculating route to find master/
call {
$master = @config (followTarget)
do pm "$master" x $.map $.pos
}
}
#goto master
automacro gotoMaster {
pm /x (.*) (.*) (.*)/
call {
$pm = $.lastpm
if ($pm != $master) stop
do move $.lastMatch1 $.lastMatch2 $.lastMatch3
}
}
#when master is found
automacro foundMaster {
console /^Found my master!/
call {
do pm "$master" clear
}
}
Also adjust your MASTER/SLAVE's route_step
For Master: make it route_step 8
For Slave: make it route_step 18
HAPPY LEVELING!!
Disclaimer:
I do not own or Im not the one who made this macro, I just made it plain and simple for the newbies to understand it easily. Thank you!
Wednesday, May 16, 2012
Custom Map
FLD Creation Guide
How to extract custom maps and create FLD file
(note: short version)
1. Extract the map (gat and rsw)
2. Copy both to OpenKore\fields\tools
3. Download Perl or Strawberry Perl
4. Execute script: gat_to_fld.pl
5. Copy created .fld data to OpenKore\fields
You can either execute the script by using:
a perl interpreter of choice
the perl interpreter kore uses: start.exe
cd to kore's root folder
run the following command:
C:\Openkore-SVN>start.exe ! .\fields\tools\gat_to_fld.pl
Note: in this example the root folder was: C:\Openkore-SVN, yours can be different depending on where you have installed kore.
You Need Perl
How to extract custom maps and create FLD file
(note: short version)
1. Extract the map (gat and rsw)
2. Copy both to OpenKore\fields\tools
3. Download Perl or Strawberry Perl
4. Execute script: gat_to_fld.pl
5. Copy created .fld data to OpenKore\fields
You can either execute the script by using:
a perl interpreter of choice
the perl interpreter kore uses: start.exe
cd to kore's root folder
run the following command:
C:\Openkore-SVN>start.exe ! .\fields\tools\gat_to_fld.pl
Note: in this example the root folder was: C:\Openkore-SVN, yours can be different depending on where you have installed kore.
You Need Perl
ServerType
ServerType
serverType
Network parser module to use with your server.
File:Development.png The following documentation describes a feature that was greatly changed in SVN trunk (latest development version) since the last release.
It may work differently or not be available if you're using 2.0.7 or any older version.
Contents
[hide]
1 ServerTypes overview
1.1 Supported
1.2 Legacy
2 Determining kRO serverType
2.1 Compilation Date
2.2 Server Version
2.3 Packet Appearance
2.4 Notes
3 Links
ServerTypes overview
Supported
Named serverTypes can be loaded since r6870 and begin to appear in r7066 (not counting kRO serverType tree which started all that madness).
Server servertype
Official, Korea kRO_RagexeRE_0 8_1
Official, Taiwan twRO 21, 22
Official, Japan none
Official, Thailand tRO 21
Official, China none
Official, International iRO 22
Official, Philippines pRO 22
Official, Indonesia idRO 22
Official, Malaysia mRO 22
Official, Brazil bRO (Odin) 0
bRO_Thor (Thor) 22
Official, Russia rRO 0
Official, France fRO 0
Official, Middle East aRO 22
Private servers kRO_RagexeRE_*
kRO_Sakexe_* *
File:Development.png Implementation of this feature is expected to become outdated with server updates.
As OpenKore is a free project, if you stumble upon such updates, you are expected to fix the problem and contribute your changes back. Usually, server supporters will do that, but there isn't any for random private servers, and some official ones may not always be covered.
Legacy
Numeric serverTypes (0-22, 8_1-8_5) are outdated and aren't being updated to follow server updates, so they probably will not work correctly - that's a real reason to update from OpenKore 2.0.7 and stop using them, if you don't want to update them by yourself. Don't complain that there's just "some problems" with them if you don't have solutions too.
They're kept in OpenKore for use with really outdated official and private servers.
serverType 0 is also used as a base for serverTypes for official servers (except kRO).
Determining kRO serverType
OpenKore 2.0.7 and previous versions does not have kRO serverType and aren't capable of loading it without changes in source. To configure for an up to date pserver, you need svn trunk (or 2.1 when it becomes released), not 2.0.7.
Only official servers have their own serverType, so other servers (private ones) must find the server's executable compilation date and use the appropriate kRO serverType (newer versions) or Sakray serverTypes (older versions)
Currently, kRO serverTypes syntax is:
kRO_RagexeRE___
And Sakray ones is:
kRO_Sakexe___
You can find all serverType files in src/Network/Receive. Only serverTypes whose files actually do exist would work.
Compilation Date
Executable's compilation date can be changed, so don't really rely on it.
1. Download IpeViewer [1].
2. Open it and go the File > Open or just press F2. Select your server's executable.
3. Go to PE Header tab.
http://www.openkore.com/images/7/7e/ServerType-header.PNG
4. Beside the Time Data Stamp box, see the executable's compilation date.
5. Find the most suitable serverType file in src/Network/Receive/kRO.
For example, if the date was January 26, 2010, file name would be RagexeRE_2010_01_26a.pm.
6. Set serverType to "kRO_" and file name without extension.
For example, if file name was RagexeRE_2010_01_26a.pm, serverType would be kRO_RagexeRE_2010_01_26a.
If there is no file with exact compilation date, try the ones near to that date, or the latest available.
Server Version
Server version changes when there are incompatible changes in protocol (usually master_login packet changes at that point). Try serverTypes corresponding to the server's version. Use eAthena's packet_db as reference.
Packet Appearance
Since there are packets being continually introduced, you may inspect packets (and packet lengths) used on the server (either from already generated recvpackets.txt or from warnings on unknown packets). Use eAthena's packet_db as reference.
Notes
If you bot on a private server that uses eAthena, DO NOT use kRO_RagexeRE_0, as it is only meant to be used for the official kRO server.
Links
OpenKore's serverType files
eAthena's packet_db.txt
rAthena's packet_db.txt
serverType
Network parser module to use with your server.
File:Development.png The following documentation describes a feature that was greatly changed in SVN trunk (latest development version) since the last release.
It may work differently or not be available if you're using 2.0.7 or any older version.
Contents
[hide]
1 ServerTypes overview
1.1 Supported
1.2 Legacy
2 Determining kRO serverType
2.1 Compilation Date
2.2 Server Version
2.3 Packet Appearance
2.4 Notes
3 Links
ServerTypes overview
Supported
Named serverTypes can be loaded since r6870 and begin to appear in r7066 (not counting kRO serverType tree which started all that madness).
Server servertype
Official, Korea kRO_RagexeRE_0 8_1
Official, Taiwan twRO 21, 22
Official, Japan none
Official, Thailand tRO 21
Official, China none
Official, International iRO 22
Official, Philippines pRO 22
Official, Indonesia idRO 22
Official, Malaysia mRO 22
Official, Brazil bRO (Odin) 0
bRO_Thor (Thor) 22
Official, Russia rRO 0
Official, France fRO 0
Official, Middle East aRO 22
Private servers kRO_RagexeRE_*
kRO_Sakexe_* *
File:Development.png Implementation of this feature is expected to become outdated with server updates.
As OpenKore is a free project, if you stumble upon such updates, you are expected to fix the problem and contribute your changes back. Usually, server supporters will do that, but there isn't any for random private servers, and some official ones may not always be covered.
Legacy
Numeric serverTypes (0-22, 8_1-8_5) are outdated and aren't being updated to follow server updates, so they probably will not work correctly - that's a real reason to update from OpenKore 2.0.7 and stop using them, if you don't want to update them by yourself. Don't complain that there's just "some problems" with them if you don't have solutions too.
They're kept in OpenKore for use with really outdated official and private servers.
serverType 0 is also used as a base for serverTypes for official servers (except kRO).
Determining kRO serverType
OpenKore 2.0.7 and previous versions does not have kRO serverType and aren't capable of loading it without changes in source. To configure for an up to date pserver, you need svn trunk (or 2.1 when it becomes released), not 2.0.7.
Only official servers have their own serverType, so other servers (private ones) must find the server's executable compilation date and use the appropriate kRO serverType (newer versions) or Sakray serverTypes (older versions)
Currently, kRO serverTypes syntax is:
kRO_RagexeRE_
And Sakray ones is:
kRO_Sakexe_
You can find all serverType files in src/Network/Receive. Only serverTypes whose files actually do exist would work.
Compilation Date
Executable's compilation date can be changed, so don't really rely on it.
1. Download IpeViewer [1].
2. Open it and go the File > Open or just press F2. Select your server's executable.
3. Go to PE Header tab.
http://www.openkore.com/images/7/7e/ServerType-header.PNG
4. Beside the Time Data Stamp box, see the executable's compilation date.
5. Find the most suitable serverType file in src/Network/Receive/kRO.
For example, if the date was January 26, 2010, file name would be RagexeRE_2010_01_26a.pm.
6. Set serverType to "kRO_" and file name without extension.
For example, if file name was RagexeRE_2010_01_26a.pm, serverType would be kRO_RagexeRE_2010_01_26a.
If there is no file with exact compilation date, try the ones near to that date, or the latest available.
Server Version
Server version changes when there are incompatible changes in protocol (usually master_login packet changes at that point). Try serverTypes corresponding to the server's version. Use eAthena's packet_db as reference.
Packet Appearance
Since there are packets being continually introduced, you may inspect packets (and packet lengths) used on the server (either from already generated recvpackets.txt or from warnings on unknown packets). Use eAthena's packet_db as reference.
Notes
If you bot on a private server that uses eAthena, DO NOT use kRO_RagexeRE_0, as it is only meant to be used for the official kRO server.
Links
OpenKore's serverType files
eAthena's packet_db.txt
rAthena's packet_db.txt
Sunday, May 13, 2012
Packet Length Extractor
Packet Length Extractor
If you're having server problems, such as:
Packet Tokenizer: Unknown switch: xxxx
Getting disconnected after a few seconds
NPCs, players and monsters are not recognized by Kore (shown as Unknown)
Then generating a new recvpackets.txt might solve the problem. It's advisable to always extract the recvpackets before running Openkore. The file must be on tables folder.
The network data that the server sends to Kore, is a byte stream. Kore must be able to recognize messages inside that byte stream to be able to do something with it. But the size of the messages can vary from to server to server. Recvpackets.txt contains information about the size of each message, so Kore can correctly split the byte stream into messages.
Contents
[hide]
1 RO Tools
1.1 Usage
2 Packet Extractor
3 Packet Extractor v3
3.1 Usage
4 Notes
RO Tools
JCV's RO Tools v1.0.3 (Link down as of Jan 19, 2012. See instructions below for OpenPacketExtractor)
It's better to use JCV's RO Tools as it is more up to date and have some fixes for newer clients. Also it's much easier to maintain, but it has undesirable and outdated options in addition to the Openkore packet extractor.
Usage
Open RO Tools.
Click in the button with ... beside the box. Search for your's server executable (not server patcher) and open it.
File:button.PNG
On Extractor Type, check Full Disarm box.
File:full.PNG
Click on Start button and wait it to finish.
File:start.PNG
After it finishes, it will ask for you to save the file. Save it on tables folder, inside your Openkore's root folder. Override current file if needed.
Packet Extractor
OpenKore Packet Length Extractor v1.1.0 (Link down as of Jan 19,2012)
Also in OpenKore SVN.
Packet Extractor v3
In OpenKore SVN. (See kLab's forum post on Open Packet Extractor for more details.)
Packet extractor branch to work with new insert server list here clients.
Usage
Run packet_extract.pl with your ragexe file name as an argument. It will generate extractor.exe.
Run extractor.exe (works with wine on non-Windows) which will output recvpackets contents to STDOUT.
Notes
Recvpackets file can be renamed as long as recvpackets option on servers.txt is set accordingly. (See Connectivity Guide)
There may be problems extracting the recvpackets if your server's client has some kind of protection. You should deal with it (like unpack if binary is packed) before using packet extractor, if it fails to find anything.
If you're having server problems, such as:
Packet Tokenizer: Unknown switch: xxxx
Getting disconnected after a few seconds
NPCs, players and monsters are not recognized by Kore (shown as Unknown)
Then generating a new recvpackets.txt might solve the problem. It's advisable to always extract the recvpackets before running Openkore. The file must be on tables folder.
The network data that the server sends to Kore, is a byte stream. Kore must be able to recognize messages inside that byte stream to be able to do something with it. But the size of the messages can vary from to server to server. Recvpackets.txt contains information about the size of each message, so Kore can correctly split the byte stream into messages.
Contents
[hide]
1 RO Tools
1.1 Usage
2 Packet Extractor
3 Packet Extractor v3
3.1 Usage
4 Notes
RO Tools
JCV's RO Tools v1.0.3 (Link down as of Jan 19, 2012. See instructions below for OpenPacketExtractor)
It's better to use JCV's RO Tools as it is more up to date and have some fixes for newer clients. Also it's much easier to maintain, but it has undesirable and outdated options in addition to the Openkore packet extractor.
Usage
Open RO Tools.
Click in the button with ... beside the box. Search for your's server executable (not server patcher) and open it.
File:button.PNG
On Extractor Type, check Full Disarm box.
File:full.PNG
Click on Start button and wait it to finish.
File:start.PNG
After it finishes, it will ask for you to save the file. Save it on tables folder, inside your Openkore's root folder. Override current file if needed.
Packet Extractor
OpenKore Packet Length Extractor v1.1.0 (Link down as of Jan 19,2012)
Also in OpenKore SVN.
Packet Extractor v3
In OpenKore SVN. (See kLab's forum post on Open Packet Extractor for more details.)
Packet extractor branch to work with new insert server list here clients.
Usage
Run packet_extract.pl with your ragexe file name as an argument. It will generate extractor.exe.
Run extractor.exe (works with wine on non-Windows) which will output recvpackets contents to STDOUT.
Notes
Recvpackets file can be renamed as long as recvpackets option on servers.txt is set accordingly. (See Connectivity Guide)
There may be problems extracting the recvpackets if your server's client has some kind of protection. You should deal with it (like unpack if binary is packed) before using packet extractor, if it fails to find anything.
Subscribe to:
Posts (Atom)