Monday, November 28, 2011

Ac1dSn0w is a New Utility to Jailbreak iOS 5 [Update]

0 comments

Ac1dSn0w is a New Utility to Jailbreak iOS 5 [Update]

Ac1dSn0w  

Beta 1


I’m pleased to announce that we’ve just released Beta 1 of Ac1dSn0w for Mac OS X Lion (should also work on Snow Leopard). Ac1dSn0w allows you to jailbreak your iDevice tethered. It also provides features like Tethered Boot, Pwned DFU, and Exit Recovery to get your device out of Recovery Loop.
Supported Devices (iOS5/iOS5.0.1):
  • iPhone 3Gs
  • iPhone 4
  • iPod Touch 4 G
  • iPad 1


You may have to perform the following steps in order to jailbreak your device successfully.
1. Download Ac1dSn0w from (Down due to legal complication)
2. After downloading, open it and you’ll see the following screen:


Note:
You can click ‘Show Console’ to see some device related information. It also shows you the current state of your jailbreaking process. The Assistant Panel helps you to put your device into DFU Mode.
3. Connect your device with your Mac.
4. Turn your device off.
5. Click ‘Show Assistant’ and follow the onscreen instructions to enter DFU Mode.
6 . Once you’re in DFU Mode just hit the ‘Jailbreak’ Button and wait until it’s done (the device will reboot).
7. Put your device again into DFU Mode (Step 5) and hit the ‘Tethered Boot’ Button.
Done: Your device should now be jailbroken with Cydia installed.

Upcoming Features

The current version of Ac1dSn0w is in an early development stage. In the future it will also be able to jailbreak remote devices. This means that you just need to install a server program on any OS (Linux, BSD, Windows) and Ac1dSn0w will jailbreak it on a client machine anywhere in the world. Other upcoming features are:
  • Custom Firmware Creation
  • iRecovery Remote (you can talk to remote devices and send your own payloads etc)
Continue reading →

Ih8sn0w Update sn0wbreeze v2.8b11

0 comments

Ih8sn0w Update sn0wbreeze v2.8b11



===============================
sn0wbreeze v2.8 [BETA 11]:
===============================
* Supports iOS 5.0 (9A334)/5.0.1 (9A405)
* Fixed iBooks sandbox crashing issues (as of 2.8b9).
* Fixed location services issues with iPhone 3GS
users running the iPad baseband (as of 2.8b9).
* Re-added iPad baseband install option to iPhone 3GS.
* Tethered devices are booted via iBooty which is
extracted to the Desktop after running sn0wbreeze.
===============================



Tethered?
===============================
- iPhone 3GS (old bootrom)...NO
- iPhone 3GS (new bootrom)..YES
- iPhone 4 (GSM)............YES
- iPhone 4 (CDMA)...........YES
- iPod Touch 3G.............YES
- iPod Touch 4..............YES
- iPad 1G...................YES
===============================




************************************************
** iPhone 3GS iPad baseband (06.15.00) users: **
************************************************
- Re-flash the iPad baseband via sn0wbreeze 
if you restore(d) to a stock 5.0 firmware.
************************************************


Download: Sn0wbreeze v2.8b11
Continue reading →

New iPhone Firmware Files

0 comments
New iPhone Firmware Files





5.0 (3GS): iPhone2,1_5.0_9A334_Restore.ipsw
5.0 (4 GSM): iPhone3,1_5.0_9A334_Restore.ipsw
5.0 (4 CDMA): iPhone3,3_5.0_9A334_Restore.ipsw
5.0 (4S): iPhone4,1_5.0_9A334_Restore.ipsw
5.0.1 (3GS): iPhone2,1_5.0.1_9A405_Restore.ipsw
5.0.1 (4 GSM): iPhone3,1_5.0.1_9A405_Restore.ipsw
5.0.1 (4 CDMA): iPhone3,3_5.0.1_9A405_Restore.ipsw
5.0.1 (4S): iPhone4,1_5.0.1_9A405_Restore.ipsw
Continue reading →

BBM Music Available In Spain and Italy

0 comments
BBM Music Available In Spain and Italy

Attention Spaniards and Italians: BBM Music is officially available to you!
If you haven't already lunged for your BlackBerry to download BBM Music, now is the time to do so!



  • Step One: Download BBM Music from the App World.
  • Step Two: Create your very own music profile and pick 50 of your favorite songs from millions up for grabs.
  • Step Three: Add your friends! Invite your fellow BBM buddies and gain access to their 50 songs as well. The more friends you have on BBM Music means the more songs you can listen to.
  • Step Four: Start listening. Grab some earphones or play through the speakers to allow everyone to enjoy and bring on the music.

Are you a fan of long road-trips or need certain songs for working out? BBM Music allows you to build custom playlists to meet your specific music needs. Each month you can switch out up to 25 (of your 50) songs to freshen up your listening habits. The songs you have listened to can also be cached to your SD card to allow access to all your songs even when you're offline and can't connect to your wireless network. Even better: free trial for a whole month! After that, access to BBM Music will cost you only $5 per month. That's 10 cents per song if you never swap them out, and roughly seven cents if you swap out 25. I'm not sure where else you can pay that little for music right on your BlackBerry, which means one thing.. Go download BBM Music now!




Source:http://www.blackberryos.com/bbm-music/26600-bbm-music-available-spain-italy.html#post235379
Continue reading →

Hot Iphone 3GS iOS 4.1 Unlock

0 comments

 
 Hot Iphone 3GS iOS 4.1 Unlock  2010




Download part 1
Download part 2
Download part 3 
Download part 4
Download part 5
Torrent Mirror Link
Continue reading →
Saturday, November 26, 2011

VQ Mileage Tracker untuk BlackBerry Melacak Info Perjalanan Anda Secara Otomatis

