yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] wlmeng11:
Nice comparison.

Glad I have this phone.
[HTC Rezound] Serinety:
Ya I just came from the rezound ad well.. This s3 has horrible reception in comparison.

Numbers aside. I drop about half my calls on the s3 in the same places I have never had issues with on my resound.

My wife still has her rezound, and standing in the same place at the same time, she will have several bars if 4g and be able to place calls and browse the Web, while my s3 has a circle with a line through it... (no signal)
[HTC Rezound] ssoares01:
Guy here at work has an S3 - I get 4 bars consistently here, he was 2-3. I was pretty surprised.
[HTC Rezound] blestsol:
Don't be. Samsung isn't ready to step their antenna game up yet.
[HTC Rezound] hchristy2013:
THis is why I am glad I got the Rezound, sure the S3 might out spec it, but the Rezound has some amazing things going for it, I have only dropped a call once in 4 months of owning it. I just get irritated with dust collecting in the headset.
[HTC Rezound] GoBlue13:
Samsung phones are notorious for having poor radios. I had a Droid Charge, my dad picked up the S3 as a replacement for his nexus and they all three had no signal where my Rezound has full bars. Pathetic!
[HTC Rezound] dogswind:
Very good test. Thanks for sharing your findings and confirming what we all know to be true.
[HTC Rezound] MikeG7265:
Very nice test. This is the exact reason I'm sticking with my Rezound and why my Nexus is a paperweight now.
[HTC Rezound] mjones73:
I was at a friend's a few months back, pulled 30mbs while his charge could barely get 4g, I was pleasantly surprised
[HTC Rezound] roosxter:
Go rezound
[HTC Rezound] xdadevnube:
I don't believe it is wise to jump to conclusions, I suggest checking out this article:

http://rootzwiki.com/topic/25921-this-is-why-your-verizon-nexus-signal-sucks/

I think it takes some real-use testing over an extended period of time to really come to a conclusion about radio quality. Cellular conditions are very dynamic due to many factors. Signal quality is also very difficult to quantify, especially when basing it off just dBm (and of course, bars are just ridiculous.) The electromagnetic environment is very complex, and changes drastically in time and space. In my limited experience with wireless communications, I found that RSSI and SNR only tell part of the story. I often measure latencies while performing bandwidth tests (say to dial in a dish), but I find myself perplexed in many cases. Sometimes I get more consistent throughput when the SNR is worse.

Interestingly, I probably drop more calls with my Rezound than I did with my Droid Charge. I also had more reliable throughput on my Droid Charge than my Rezound on EVDO. Admittedly, the old radio firmware on the Charge was pretty crummy, but the later releases definitely stabilized it. It is difficult to come to conclusions due to many factors and it is possible a device may have a defect.

I'm not complaining about the Rezound too much, I'd say its roughly the same experience in regards to radios as my Droid Charge.

Just sayin'.
[HTC Rezound] PhantomApollyon:
Not that I'm defending Samsung in the least here, I sincerely dislike most of their devices, but you might want to take a look at the fact that Samsung's devices show the LTE RSRP and NOT the RSSI like the Rezound does. There's a big difference between the measurements but to simplify it -80dbm RSSI is roughly equal to -100dbm RSRP, you just add -20dbm to the RSSI number to get the applicable RSRP number. So the signal NUMBER that you see might be seriously misleading you into thinking the signal is really poor if you're not doing the conversion before comparing. However, I much prefer my Rezound to the S3 without question, I gladly returned the S3 :)

EDIT -RSSI vs RSRP Information: http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/
[HTC Rezound] hchristy2013:
I went to the store this morning, I swear there was 70+ peple in the store

Sent from my ADR6425LVW
[HTC Rezound] zetsumeikuro:
Edit:NVM another nerd posted the same link.
[HTC Rezound] blestsol:
Regardless of the terminology, it's weird as hell that people get better reception on the rezounds than the Samsung produced phones myself to included. I'll be damned if someone tries to convince me we're suffering from the placebo effect. Especially with people using them in real world.
[HTC Rezound] Freedom First:
I'll vouch for the fact that (in a non-scientific, purely anecdotal test) the G-Nex has less signal strength compared to the Rezound. My wife received one for her job... the first one wouldn't hold signal long enough to download an app, or make a phone call, all the while my Rezound had 3-4 bars of signal. Her replacement phone is better, but if I hold both phones in my hands, the G-Nex shows only 1-2 bars of signal, while my Rezound has 3-4 (her battery life is PATHETIC, as well). Her co-worker was given a SGSIII, and she's already complaining of poor signal and dropped calls. We're in a large metropolitan area (Seattle-Tacoma) and have excellent 4G coverage here.

