Sony Xperia M2 Aqua Not Charging Problem Repair Solution

                                                                      Sony Xperia M2 D2402 D2406 Charging Ways Solution JumperThis post serves as your troubleshooting guide in case your Sony Xperia M2 Aqua won’t charge. Whether you are charging with Samsung’s manufacturer charger or a wireless charging pad, charging issues are among the most common problems any Android smartphone owner may face. It is also among the problems that need to be addressed immediately as your phone will only sit atop your table when it totally depletes its battery.

Solution 

Before doing, Be sure to check the battery and charger are Exactly working condition. then verify the phone’s USB pin connector is broken or any fault.

Check the charging (+) and (-) line paths are short using multimeter, if it shows short them, remove/replace the diode, capacitors and filers. also replace the fuse. Note: use these work at your own risk.

Check all the components shown on the image below.

Repair hints for Sony Xperia M2 Aqua Not Charging Problem:
1. Try to use another working charger.
2. Check, clean or replace the charging pin connector if oxidized.
3. Clean the charging pin connector terminal contact pads.
4. Check/ replace the fuse and the chip diode.
5. Check/replace the highligted transistor, resistors and capacitor.
6. If the above procedure won’t fix the problem, the possible faulty Charging IC.
7. Reheat, rework charging ic, replace if necessary.

Samsung Explains Why the Galaxy Note 7 Kept Exploding

     

                                              Samsung has released its official report on why the batteries in the Galaxy Note 7 smartphone were exploding. Notably, the issues differed between the original battery and the replacement battery used after the first recall.

“For the last several months, together with independent industry expert organizations, we conducted thorough investigation to find cause to the Galaxy Note7 incidents,” DJ Koh, President of Mobile Communications Business said. “Today, more than ever, we are committed to earning the trust of our customers through innovation that redefines what is possible in safety, and as a gateway to unlimited possibilities and incredible new experiences.”

Based on what the company learned from the investigation, Samsung implemented a broad range of internal quality and safety processes to further enhance product safety including additional protocols such as the multi-layer safety measures and 8-Point Battery Safety Check. Samsung also formed a Battery Advisory Group of external advisers, academic and research experts to ensure it maintains a clear and objective perspective on battery safety and innovation. 

Here are some of the main issues uncovered by the investigation:

Root Cause: Manufacturer A

Based on the results of analysis and testing, the most likely root cause for the thermal failure of certain Manufacturer A cells was determined to be unintended damage to the negative electrode windings consistently in the corner of the cell closest to the negative tab

Root Cause: Manufacturer B

Based on the results of analysis and testing, the most likely root cause for the thermal failure of Manufacturer B cells was determined to be internal cell faulting between positive electrode tab welding defects and the copper foil of the negative electrode directly opposite the defective welds

Check out the infographic below for more details...

Semi-Restore tutorial: How to wipe your iDevice without doing a full restore (iOS 5.0-6.1.2)

 

 

Last month we brought you news that there was a new iOS restore tool in the works called Semi-Restore. Semi-Restore is a next-to last resort for iOS issues. If you've done everything you can think of to fix your sluggish firmware to no avail and you have a device which doesn't have SHSH blobs for a jailbreakable firmware or you simply have a device that cannot be downgraded, Semi-Restore will wipe your iOS installation clean without actually doing a full restore.
Semi-Restore is available now as a Windows and OSX GUI tool, there is a Linux version in development and there is also an SSH version for advanced users available now. Remember that you should only be using this method if you've tried everything else to solve your problems as this method is much like a complete restore. This method is compatible with any jailbroken iOS device running firmware 5.0-6.1.2
Step 1: Download Semi-Restore for Windows or for OSX
Step 2: Connect your device and open the tool, you will be greeted with this welcome screen containing your device and iOS information:

Step 3: Once you are sure you want to proceed(this process is not reversible) simply hit the "SemiRestore" button and you're off! The device will reboot multiple times during this process which is normal, just let it do it's thing.
Step 4: Once the device reboots, you will see "cleaning up" and then you will see the screen below. At this point your device will reboot again and you will see the loading bar like you would in a normal restore.

Step 5: Once your device reboots you will have to complete the initial setup process like you would a normal restore. Once that is complete you will notice that your device looks exactly like a stock device after a normal iTunes restore, with one exception. You will still have Cydia on your springboard! That's right, this process retains your jailbreak so you don't have to go through that process again. Once it's done you're ready to go and you can immediately start reinstalling tweaks and themes!
 

            Skype for iPhone Update Brings  Back URI Support

 

 

 

Skype for iPhone has received an update that brings back URI support, offers new improvements to the dialer, and improves chat notification reliability.

Skype 5.10 for iPhone brings support back for Skype URIs, which enable developers to easily use Skype’s messaging and calling infrastructure to start calls and chats straight from their mobile app or mobile website, rather than building their own. As long as the Skype app is installed on an iPhone, when a user taps on a Skype name or phone number, the URI will open the Skype app to connect a call or send a message*, making it faster than ever to reach friends, family or businesses.

Features:
• Find all your friends and family in an instant - With over 300 million people using Skype, you’re bound to bump into someone you know.
• Talk with your fingers - No matter where you are, your friends are always available with free messaging.
• Call your world from Skype - Free voice and video calls let you talk to your heart’s content with all your friends and family on Skype.
• Low cost calls to mobiles and landlines too - Keep in touch, even if they’re not on Skype, with low cost calls to mobiles and landlines on the other side of town or the world.
• Share your favorite snaps - Take a great photo you want to share? Send it over Skype to friends and family and you won’t have to worry about email size limits or expensive MMS charges.
• Video messaging – Record life’s everyday moments and share them with the people who matter most, with free and unlimited video messaging over Skype.
• Chat with anyone, anywhere - Skype’s available on smartphones, tablets, Macs, PCs, and even TVs. Whatever your friends or family use, Skype is there. Simple.

What's New In This Version:
·        Improved chat notification reliability - we are continuing to work on improving reliability but if you encounter issues please let us know by tapping your profile picture, tapping the more button and selecting send feedback
·        Now save phone numbers entered into the dial pad and numbers in the recent calls list
·        General Improvements

You can download Skype for iPhone from the App Store for free.
Read More [Download]