0 comments
http://indobb.com/wp-content/uploads/2010/03/screenshot1i1.jpgagi Anda yang suka travel dan selalu ada di jalan, Anda pasti tahu betapa repotnya kalau harus terus mencatat
kilometer, waktu dan tanggal. Nah, VQ Mileage Tracker adalah jawaban dari masalah Anda. Aplikasi ini secara otomatis mengumpulkan informasi yang paling dibutuhkan. VQ mileage Tracker menggunakan GPS sekaligus Bluetooth yang terintegrasi (atau Bluetooth car charger)
di kendaraan untuk menentukan kapan Anda memulai dan mengakhiri perjalanan. VQ Mileage Tracker bertugas mengumpulkan informasi untuk laporan pengeluaran Anda, termasuk tanggal dan waktu, jarak perjalanan, bahkan alamat tujuan. Cukup satu klik, Anda sudah langsung bisa membuat laporan dan mengirimnya via email.

“Aplikasi-aplikasi pelacak perjalanan yang ada kami sebut ‘pensil digital’ di mana Anda harus mengatur semuanya secara manual,” tambah Korn. “VQ Mileage Tracker melakukan semuanya untuk pengguna. Secara otomatis, dia akan mencatat tanggal dan waktu, seberapa jauh Anda menyetir, dan alamat yang dituju setiap kali Anda menyetir mobil, lalu meng-email info ini ketika Anda siap menyerahkan laporan pengeluaran.”
VQ Mileage Tracker tersedia dengan harga perkenalan $6.99 dan uji coba gratis. Untuk info lebih lanjut, kunjungi toko aplikasi Mobihand.
* Info lebih lanjut dan unduh VQ Mileage Tracker
Continue reading →

OS 6.0.0.448 Beta untuk BlackBerry Torch 9800

0 comments
Continue reading →

iphone themes for 9780

0 comments





Features:

wallpaper easily replaced
bottom 6 icons
icons iphone

Hotkey

$ = SMS and MMS
e = Profiles
Browser

Model: 9780/9700/9650
OS: 6.0
Author: mobiworld

Thanks and as always, if you want something changed or something different, don’t hesitate to ask, I like making themes and will try to accommodate everyone I can.

Downloads Free

Enjoy

OTA Themes
Continue reading →

Blackberry Themes Collection OS 6

0 comments
 Blackberry Themes Collection OS 6



Link Download


Themes Collection
mirror
Themes Collection

if link dead please PM me :D
Continue reading →

manchester united blackberry curve themes

0 comments
Features:



- 6 customizable homescreen icon
- Wallpaper Friendly
- sms and mms = $
- calendar = c
- Browser = b
- Manage connection


downloads free

OTA manchester
Continue reading →

nike themes for blackberry curve

0 comments

Features:



- 9 customizable homescreen icon
- Wallpaper Friendly
- sms and mms = $
- icons 6.1 

downloads free


Enjoy

OTA nike themes
Continue reading →

pink themes for blackberry curve

1 comments

Features:

- 7 customizable homescreen icon

- Wallpaper Friendly
- icons 6.1
- $ = SMS and MMS
- c = calendar
- b = browser

themes for 83xx/87xx/88xx
OS: 4.5

downloads free

Enjoy

Zip pink themes
Continue reading →

blackberry pearl 8100 themes free

0 comments

 I am not a professional theme builder. I take no responsibility for anything this theme may do to your BB. It was created using Theme Builder from RIM so everything should be fine.



Features:

- 5 customizable homescreen icon
- Wallpaper Friendly
- Storm Themes icons 6.1



themes for 8100
OS: 4.5

downloads free

Enjoy

Zip
Continue reading →

free zebra themes for blackberry curve 8530

0 comments

Features include better icons, a weather slot that you can toggle on/off just by a touch of a hotkey,



Features:

- 8 customizable homescreen icon
- Wallpaper Friendly
- Themes icons 6.0
- $ = SMS and MMS
- a = Contacs
- b = Browser
- c= Calandar
- o = Options

Themes for 85xx
OS: 5.0

downloads free

Enjoy

Zip
Continue reading →

themes for blackberry curve

0 comments

Features:



- 6 customizable homescreen icon
- Wallpaper Friendly
- Storm Themes icons 6.1
- $ = SMS and MMS
- b = browser

themes for 85xx
OS: 5.0

downloads free

Enjoy

Zip
Continue reading →
Thursday, November 24, 2011

unlock i-phone

0 comments
disini saya akan sharre tutorial cara unlock device i-phone

pertama
pastikan device tidak disable dan sudah di jailbreak yang terinstall cydia

tuts:


masuk menu >> cydia

Posted Image




setelah masuk cydia >> masuk tab manage

Posted Image


setelah masuk tab manage >> lalu buka source >> klo sudah ada link http://repo666.ultrasn0w.com tinggal install tapi klo blum ada,,add source dengan mengetik http://repo666.ultrasn0w.com lalu add seperti ini :



Posted Image

jika terinstall maka di layar akan terlihat seperti ini

Posted Image

device akan reboot dan terunlock
Continue reading →

all about jailbreak apple device wiki

0 comments
jailbreak

iOS jailbreaking, atau yang biasa disingkat jailbreaking, adalah proses menghilangkan batasan yang diberlakukan oleh Apple pada perangkat genggam dengan sistem operasi iOS, yakni iPhone, iPod Touch, iPad dan Apple TV
generasi ke-2. Jailbreaking akan membuat sang pengguna bisa mendapatkan akses penuh (atau root access) terhadap sistem operasi, yang darinya pengguna iOS itu bisa mengunduh perangkat lunak, baik yang bajakan ataupun yang orisinil namun tidak tersedia di Apple App Store.
Pada dasarnya, jailbreaking pada iOS membuat sang pengguna memiliki akses pada sistem file root yang memampukan dirinya untuk mengaktifkan serangkaian fitur yang sebelumnya dikunci oleh Apple.
Aktivitas jailbreaking pada umumnya akan menggugurkan garansi dari perangkat iOS [1]. Di Amerika sendiri, aktivitas jailbreaking terbilang legal secara hukum, namun tetap saja, aktivitas tersebut akan menghanguskan garansi. Bagaimanapun, mengingat aktivitas jailbreaking tidak meliputi aktivitas modifikasi terhadap perangkat keras, maka prosesnya bisa dengan mudah dibalik hingga kembali ke kondisi asal melalui iTunes.