I'll keep my Rezound, thanks!
[HTC Rezound] mtotho:
I can't speak much on signal strength other than I haven't had any problems and I think it is a bit better than my Droid Incredible
[HTC Rezound] platinumrims:
Samsung has worse radios for whatever reason and always have... Any real world use would show that. Can't get 4G here in a 4G area... oh look the rezzy has 4G w/20megs down. As far as 3G goes the difference has been much less noticeable. I guess there 3G radios are ok. I've seen and experienced 4G issues a lot more frequently with Samsung than HTC.
[HTC Rezound] shrike1978:
That's one of the reasons I chose the Rezound over the Nexus when I decided to dump my Charge. The radios were ticking me off something fierce and I wasn't going to go right to another product with virtually the same radios. The Rez will be in my hands about 5:00 this afternoon. Can't wait to be rid of Samsung.
[Android Software/Hacking General [Developers Only]] m.sabra:
ok so not long ago i had a problem with a locked android device with a pattern and i managed to unlock it using adb,so here's how in case you were stuck one day with a locked device.

the device needs to have usb debugging enabled in case usb debugging isn't enabled and you have cwm you can run the same instructions from cwm,root is not required (though it will be so better if the device was rooted)

this was tested on:gingerbread,ice cream sandwich and jelly bean.

both method are through adb.

method 1:

adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit

-AND/OR-

method 2:

adb shell rm /data/system/gesture.key

and that's a video showing how method 2 is done (thanks to melvinchng) : http://www.youtube.com/watch?v=tVJ7T2oC_Zs&feature=player_embedded

you can try both of them,here is how i managed to remove the lock:

1- run the first method.

2-reboot

3-run the second method

4-reboot

NOTES:

-in the first method each line is a seperate command so click enter after typing each line.

-in the second method type all the command and then press enter.

-after running both methods and rebooting you may see the pattern lock,that doesn't necessarily mean it doesn't work,just try any random pattern and it may unlock then remove the pattern from settings.

-this may and may not work,it may work on some devices and don't on others,so all you can do is trying it but i can't assure it will work.

a small donation would be much appreciated thank :) (check my signature)
[Android Software/Hacking General [Developers Only]] creagrox:
But What if i remember the password well enough, but didnt have data enabled the moment it got locked?

Explained elaborately here>>>http://xdaforums.com/showthread.php?p=29963687
[Android Software/Hacking General [Developers Only]] ashirviskas:
It will unlock either ;) (Loook at the time of message above - I am time traveler :D )
[Android Software/Hacking General [Developers Only]] vNa5h:
i have better method than bot the above ones

look for smudges on the phone ;)
[Android Software/Hacking General [Developers Only]] simster007:
Do the files need to be restored or are they just the user data for the pattern locks?
[Android Software/Hacking General [Developers Only]] spiderio:
This is really great...

i wonder how do you discover this

you must be a hacker
[Android Software/Hacking General [Developers Only]] manemzjum:
Or you could boot into recovery backup data

wipe factory reset and reboot

Could try restoring data but most likely restore pattern lock

Or simply enter your gmail address as requested
[Android Software/Hacking General [Developers Only]] Thunder07:
2nd option...

if you have Custom recovery

use AROMA File Explorer and you can do the same thing through the recovery :)

or adb through the recovery
[Android Software/Hacking General [Developers Only]] zmore:
FWIW, on CM10 neither method works as non-root. Yay CyanogenMod.

Method #1 FAIL:

1|shell@android:/data/data/com.android.providers.settings/databases $ ll

opendir failed, Permission denied

255|shell@android:/data/data/com.android.providers.settings/databases $ sqlite3 settings.db

Error: unable to open database "settings.db": unable to open database file

Method #2 FAIL:

shell@android:/data $ ll /data/system/gesture.key

-rw------- system system 20 2012-08-11 04:51 gesture.key

shell@android:/data $ rm /data/system/gesture.key

