Data reset didn't do anything even though the screen said success. As a final question, when I tried to wipe clean my internal storage from recovery this morning, I got this message:
Using rm -rf on '/dev/block/mmcblk1p25'
E:tw_format_rmfr: unable to locate volume for device "
Putting this in google sent me to a thread in another forum where someone else had a similar problem on a different android phone and that thread didn't have any answers. Any thoughts on this?
Not sure there sounds like it can't read the internal storage. The tool should be able write over it back to stock.
Sent from my cm_tenderloin using Tapatalk 2
Anybody else been dealing with the "adb server is out of date" errors when running the tool? It's always worked fine, but in a bout of pilot error I decided to unroot before the JB OTA. Unrooting worked fine, but then I had second thoughts and figured I should probably use the Voodoo Rootkeeper. I hopped back onto the tool this morning to root, and it's not working and returning a bunch of errors indicating the adb server is out of date, and subsequently the device isn't being found properly. I've found some resources on the Intertubes, but nothing directly relating to the Droid 4 and this tool; I'd rather not make generalizations and use an answer for the same problem in another context if it will result in my having a Motorola Tire Chock. Anybody dealt with this?
Most likely it just means that the adb server has been running for awhile. Restarting the tool or maybe your pc should be all that is needed.
Thank you much, I'll give it a try from a cold boot when I get home. Just out of curiosity, is the download link still active? I'm getting a 404 error at Dropbox when I try to hit the page at work. Thanks again for the reply, as well as all of your hard work!
The dropbox link is dead, kept going over the bandwidth. Just use the dev-host one in my signature.
Every time I run the tool, it stops and restarts the ADB daemon then closes. It will not stay open for me to select any options. I downloaded the lite version from the dev's file list. Yes, I have admin rights on my PC and have also attempted to "Run as administrator." I've looked through the .bat, but don't see any reason as to why the CMD window would not stay open. I began inserting "Pause" commands after every line to troubleshoot and the bad command seems to be the following:
::Load up our menu selections
for /f "tokens=1,2,* delims=_ " %%A in ('"findstr /b /c:":menu_" "%~f0""') do echo.
Any idea why the CMD window would close upon receiving this command?
Last edited by BornAgainBassist; 03-19-2013 at 01:15 PM.