* Untethered jailbreak : ketika iPhone anda dimatikan, kemudian dinyalakan kembali, iPhone anda akan kembali ke Springboard, seperti sedia kala.


* Tethered jailbreak : ketika iPhone anda dimatikan, kemudian dinyalakan kembali, iPhone anda akan tersangkut di Recovery Mode dan iTunes akan meminta anda untuk merestore kembali iPhone anda. Hal yang harus anda lakukan adalah untuk meluncurkan redsn0w, lakukan proses yang sama dengan proses jailbreak HANYA tinggal lakukan ‘Just boot tethered right now’ SAJA!
Continue reading →

Loaders new 9900, 9810, 9670, 9650, 9330

0 comments

Loaders new 9900, 9810, 9670, 9650, 9330

 

9900 https://rapidshare.com/files/2490999569/LOADER_9900.rar




9810 https://rapidshare.c...LOADER_9810.rar

9670 https://rapidshare.c...LOADER_9670.rar

9650 https://rapidshare.c...LOADER_9650.rar

9330 https://rapidshare.c...LOADER_9330.rar
 

Continue reading →

JVM Error Code & Led instrument error code Description

0 comments
Description

The following table lists errors that can occur in the Java virtual machine (JVM) on BlackBerry devices. Contact Research In Motion® (RIM®) if you encounter any error codes not listed in this table.


Value Error Description

101Previous startup failed
The device was reset during the JVM boot process. The JVM found the boot in progress flag was set on startup. The screen is intended to break continuous reset loops so that corrective action can be taken.

102Invalid code in filesystem
The system checked the COD files in the device for modification and determined that a problem exists with one or more COD files.

If all loads fail, a build process error might occur (a problem exists with signing the COD files).

If a user action on the device resulted in this problem, the reset cycle is continuous because the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system.

103 Cannot find starting address
The starting address for the boot COD file cannot be found. This might indicate that a boot COD file has not been installed on the device or that its format is invalid or corrupt.


104
Uncaught:

An uncaught Java exception was thrown by the Java code and diagnosed by the JVM. Execution can continue, or the device can be attached to a debugger on a desktop computer. The Microsoft® Windows® Event Viewer log should contain the traceback of the thrown exception.

105
Example, DbRecSize( %d ) -> %d

The file system application programming interface (API) has returned an error status for a specific operation. This might indicate a corrupt filesystem or an error in the JVM.

106
Graphics system error
An error was detected in the graphics system on the device.

107
operator new() called

A C++ class in the JVM was coded incorrectly to inherit from VMRamObject that has the correct override for operator new. Extract the current (post-reset) BUGDISP.

108
operator delete() called

A C++ class in the JVM has was coded incorrectly to inherit from VMRamObject that has the correct override for operator delete. Extract the current (post-reset) BUGDISP.

109
PriorityMessageCount error:

The value returned by RimPriorityMessageCount is negative. It should always be greater than, or equal to, zero. This indicates an error in the operating system code. Extract the current (post-reset) BUGDISP and EVENTLOG.

110
Non-idle event downtime error:

A problem was detected in the accumulation of JVM down time, which represents how long the JVM has been idle. This usually indicates an error in the device firmware or the JVM. This could also occur if the tick count rolls over after 400 or more days of device time.

111
Font engine error

An error was detected in the font engine system on the device. Extract the current (post-reset) BUGDISP and EVENTLOG.

112
Java Native Assertion Failure

An error was detected in the Java native code. Extract the current (post-reset) BUGDISP and EVENTLOG.

200
Application manager threw an uncaught exception

The application manager event thread threw an uncaught exception and cannot continue execution.

201
Crypto initialization code failed

The initialization of the crypto system failed and the device cannot continue execution.

202
An attack on the key store has been detected

An attack has been detected and execution cannot continue.


203
Console process died

The application manager console process (usually the Ribbon) has died. This is likely due to an uncaught exception during execution.

204
Persistent Content Exception

An application tried to commit a plaintext object to the Persistent Store. This will only happen if Content Protection is on and a process tries to save something in the PersistentStore that is marked as plaintext. Since this exception was not handled, the persistent store is in a bad state. You should reset to roll back to the last good commit point.
Note: This is not a JVM erro; the JVM is simply diagnosing the problem. The eventlog contains information about the erroneous Java code.


501 VM_THREAD_SWITCHED:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.

502 VM_PROCESS_DEATH:
All processes exited The last Java process has terminated. There is nothing left to execute.

503 VM_THREAD_DEATH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.

504 VM_THREAD_SWITCH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.

505 VM_BAD_CODE:
Bad Byte Code An error has occurred in the JIT compiler.

506 Uncaught Exception
An uncaught Java exception was thrown in the initial VM Java thread, thus ending the only live thread in the system. The eventlog contains the traceback for the exception.

507 Unsatisfied Link
A dependency on a COD file could not be satisfied because the COD file is missing.

508 Invalid object
A problem has been detected with a debugger command to the VM.

509 VM_PPO_INFINITE_LOOP:
infinite loop in PPO phase of GC The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count exceeds the maximum. Hence, a flaw exists in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.

510 Deadlock
All threads are waiting on objects, resulting in deadlock. The system cannot recover from this state because no thread can release a lock.

511 Debug connection died
A problem has occurred while debugging that may be caused by a VM problem or an incorrect debugging command being sent to the VM.

512 GC Aborted
An idle garbage collection has been interrupted by a user event (for instance, a key was pressed or the trackwheel was used).

513 needs running
An opcode requires that a class execute before it can continue execution.

514 needs running
A new instance of a class has been allocated and it must be initialized by the default constructor before it can be used.