rm failed for /data/system/gesture.key, Permission denied

(I use faceunlock + pattern (mostly to keep my kid outta my phone), but if I actually cared more about security I'd encrypt my phone and use a passphrase instead)
[Android Software/Hacking General [Developers Only]] D0GuKaN:
This is a useful guide, thanks, I will try it :good:
[Android Software/Hacking General [Developers Only]] daniel_loft:
So I guess if Debugging wasn't previously enabled, you have no chance to unlock it...

I've noticed a locked Archos tablet in a shop (probably some stupid shopper locked it) and when I saw this thread announced on the first page I was thinking of helping the shop owner. But I guess I cannot.

Have a nice day!
[Android Software/Hacking General [Developers Only]] CKKnot:
Download the By-pass security Hack.7z

Extract it to anywhere using 7-zip.

Open SQLite Database Browser 2.0.exe in SQLite Database Browser.

Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone.

Drag settings.db and drop to SQLite Database Browser 2.0.exe program.

Navigate to Browse data tab, At table there, click to list down the selection & selete secure

Now, find lock_pattern_autolock, Delete Record

Close & save database

Run push settings.db.cmd and reboot your phone :)

Now, Find Or Create lockscreen.password_type, double-click & change it's value to 65536, Apply changes!

Now, find lock_pattern_autolock, Delete Record, If doesn't exist, Ignore

Close & save database

Run push settings.db.cmd and reboot your phone :)

Now, find lockscreen.password_salt, Delete Record

Now, find lockscreen.password_type, Delete Record

Close & save database

Run push settings.db.cmd and reboot your phone :)
[Android Software/Hacking General [Developers Only]] mixtapes08:
hmmm i hope those thief's don't find these thread lol
[Android Software/Hacking General [Developers Only]] kupuguy:
Nor does either method work on unrooted Galaxy Nexus with stock Jelly Bean. Yay stock Android.
[Android Software/Hacking General [Developers Only]] aussiebum:
don't leave usb debugging checked on then.
[Android Software/Hacking General [Developers Only]] daniel_loft:
I advise you guys to also post your Android version. My opinion is that the security hole that permits this hack has been removed in JellyBean, maybe even in an earlier version.

I will try it too a little later, just for the fun's sake.
[Android Software/Hacking General [Developers Only]] HQRaja:
If you have forgotten to leave USB debugging enabled, reboot your phone into recovery and do the same. No USB debugging required.

You may however need to mount the partition being accessed by this method, and you can do that only if you have a custom recovery installed (which you more-than-likely have, since you're here on XDA). Just go to 'Mounts and Storage' and mount /data. Then use the method just the normal way. Cheers!
[Android Software/Hacking General [Developers Only]] evaradar:
Useful guide for sure. Will keep this as reference!
[Android Software/Hacking General [Developers Only]] thelastemperor24:
Does this only work for the pattern unlock or will it also work on the password or the PIN unlock screen?
[Android Software/Hacking General [Developers Only]] daniel_loft:
I can confirm that it is working on a CM7.2 Motorola Defy.

Thanks m.sabra!
[Android Software/Hacking General [Developers Only]] simo24:
Neither method works (permission denied) in the first instance I tried:

Non-rooted HTC Evo 4G (Android 2.3.4)
[Android Software/Hacking General [Developers Only]] guoloong:
I believe without root, you cannot access and modify /data folder right? This exploit should be only for rooted devices?
[Android Software/Hacking General [Developers Only]] RivaultUser:
you're an amazing guy!:laugh:
[Android Software/Hacking General [Developers Only]] shafty023:
The exploit/workaround has nothing to do with root. The issue is some OEMs grant the adb shell root access instead of restricting it to a lower permission user. When the adb shell is granted root access someone is then able to access the /data permission which is normally blocked off from any user besides root.

So you could encounter this exploit by using a phone with USB debugging enabled where the OEM grants the adb shell root access. Or, on a custom ROM where the kernel is granting the adb shell root access. Having your phone rooted just makes it easier where, even if adb was protected with a lower permission user, you could still "su" to root once in a shell and wreck havoc.

Summary:

Without a rooted phone if your phone grants the adb shell root access (this is something an OEM mistakenly would have done) then you can access this exploit

With a rooted phone you can type "su" after getting a shell via "adb shell" and then execute the exploit
[Android Software/Hacking General [Developers Only]] -DarthNihilus-:
This wouldn't work because the files required by lock are actually stored on /data. Hence the term "USER data."
[Android Software/Hacking General [Developers Only]] guoloong:
Thanks for the information.

Say if we disabled USB debugging, are we safe from this exploit? I'm wondering if we have installed CWM recovery, adb shell can still work in this manner?
[Android Software/Hacking General [Developers Only]] hanaheeno:
Easier way to force unlock

I found more simple method to do so on my Galaxy Nexus 4.1.1 ParanoidAndroid 1.99 ROM.

adb shell
su
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
reboot

And you're done :)
[Android Software/Hacking General [Developers Only]] melvinchng:
Basically you need to crack, you must either have

-USB debugging enabled

Right?

Accidentally sent from my Google Nexus S
[Android Software/Hacking General [Developers Only]] myungz:
request rooted :confused:
[Android Software/Hacking General [Developers Only]] m.sabra:
a quick reply for general concerns.

this method have been confirmed working on gingerbread,ics and jelly bean.

if usb debugging isn't enabled and you have cwm,you can use this from cwm.

having root will make the chances of the crack working really high,without root or cwm you still have a chance but not a very good one.

any other questions ? feel free to ask :)
[Android Software/Hacking General [Developers Only]] melvinchng:
when i type "sqlite3 settings.db"

