hotel rom: November 2015

Sunday, November 29, 2015

M HORSE STOCK FIRMWARE DOWNLOAD

M-HORSE PAC FILE FIRMWARE Stock ROM

M HORSE MINI 9500

Download Now

M HORSE MINI 9500 NEW

You can't beat a phone that rhymes, so let's cultivate the Huawei Mate 8

You can't beat a phone that rhymes, so let's cultivate the Huawei Mate 8.

Announced on the day of US Thanksgiving, the 6-inch phablet goes on sale in China in the first three months of 2016. No time to wait, debate or hesitate -- let's ruminate on the Mate 8's great traits.

Up front is a slab-like 6-inch LCD screen with a high definition 1080p resolution, which

gives you 367 pixels per inch. That's perfectly respectable but not as crisply detailed as similarly sized rivals like the 5.7-inch Samsung Galaxy Note 5, which boasts an eye-scorching 518ppi. Even older phones like the Nokia Lumia 1520 and Google Nexus 6 match or beat the Mate 8's pixel count.

The Mate 8 is up to date with its software, offering the latest version of Google's Android operating system, 6.0 Marshmallow. The manufacturer has added its own Huawei Emotion 4.0 skin on top, which isn't to everyone's taste. Adding an own-brand interface on top of Android also tends to slow down updates.

Under that huge screen is an octa-core HiSilicon Kirin 950 processor. The processor consists of four 2.3GHz Cortex A72 chips and four 1.8GHz Cortex A53 chips, and it's backed by 3GB of RAM.

Also inside is 32GB or 64GB storage for firmware, music, movies, apps and snaps. On the front is an 8-megapixel Sony job with f/2.4 aperture for video chat and selfies. The main camera on the back is a 16-megapixel Sony snapper with f/2.0 aperture and three-axis optical image stabilisation.

Also round the back is a fingerprint sensor to unlock the phone and verify your identity. That can be used to open secure files and photos, unlock apps and turn off the alarm. Users in China will also be able to pay for stuff with the sensor.

The battery is a whipping 4,000mAh powerhouse, which you'll need to keep that giant screen lit up and that beefy processor humming. The phone supports quick charging too.

The Mate 8 is the follow-up to last year's Mate 7, which we gave a very respectable 4 stars for its big screen and long-lasting battery. Since then, Huawei's latest offering is its flagship Mate S, a classily styled but rather pricey 5.5-inch phone with an interesting pressure-sensing display.

We expect to get our hands on the Mate 8 in January at CES, the annual technology trade show wherein the world's tech giants gather to show off their wares for the coming year.

Released 2015, November

185g, 7.9mm thickness

Android OS, v6.0

32GB storage, microSD card slot

23%762,879 HITS

114BECOME A FAN

6.0"1080x1920 pixels

16MP1080p

4GB RAMHiSilicon Kirin 950

4000mAhLi-Po

Also known as Huawei Ascend Mate8

NETWORK Technology GSM / HSPA / LTE

LAUNCH Announced 2015, November

Status Available. Released 2015, November

BODY Dimensions 157.1 x 80.6 x 7.9 mm (6.19 x 3.17 x 0.31 in)

Weight 185 g (6.53 oz)

SIM Optional Dual SIM (Nano-SIM, dual stand-by)

DISPLAY Type IPS-NEO LCD capacitive touchscreen, 16M colors

Size 6.0 inches (~78.0% screen-to-body ratio)

Resolution 1080 x 1920 pixels (~368 ppi pixel density)

Multitouch Yes

Protection Corning Gorilla Glass 4

- Emotion UI 4.0

PLATFORM OS Android OS, v6.0 (Marshmallow)

Chipset HiSilicon Kirin 950

CPU Quad-core 2.3 GHz Cortex-A72 + quad-core 1.8 GHz Cortex A53

GPU Mali-T880 MP4

MEMORY Card slot microSD, up to 128 GB (uses SIM 2 slot)

Internal 32 GB, 3 GB RAM/ 64 or 128 GB, 4 GB RAM

CAMERA Primary 16 MP, 4608 x 3456 pixels, optical image stabilization, phase detection autofocus, dual-LED (dual tone) flash

Features 1/2.8' sensor size, geo-tagging, touch focus, face/smile detection, panorama, HDR