515 Object group too big
The reachable objects form a group that cannot be represented properly by the JVM because either there are too many objects or the total size of the objects is too large.

516 Persistent ids exhausted
When committing a persistent object, the JVM found that the persistent store id counter reached its limit. The object was not committed and a critical error was reported. This error should not occur unless a device is heavily used for years.

517 Filesystem corrupt
An inconsistency was detected in the JVM persistent object store.

518 Unexpected longjmp
A garbage collection marking phase was terminated via a longjmp. This indicates that the marking phase was interrupted when it should have completed without interruption. This error should not occur because these actions are executed when the device is not idle, and GCs can only be interrupted when the device is idle.

519 Internal Error
The JVM host is missing or has been disabled.

520 Internal Return
This is an internal state that indicates a Java method return needs to be executed.

521 Dangerous Wait
An Object.wait() was executed by a thread that holds a lock on another object.

522 Interlaced synchronization
A thread acquired two locks on objects in an order that doesn't match the order in which a lock on the two types were previously acquired. This indicates a future potential deadlock situation and is reported. The check is only available in the simulator under the control of the JvmDebugLocks application switch.


523 System process died
A critical Java process has terminated, and the device cannot continue to operate in a normal manner.

524 LMM error
An object has been marked as recovered by the Low Memory Manager, but it was not freed during a garbage collection.

525 Bad persistent object
An auto-commit operation during a garbage collection detected a non-persistent object reachable from the persistent store root. The type of the object was output into the eventlog.

526 java.lang.Object not found
The class definition for java.lang.Object cannot be found.

527 java.lang.String not found
The class definition for java.lang.String cannot be found.

528 Corrupt filesystem.
Unrecoverable. All data will be lost All data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file was removed because the JVM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes:
Root array reference is not a valid array reference
Root array type is not Object[]
Root array size < 1 (i.e., Object[0])
Contents of root[0] is not a valid ref
Type of root[0] is not a LongIntHashtable
Persistent segmented array header contains an invalid reference
An entry in a persistent Object[] contains an invalid reference
An Object's type refers to an unknown codfile
An Object's type description in the codfile doesn't match the size in the store
A reference type field in an Object has an invalid reference in it
A reference type field in an object points to an object of the wrong type
A persistent Object[] is missing its descriptor
Object in persistent store is not marked as persistable
Root array is segmented and one of the segments is invalid


529 Corrupt filesystem.
About to attempt recovery. Some data may be lost Some data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file WAS removed because the VM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes:
Root array reference is not a valid array reference
Root array type is not Object[]
Root array size < 1 (i.e., Object[0])
Contents of root[0] is not a valid ref
Type of root[0] is not a LongIntHashtable
Persistent segmented array header contains an invalid reference
An entry in a persistent Object[] contains an invalid reference
An Object's type refers to an unknown codfile
An Object's type description in the codfile doesn't match the size in the store
A reference type field in an Object has an invalid reference in it
A reference type field in an object points to an object of the wrong type
A persistent Object[] is missing its descriptor
Object in persistent store is not marked as persistable
Root array is segmented and one of the segments is invalid


530 VM_PREVENT_GC_OVERFLOW: _preventGC overflow
A fixed number of native objects can be protected from garbage collection. This error indicates that a native has exceeded the fixed limit of objects that can be protected. If the device is reset or thread tracebacks are logged, the name of the actual native can be extracted.

531 Flash exhausted
There are certain operations where the JVM cannot withstand running out of flash space. In these circumstances, this error will be reported if the JVM cannot allocate a required amount of flash space.

532 VM_ASSERTION_FAILED:
Assertion failed Normally this JVM error should not be reported since the device is not shipped with assertions enabled. The simulator may report this error in debug mode indicating a VM assertion was violated. Try typing BKPT to activate the debugger and dump the native call stack for forwarding to the VM team.

533 VM_RUN_METHOD: needs running
This is used internally for ECMAScript to call Java methods.

534 VM_FAST_RESET_DISABLED:
Fast Reset Disabled This is used internally to indicate that fast reset capability is not available. Often used in platform-specific code.

535 VM_UNUSED_535:
Unused This is an unused VM error.

536 VM_FAST_RESET_BAD_INSTANCE: VM Instance Check Failed
This is used internally to indicate that the VM structure passed in is at the wrong address or has been corrupted.

537 VM_FAST_RESET_BAD_HEAP: Heap Check Failed
This is used internally to indicate that the VM heap has been corrupted or pointers into the heap have been corrupted.

538 VM_FAST_RESET_BAD_IRAM: IRAM Check Failed
This is used internally to indicate that the VM IRAM checks have detected corruption of VM data structures (threads and local stacks) that reside in IRAM.

539 VM_FAST_RESET_NOT_IDLE: Not Idle
This is used internally to indicate that the VM was not idle when the reset occurred and, as such, cannot continue with a fast reset.

540 VM_FAST_RESET_MULTIPLE_RESETS: Multiple Resets
This is used internally to indicate that the time since the last fast reset is less than a minimum time. By disallowing multiple fast resets in a short amount of time, this should prevent fast reset loops.

541 VM_HEAP_COMPACT_INFINITE_LOOP: infinite loop detected in heap compaction
The VM detected a problem in its RAM heap that indicates its RAM was corrupted. The problem was detected by identifying a possible infinite loop during RAM heap compaction. A bugdisp log and eventlog should be extracted quickly when the device is in this condition. If possible, images of RAM should be saved.

542 Transient memory leak
The JVM detected that some memory was not freed, indicating that a memory leak has occurred. This condition is detected as early as possible to improve chances of isolating the cause.


543 VM_FS_MISMATCH: Incompatible Java filesystem installed
The VM detected that the operating system binary is different from the operating system binary used to create the Java file system. This means that the Java native methods may not be linked properly and as such, the integrity of the system cannot be guaranteed. The system can be recovered by using the VM DLFX and DLPS commands to delete the fixups and persistent store. This will clear all data and fixups and let the filesystem re-link to match the new operating system binary.
Note: The recovery order is:

