First, to answer mixed responses:
- don't have HDMI cable - never messed with an "otg mouse" before, didn't know about it, and would have probably presumed it needed some screen interaction to configure/enable. Anything requiring more money just to try was low priority, especially since the web had this as a recurring unresolved problem.
- files .... hmm.... well when I started this project, the drivers I had installed wouldn't allow me access to the internal SD card. After everything I've installed and updated throughout this journey, I now have PC access to these files. Too bad I didn't read your post sooner. Regardless, I wanted access to the phone to fully backup, transfer as well as clean before I disposed of it. Besides ... since when does a hack require a "why"?
So - hack is complete. It involved getting started with another droid razr that was still functional to get screen coordinates. Basically, I used various ADB commands to issue events to simulate touching the screen, input keyevent to navigate, android screencast to observe and an extreme amount of patience.
WARNING: PERFORM AT YOUR OWN RISK. ITS AKIN TO BUILDING A SHIP IN A BOTTLE! Different phones and screen sizes require a change in click coordinates. You may drop icons in the trash, unintentionally call bosses or ex girlfriends or worse.
Relevant information links:
Please Login or Register to see this Hidden Content
Please Login or Register to see this Hidden Content
also very helpful was the input.h header file.
1) I started with the instructions on the softteco blog at the bottom of the list. I connected my working droid razr and got the events needed to simulate unlocking the screen. From there I hacked around for a few days to map out all the locations I would need to click. This was frustrating because I'm guessing the digitizer's dimensions and coordinates are independent of the display screen. Points weren't proportional to the screen dimensions and I couldn't predict where to click. - So I abandoned any functional mapping and documenting.
From the above I have to warn you - depending upon your device's digitizer calibration, my X Y coordinates may be different than yours. You may need to read the above links, my scripts, and adjust your coordinates slightly.
2) I built a DOS batch script to help unlock quickly. This assumes you're already connected with ADB and watching interactively with android screencast:
Please Login or Register to see this Hidden Content
3) I also ran into an issue with my WiFi not being on. So I had to fumble with this a little. This batch script assumes you're unlocked already and you have a good WiFi configuration that will automatically connect:
Please Login or Register to see this Hidden Content
4) The bulk of my navigation consisted of arrow-keys, enter buttons and so forth. I leveraged the search feature in Google Play store to quickly access apps that I knew were 5 pages deep in my apps folder. The key events from the above stackoverflow link were indispensible. Namely Arrows and enter:
Please Login or Register to see this Hidden Content
5) I went ahead and was able to root my droid using the razr_blade hack. I split the run.bat script into two at the steps needed to configure smart actions. Because of the bugginess of running screencast, I didn't do side-by-side so ADB wouldn't crash mid-rooting. When the first half was complete, I used my unlock batch script, navigated with keys to find smart actions, simple arrows and enter to make it work and completed the second half of the script.
6) Android screencast was a disappointment, although I rooted the phone, changed the permissions per the web site, the java applet didn't function as an interface. I resorted to using droid VNC Server using the above navigation to get it installed. Its slow, but functions and I have a remote interface now. I still need to get into settings to make sure it will run on reboot w/o additional config.
Incidentally - you need to get adept at your keystrokes by the time you need to use any root apps. The SU pop-up only lasts a few seconds and you need to down-arrow, side-arrow and hit enter to grant the app SU permissions.
Hope this helps!
.gif)