Video 1080p@30fps, 720p@120fps

Secondary 8 MP, 1080p

SOUND Alert types Vibration; MP3, WAV ringtones

Loudspeaker Yes

3.5mm jack Yes

COMMS WLAN Wi-Fi 802.11 a/b/g/n/ac, dual-band, DLNA, WiFi Direct, hotspot

Bluetooth v4.2, A2DP, EDR, LE

GPS Yes, with A-GPS, GLONASS, BDS

NFC Yes

Radio FM radio

USB microUSB v2.0, USB Host

FEATURES Sensors Fingerprint, accelerometer, gyro, proximity, compass

Messaging SMS (threaded view), MMS, Email, Push Email

Browser HTML5

Java No

- Fast battery charging: 37% in 30 min

- Active noise cancellation with dedicated mic

- DivX/XviD/MP4/H.265/WMV player

- MP3/eAAC+/WMA/WAV/Flac player

- Document editor

- Photo/video editor

BATTERY Li-Po 4000 mAh battery

Stand-by

Talk time

MISC Colors Champagne Gold, Moonlight Silver, Space Gray, Mocha Brown

Price group 9/10

Disclaimer. We can not guarantee that the information on this page is 100% correct. Read more

Friday, November 27, 2015

Here's How Google Can "Remotely Bypass" Pattern Lock Of Android Device

Older versions of Android can be remotely reset by Google if the company is issued with a court order, but only if they're locked using a pattern.

This is according to a document prepared by the New York District Attorney's Office which revealed just how easily investigators could see the contents of a device.

Devices running Android 5.0 and newer cannot be remotely reset as they use full disk encryption.

However, this option is not switched on by default.

The report found any device using an older version of the operating system is vulnerable to remote reset and according to the Android Developer Dashboard, this is 74.1 per cent of Android devices currently being used.

However, this figure is slightly misleading.

The remote reset feature does apply to phones running operating systems before Android L, but it only applies to people how have secured their device with a pattern.

Google can't remotely reset phones secured with a PIN or passcode, meaning the number of affected devices could be lower.

A post from Google's Adrian Ludwig attempted to clarify the situation.

He said: 'Google has no ability to facilitate unlocking any device that has been protected with a PIN, Password, or fingerprint.

'This is the case whether or not the device is encrypted, and for all versions of Android.

'Google also does not have any mechanism to facilitate access to devices that have been encrypted (whether encrypted by the user, as has been available since Android 3.0 for all Android devices, or encrypted by default, as has been available since Android 5.0 on select devices).

'There are some devicesthat have been configured to use a "pattern" to unlock. Until Android L, "pattern" unlock did provide a recovery option with the Google account.

'This recovery feature was discontinued with Android L.

'Also, the lost pattern recovery feature never applied to PIN or Password so if you are on an earlier model device and don't want to use the pattern recovery feature, you can switch to a PIN or Password and it will be disabled.'

However, the report insists that forensic examiners are able to bypass passcodes on devices using a 'variety of forensic techniques.'

NSA to shut down bulk phone surveillance program by Sunday

The National Security Agency will end its mass metadata surveillance program this weekend, two and a half years after Edward Snowden’s revelations. However, he NSA’s replacement “reasonable compromise” is far from being celebrated by privacy advocates.

Signed into law this past June, the USA Freedom Act requires that by 11:59pm EST on November 28, the NSA must cease its bulk collection of telephony metadata. The NSA is ready to move ahead with a different program, also ordered by the law, at the same time.

No longer will the NSA rely on the Patriot Act’s Section 215 to collect all phone records. Instead it will have to contact telecommunications companies holding the data for them. Unlike general warrants leaked by former NSA contractor Edward Snowden such as the one issued by the Foreign Intelligence Surveillance Court (FISC) granting the NSA access to all Verizon customers’ records, the new program only allows the NSA to collect records from telecoms when a “specific selection term” pertaining to limited data is outlined in a FISC warrant, which will limit investigations of the metadata to six months.

The move has encouraged a wide variety of opinions to be voiced.

"The act struck a reasonable compromise which allows us to continue to protect the country while implementing various reforms," Ned Price, a spokesman of the National Security Council, an advisory group to the US President, told Reuters.

