yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] TimelesslyPrecise:
Source

OP, can you post these zips in the original post??

Q9, can you source a link to where you found these?

Thanks in Advance (and Thanks!!)

;]

Also, general question for everyone...

Is there any other NV edits (anybody may be aware of) not limited to, but mainly, pertaining to tethering hack?

i feel like i have done this hack, and tethering still not working.. (using cdma, not gsm)

T.I.A.

---------- Post added at 05:18 PM ---------- Previous post was at 05:09 PM ----------

Hey, could this be where you got RadioComm??

http://xdaforums.com/showthread.php?t=1138072

;]

Links still good as of 4-7-12

(Feel free to create a direct link to my post, here at your original post)
[Motorola Droid 3] cellzealot:
Q9Nap is an old friend and we went over it together and figured out what wasn 't working with the strings for the older zips and he made these up with the proper strings and updated binaries and tested them.

I no longer have a D3 to test them myself.

Any any recent versions of RadioComm you find on the net were released by me on various forums, going back to 11.7.4 from almost 3 years ago. ;)

Here is 11.12.1 which is not the latest, but is the most recent posted publicly, I believe.

http://db.tt/JiTsoSd1
[Motorola Droid 3] TimelesslyPrecise:
Haha, Sneaky!!! ;]

Mind if i update my post with this link?

well, upload to MediaFire, then update my post.. given your permission is granted..

Check PM ;]

I've got many questions related to D3 Radio, GSM, and cdma tethering
[Motorola Droid 3] cellzealot:
I don't mind however you would like to host it.

Regarding your questions about the D3 and the band unlock, there is no NV editing to band unlock the D3 because they changed the may the lock mechanism works and removed it from the NVM and made it inaccessible in the signed radio image. Since only signed radio images can be flashed, they can't be modified.

Fortunately, as you will note in the thread on this forum, there is a band unlocked Chinese radio from the XT883 that can be flashed to the D3 because they are identical hardware and the signatures are accepted. This means that you can run that radio under all of the stock builds available and most of the custom ROMs that I have seen reports about, including ICS builds. You need to use an edited build.prop as well to get the radio properly recognized had configured for GSM use.

Unlocking the SIM is a separate matter and also does not involve the NVM.

So, I am not certain if that answers your questions or not, but the NV edits like those on the original firmware builds for D2G and Pro were considered far too vulnerable to tampering and were changed at the behest of VZW almost immediately after release.
[Motorola Droid 3] TimelesslyPrecise:
****e..

i recall that.. the hack was discovered for the old BB, but the new broke it.

Well, with the RadioCOmm.. do you think i have the capability to change\force the 1700 band for upload? (as far as editing and manipulating the baseband?)

possibly, comparing the values between the chinese radio, and the US radio?

Do i have this type of flexibility with the Radio and RadioComm?

do i have this type of flexibility with QPST, DFS, or CDMAware?

Thanks for the resonses
[Motorola Droid 3] jb265536:
Oh no!

Performed all the steps as listed on Rooted Droid 3. Tether still doesn't work, but now I can't download anything from the Google Play store without wifi. Everything else works, internet on browser, etc. Was interested in reversing the hack, by by copying in the original values for 8013, 8014, etc. in the appropriate locations and see if this does anything. Does anyone have the Dec Values saved pre-hack?

John
[Motorola Droid 3] Jason Roach:
If those r the numbers u used then that the problem. I think its 8041 8042... so on

There is an awesome video on youtube by TweakMyDevice that shows exactly how do it and he even mentioned that its the exact way for the d3
[Motorola Droid 3] TimelesslyPrecise:
Ouch.. Def put those values back... Try the values listed in the guide..

If it still doesn't work, try another ROM... Aosp gingerbread, or ics. I couldn't get tether working with steel Droid or stock... But this hack did allow for it to work with ics..

Take your time, read through the guide, and have faith. You can do it :)
[Motorola Droid 3] yanger:
Any easy methods to just flash a file to make the change happen vs using the extra software?
[Motorola Droid 3] Jason Roach:
i lose my connection to google when i activate the tether and it causes it to run slow, the icon just stays white. any ideas? d3 rooted mav 4.0
[Motorola Droid 3] Q9Nap:
http://xdaforums.com/showthread.php?t=1628982
[Motorola Droid 3] y0himba:
I think he posted this as an idea, since it worked on another device, without verifying it worked on the Droid 3, then prematurely posted it to the other threads telling folks the other methods were not needed.