Delete fixups
Delete persistent store
Reset device

544 VM_SECTION_MAP_OVERFLOW: a module references more than 255 other modules
The VM detected that a module is trying to reference more than 255 other modules. Extract the filesystem immediately when this error is
detected.

545 VM_INCOMPATIBLE_FILESYS: an incompatible or corrupt filesystem was found
The VM detected an incompatible or corrupt filesystem. Extract the filesystem immediately when this error is detected.

546 VM_UNUSED_546: unused
The VM detected that the RAM image of its filesystem is corrupted (failed CRC check). Better to reset than to duplicate the corruption into flash.

547 VM_UNUSED_547: unused
This is an unused VM error.

548 VM_UNUSED_548: unused
This is an unused VM error.

549 VM_UNUSED_549: unused
This is an unused VM error.
Continue reading →

Fix Disabled iPod

0 comments
Fix Disabled iPod 
 


Continue reading →

A-key Calculator v1.0 FULL

0 comments
A-key Calculator v1.0 FULL



Posted Image 
 Cara pakai:
1. Dobel klik a-key.key dulu baru kemudian jalankan Cave.exe
2. Isi kolom ESN dan sesuaikan apakah menggunakan bilangan hex atau decimal
3. Dibawah kolom ESN ada 2 kolom kiri dan kanan,yang sebelah kiri itu angka yang bisa kita isi sendiri semau kita sebanyak 20 digit. Tetapi 2 digit pertama tidak boleh diatas "11".
Contoh: 06xxx,08xxx,09xxx,ataupun 11xxx tetapi tidak boleh 12xxx,dst
4. Kolom kiri dan kanan digabung dan jadilah 26 digit A-Key 
 


DOWNLOAD
Continue reading →

Iphone Model List According to countries

0 comments
Iphone Model List According to countries





Setting>General>About

Iphone4 Model

Egypt

16G MC603AB/A
32G MC605AB/A

******

16G MC603AB/B
32G MC605AB/B
******************

South Africa

16G MC603SO/A
32G MC605SO/A




United Arab Emirates

16G MC603AB/B
32G MC605AB/B
***************

Australia

16G MC603X/A
32G MC605X/A


China

16G MC603CH/A
32G MC605CH/A
****************

Hong Kong

16G MC603ZP/A
16G MC607ZP/A
32G MC605ZP/A
***************

Japan

16G MC603J/A
32G MC605J/A
***************

Korea

16G MC603KH/A
32G MC605KH/A
***************

Macau

16G MC603ZP/A
32G MC605ZP/A
***************

Malaysia

16G MC603ZA/A
32G MC605ZA/A
***************

New Zealand

16G MC603X/A
32G MC605X/A
***************

Philippines

16G MC603PP/A
32G MC605PP/A
***************



Singapore

16G MC603ZA/A
32G MC605ZA/A
***************

Taiwan

16G MC603TA/A
32G MC605TA/A
***************

Thailand

16G MC603TH/A
32G MC605TH/A
***************

Bulgaria

16G MC603BG/A
32G MC605BG/A
***************

Danmark

16G MC603KN/A
32G MC605KN/A
***************

Germany

16G MC603DN/A
32G MC605DN/A
***************

Estonia

16G MC603EE/A
32G MC605EE/A
**************

Spain

16G MC603Y/A
32G MC605Y/A
**************

France

16G MC603NF/A
16G MC603FB/A
32G MC605NF/A
32G MC605FB/A
***************

Greece

16G MC603GR/A
32G MC605GR/A
***************

Croatia

16G MC603CR/A
32G MC605CR/A
***************

India
MC603HN - 16GB Black
MC605HN - 32GB Black
********************

Ireland

16G MC603B/A
32G MC605B/A
**************

Italy

16G MC603IP/A
32G MC605IP/A
**************

Latvia

16G MC603LV/A
32G MC605LV/A
**************



Liechtenstein

16G MC603FD/A
32G MC605FD/A
***************

Luxembourg

16G MC603NF/A
16G MC603FB/A
32G MC605NF/A
32G MC605FB/A
***************

Macedonia

16G MC603MM/A
32G MC605MM/A
****************

Malta

16G MC603B/A
32G MC605B/A
**************

Moldova

16G MC603RO/A
32G MC605RO/A
***************

Montenegro

16G MC603MM/A
32G MC605MM/A
***************

Netherlands

16G MC603DN/A
32G MC605DN/A
****************

Norway

16G MC603KN/A
32G MC605KN/A
***************

Austria

16G MC603FD/A
32G MC605FD/A
***************

Poland

16G MC603PL/A
32G MC605PL/A
***************

Portugal

16G MC603PO/A
32G MC605PO/A
***************

Romania

16G MC603RO/A
32G MC605RO/A
***************

Russia

16G MC603RS/A
32G MC605RS/A
***************

Slovakia

16G MC603SL/A
32G MC605SL/A
***************

Switzerland

16G MC603FD/A
32G MC605FD/A
***************

Finland

16G MC603KS/A
32G MC605KS/A
***************

Sweden

16G MC603KS/A
32G MC605KS/A
***************

Turkey

16G MC603TU/A
32G MC605TU/A
***************

UK

16G MC603B/A
32G MC605B/A
**************


Argentina

16G MC603LE/A
32G MC605LE/A
**************

Brazil

16G MC603BZ/A
32G MC605BZ/A
**************

Chile

16G MC603LZ/A
32G MC605LZ/A
***************

Colombia

16G MC603LA/A
32G MC605LA/A
****************

Republic of Dominican

16G MC603LA/A
32G MC605LA/A
**************

Ecuador

16G MC603LA/A
32G MC605LA/A
**************

El Salvador

16G MC603LA/A
32G MC605LA/A
**************

Guatemala

16G MC603LA/A
32G MC605LA/A
***************


Honduras

16G MC603LA/A
32G MC605LA/A
***************