Error: unable to open database "setting.db": unable to open database file shell@android:data/data/com.android.providers.setting/databses $

this is how i do,

i set a pattern unlock.

connect phone to pc with debugging on

run adb

and type all those things.

I tried both recovery and normal. Both also not working, stuck at setting.db

nexus s, 4.1.1, CNA
[Android Software/Hacking General [Developers Only]] m.sabra:
i have a nexus s too but i never had similar error,you should check your spelling,i see you used setting.db instead of settings.db several times,and you should also try the second method.
[Android Software/Hacking General [Developers Only]] melvinchng:
The first one wont work... a reboot and wont unlock with random unlock.

I made two videos showing users how to do it.

[youtube]tVJ7T2oC_Zs[/youtube]

[youtube]deVEYhDdoHA[/youtube]

but the second one does.

Accidentally sent from my Google Nexus S
[Android Software/Hacking General [Developers Only]] shafty023:
If you disable USB debugging and you're NOT rooted, then you're perfectly fine. If you're rooted or you've installed a 3rd party recovery image then you're screwed no matter what because someone can just reboot your phone into recovery and execute these commands easily.

Of course, if someone really wanted to they could take your unrooted phone with a pattern lock and:

Unlock your bootloader

Install a custom recovery

Execute the exploit from the recovery environment

Reboot your phone and they can now get into the phone

So technically the only "safe" phone is a phone with a locked bootloader by the OEM.
[Android Software/Hacking General [Developers Only]] scandiun:
Well, and how can I lock the bootloader of a samsung galaxy s2 GT-I9100 that comes unlocked by default?
[Android Software/Hacking General [Developers Only]] guoloong:
Thanks for your explanation. It simply means that if you are rooted, you are more or less screwed. :(

However, if your phone is has locked bootloader, when someone unlock your bootloader (eg. using fastboot oem unlock) it should wipe out all data from the phone. Technically, your data is still safe.
[Android Software/Hacking General [Developers Only]] scandiun:
Yes, that's the objective of a locked bootloader, don't allow access to data unless you unlock the screen. For example, the Galaxy Nexus comes with that by default, even if you don't use encryption you are very safe. But of course, without root you can't use a lot of programs, even clockworkmod recovery.

On the other hand, there are other devices like Galaxy S2 or S3 that come with bootloader unlocked by default and there is not way to lock it, so you are screwed even if the phone is not rooted and with adb disabled, because you can launch CWM from sdcard and get the data. So well, what device you buy also matters on security.
[Android Software/Hacking General [Developers Only]] subworx:
You do know that unlocked doesn't have anything to do with root? Take Moto phones, they have a locked bootloader so nobody could install CWM (except with the newer ones which are unlockable but lose all data during this, not sure about older models), but they can still be rooted. Turn off USB Debugging there and you're good.

More on topic, a rather nice app to pretty much replace USB Debugging for adb functionality is adbWireless which puts a widget on the screen that enables adb over wifi, also showing a toast with the IP to connect to. It needs to be run directly once for root permissions, after that the widget just works.

Some might find it rather uncomfortable to type "adb connect <IP>" before doing anything, but hey - your screenlock is safe :)