Z3X-BOX Samsung Update v18.9. New phones added, QCN reader/writer changes Samsung Tool 18.9 Update. Some new phones added. New phones added: - support S5570B (Flashing, Direct unlock/imei repair, read/write QCN) - support GT-S7390g (flashing, Unlock, Imei repair, Network repair, READ/WRITE cert) - support SM-J100H (flashing, Unlock, Imei repair, Network repair, READ/WRITE cert) BETA - first in the world - support SM-G800H (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G530FZ (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - first in the world - support SM-G5108 (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G5108Q (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G5109 (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G5306W (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G5308W (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) - support SM-G5309W (Flashing, WIPE efs, write CERT, Read/write QCN, Auto detect CERT compatiblity) Addition function added for: - I9060 (cert Read/Write) - I9060L (cert Read/Write) - I9063T (cert Read/Write) - I9080E (cert Read/Write) - I9082C (cert Read/Write) - S7390 (cert Read/Write) - S7390E (cert Read/Write) - S7390G (cert Read/Write) - S7390L (cert Read/Write) - S7392 (cert Read/Write) - S7392L (cert Read/Write) - S7580 (cert Read/Write) - S7580L (cert Read/Write) - S7582 (cert Read/Write) - S7582L (cert Read/Write) - S7583T (cert Read/Write) - SM-P601 (cert Read/Write) - SM-P602 (cert Read/Write) - SM-P901 (cert Read/Write) - SM-T311 (cert Read/Write) - SM-T312 (cert Read/Write) QCN Reader/Writer - new supported MCU added. Fixed: G530H/G530H cert writing for SIM2 (need double cert file!!!!) Discuss here

Unlock iOS 6 On iPhone 4/iPhone 3GS With Ultrasn0w Fixer

Those of you who were unwilling to update to the latest iOS 6 because there was no unlock available can now update because Ultrasn0w Fixer can now unlock iOS 6 for iPhone 4 and 3GS. 

iOS 6 Utrasn0w Fixer unlock
This is not the ultrasn0w official tool. However, it works with the official tool for basebands that are compatible, and can be unlocked by the official ultrasn0w. It can be used until there’s an update for the official tool to unlock the latest iOS 6 firmware.
iOS 6 Ultrasn0w fixer supported devices

• iPhone 3GS
• iPhone 4

iOS 6 ultrasn0w fixer supported basebands

• 01.59.00 (iPhone 4)
• 04.26.08 (iPhone 3GS)
• 05.11.07 (iPhone 3GS)
• 05.13.01 (iPhone 3GS)
• 05.12.01 (iPhone 3GS)
• 06.15.00 (iPhone 3GS)

How to unlock iOS 6 on iphone 4/ iPhone 3GS Using Ultrasn0w fixer:


Step 1: Jailbreak your i device @ ios 6

Step 2: Launch Cydia.
Step 3: Open Manage > Sources. Tap ‘Edit’ at the right corner at the top and add this repo:

http://repo.iparelhos.com

Step 4: Tap on the URL you entered above.
Step 6: Ultrasn0w fixer for iOS 6 will be visible. Start the process by tapping on it.
Step 7: Download the official tool of ultrasn0w unlocker.
Congrats. You would now be able to get the iOS 6 unlock for iPhone 4/3GS. This can be used until the official tool is updated. Remember to download the ultrasn0w fixer first before the official tool.

iPhone Dev-Team Announces Massive Update to RedSn0w

The iPhone Dev-Team has announced RedSn0w 0.9.15b1 which brings numerous new features including the ability to restore to older firmware not being signed by Apple.

New Features:
● restore from any 5.x iOS to any other (up, down or the same) 5.x iOS on all devices as long as you have the correct blobs (see more below)
● Cydia now included in the tethered 6.0 jailbreak on A4 devices
● automatically "Just Boot" tethered when qualifying A4 device connects in DFU mode
untethered 6.0 jailbreak on old-bootrom 3GS
● untethered 6.0 hactivation on any 3GS or iPhone4
● directly restore pre-A5 devices to earlier firmware - no more complicated 15-step how-to's with stitching, iTunes errors, and "hosts file" concerns
● fetch new signed blobs for any IPSW (present or future - no redsn0w update required) using Extras->SHSH Blobs->New
● block the BB update for any 3GS or iPhone4 restore (past, present, or future - no redsn0w update required) using Extras->Even More->Restore
● deactivate any iPhone, useful for testing your "official" unlock status through iTunes. (Please only deactivate your own iPhone!)
● activation status shown on "Even more" page
● significantly more (very nerdy) info returned by "Identify" button when device is in Normal mode
● tethered jailbreak of ATV2 supported (but the only thing available for it is the SSH2 custom bundle available here - no Cydia yet. Must use "Select IPSW" for tethered boot of ATV2 for now).
● auto-exit WTF mode for older devices with broken buttons
● any time a set of blobs is fetched remotely (from Apple or Cydia), redsn0w also saves them locally (and will check there first if you click "Local")
● for your future restoring convenience, you should also submit all of your past and present TinyUmbrella blobs to Cydia if you haven't done so yet. Resubmitting is okay and won't cause conflicts.


iOS 5 to iOS 5 Restores for A5+ Devices

1. redsn0w now lets you restore an A5+ device from any iOS5 to any other iOS5 as long as you have correct 5.x blobs for the starting (current) and ending points of the restore
● APtickets eliminated "higher-version only" comparison of firmware restores (just like BBtickets did for the baseband)
● example restores supported by redsn0w if you have the correct blobs: 5.1.1-to-5.0.1, 5.0.1-to-5.1.1, 5.1.1-to-5.1.1, 5.0.1-to-5.0.1
● if you don't have the blobs locally, let redsn0w try to fetch them remotely (redsn0w always tries both Apple and Cydia). Any succesful remote fetch also saves a local copy too.

2. You DO NOT QUALIFY for iOS5-to-iOS5 restores if you got to your current 5.x via an OTA update
● the tickets saved by Cydia, redsn0w, and TinyUmbrella do not cover OTA update ramdisk images 
● even if they did, it's the "wrong kind" of ramdisk (you'd need to start at that earlier pre-OTA FW)
● devices fresh from factory or refurb may fall in the "does not qualify" category (your results will vary)
● it's okay if you previously got to 5.x via an OTA update, as long as your current 5.x was installed via a normal iTunes restore. All that matters is how you got to your current 5.x most recently
● redsn0w detects an OTA/normal-restore APticket mismatch very early, so if you don't know your status there should be no harm in trying. Any device in recovery mode after such a mismatch can boot normally again just by going back to "Even More" screen from the "Restore" screen (or use "Recovery Fix" if you quit redsn0w before doing that).

3. Unlike the A4 devices, redsn0w can't (usefully) prevent the baseband updates of A5+ iPhones and iPads.
● and so, redsn0w automatically flashes the currently signed baseband when it does A5+ restores, even if those basebands didn't come with the original firmware
● stay away from this if you have an unofficial unlock that isn't supported by the newest baseband
● the least-tested baseband update code in redsn0w is for iPad2,3 and iPad3,2. Please give any feedback on those iOS5 restores in the comments section below.

4. iPad2 owners (all three models) with saved 4.x blobs can use those instead, even from 6.x
● if you have both 4.x and 5.x iPad2 blobs, you can always get to 5.x via the 4.x blobs, even if you're currently on 6.x
● you cannot get to 5.x from 6.x without the 4.x blobs (but you may still qualify for the iOS5-to-iOS5 restore described above)
● if somehow you have 4.x blobs but no 5.x blobs, you can still go down to 4.x from 6.x
● this only applies to iPad2 owners (they're the only A5+ devices that ever had a public 4.x FW)
● redsn0w still supports (but doesn't require) jailbreaking A5+ devices at 5.0.1 and 5.1.1. Just head back to the first page after re-restoring to 5.x. It's always much faster to jailbreak those FW versions with a freshly-restored device, before letting iTunes restore from a saved userland backup.

5. ultrasn0w isn't yet updated for 6.x
● by now you probably should be taking advantage of the extremely cheap IMEI-based unlocks of iPhones sold by established online retailers like http:://cutyoursim.com
● still, IMEI-based unlocks don't work in all cases. We'll announce when ultrasn0w is ported up to 6.x
● redsn0w will still hactivate your 3GS or iPhone4 if you run it before the device is activated. Due to the current tethered 6.x JB status, redsn0w now hactivates 6.x without requiring subsequent tethered boots. If you accidentally hactivate with redsn0w, use the "Deactivate" checkbox available from the Jailbreak screen, not the normal one in "Even more"

6. As always, redsn0w lets you "Fetch" the SHSH blobs currently flashed onto your pre-A5 device
● use this if you're at 5.x or 4.x but without having saved your blobs when the window was open
● this is only useful when Apple is no longer signing the firmware, otherwise Cydia/redsn0w "New"/TinyUmbrella blobs are superior (but you're welcome to fetch your 6.0 blobs this way anyway)
● fetching blobs in this fashion will automatically forward them up to Cydia, as well as save a local copy

We'll be posting tutorials on how to use these new features shortly. You can follow us on Twitter, Facebook, and RSS.

Tutorials:
● How to Manually Submit Your Saved SHSH Blobs to Cydia (Windows, Mac)
● How to Jailbreak Your iPhone 4 Using RedSn0w [6.0] (Windows, Mac)
● How to Jailbreak Your iPod Touch 4G Using RedSn0w [6.0] (Windows, Mac]
● How to Re-Restore Your iPhone From iOS 5.x to iOS 5.x (Windows, Mac)
● How to Re-Restore Your iPad From iOS 5.x to iOS 5.x (Windows, Mac)
● How to Upgrade Your iPhone 4, 3GS Without Updating the Baseband (Windows, Mac)
● How to Downgrade Your iPhone 4 From iOS 6.x to iOS 5.x (Windows, Mac)
...more to come!

You can download RedSn0w 0.9.15b1 from here.

Read More

How to Downgrade Your iPhone 3GS From iOS 6.x to iOS 5.x (Windows)

These are instructions on how to downgrade your iPhone 3GS from iOS 6.x to iOS 5.x using saved SHSH blobs and Redsn0w for Windows.

Step One
Create a folder on your desktop called Pwnage

Download the latest version of RedSn0w from here and place it in the Pwnage folder. Likewise, download the firmware you would like to restore to and the firmware you are current on from here and place it/them in the Pwnage folder. 

Extract the RedSn0w zip file to the Pwnage folder.


Step Two
Right click or control-click the redsn0w application from the redsn0w folder we extracted earlier and chooseRun as administrator from the popup menu that appears.




Step Three
Click Extras from the main menu.


Step Four
Click Even More from the Extras menu.


Step Five
Click Restore from the Even More menu.


Step Six
Click IPSW from the Restore menu, choose the IPSW you would like to restore to from the window that appears, and click Open.




Step Seven
Redsn0w will ask you if you would like to prevent the baseband from being updated. Click Yes.


Step Eight
Redsn0w will inform you that Pwned DFU mode is needed to restore. Click the OK button.


Step Nine
Connect your device, turn it off, and then click the Next button


Step Ten
RedSn0w will now guide you through the steps to get into DFU mode. You can find more help with DFU modehere.


Hold down both the Home button and the Power button for 10 seconds.


Release the Power button and continue holding the Home button until RedSn0w detects the device.


Step Eleven
Your iPhone will now be exploited with limera1n.


Step Twelve
RedSn0w will check Cydia to see if you have the correct blobs saved.

If RedSn0w is unable to find your blobs automatically you can try to click the Remote button to try again or you can click the Local button to search for blobs on your computer.


Step Thirteen
RedSn0w will now prepare a system restore image.


Step Fourteen
Your device will then be restored to the new firmware.


Step Fifteen
You'll be informed when your restore has completed successfully. 

ATF SL3 Simlock Recovery v9.0 Update!

Introduction:


In the past, when a dead Nokia BB5 SL3 Phone comes to your shop, it was only
possible for you to backup the IMEI via a Backup RPL Function. There was no
way for you to backup a possibly 100% working SIMLOCK inside the phone because
you needed Local/Test Mode in order to get the PM Backups. Dead Phones cannot
give you Local/Test Mode at all, so you cannot backup the Simlocks even if you
wanted to.
Now here comes the Solution... The ATF Simlock Recovery Module v1.0 will allow
you to BACKUP SIMLOCKS from a DEAD PHONE! Just a 1-click solution for Recovery
Level 1 and Level 2 for NON-CORRUPTED SIMLOCKS on a DEAD PHONE. 
Even if your phone SIMLOCKS are CORRUPTED, The ATF Network can still attempt to 
perform a Level 3 Recovery from it, but it will cost you some ATF SL3 Credits.

Here is a Short Description about the three Simlock Recovery Levels:

Recovery Level 1:

* FREE for ALL ATF BOX Users (DOES NOT NEED CREDITS or ATF NETWORK ACTIVATION)
* Phone DOES NOT need to be AUthorized
* 100% Stand Alone
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL2 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL1 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recover from DUMP FILE or from Connected PHONE
* Super Fast Recovery, BUT SIMLOCKS WILL NOT BE VERIFIED
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3
* DOES NOT SUPPORT FULLY ERASED PHONES
* SUCCESS RATE = 70% if the CORRECT SIMLOCKS ARE STILL INSIDE THE FLASH DUMP 

Recovery Level 2:

* FREE for ALL ATF Network Users (DOES NOT NEED CREDITS)
* Phone NEEDS to be Authorized via The ATF Network
* Stand Alone ONLY AFTER PHONE IS AUTHORIZED via The ATF Network
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY + RECOVER ORIGINAL SIMLOCKS if SIMLOCKS are OVERWRITTEN)
* Supports ALL SL2 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL1 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recover from Connected PHONE ONLY
* Recovery Time will depend on Fragmentation Level of the XSR Blocks
* SIMLOCKS WILL BE VERIFIED (Since Phone is already Authorized)
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3
* DOES NOT SUPPORT FULLY ERASED PHONES
* SUCCESS RATE = 95% if the CORRECT SIMLOCKS ARE STILL INSIDE THE FLASH DUMP 

Recovery Level 3:

* Needs SL3 Credits and only available for ATF Network Activated Users
* Phone NEEDS to be Authorized via The ATF Network
* Recovery is performed by our Servers (NOT STAND ALONE)
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM
* Supports ALL SL3 NOR Blocks for RAP3Gv3
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recovery Time will depend on CURRENT TASK LOAD on the ATF Simlock Recovery Server
* SIMLOCKS WILL BE VERIFIED (Since Phone is already Authorized)
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3
* POSSIBLE TO SUPPORT OVERWRITTEN PM 120 Blocks with Wrong PM 120 Blocks
* POSSIBLE TO SUPPORT FULLY ERASED PHONES
* DOES NOT SUPPORT WRONG FLASHED PHONES with WRONG FIRMWARE (Repartitioned NANDs)
* SUCCESS RATE = 95% if the Phone is not wrongly Repartitioned by a wrong Firmware 

IMPORTANT INFORMATION:


1. Level 1 Recovered Simlocks are NOT VERFIED to be Working (NOT GUARANTEED)
2. Level 2 Recovered Simlocks are 100% VERIFIED and Guaranteed to WORK
3. Level 3 Recovered Simlocks are 100% VERIFIED and Guaranteed to WORK

Summary:

If your phone is DEAD, but the SIMLOCKS are 100% OK, then the ATF Simlock 
Recovery Module will recover your simlocks for you via Recovery Level 1 or 2.
If your phone is DEAD, and the SIMLOCKS are possibly corrupted, then the 
ATF Simlock Recovery Module will recover your simlocks for you via Recovery
Level 3 + ATF SL3 Credits.

Box Firmware Update:

New ATF Firmware LogiCore 10.3.15 for ATF Chrome, ATF Lightning and ATF Nitro Boxes

Other Updates:
* MEEGO PHONE Authorization EVEN IF 20-digit SL3 Code is detected.
* Shows full RPL (Certificates) Information during Backup RPL on BB5 Phones.
--> Checks Original IMEI
--> Checks Original Product Code
--> Checks PA_PUBLIC_ID
--> Checks PA_PUBLIC_KEYS_HASH
--> Checks Original BT ID
--> Checks Original WLAN ID

* New option in Settings "Select USB Connection by Default when ATF Software Starts"
* Cross Flashing is now IMPOSSIBLE if Phone has good IMEI (NO MORE WRONG FIRMWARES)
* Flash File CRC32 is now CHECKED BY DEFAULT on Flash Files downloaded from NaviFirm etc... 
* Other small tweaks which I already forgot to mention...