Jamaica

16G MC603ZQ/A
32G MC605ZQ/A
***************


Mexico

16G MC603E/A
32G MC605E/A
***************


Nicaragua

16G MC603LA/A
32G MC605LA/A
**************


Panama

16G MC603LA/A
32G MC605LA/A
**************


Paraguay

16G MC603LZ/A
32G MC605LZ/A
***************


Peru

16G MC603LA/A
32G MC605LA/A
***************


Uruguay

16G MC603LZ/A
32G MC605LZ/A
**************


Canada

16G MC603C/A
32G MC605C/A
**************


USA

16G MC608LL/A
16G MC318LL/A
32G MC610LL/A
32G MC319LL/A
**************
Continue reading →

video panduan cara bongkar iPad2

0 comments



Continue reading →

Warning -- be aware of new iphone 3gs update not unlock it whit ipad baseband

0 comments
Apple has released a brand new iPhone 3GS that have a new bootroom this 28 weeks of 2011.
Version is 4.3.5 with baseband 5.14.
A lot of jailbreakers and unlockers have encountered that when you update this baseband to 6.15 to unlock it,

You got corrupted baseband and it cannot used anymore.
Symptoms are:
No wifi
No ECID
No Imei
No bluetooth

as of now all informations i've got is all serial up to XXX109XXX is risky to update baseband.

XX109XX = 1 is the year of 2011 and 09 is week 9 of 1 year.
so if serial is XX931XXX means 2009 with week 31.
and its safe to update baseband.

Much better check the serial first before you update to baseband 6.15






THANX FOR EVERY ONE WORKS ON THIS INFO..And be carful.
Continue reading →

Tutorial cara install android di iPhone

0 comments
Tutorial cara install android di iPhone

Langsung to the point aja yah gan

PREPARE YOUR IPHONE


banyak sekali pilihan untuk melakukan jailbreaking antara lain dengan menggunakan PwnageTool, Redsn0w, and Blackra1n. pilih salah satu yang cocok denganmu.

untuk bisa melakukannya, pilih Cydia dari homescreen->Manage->Sources->Edit->Add. repository yang diperlukan adalah repo.neonkoala.co.uk. tap Add Source, biarkan Cydia bekerja lalu tap repository yang sudah kamu tambahkan dan install bootlace.

tutup cydia lalu jalankan bootlace, kalo belum ada bootlace di homescreenmu reboot iphonemu. lalu jalankan bootlace dan biarkan dia mendownload patch kernel terbaru. kalo sudah selesai tap Reboot dan biarkan iphonemu melakukan reboot

lalu jalankan bootlace lagi, lalu tap OpeniBoot dan tap install. OpeniBoot akan di download dan diinstall


keltika OpeniBoot sudah diinstall tap iDroid->Install->OK lalu tunggu. proses ini memakan waktu agak lama, pastikan baterai iphonenya masih full ato dicharge aja kalo mau habis.

nah sekarang Android sudah terpasang di Iphonemu. untuk menjalankannya tap QuickBoot pada Bootlace, lalu tap ikon Android. lalu confirm untuk melakukan reboot ke Android.
Continue reading →

MEMBEDAKAN IPHONE FU (FACTORY UNLOCK ) dgn IPHONE SU (SOFTWARE UNLOCK)

0 comments
Apa itu iPhone FU & SU?:

iPhone FU (Factory Unlock):


* iPhone yang bisa dicolok SIM card apa aja langsung tanpa proses unlock, karena iPhone jenis ini udah diunlock langsung dari pabrik.
* Keuntungan iPhone FU adalah bisa langsung dipakai tanpa harus menunggu unlock tools dulu.
* Keuntungan lain iPhone FU adalah Push Notificationnya berjalan lebih sempurna.



iPhone SU (Software Unlock):

* iPhone yang agar bisa dipakai dengan SIM card Indonesia harus melalui proses unlock, karena iPhone jenis ini locked ke carrier negara asal.
* Keuntungan iPhone SU adalah harganya yang lebih terjangkau daripada iPhone jenis FU.

Bagaimana membedakan iPhone FU dan SU?

Kalau berencana keluar negeri dan membeli iPhone di sana, cek dulu apakah negara itu menjual iPhone FU atau SU.
Lihat link di bawah, bagian kolom Locked to carrier, kalau dicentang berarti iPhone negara itu SU, kalau tidak berarti FU.

http://support.apple.com/kb/HT1937

Cek model number iPhone (Setting > General > About > Model) dan bandingkan dengan list model number iPhone FU

Mana yang sebaiknya dibeli, iPhone FU atau iPhone SU?

* Kalau punya budget cukup, disarankan membeli iPhone FU agar tidak kesulitan dalam update firmware berikutnya, karena makin ke depan Apple semakin memperkuat proteksi iPhone.
* Kalau budget hanya cukup untuk membeli iPhone SU, tidak masalah, TAPI harus memperhatikan firmware yang dipakai iPhone SU tersebut dan terus memantau perkembangan unlock tools yang tersedia. Jangan sembarang mengupdate firmware!


Tips membeli iPhone selain memperhatikan FU - SU

# Pastikan iPhone yang mau dibeli itu adalah Apple iPhone, bukan iPhone replika. Apple iPhone tidak punya fasilitas dual SIM card, TV, dan Bluetooth yang bisa terhubung dengan handset lainnya. Kalau ada yang menawarkan kelebihan itu di iPhonenya, bisa dipastikan itu iPhone replika.
# Cara lain mengecek iPhone replika/tidak dengan mencoba layar sentuhnya, layar Apple iPhone yang asli tidak responsif bila hanya ditekan menggunakan kuku. Kalau bisa menggunakan kuku, bisa dipastikan itu iPhone replika.
# Cek firmware yang digunakan (Settings > General > About > Version). Tanyakan apakah versi itu sudah bisa diunlock (khusus iPhone SU) atau dijailbreak (khusus yang mau menjailbreak iPhonenya).
# Cek kelengkapan standar, kualitas layar (ada deadpixel/tidak), tombol Home berfungsi/tidak, suara speaker (speaker iPhone hanya 1 sisi, sebelah kiri, sedangkan sebelah kanan adalah mic), Accelerometer sensor, dsb.
# Last but not least, pastikan anda membawa dompet waktu mau transaksi beli iPhone
Continue reading →
Wednesday, November 23, 2011