I am sticking with the radiocomm method.
[Motorola Droid 3] insanespain:
I've been sifting through this thread for awhile now. I've got a couple questions if someone could answer them. I was originally going to do this hack, but then hopped on the ics kick back on hash's alpha 4 and I've been on ics until now. Tether ALWAYS worked on ics roms without doing any hacks at all. But the lack of being able to send mms and the lack of video camera has finally made me go to mavrom. I've been unable to get tethering to work with any of the market apps, which brings me here. Why does it work on ics without this hack, but not on gb? And is there a flashable zip that I can use with safestrap instead of messing with the radiocomm software?
[Motorola Droid 3] TimelesslyPrecise:
I don't know why it works on ics, but not the other roms.. Same issue here :p

It would be nice to know..

But, look a few posts up, there are links for the clockwork recOvery flasher zips which you can use to bake things easier..
[Motorola Droid 3] cybersud:
Impact of new DROID3 update?

I have been using this hack for awhile on my VZW Droid 3 and it works great.

I recently got notification of an update to the OS to a new version. Does anyone know if this messes up the tether hack? I don't want to update if I lose tethering.

Thanks in advance.
[Motorola Droid 3] TimelesslyPrecise:
Is it ics?

It might mess it up.. Not sure.. Most of the time, factory updates ruin root and possible radio hacks, like this one..

Couldn't hurt to test it out and report back.. If it does break it, you can always use an sbf back to older state. Check around the forum for older sbf files.
[Motorola Droid 3] cybersud:
Thanks for the note.

I am currently on the original Verizon distribution, but now I am getting a notice about version 5.7.906.en.US as being available.

I wondering if anyone else was running that version and if the radio hack still worked. I have looked far and wide and in some places it says moving to the new version is no impact and then in others it says it breaks it. So, I am confused.

Any input appreciated.

Thanks
[Motorola Droid 3] cellzealot:
Any update to the radio will overwrite the NV edits, so you will simply need to redo the procedure.

This method will always work for 3g devices because of the nature of how they authenticate the data connection.
[Motorola Droid 3] nodixe:
This question is directed @cellzealot or any other such knowledgeable person: I woul like like to revisit insanespain's question a few posts above. I am coming from a DX so I am familiar with TBH tether patch but once I found 2nit aosp roms I never needed it as the wireless tether app would allow the hostedap (infrastructure mode) setup in settings. Then again on my D3 it is similar where the aosp based ICS roms allow hostedap setting. I was wondering why/what's the difference? Also is there a rom that has a working hotspot and hdmi mirror mode?
[Motorola Droid 3] ovelayer:
yes you can still teather with the .906 update..i have never done the tbh hack..

if you dont wanna do the hack try wifi teather for root users on the market combined with most of the newer roms..i use eclipse 3.0 and together i wifi teather great and free..
[Motorola Droid 3] nabilalk:
Ridiculously simple

Much much easier than it looks from the description. Piece of cake, once all the RC program and the drivers were installed, this took less than 5 mins. Thank you OP
[Motorola Droid 3] redsox985:
Unless our radios are written upon activation of the phone and it's done specific to our number, the 8040-8043 strings that I pulled from my replacement D3 matched those pulled from a previous D3. Would they be the same for all of us? Plus, 8041-8043 are all the same.
[Motorola Droid 3] cellzealot:
Yes, the strings are the same for all devices. The way the hack works is by making the values in 8041, 8042 and 8043 match the values in 8040 meaning that the NAI and Tethered NAI show the same authentication to the network.
[Motorola Droid 3] wattnxt:
Did this the day it came out. Before root was obtained for the D3.

It has survived every update so far, never had to update it. Tether still works fine. And I agree, it is WAY easier to actually do than what it looks like.

However; the consequences to not reading and following instructions perfectly can be disastrous

, but was well worth the effort.

After the success with the D3, a similar hack can be applied to the Xoom 4g. Was applied as a 3g Xoom, sent to Moto for the 4g update, and came back fully updated with newest version (at the time) and the hack survived the 4g upgrade and ROM update as well. Been flawless since. Flashed everything from 3.2.2 up to Jelly Bean and back. Still works.

