[HACKS] UPDATED Droid RAZR Utility [WINDOWS]

Thank you for taking time to elaborate the method you describe for everyone to potentially benefit from. It seems at times that developers speak through such a familiarity with the process and lingo that the length of explanation they give - no matter how detailed or concise they make it, seems completely intuitive to them however for a newbie or someone who is not technically savvy, it's hard to follow and may lead them down paths that can sometimes result in dire consequences. I see it often (especially when doing things such as rooting, flashing roms, etc.), and in the past, often I have been one who tries to decipher that lingo and put it into plain English for the benefit of others. This is why I can appreciate what you've done.

In my case, I am guilty now of perhaps not having clearly conveyed my steps taken earlier. To clarify, I didn't extract the separate files to the c:\ root directory, but to its own named folder (DroidRAZRUtility1.4) as you suggest. It works there. The problem is it's completely where the folder with the rootkit is placed that makes all the difference for me.

Initially I extracted the files to a folder named "DroidRAZRUtility1.4" on the desktop. I did this because I typically treat the desktop as sort of an incubator for new tools, and only once I am sure they work the way they were intended, do I move the folder to a permanent storage location such as "c:\Program Files\DroidRAZRUtility1.4". I've found that when the folder named "DroidRAZRUtility1.4" and containing the rootkit (DroidRAZRUtility.bat, folder named "files", OverclockingREADME.txt, and the file called "1300mhz") is placed on the desktop, running the bat file will not open a command window properly. When I double-click on the bat file, it initially appears to open and I see a flash of a command black screen with yellow text, but it closes before I can even make out any of the text. This can be reproduced an infinite number of times and the results are the same each time.

To prove that it's being on the desktop that makes the difference, I just now tried (based upon your suggestion) to put a shortcut on the desktop that points to the bat file in the folder on the desktop. When I run that shortcut I get the same results, so it doesn't matter whether I try to run it directly from inside that folder, or if I use a shortcut pointing to the same bat file. What's even more interesting to me is when I actually explore to the physical folder on the hard drive that points to the desktop (C:\Documents and Settings\UserName\Desktop\DroidRAZRUtility1.4), and try to run the bat file from within the physical folder it still doesn't open the tool successfully either.

However, if I take that entire folder and move it to the root directory of the C: drive (C:\DroidRAZRUtility1.4) then the bat file not only works from inside the folder directly, but will also work as a shortcut placed on the desktop or anywhere else on the computer, with the target pointing to the file and folder on the C drive (C:\DroidRAZRUtility1.4\DroidRAZRUtility.bat) as well. Again, to further prove that having the folder anywhere else other than on the desktop will work, I moved the folder to the program files folder (C:\Program Files\DroidRAZRUtility1.4), and again it works without a problem, and again no matter where I put a shortcut including on the desktop it works.

I am not sure why this is so since I am very rusty on my code and really only experienced in BASIC (yeah, BASIC...LOL), but I am speculating that in the script contained in the bat file, at least one file or folder is called with a command that is pointing to the physical root (C:\) directory and then to the self-named folder, rather than pointing to the relative directory or virtual folder no matter where that folder is contained. The other possibility is that since the desktop isn't really a folder in the strictest sense of the word, but is more an image or virtual mirror of the folder "C:\Documents and Settings\UserName\Desktop", perhaps the bat file can't resolve the actual folder name contained in the shortcut or on the desktop.

So why make such an issue of it? Well I am not really trying to make an issue of it so much as to understand why I was so frustrated in trying to get it to work while most everyone else was apparently not having the same problem, and to also assist others who just might stumble onto the same problem I'd had. Should it be noted in the instructions that the folder should NOT be extracted to the desktop? Should the code be revised to resolve the proper folder address? Is either necessary or even (in the case of the code and address resolving) possible? I don't know. What I do know, at least on MY PC is that if this rootkit in its extracted form inside its own named folder it will not run if the named folder is placed on the desktop.

 

You don't need to apologize. If it's a quirk in my Windows installation as your research apparently proves then it's something that I have to work through myself.



Sent from my DROID RAZR using DroidForums

 

Was it a 10 character minimum? I thought it was a 10K minimum. I am sorry for the rant.

Sent from my DROID RAZR using DroidForums

 

Used the updated utility this morning - worked great! Thank you again for the hard work on this!

 

I used it too and it was successful in fastbooting my RAZR. I had fastbooted to 744 before, and then OTA'd to 748 and then to 173. When I did it the old fashioned way, all apps and settings remained. Unfortunately I missed the line that warned the internal SD Card would be formatted in the rootkit. Since I had fastbooted before I expected nothing different. Obviously my oversight.


Sent from my DROID RAZR using DroidForums

 

Oh, mine was not planned and I had no way to back it up so I lost all of that too...I have a calendar reminder to back up to my hard drive now at least weekly...