Also, leaving adbWireless turned on will not open the same security gap as leaving USB Debugging enabled. adbWireless only works with WiFi enabled. With screenlock turned on, nobody can join the phone to their home wifi network, as Android does not simply join any open network (please correct me if I am wrong). No WiFi - no adbWireless, no access to the device.

You might consider this :)

And getting an older Motorola phone that nobody found a way to unlock the bootloader on ;)

Regards,

Sub
[Android Software/Hacking General [Developers Only]] Eddy130306:
Both methods worked! And the FBI had trouble cracking the unlock pattern :p

Well not cracking, but getting passed the pattern.
[Android Software/Hacking General [Developers Only]] defim:
The problem is that adb starts every reboot
[Android Software/Hacking General [Developers Only]] m.sabra:
well they should have come to xda for help :P
[Android Software/Hacking General [Developers Only]] anonymous572:
Read all thread. Absolutly none of these methods won't work with my Galaxy Note 4.0.4 stock with root and debugging on. Tried almost everything.
[Android Software/Hacking General [Developers Only]] melvinchng:
none working or all working?

Accidentally sent from my Google Nexus S
[Android Software/Hacking General [Developers Only]] surajkala:
unable to unlock samsung galaxy 3

I have samsung I5800 / 5801 which got locked.. after many retries for Pattern lock

Although i have the username & password.. but my phone wont connect to net

I went thru this post.. but my issue is ..

the device is

1) Not rooted

2) USB debugging is off

3) wifi off

4) mobile data off

5) No CWM

6) Eclair 2.1

Please let me know.. how can i fix it.. without loosing any data .. Even i tries the method where u need to make a call to device and click back button.. but that doesn't work either

plz guide

NB: only last option i have is phone reset.. but in that case data will be lost
[Android Software/Hacking General [Developers Only]] quietcblongs:
For those having trouble with the first method, the rows may not be in the system table. For my EVO 4G, it was in the secure table. So just change the statement from "update system..." to "update secure..." and reboot after running the statements.
[Android Software/Hacking General [Developers Only]] bearshark:
Thanks to HANAHEENO! My stupid noobness just flashed ParanoidAndroid 2.16 (my very first flashed ROM) and was laying in bed trying to unlock. I had the right code, but I suspect the phone was tilted a little and did not accept my pattern unlock. It went to Google's email and password unlock and of course, I didn't have data or wifi on.

I did a factory reset using bootloader and flashed PA 2.16 and GApps again. I'm not sure if this is the right thing to do, but it didn't work. Thought I was forever stuck, but I found this code and it worked. Thanks so much!!!
[Android Software/Hacking General [Developers Only]] Copper Green:
Bad to remove the files.. with CM10 it's the following:

/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/locksettings.db \
"UPDATE locksettings SET value=0 WHERE name LIKE 'lock_pattern_autolock';"

You need to restart the lock screen app nonetheless. I'm trying to figure out how.

For unlocking purposes you can just remove the battery, boot up and be happy again.
[Android Software/Hacking General [Developers Only]] fireincairo:
Great post. I have one question: is it similar to unlock the password lock screen? I guess by using the statement "UPDATE locksettings SET value=0 WHERE name LIKE 'lock_pattern_autolock';" but instead of 'lock_pattern_autolock' maybe another parameter like 'lock_password_autolock'? Anyone has a clue?

And there's also an app lock screen too, i.e. when you are in the device and try to start an app, it will ask for a password defined by you previously. Is there a way to hack this?

And... most importantly, after setting the parameter to 0, if I change it back to 1, is the old password retained, so that the device owner will not notice a thing?

BR, fire
[Android Software/Hacking General [Developers Only]] lucubrb:
second method is very nice. better use another option to lock my droid :p
[Android Software/Hacking General [Developers Only]] Ahish.s:
This should be used only for educational purposes or in situations where you are locked out of the device. Not for hacking or intruding someone's device.
[Android Software/Hacking General [Developers Only]] nosiyeas:
adb

after the process completed.wil the pattern will remain open forever?like if any patterm i put will unlock it?