If I had to make the changes again, I would. Thanks to TBH for all their work, and cellzealot for all his help with my endeavors to apply this to the Stingray (M602 Xoom).
[Motorola Droid 3] dalvear88:
Since this phone has root now, is the flash able zip able to be used?
[Motorola Droid 3] apronouva:
Hi,

I've read that this hack will only be able to tether Droid 3 which using CDMA whilst I'm using GSM only on my country. I searched through this forum and perhaps my unfortune that I couldn't find a working answers. A few things I've tried :

1. Applying Droid 3 Tether hack mentioned at the first posts, steps completed and obviously still won't work because this hack intended for CDMA

2. Add APN type as "dun" on the APN setting page still not working

3. Using 3rd party applications like FoxFi and Barnacles.

Nothing worked so far. FYI, I'm at stock 906 ROM rooted with Safebloatremoval script by psouza4.

Any leads ? I'm sure there are solutions to comprehend this issue out there, its just that I'm not knowledgeable enough to solve it by myself.

Thank you in advance,

apronouva
[Motorola Droid 3] crackface:
Unable to apply radio hack to D3

I originally had stock and this radio hack worked using a Win7 laptop.

I then moved to the Eclipse ROM, which instructed us to use the Wifi Tether app from Playstore, which worked.

I not have the minimoto ROM installed, and the Wifi Tether app doesn't work, so I thought I'd try this radio hack again, but it didn't work:

On Windows 8, I installed the latest driver I could find off Moto's web site (MotorolaDeviceManager_2.3.4.exe), then installed Radiocomm 11.11.11, opened Radiocomm and selected the PST USB driver in settings, and plugged in the phone via USB. The light in the upper right corner of Radiocomm stayed red....it never turned green.

On Windows 7, I still had the moto drivers and Radiocomm installed from when I did this when phone was stock. I fired up Radiocomm, plugged in the phone, and the light did turn green. However when I tried to get the SW Version, the white box remained blank, so I did not proceed. I then tried installing the updated Moto drivers I used on Win8, and get the same result with one addition: when I plug in the phone, it fails on installing the MTP USB Device, and when I click on that device in Device Manager, its status says "The device cannot start".

I think I read somewhere that this hack has to applied to stock only...is this true? Otherwise any ideas what could be going on?

Thanks in advance for any advice or help.
[Motorola Droid 3] cobravnm13:
I believe you have a higher chance of success trying the Radiocomm on the stock ROM.
[Motorola Droid 3] three west:
I use it on Eclipse on my DX2.

Having done this a few times, I've found that rebooting the device while in radiocomm can help.