Meanwhile, Alex Abdo of the American Civil Liberties Union told the Baltimore Sun that “the ending of the phone records program may in the future seem to be more a symbolic victory, given it was the first major concession the intelligence agencies had to make.”

While privacy advocates described the change as only a single step with the prospect of more progress to come, lawmakers adopted a tone of finality.

"I think we have the balance right," Representative C. A. Dutch Ruppersberger (D-Maryland) told the Sun. Ruppersberger has called Snowden a traitor and was ranking member of House Permanent Select Committee on Intelligence when the leaks were published.

Marcy Wheeler, a national security blogger, disagreed strongly. Wheeler wrote that the USA Freedom Act expands on, rather than replaces, what the NSA interpreted Section 215 as authorizing. What’s more, a separate executive order is in place, she says, to run parallel to the bulk metadata collection.

“Right now, the Section 215 phone dragnet is not getting some cell records, probably not getting all VOIP, and probably not getting non-telephony messaging,” Wheeler wrote on the Empty Wheel blog, adding “just a tiny corner of the phone dragnet will shut down, and the government will continue to collect telephony metadata records in bulk … including records of both U.S. and non-U.S. persons’ under EO 12333,” in reference to an executive order issued in 1981 by President Ronald Reagan.

Although the bulk metadata collection is coming to an end, what’s already been collected will not be immediately destroyed, as an NSA request to keep the metadata until the end of February 2016 is under FISC consideration. The White House told Reuters the NSA still needs limited access to it, not for analytical purposes but “data integrity purposes,” while the reliability of the new focus-oriented program is monitored.

This month, a federal court found the soon-to-end program unconstitutional, ordering that the past data be destroyed. However, an appeals court stayed that ruling out of national security interests. Larry Klayman, founder of public interest groups Judicial Watch and Freedom Watch, has been in court with the NSA since 2013 over its mass surveillance, and he says his case depends on that data not being destroyed.

On Wednesday, FISC fulfilled another part of the new surveillance law, adding five advisers to a panel, known as an amicus curiae in legal-speak, to offer legal advice from a perspective promoting civil liberties when applicable to a warrant request. The panel consists of four lawyers and a law professor.

Vulnerability Discovered That Exposes Real IP-Addresses Of "Vpn Users"

We live in a world where everything we say, everything we do, everyone we talk to, everything we watch on the internet, every expression of creativity, or love, or friendship is recorded.We can be tracked by a many different organizations.
By simply visiting a website can allow its operators to figure out your general physical location, identify details about your device information, and install advertising cookies that can track your movements around the Web.

So we often use VPN to hide our IP address while surfing the internet to maintain online anonymity, to access geo-restricted content, Bypass Government Censorship, Torrent Downloading(in some countries).

But a new vulnerability discovered can reveal real IP-addresses of VPN users with relative ease. The issue, that affects all VPN protocols and OS, was uncovered by "Perfect Privacy" who alerted many affected VPN providers to the threat before making it public.

For the past many years interest in encrypted and anonymous communications has increase to a far wider audience.VPN suppliers are significantly prominent among BitTorrent users, who by default broadcast their IP-addresses to many individuals once downloading a preferred file.

The goal of VPN is to protect one’s ISP IP-address, however a freshly discovered vulnerability shows that this can be simply bypassed on some providers.

The problem, uncovered by VPN provider Perfect Privacy, is a port forwarding trick. If an hacker/attacker uses a similar VPN than the victim actual IP-address is exposed by forwarding traffic on a particular port.

The security flaw affects all VPN protocols together with OpenVPN and IPSec and applies to all OS.

“Affected are VPN providers that provide port forwarding and don't have any protection against this specific attack,” Perfect Privacy notes.

For example, if an attacker activates port forwarding for the default BitTorrent port then a VPN user on a similar network can expose his or her real IP-address.

The same is true for normal internet traffic, however in this case the attacker needs to direct the victim to a page that connects to the forwarded port, as Perfect Privacy explains it.

The vulnerability affected many VPN providers, who were warned last week. This includes Private Internet Access (PIA), Ovpn.to and nVPN, who have all fixed the problem before public disclosure.

PIA’s Amir Malik said that their fix was comparatively easy and was enforced swiftly once they were notified.