BlackBerry Bold 9000 Keypad solution

0 comments
BlackBerry Bold 9000 Keypad solution

BlackBerry Full keypad Jumper 








Continue reading →

BlackBerry Upgrade Instructions

0 comments
Upgrade instructions



This document contains information on upgrading to BlackBerry™
Desktop Software version 3.6 or later. It also contains information on
upgrading your BlackBerry handheld software.
Contents

• Upgrading the desktop software
• Adding handheld applications to the desktop software
• To verify whether handheld applications have been added to
the desktop software
• To add handheld applications to the desktop software
• Connecting to the desktop software
• To verify the desktop-to-handheld connection
• Loading handheld applications
• System requirements
• System requirements for handhelds with serial connectors
• System requirements for handhelds with USB connectors

2 Upgrade instructions
Upgrading the desktop software
1. If it is open, close the BlackBerry Desktop Manager.
2. Download the appropriate file for upgrading your desktop software.
3. Double-click the .exe file that you downloaded.
4. The Choose Setup Language dialog box might appear. Select your language and
click OK. The Welcome window appears.
5. Click Next. The Country or Region Selection window appears.
6. Select your country and click Next. The License Agreement window appears.
Read the License Agreement carefully and, if you accept its terms, click Yes. The
Customer Information window appears.
7. Follow the on-screen instructions.
If your system administrator has not configured your desktop software upgrade, you
might need to add handheld applications to the desktop software before you load
applications onto your handheld. Refer to "Adding handheld applications to the
desktop software" below for more information.
If your system administrator has configured the desktop software upgrade and added
handheld applications to the desktop software, you can load applications onto your
handheld but you do not need to add applications to the desktop software. Refer to
"Loading handheld applications" on page 4 for more information.
Adding handheld applications to the desktop
software
After you upgrade the desktop software, you might need to add handheld
applications to the desktop software manually to complete one of the following
actions:
• upgrade your handheld
• install software from a different service provider
• switch to a different handheld model
• add third-party applications to your handheld
Note: To add handheld applications to the desktop software, your desktop software must be
version 3.6 or later.
You are solely responsible for the selection, implementation, and performance of any
third-party applications that you use with the desktop software or the handheld. Research In
Motion Limited does not in any way endorse or guarantee the security, compatibility,
performance, or trustworthiness of any third-party application, and shall have no liability to you
or any third party for issues arising from such third-party applications.



Upgrade instructions 3
To verify whether handheld applications have been added to
the desktop software
1. On the Windows taskbar, click Start. Select Programs > BlackBerry > Desktop
Manager. The BlackBerry Desktop Manager appears.
2. On the Help menu, click About Desktop Manager. The About Desktop Manager
screen appears.
3. Click the Handheld Software tab. A screen appears and displays installed
handheld application software.
• If the screen is blank, no handheld applications have been added to your
desktop software. You must add handheld applications to the desktop
software before you can load them onto your handheld. Refer to "To add
handheld applications to the desktop software" below for more information.
• If the screen displays the name of your handheld series, applications have
already been added to your desktop software and you can load applications
using the Application Loader tool. Refer to "Loading handheld applications"
on page 4 for more information.
To add handheld applications to the desktop software
Depending on your system administrator or service provider, you can download the
latest handheld applications from your service provider or network operator web site.
Contact your system administrator or service provider for more information.
1. If it is open, close the BlackBerry Desktop Manager.
2. Download the file for the handheld applications that you want to add to your
desktop software.
3. Double-click the .exe file that you downloaded.
4. The Choose Setup Language dialog box might appear. Select your language and
click OK. The Welcome window appears.
5. Click Next. The handheld applications are added to your desktop software.
6. Click Finish.
You can now connect your handheld to your computer, start the desktop software,
and use the Application Loader tool to load applications onto your handheld. Refer to
"Loading handheld applications" on page 4 for more information.
Connecting to the desktop software
To use the desktop software, your handheld must be connected to your computer.
Note: You are solely responsible for verifying that the handheld applications that you
download are appropriate for, and compatible with, your handheld.



4 Upgrade instructions
To verify the desktop-to-handheld connection
1. In the desktop manager, on the Options menu, click Connection Settings. The
Connection Settings window appears.
2. Click Detect. A warning dialog box appears, prompting you to verify that your
handheld is connected properly.
3. Click OK. The software notifies you when the handheld has been detected.
4. Click OK to close the Connection Settings window.
If the connection is successful, the desktop manager displays your handheld PIN and
current handheld connection status (now Connected) in the status bar at the bottom
of the window.
Loading handheld applications
Use the Application Loader tool to load applications onto your handheld.
1. Verify that your handheld is connected to your computer.
2. Start the desktop software: on the Windows taskbar, click Start and select
Programs > BlackBerry > Desktop Manager. The BlackBerry Desktop Manager
appears.
3. Double-click the Application Loader icon. The Welcome to the Application
Loader window appears.
4. Click Next. The desktop software reads the handheld’s configuration, and
depending on your handheld, the LCD screen displays Loader activity or an icon.
At the same time, the Handheld Application Selection window appears on your
computer.
5. Select the check boxes beside the applications that you want to load.
Note: A dialog box with the message Handheld not found appears on your computer if the
desktop software cannot detect your handheld. If your handheld is connected securely, verify
that no other devices are sharing the port, such as a PC card. Verify that no other connectivity
software is running on your computer, and that you are not using the same port that your
mouse uses.
Note: If the software on your handheld is not current, the Application Updates Available dialog
box appears. To update your handheld software, click Update Now. The Application Loader
Wizard appears. If you are unsure of the status of your handheld software or your computer
software, click Cancel. If you click Cancel, the Application Updates Available dialog box
appears each time that you start the desktop software.
Note: If a message appears to indicate that no system software is available for your handheld,
you have not added handheld applications to the desktop software. You must add handheld
applications to your desktop software before you use the Application Loader tool. Refer to
"Adding handheld applications to the desktop software" on page 2 for more information.