Its a small thing, but maybe it'll help.
[Motorola Droid 3] yanger:
I was soo reluctant in doing this... but since the D3 is pretty old (and this is my replacement phone, which was hardbranded XT861 [see my prev posts, long story] I tried this. It works! Kinda?

The instructions were perfect. Only minor issues I saw were:

I did run this on a Windows 7 x86 PC. Errors were shown just as noted

I tried and tried and tried, and this would never give me my Android version at all. FYI, i'm on Stock Android 2.3.4, 5.7.906.XT862.Verizon.en.US, rooted, safestrapped, safestrap disabled... I risked it and skipped that part after 10 or so reinstallations of the drivers, RadioComm, and triple checking all was correct...

The SIM card not found message didn't appear for me. It did reboot and went right to 3G, Wifi worked, calls worked.

What you didn't mention was if you used the "Tethering and Mobile Hotspot" or the "Wifi Tether" app. I used the Wifi Tether app, and it's working perfectly.... until you disconnect.. sometimes it lags suddenly and the sync icon appears, and anything that requires network gets "queued" but nothing happens until a reboot is done. (Google Voice queues the messages sent, but does not send them.)

I'll try the stock method later today :) but i do enjoy that I don't have to use the bluetooth tether method anymore [it's darned slow]

thanks!!
[Motorola Droid 3] elkay:
Everything worked for me up until trying to get SW Version or doing the RDELEM. Instead of turning green, mine turns red and puts "Error" into the version, and doesn't read data with RDELEM. My light is green at the right, and pink if I use TCPIP. I noticed when I plugged my phone in, I didn't get any "details" screen to pop up like what is mentioned in the original notes. I tried the second page instructinos with the MDM 6x00 selected and no dice, either. The error I'm getting is:

VERSION (or RDELEM) ==>FAILED

Sequence tag mismatch

Error Description ==> Unknown Error
[Motorola Droid 3] elkay:
Ok, so one of 3 things fixed it. I changed all 3 at once, but it's coming back green now. I set the icon to XP SP3 Compatibility Mode, I disabled my Bitdefender firewall, and also in the background behind all my other windows was an update for Motohelper that installed newer USB drivers. Whichever of the 3 it was, I'm back on the right track now.
[Motorola Droid 3] elkay:
Well this doesn't seem to be working for me. I can't make a connection to the mobile hotspot even, regardless of secured or open network. I've tried with a Dell laptop, Alienware laptop, and a Macbook Pro. All of them can find the network but can't make the connection. I also get errors on the phone saying lost connection from 0.0.0.0 with the correct MAC Address for my laptop. I've tried channels 1, 6 and 11. There isn't any network congestion around my house. I've tried reboots will all of my changes. I'm at a complete loss at this point. It's like my phone won't give an IP address to any of my devices.

Also just tried USB tethering, it also does not work. It finds my "network adapter" but does not get internet access. This is on my Windows 7 PC. Mac doesn't support USB tethering without major hassles.

I also just plugged my phone back into RadioComm and read out the 4 values, confirming all 4 match and are correct. I should also note that it looks like my phone is constantly falling into and out of being visible as an access point. Wifi on the phone itself works fine.. but I'm wondering if maybe something is wrong with my adapter in the phone?

Another edit... I also still had my Droid X2 lying around, albeit without being activated anymore. I was still able to load up Mobile Hotspot on it and immediately get my Macbook to see the hotspot and connect, getting an IP address without problems. Obviously I wouldn't be able to navigate anywhere on it, but there was no problem getting to the phone from the laptop. I'm completely boggled at this point.

One last edit... old Droid X laying around, too. It worked fine as a hotspot connection on the first shot (without internet access as it wasn't activated, either). I'm really starting to think the Wifi in my Droid 3 is bad.
[Motorola Droid 3] jasonkaw:
Mine is doing the same thing, When I first got my droid 3 I couldnt get the wifi to work at all it would just reboot the phone after trying to wireless on and off. It finally worked a day or so later.
[Motorola Droid 3] elkay:
Well once I set my router to WPA+WPA2, my D3 connected to my router fine, but looking back I *really* shouldn't have had to do that. Combining that issue along with this, I'm pretty sure I do actually have a bad Wifi chip in my phone. Going to call Verizon to see if they have one in stock by me and swing by to show them the problem (probably with a hard-reset since I will be exchanging anyway *sigh*).
[Motorola Droid 3] elkay:
Verdict: bad Wifi chip in the phone. The new one connects to my laptops fine, and I was even able to set my home router back to WPA2-only. My old phone wouldn't hold the WPA2-only connection more than 2-3 minutes tops without bailing. I haven't tried applying this patch again, going to give it a few days of normal use to make sure all is good. I'm just glad I was able to get a brand new phone even though I'm a few days out of the 14 day window. That would have sucked getting a refurb already, even though the refurb would have likely still been new this early after release.
[Motorola Droid 3] FlyRyan:
I just wanted to reply to this and give thanks. This worked from me and I'm actually posting this while tethered. My experience varied a bit so I'll explain mine in hopes to help others.

I'm on Win 7 x64 on a MacBook Pro with Bootcamp. I got some of the errors you listed when I installed, but not all. I just kept clicking through until it launched. No real hiccups besides the popups.

When I first connected, the light in the upper right was purple. To get the green light, I clicked Settings -> USB -> PST USB Driver. It went yellow for a second, and then green.

When I tried to Get SW Version, I got no response. However, I soldiered on with the rest of the instructions and it all went smooth. I clicked Restart, and I was done. I did NOT get the "bad SIM" error.

This was SUPER easy to do. I recommend ignoring the screenshots and just following the text instructions. They are easy to follow and simple to perform.

Thanks again! You rock!
[Motorola Droid 3] elkay:
I never got a bad SIM either time I tried. To above, pink meant you were connected via LAN instead of USB. It probably would have been fine.

Curiosity didn't kill the cat this time. I bit the bullet and just gave this a shot with the new phone. Worked like a charm. Both my Macbook Pro and my Alienware M17x connected fine on the first shot. Now I just have to finish reinstalling all my apps and settings to the new phone. *sigh*
[Motorola Droid 3] redddog:
No SIM card message here either.
[Motorola Droid 3] jasonkaw:
Well mine wont work with my laptop, no IP, but my other phones can connect to it and get an IP and browse the internet just fine. Will have to try the nook once the wife gets home with it.
[Motorola Droid 3] elkay:
I'm wondering if the people getting the SIM message have their phones still set to Global. I'm set to CDMA-only.
[Motorola Droid 3] neilrl79:
well i bit the bullet and tried it out, i got through every step with no issues, restarted the phone and all is well.... except that everytime i try to turn on the hotspot app my phone reboots, any thoughts on what is happening?

edit: after powering down and pulling the battery then powering back on, the reboots have stopped and i am in fact editing this post while tethered to my droid.
[Motorola Droid 3] jchenny:
Hi, does this also work if I'm using Droid 3 with foreign SIM card in a foreign country under GSM network (not CDMA)?

Thanks so much.
[Motorola Droid 3] pplude:
This worked great (using the modified PK4 post, thanks!). I followed some advice right off the bat and did 3 reboots.

The only thing is that when I start and stop the hotspot I lose 3G/1X for about 30 seconds. No big deal, but unusual.
[Motorola Droid 3] cellzealot:
That is how it is supposed to work. The normal data connection using the NAI

is dropped and it switches to the tethered NAI for the 3g Hotspot. This is how they differentiate between internal data use and external data for the tethered device, except because those values have been altered in the NVM to be the same the network can no longer see the difference between them and registers all data use as internal.

That is why this is such a powerful hack and why it will always continue to work on all 3g devices until they change the network authentication protocols.
[Motorola Droid 3] pplude:
Cool. Wasn't aware of that. Thanks for the dummy explanation
[Motorola Droid 3] neilrl79:
Will this hack survive a factory reset?
[Motorola Droid 3] cellzealot:
Yes, and it will even survive *228 OTA programming because it is writing to items that are not part of the standard service programming NVM, but actually to the locations in the Moto proprietary NVM where the default authentication strings are stored.

The only things that will remove it are an update.zip OTA that includes a baseband update or flashing with an SBF file. This is why it's very important for users to understand what they are doing when they make these edits because they are very low level changes that are not easily managed by end users.

The easiest way to revert them is to simply save the default hex values and write them back with RadioComm if you need/want to have a clean default NVM configuration for any reason.
[Motorola Droid 3] neilrl79:
Ok, so let me ask you this, are the default hex values the same on each device, meaning alll D3 are the same or is each individual device different? And if they are the same does someone have the values saved?
[Motorola Droid 3] cellzealot:
Here is a zip file containing two .NVM seem tables for use with RadioComm NV/SEEM feature which writes these files in a single operation.

One file will write these SEEMs enabling tethering on any Moto Droid device and the other will write the default values to disable it on any Moto Droid device.

Or you can open them up in Wordpad to just read the data and write it manually if you prefer.
[Motorola Droid 3] elkay:
I was thinking of taking a dump of the NVRAM to see if the MCC 310 block was in there.. you think that's a possibility? Even just zeroing it out should allow AT&T & TMo SIM cards on the D3.
[Motorola Droid 3] neilrl79:
Thank you cellzealot, this is a big help.
[Motorola Droid 3] kerryrey:
Works like a champ

Perfect thanks folks
[Motorola Droid 3] neilrl79:
For some reason i can't get this zip file to download/open properly. Can someone post up the seem tables individually. I found tthe seem table to tether on the MDW thread but i can't find the seem table to undo the hack. I would greatly appreciate it.

Edit: I found a tble to undo the hack on a DroidX thread, am I correct in the thinking that it's exactly the same 128 character strings that the D3 uses?
[Motorola Droid 3] cellzealot:
yes the strings are the same on all devices.
[Motorola Droid 3] neilrl79:
Cool.... i noticed that with all of the zero's it seems like there are more than 128 characters in each string, is that right?