“We enforced firewall rules at our VPN server level to block access to forwarded ports from clients’ real ip addresses. The fix was deployed on all our servers within twelve hours of the initial report,”
In addition, PIA complimented Perfect Privacy for responsibly revealing the vulnerability before disclosing it public and awarded their competitor with a $5,000 bounty under its Whitehat Alert Security Program.

Android HttpURLConnection code for GET and POST Methods

package com.infodat.selltis2;

import android.util.Log;

import com.infodat.selltis2.utils.Constants;
import com.infodat.selltis2.utils.Utils;

import java.io.BufferedInputStream;
import java.io.BufferedReader;
import java.io.BufferedWriter;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStream;
import java.io.OutputStreamWriter;
import java.io.UnsupportedEncodingException;
import java.net.HttpURLConnection;
import java.net.URL;
import java.net.URLEncoder;
import java.util.HashMap;
import java.util.Map;

import javax.net.ssl.HttpsURLConnection;

public class HttpWebServiceHandlerSample {

    static String response = null;


    public HttpWebServiceHandlerSample() {

    }


    /**
     * Making service call
     *
     * @url - url to make request
     * @method - http request method
     * @params - http request params
     */


    // Get Request using HttpURLConnection  Code
    public String makeGetServiceCall(String requestURL, HashMap<String, String> postDataParams) {

        InputStream inputStream = null;

        HttpURLConnection conn = null;

        String response = "";
        try {
                /* forming th java.net.URL object */


            String newRequestURL = requestURL + getQueryString(postDataParams);

            URL url = new URL(newRequestURL);
            Log.i("URL ", newRequestURL);

            conn = (HttpURLConnection) url.openConnection();

                 /* optional request header */
            conn.setRequestProperty("Content-Type", "application/json");

                /* optional request header */
            conn.setRequestProperty("Accept", "application/json");

            //  urlConnection.setConnectTimeout(100000);

                /* for Get request */
            conn.setRequestMethod("GET");

            int statusCode = conn.getResponseCode();

                /* 200 represents HTTP OK */
            if (statusCode == 200) {

                inputStream = new BufferedInputStream(conn.getInputStream());

                response = convertInputStreamToString(inputStream);


            } else {
                response = Constants.NetWorkErrorMSG;
            }

        } catch (Exception e) {
            //    Log.i("Selltis N/w Error", e.getLocalizedMessage());
            response = Constants.NetWorkErrorMSG;

        } finally {

            if (conn != null)
                conn.disconnect();
        }

        Log.i("RESPONSE", response);
        return response; // return response

    }


    // Convert all key/Value pairs to URL request parameters
    private String getQueryString(HashMap<String, String> params) throws UnsupportedEncodingException {
        StringBuilder result = new StringBuilder();
        boolean first = true;
        for (Map.Entry<String, String> entry : params.entrySet()) {
            if (first)
                first = false;
            else
                result.append("&");

            result.append(URLEncoder.encode(entry.getKey(), "UTF-8"));
            result.append("=");
            result.append(URLEncoder.encode(entry.getValue(), "UTF-8"));
        }

        return result.toString();
    }


    // convert InputStream to String
    private String convertInputStreamToString(InputStream inputStream) throws IOException {

        BufferedReader bufferedReader = new BufferedReader(new InputStreamReader(inputStream));

        String line = "";
        String result = "";

        while ((line = bufferedReader.readLine()) != null) {
            result += line;
        }

            /* Close Stream */
        if (null != inputStream) {
            inputStream.close();
        }

        return result;
    }