Upgrade instructions 5
6. Click Next. A summary window displays the actions that will occur during the
loading process.
7. Click Finish. If necessary, the Application Loader tool backs up your handheld’s
data and loads the applications onto your handheld.
8. When the loading process is complete, the Application Loader indicates whether
the process was successful. Click Close.
After the loading process is complete, you might need to turn on your handheld radio
to send and receive email messages. Refer to the documentation that came with your
handheld for more information.
System requirements
System requirements for handhelds with serial connectors
If you connect your handheld to your computer using a serial port, the following
components are required to upgrade the desktop software:
• Intel®-compatible 486 or higher computer with an available serial port
• Windows® 98, Windows Me, Windows 2000, Windows XP, or Windows NT 4.0
Service Pack 6 or later
Warning: Do not disconnect your handheld from your computer until the loading process is
complete. If the loading process is interrupted, your handheld applications might not load
correctly. If an interruption occurs, you must repeat the loading process.
Microsoft
Exchange
Microsoft® Exchange Client, Microsoft Outlook® 98, 2000, or XP (Corporate or
Workgroup Installation) with an email account on a Microsoft Exchange
Server version 5.5 or later that can receive email from the Internet.
Lotus Domino Lotus Notes® 4.6 or later, with an email account on a Lotus® Domino™ Server
version 4.6 or later that can receive email from the Internet.
Integration
with new or ISP
email account
To set up your BlackBerry Web Client account, you must have access to the
Internet. You must also have Netscape® Navigator version 4.08, 4.58, or later
patches, or Microsoft Internet Explorer version 5.01, 5.5, 6.0, or later patches.
(You cannot use Netscape Navigator version 5.0.)
Note: To use the Intellisync™ tool of the BlackBerry Desktop Software, you must be running
personal information management (PIM) software, such as Microsoft Outlook, Microsoft
Exchange, or Microsoft Schedule+; ACT!®; Lotus Notes or Lotus Organizer®; GroupWise®;
GoldMine®; or Netscape®.

6 Upgrade instructions
System requirements for handhelds with USB connectors
If you connect your handheld to your computer using a USB port, the following
components are required to upgrade the desktop software:
• Intel-compatible 486 or higher computer that is compliant with USB 1.1 or higher
• An available USB port
• Windows 98, Windows Me, Windows 2000, or Windows XP
Note: This document is provided for informational purposes only, and does not constitute a binding legal
document. RIM assumes no responsibility for any typographical, technical or other inaccuracies in this
document, and makes no warranties, express or implied, with respect to the content of this document. RIM
reserves the right to periodically change information that is contained in this document; however, RIM
makes no commitment to provide any such changes, updates, enhancements or other additions to this
document to you in a timely manner or at all. IN NO EVENT SHALL RIM BE LIABLE TO ANY PARTY
FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES FOR ANY USE OF THIS
DOCUMENT, INCLUDING WITHOUT LIMITATION, RELIANCE ON THE INFORMATION
PRESENTED, LOST PROFITS OR BUSINESS INTERRUPTION, EVEN IF RIM WAS EXPRESSLY ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES.
Any software that is provided with this document will be governed by the terms and conditions of the RIM
software license provided to you with your RIM wireless handheld, the RIM BlackBerry Enterprise Server
Software, or any upgrade to your desktop, handheld, or BlackBerry Enterprise Server Software, as
applicable, and, by using the software provided with this document, you agree to be bound by such terms.
Note: If you use Windows 98 (not Windows 98 Second Edition), you must download an update
from http://www.microsoft.com/com/dcom/dcom98/dcom1_3.asp. before the USB drivers will
operate as expected.
Microsoft
Exchange
Microsoft Exchange Client, Microsoft Outlook 98, 2000, or XP (Corporate or
Workgroup Installation) with an email account on a Microsoft Exchange
Server version 5.5 or later that can receive email from the Internet.
Lotus Domino Lotus Notes 4.6 or later, with an email account on a Lotus Domino Server
version 4.6 or later that can receive email from the Internet.
Integration
with new or ISP
email account
To set up your BlackBerry Web Client account, you must have access to the
Internet. You must also have Netscape Navigator version 4.08, 4.58, or later
patches, or Microsoft Internet Explorer version 5.01, 5.5, 6.0, or later patches.
(You cannot use Netscape Navigator version 5.0.)
Note: To use the Intellisync tool of the BlackBerry Desktop Software, you must be running
personal information management (PIM) software, such as Microsoft Outlook, Microsoft
Exchange, or Microsoft Schedule+; ACT!; Lotus Notes or Lotus Organizer; GroupWise; GoldMine;
or Netscape.

Upgrade instructions 7
Warning: This document is for the use of licensed users only. Any unauthorized copying, distribution or
disclosure of information is a violation of copyright laws. No reproduction in whole or in part of this
document may be made without express written consent of RIM.
© 2003 Research In Motion Limited. All rights reserved. The BlackBerry and RIM families of related marks,
images and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion,
’Always On, Always Connected’, the “envelope in motion” symbol and the BlackBerry logo are registered
with the U.S. Patent and Trademark Office and may be pending or registered in other countries. All other
brands, product names, company names, trademarks and service marks are the properties of their
respective owners. The handheld and/or associated software are protected by copyright, international
treaties and various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605;
6,219,694; 6,075,470; 6,073,318; D,445,428; D,433,460; D,416,256. Other patents are registered or pending in
various countries around the world. Please visit www.rim.com/patents.shtml for a current listing of
applicable patents. Published in Canada.
Continue reading →