Develop Bugs

[DEV] Backtrack 5 on T-mobile SGS2 3/5/2012 (NEED KERNEL DEVS!!!)

DISCLAIMER:
I am not responsible for you bricking your device.
BOTTOM LINE
WHAT IS BACKTRACK?
Ok ladies and gentlemen. I guess I should have started with this. But, as another poster stated, if you don't know what Backtrack is, then you don't need this. But, I have to clarify some misconceptions as well. No one has stated correctly what Backtrack is. Backtrack is more than a tool to crack wifi passwords. Its an entire security distro. It it literally packed with thousands of tools to do everything a security tester or "hacker" needs. It is packed with metasploit (google it), sslstrip, nmap,wireshark, just to name a few. Why would they make an entire linux distro just to hack wifi routers? If you have questions, just ask.
Now with that out of the way. Backtrack runs on an image that is never mounted to your system. Nothing is replaced. It is basically a side load which can be turned on or off whenever you want while the phone is on. There is no flashing involved what-so-ever. It is so easy a caveman can do it.
This is a persistant version.
Finally on our device. Everything is fully functional with the exception of using anything that involves packet injection and setting your adapter to monitor mode (yes, this means you cannot crack WEP/WPA yet). The concept is just that we have to modify the wifi adapter driver to accept monitor mode as well as allowing packet injection. Everything else works perfectly.
NEEDED APPS
7zip PC ONLY
Terminal Emulator (Free)
AndroidVNC (Free)
(Optional)
Tasker (Paid)
NOTE: You will need approximately 3.5GB of free space on your internal SDcard (not the removable SD Card at /sdcard/external_sd/)
FOLLOW THESE DIRECTIONS SPECIFICALLY
INITIAL SETUP (only needs to be completed once)
1. Create a folder called "bt" on the base of your Internal sdcard (directory should look like it does below:
/sdcard/bt
2. Download the following scripts and put them directly to the new "bt" folder you just created. The directory should look like it does below:
bt
installbt.sh
startbt
stopbt
/sdcard/bt/bt
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
3. Download this version of busybox for temp use and put it in the following directory shown below (you may need Root Explorer to change permissions to create the directory tree and upload the file):
busybox
/data/local/tmp/bt/busybox
NOTE: /data/local/ should already be there as well as tmp. You will have to create the "bt" folder in that tree. You must have the directory tree and file shown exactally as shown: /data/local/tmp/bt/busybox . If you don't, you can't complain to me why you are getting errors.
4. After you verify that those 5 files are in that directory, then you can proceed to downloading the bt.img file below and put it in the "bt" directory as shown below:
Update
Download each of these and use 7zip to extract the bt.img from them.
bt.7z.001
bt.7z.002
bt.7z.003
bt.7z.004
bt.7z.005
bt.7z.006
bt.7z.007
bt.7z.008
bt.7z.009
bt.7z.010
NOTE: these files total approximately 3.3GB
Extract on your PC and upload to:
/sdcard/bt/bt.img
5. After you have completed the above steps, reboot your phone and re-verify all the above files are in their correct directories:
/sdcard/bt/bt.img
/sdcard/bt/bt
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
/data/local/tmp/bt/busybox
6. Open Terminal Emulator and type the following commands. If you recieve any errors then the above steps were not completed correctly, so go back to setp 1.
$ su
# cd sdcard
# cd bt
# sh installbt.sh
# startbt
# bt
7. At this point you have installed Backtrack and have a Backtrack 5 shell.
8. Now the good part. To open the GUI of Backtrack, enter the following command:
# ui
9. Nothing? Be patient. Look at the output and take note of the number "X" located at "localhost:X" from the X desktop line of the output. The VNC server is running at port 5900 so you must add "X" to get the new server port for Backtrack, ie. X=1, then 5900 + 1 would give you 5901 as the new server port.
10. Open AndroidVNC and enter the following info:
Nickname: whatever you want
Password: 12345678
Address: 127.0.0.1
Port: whatever you got from your little math problem above
Username: leave blank
Change Color Format to 24-bit color (4 bpp)
11. Now all you have to do is connect after you have created the connection.
START EACH TIME
1. Open Terminal Emulator and type the following commands.
$ su
# cd sdcard
# cd bt
# startbt
# bt
# ui
2. Open up AndroidVNC and connect to the privously created connection.
SHUTDOWN
1. Tap the settings softkey and tap disconnect (to disconnect you from the VNC server).
2. In Terminal Emulator, type the following commands:
[email protected]: # killui
[email protected]: # exit
# stopbt
# exit
# exit
3. This will close it all out for you, but to ensure a full shutdown, reboot your phone.
Thats all!!!!
Optional Automation
If you have Tasker, then you can add some automation that will automatically execute the Terminal commands and open AndroidVNC.
Download the following file and put it in the following directory which should look like this after it is added:
bt.prj.xml
/sdcard/Tasker/tasks/bt.prj.xml
Then open Tasker. Then go to Settings > Preferences > UI and uncheck "Beginner Mode" and touch the gree checkmark.
Now under the buttons across the top (Profiles, Tasks, Scenes, Variables), you will see a very faint arrow pointing down. Touch and drag down and a tab(s) will be seen across the top. touch and hole the tab with the house. Touch "Import". A "Project File Select" window will pop up. If the file does not show up, then touch the back arrow, and click on the "tasks" folder. Then click on the file "bt". Then a tab at the top will be created that is labled "bt". At the bottom right of the app, make sure that the button says "on". Now exit out of the app. Go to your favorite screen and long click the screen. Next, add a widget, the touch tasker. A window will pop up with alot of entries. Go to the bottom and find "bt on" and touch it. After that, another window will pop up. At this point you could just click the green checkmark and be done. But another thing you can do (optional) is touch the button to add an icon, then check the green checkmark.
Now you will have an icon on your screen that will automatically boot up backtrack and bring you straight to the UI. The next step you want to do is have an icon that will turn it off. To do this, Go to your favorite screen and long click the screen. Next, add a widget, the touch tasker. A window will pop up with alot of entries. Go to the bottom and find "bt off" and touch it. After that, another window will pop up. At this point you could just click the green checkmark and be done. But another thing you can do (optional) is touch the button to add an icon, then check the green checkmark.
Now you will have an on and off button for Backtrack!!!
Please thank me if you like this and donate if it helped you!!!
If you are also a DEV that would like to help on modifying the wifi drivers to allow injection and adding monitoring, please contact me ASAP.

Very awesome !! Can't wait for monitor mode working !
Ty and im following this thread intently
Sent from my SGH-T989 using xda premium

No problem. Im trying to work on it but honestly. I may need some serious DEV helpers to mod the drivers.

Good work man thank u
Sent from my SGH-T989 using Tapatalk

Could this essentially help me in helping my neighbor remember his wifi password
Sent from my SGH-T989 using xda premium

im rly sry but what is this for something for wifi?

Sorry I know this is going to sound noobish, what is this used for? Why would I want it?
Dfjcisnv

If you don't know what this is for then you don't need it lol
Sent from my SGH-T989 using xda premium

Thank you, both of you. I admit after I hit submit I went and googled backtrack. While I guess its a cool party trick, in my opinion of course, I wouldn't have any use for this. Its cool that it is working and the effort the OP put into this, so I apologize if this is taken in the wrong context.
On the other hand, im looking to run Ubuntu on this phone and hook it up to my TV, using a Bluetooth keyboard and utilize the full functionality of this device.
Dfjcisnv

slightly off topic but I have Back Track 5 and a wireless router capable of packet injection. I have no idea how to install the drivers for it on my computer. I read through the instructions but its very complicated anyone familiar with doing this could you pm me?

This is something I can use and appreciate your work. Unfortunately, the links are down.
Thanks in advance
Sent from my SGH-T989 using xda premium

I just a notification from the host saying that I violated their bandwidth restriction and disabled the link permanently. Can anyone help me out with a host that will allow a 3.26GB file for hosting?
Sent from my SGH-T989 using xda premium

OP updated!!!!
Sent from my SGH-T989 using xda premium

When someone gets it running on their device, please let me know what you think. Also add anything that you would think is benefitial.

Could this methods be used loosely to "flash" other Linux distros?
Sent from my SGH-T989 using XDA App

Yes if that distro offered an ARM version of their distro. Then you just need to write a couple scripts to launch the .img file.
Sent from my SGH-T989 using xda premium

Some of you are PM'img me questions about something now working and they are all due to file downloads. Not to sound like an a$$hole, but go back to the directions and follow the directions specifically. Re-download the files and try it again.

YES! you rock!

mrgman421 said:
YES! you rock!
Click to expand...
Click to collapse
Thanks. Just need a little help with the drivers to complete my mission.
Sent from my SGH-T989 using xda premium

Very very awesome!

Finally! Found out how to disable the proximity sensor on Gingerbread!

WARNING: I am NOT responsible if you **** up your device doing this. While I see no reason why bad things would happen, you still execute this (admittedly primitive) procedure at your own risk.
As some of you will now, the cm3602, the proximity sensor of the HTC Desire (and many other HTC devices) is a bad piece of hardware with a high tendency to malfunction. This causes users to be unable to light up the screen during calls (so you can't end calls or dial or do anything until the other person hangs up).
Well I have the solution!
But you need to be rooted
For Froyo users: append gsm.proximity.enable=false to the build.prop file (download a build.prop editor from the market, add property, as a name put gsm.proximity.enable and as key or value put false).
For people with Gingerbread or for those that find the previous method to not be working, there is the following brute force method. Again, you need to be rooted to do this.
What this does:
- This method ****s up the registry key that the system uses to load up the proximity sensor's drivers. Basically, Android doesn't know how to manage the proximity sensor so the sensor doesn't work (but you don't care because it's broken anyway)
You'll need:
- rooted phone
- the app Hex Editor (free on Google Play)
Instructions:
- Open Hex Editor
- navigate to /system/lib/hw
- click on the file sensors.bravo.so
- you'll see a bunch of numbers, some white, some green; don't worry
- in Hex Editor go to settings and check Root permissions, click allow on the SU prompt
- in Hex Editor, click on the search icon, select ASCII, and search 3602
- 4 pairs of green numbers will be highlighted. Click on any one of the pairs and change its value to something else (use 55)
- in the Edit screen, click on the little save icon to save the edited value
- keep searching for 3602 and editing it like before, there aren't many entries
- when you have edited them all, click on the save icon in Hex Editor. If everything went well, it should tell you that it has saved the file. If not, you have not given it root permissions.
- reboot the phone and try calling, your proximity sensor will be dead!
Tested on Android 2.3.7 with CronMod 1.0.6 and kernel 2.6.35.14-CronModKernel-1.6-GSM-RC
If someone with actual skills wants to build this patch into an app or flashable zip it would be great!

Thanks but neither method worked for me on Oxy ZM. The first method did nothing, the second bricked my phone forcing me to restore a nandroid.
Just a warning to anyone who tries this on any other ROM than stock.

Gingerbread method worked for me. Thank you !!
Htc desite on Mildwild CM8 GB Stable. (2.3.7)

I just registered to say THANK YOU from the bottom of my heart. I got HTC Desire a few weeks back and I've tried bunch of stuff, I've settled down for MIUI rom that has got Proximity off option in call settings, but I couldn't get past the fact Runkeeper app wasn't working for me.
To all the others, I've followed this Gingerbread tutorial with Hex Editor, step by step, I even wrote 55 instead of other values and it's all working!!! Awesome, man. Thank you. Thank you. THANK YOU! :good:

Doent work on my Desire S
I've tried everything....

Serious issue with sudden turnoffs

I've noticed that my device has suddenly turned off on several occasions; I only notice because it does not respond to the power button and to use it I must take out and reinsert the battery.
I am running the latest installer build. Is this an issue with CM, the phone or something else? I need it fixed quickly because I am missing important text messages and phone calls. Should I flash M9 over the installer build, or is it something serious enough to merit a deeper change?

RaymieHumbert said:
I've noticed that my device has suddenly turned off on several occasions; I only notice because it does not respond to the power button and to use it I must take out and reinsert the battery.
I am running the latest installer build. Is this an issue with CM, the phone or something else? I need it fixed quickly because I am missing important text messages and phone calls. Should I flash M9 over the installer build, or is it something serious enough to merit a deeper change?
Click to expand...
Click to collapse
It sounds like you're having issues with your phone not waking up. A couple things you can try immediately(these are terminal commands to enter in terminal emulator or adb):
### lower wakeup thresholds
Code:
su
sysctl -w kernel.random.read_wakeup_threshold = 64
sysctl -w kernel.random.write_wakeup_threshold = 128
### increase max frequency
Code:
su
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
When your phone screen doesn't turn on when you press the power button, try plugging it into the charger to see if turns on then.
Also this can sometimes be a kernel related issue. Try flashing some afterstock kernels like Fancy or Dirty V.

Proximity Sensor Issue

I have been using the Galaxy Note 2 for about 2years and not until 1year, I started rooting/fiddling with the phone to enjoy maximum features samsung has to offer i started facing this problem since then(dont remember when exactly). The proximity sensor fails to function like it used to. Whenever i make a call, the screen turns off and doesn't turn back on until i press the power or home button or bring the device to a bright sunlight. I ignored this thinking the sensor was broken/damaged. I have reflashed the device several times to stock and customs and still the sensor seemed to not function. I was reading the a thread and tried the following command using Terminal Emulator with root permissions:
Code:
$ su
$ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
To my surprise the sensor works perfectly now BUT it does till i reboot, after that it is the same problem.
My question is, is the calibration gone wrong? If so where are the values stored?(i'm asking this because even after flashing the device with stock ROM and factory reset, it still persists). How do i permanently fix this?
I'm using Ditto Note 3 ROM v5.2

Themes / Apps / Mods [FIX]IN CALL PROXIMITY SENSOR FIX

Congratulations guys I have created n tested highly advanced fully automated solution , now screen will work during calls as it should W/O NEED OF PROXIMITY SENSOR, WAIT FOR NXT RELEASE, TESTING.....
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
proximity_fix2.xml
Backup from action
drive.google.com
7. What's next.
Probably u will have a very good workaround where by screen will act like it should during call WITHOUT PROXIMITY SENSOR

using this method to import the xml file ended up removing all my custom tasker profiles, so if possible please share your profile using this method: https://tasker.joaoapps.com/userguide/en/sharecreation.html
Edit: also this seems like a duplicate of this thread that was locked by a moderator a couple of days ago : https://forum.xda-developers.com/t/closed-fix-proximity-in-call-malfunction-fix.4344539/

ticktock666 said:
using this method to import the xml file ended up removing all my custom tasker profiles, so if possible please share your profile using this method: https://tasker.joaoapps.com/userguide/en/sharecreation.html
Edit: also this seems like a duplicate of this thread that was locked by a moderator a couple of days ago : https://forum.xda-developers.com/t/closed-fix-proximity-in-call-malfunction-fix.4344539/
Click to expand...
Click to collapse
yes it was locked since i had hot talk with moderator on their "rules"

varunrocks17 said:
Congratulations guys I have created n tested highly advanced fully automated solution , now screen will work during calls as it should W/O NEED OF PROXIMITY SENSOR, WAIT FOR NXT RELEASE, TESTING.....
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
proximity_fix2.xml
Backup from action
drive.google.com
7. What's next.
Probably u will have a very good workaround where by screen will act like it should during call WITHOUT PROXIMITY SENSOR
Click to expand...
Click to collapse
Hi , i have a Redmi Note 8 Pro my sensor is completly damage i want to lock it value at 5 forever so that the screen never turn black on a Phone Calls , how can i do it please ?