    // POST Request using HttpURLConnection  Code
    public String makePostServiceCall(String requestURL, String postJosnData) {
        InputStream inputStream = null;
        URL url;
        String response = "";
        HttpURLConnection conn = null;
        try {
            url = new URL(requestURL);

            conn = (HttpURLConnection) url.openConnection();
            conn.setReadTimeout(10000);
            conn.setConnectTimeout(10000);
            conn.setRequestMethod("POST");
            conn.setDoInput(true);
            conn.setDoOutput(true);

                 /* optional request header */
            conn.setRequestProperty("Content-Type", "application/json");

                /* optional request header */
            conn.setRequestProperty("Accept", "application/json");

            OutputStream os = conn.getOutputStream();
            BufferedWriter writer = new BufferedWriter(
                    new OutputStreamWriter(os, "UTF-8"));
            writer.write(postJosnData);

            //    Log.i("POST URL", url.toString());
            //   Log.i("POST DATA", postJosnData);

            writer.flush();
            writer.close();
            os.close();
            int responseCode = conn.getResponseCode();

            if (responseCode == HttpURLConnection.HTTP_OK) {

                inputStream = new BufferedInputStream(conn.getInputStream());

                response = convertInputStreamToString(inputStream);


            } else {
                response = Utils.ServerErrorMessage;

            }
        } catch (Exception e) {

            //   Log.i("Selltis N/w Error", e.getLocalizedMessage());
            response = Utils.ServerErrorMessage;
        } finally {

            if (conn != null)
                conn.disconnect();
        }

        return response;

    }


}

Thursday, November 26, 2015

SAMSUNG GALAXY Y B5510 HAR RESET

HOW TO ENTER SAMSUNG GALAXY Y PRO RECOVERY MODE

Samsung Galaxy Y Pro B5510 hard reset recovery mode

Turn off phone first. Press Volume Up + HOME Key + power On together. After 10 seconds leave power key to enter in recovery.

Select Factory reset/ wipe data with volume key and Confirm with HOME key.

Go to Yes -- delete all user data press Home key. Phone will reboot.

All data will be lost!

Normal reset B5510 soft reset reboot your phone.

If your device has fatal errors or hang-ups, or freezes, you may need to reset the device to regain functionality.

Reset the device (press and hold Power/Reset/Lock key for 8-10 seconds and release)

Or go to Menu > Settings > Privacy > Factory data reset: Reset your settings to the factory

default values and delete all your data.

Your device freezes or has fatal errors

If your device freezes or hangs, you may need to close programs or reset the device to regain functionality. If your device is frozen and unresponsive, press and hold [POWER key] for 8-10 seconds and release. The device will reboot automatically.

BLACKBERRY ERROR CODES AND THEIR MEANINGS:

Blackberry Error Codes And Their Meanings: These are the most common Blackberry codes that are displayed in any Blackberry. Read further to know what they mean.

* 101 Internal JVM error.

* 102 Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files.

* 103 The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or its format is invalid or corrupt.

* 104 An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.

* 105 An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.

* 106 An error has been detected in the graphics system of the handheld.

* 107 Internal JVM error.

* 108 Internal JVM error.

* 109 Internal OS error.

* 110 Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code.

* 200 Application manager threw an uncaught exception and so it cannot continue running.

* 201 Initialization of the cryptographic system failed and the handheld cannot continue to operate.

* 202 An attack on the key store has been detected, and the handheld cannot continue to operate.

* 203 The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.

* 501 Internal error.

* 502 All processes exited. The last Java process has terminated, and there is nothing left to execute.

* 503 Internal error.

* 504 Internal error.

* 505 Internal error.

* 506 An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.

* 507 A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.

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

* 516 Error occurred during garbage collection, which might indicate a corrupted file system.

* 510 All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.

* 511 A problem has occurred during debugging.

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

* 516 When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed.

* 517 An inconsistency has been detected in the VM persistent object store.

* 518 Internal error.

* 519 Internal error.

* 520 Internal error.

* 521 Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.

* 522 A thread has acquired two locks on objects in an order that doesn’t match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.

* 523 A critical Java process has died and the device cannot continue to operate normally.

* 524 An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.

* 525 Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the persistent store root. The type of the object has been output into the event log.

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

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

* 528 The file system is corrupted. Data on the handheld is unrecoverable.

* 529 The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.

* 530 Internal JVM error.

* 531 Flash memory has been exhausted.

* 532 A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld.

Wednesday, November 25, 2015

DOWNLOAD SAMSUNG PIT OPS COLLECTION

PIT and OPS files: For Samsung

We try to give you the most we can of Pit and Ops files to use with Odin flasher but you are taking the complete Responsibility to use them, So in case you are not sure what or how to use do not use any.

A300F: Download

A300FU: Download

A300G: Download

A300H: Download

A300XU: Download

A300XZ: Download

A500F: Download

A500FU: Download

A500H: Download

A500K: Download

A500XZ: Download

A700F: Download