Database Develop

[Q]How to activate G1 through wifi?

Upon reading the title you probably entered ready to flame me for not using the search button. The reality is though, that is just one of my many problems I'm having. I'll start from the beginning, give you the whole rundown and hopefully you can help, because if I can't figure this out soon I'm going to start smashing things, my G1 being first on the list.
A couple of days ago i was just surfing around, heard about custom ROMS, rooting, etc. so I started my journey. Thinking this would just take an afternoon, at the max, was a mistake on my part. I started here:
[ROM]TheOfficial TMO (US/EU) & HTC ADP - CRC1- Rooted [8/17/09]- v1.5.2-SecurityPatch
Looking at the prerequisites, I realized I lacked both the requirements so I followed that threads link to here:
Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
I was able to complete up to step 7, but 8 posed a problem.
When trying to sync my google account to the phone it gave that old message we all know and love from when the G1's were just released. The one where it tells you: "There is a problem communicating with the Google servers. - This could be a temporary problem or your SIM card may not be provisioned for data services. If it continues, call Customer Care."
At first, I thought maybe it was because I had horrible service in my house, ranging anywhere from 0-2 bars. Thinking I could easily fix the problem by walking up the road to get 4 bars, that's what I did. Still having trouble communicating with the servers. It's obviously not server overload like they tried to say at launch and it can't be I don't have data services because I've been paying and using them for about 9 months now. So I set off to the internet for a fix. I came across this:
[How To] Activation over Wifi
Reading the first sentence, it told me to set up ADB. So I went here:
Setting up ADB
But, I obviously couldn't complete the steps listed because I can't set my phone to debugging mode with out it being activated. So I went back to the Wifi act. page and scrolled down to find this:
[How To] Activation over Wifi (12th Post)
Following the first step, I typed <enter>reboot<enter> and nothing happened.
This, obviously, confused me very much. Because, did I not just wipe my whole phone and install rc29?
But I disregarded it, putting it to the side as a fluke and hoping the rest would work anyway, because at this point I just wanted things to start working.
I went to step 2, but once again I can't do that because I don't have access to the phone settings.
But I just continued.
Upon trying to complete step 5, I was just pissed... This seems like a never ending road. Of course, my phone had to be wrong and show up as a USB mass storage device. So I followed the steps, but I don't understand part D in step 5 because it only gives me one choice on the list which is USB mass storage device. After this I started trying everything, uninstalling that driver, turning of PnP, just about everything I could think of.
If someone could just help me, even a little, I would be so very happy.
If you need any info at all just, pictures, build info, w/e I/'ll have it to you as soon as I see your message. If you don't understand something I said, ask right away and I'll answer. Thank you so much in advance lol
Mind you, I've tried all these guides a couple times over, I've tried different guides and I've installed rc29 3 times now. Still no luck

I'm confused....
I have a few questions before we start you on the journey to getting you rooted.
Firstly, am I understanding things correctly when I assume that you have already flashed DREAIMG.nbh (RC29) onto your phone and can't get past the setup screen?
Secondly, you say that you have data service, but then say that you didn't have enough "bars" so you headed up the street for more "bars". Are you sure you have data service because the bars on the phone have to do with cell reception and have nothing to do with data service.....
Thirdly, are you on 3G or EDGE in your area?
If you do indeed have a data plan for sure, then other than a crappy 3G or EDGE signal, there really shouldn't be a reason for the error message your getting other than google's servers might actually be experiencing difficulty. No way to know for sure.
If/when you are able to get past the login screen to root, go to this link
http://forum.xda-developers.com/showthread.php?t=548924
instead of Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
its recently updated, and easier to follow.

I have bad service...
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?

KingTasty said:
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
Click to expand...
Click to collapse
If you cannot get adb working properly, then you cannot use JF's method to bypass the signin screen therefore you just have to wait until you can get to a better service area.
Your two choices are: bypass the signin screen or sign in over the network. You can't sign in over the network as previously stated by you, and you cannot bypass the signin screen because you can't get adb working. There is no way to setup wifi within android if you are stuck at the signin screen

but wait?
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?

KingTasty said:
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
Click to expand...
Click to collapse
There are plenty of guides on how to get adb working... its just so happens that you reported that you can't figure it out. If you can't figure it out and get it working, then you can't use the sign in screen work around as outlined in JF's post.
The very first step in JF's work around is
You have to connect to your phone with adb shell and get root access, and then type the following command:
Click to expand...
Click to collapse
Since you can't do that, you can't do the work around. Try reading up more on adb and see if you can get it working.

Couple questions
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?

OMG help me too i have the same problem !!!

KingTasty said:
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
Click to expand...
Click to collapse
I know for a fact there that I saw some terminal command not too long ago to be able to activate usb debugging from the command line. I can't for the life of me remember where I saw it, but if you can be patient, I may be able to find it eventually.

florevil said:
OMG help me too i have the same problem !!!
Click to expand...
Click to collapse
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far

KingTasty said:
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
Click to expand...
Click to collapse
RC29 has the hidden shell also which is what allows the telnetd command to be entered to start the rooting process. It sounds like when you enter the reboot command at the welcome screen you should be getting a reboot because you said you installed RC29. It also sounds like your doing the commands in the correct spot but just to recap, you should be at the "touch the android to begin" screen, once there, just slide out the keyboard, hit enter, type reboot, hit enter again and the phone should reboot.
What happens if you keep trying to follow JF's guide even though you can't get the reboot to work? Have you made any promising progress with steps after the A few tips and tricks section?

I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.

KingTasty said:
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
Click to expand...
Click to collapse
Glad to hear it and yes, your right, nothing that you can see will happen. Essentially what it is doing is executing the command behind the scenes same as would happen if you were to hit the check box next to usb debugging if you were able to.
The way you will see if it worked is you should be able to open up a command prompt assuming your a windows user and type:
Code:
adb devices
You should see a device listed something like HT.........
Lemme know if you have anymore problems

Still nothing.
I tried but I don't think it worked, but it may have. The problem could be my drivers so I followed this.
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Click to expand...
Click to collapse
I did that but every time I plug my g1 back one it makes a new one, calling it USB Mass Storage Device. I keep deleting it but it keeps coming back every time.
Here's what I got in cmd.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tyler>cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools>adb devices
List of devices attached
C:\android-sdk-windows-1.5_r3\tools>adb shell
error: device not found
C:\android-sdk-windows-1.5_r3\tools>
I'm not really sure what to do now... I guess I keep trying to see if it'll work. Meanwhile, what do you think?

King,
PM me your contact info and I'll try to troubleshoot this with you. I did it the old fashion way without any programs and I think I remember my steps so I just have to walk through it again.
You could also try this adb tutorial, thats the one I used and would use if I were to walk you through it.
http://forum.xda-developers.com/showthread.php?t=502010

Alright yeh, sounds good.
Gimme like 20 min, I'm gonna go grab something to eat quick.
Take a look here though, I uploaded what re appears every time I plug in my g1. Something must have been turned on or changed be cause now 3 new drivers appear every time instead of just one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But still no luck in cmd, so something is still wrong...

Hi! I have the same problem too. There're a lot of tutors online but they are just copy and paste from each others. I did pass by the first time via wifi when I root my G1 but cann't the second time rooting my girlfriend's.
The USB driver that window or HTC using before works on vista and only see the device as ADB composite deivce, but not anymore, Windows now recognized the devices as ADB composite device AND mass storage. I don't know about XP. and don't know what to do about it
I think that's why I can not enable ADB on G1 by typing "setprop....enable 1"
Anybody help? Offering your Tmo SIM card for 5 mins? I am at Dallas. Txt [email protected] #469-759-9897 Really need it PLZ

I guess this is obvious but I just want to clarify: Everytime you flash the rom you need to re-activate the phone? Or is activation only a one time requirement?
I just purchased a used, tmobile g1 (from the US) and am hoping to root it and flash SuperD's wrong as soon as I get it. However, the problem is I obviously don't have a Tmobile SIM and I don't have a data connection on my local sim card.
Do I have to go through these ADB steps to activate the phone? Thanks!

[Q] Captivate - Soft Brick help

Hi there,
I have a stock Captivate. I patiently waited for the Froyo update because I didn't want to do anything that might void my warranty that I'm paying for every month.
Very, VERY long story short: I believe my phone is has been "soft bricked" - that's a term I found on here after reading countless hours worth of posts. I've got the phone--!--cpu thing, can get to the download screen, but the Kies Mini won't recognize my phone in emergency recovery mode. My computer recognizes it *sometimes*.
I followed the official Samsung update directions to a T, but Kies is garbage and it booted me out of the installation and left my phone screwed up. I've tried using two different computers (Win7, a 32-bit and 64-bit) and three different stock USB cables. I've turned off firewalls and uninstalled IE9; basically, I've tried everything I could find while searching for about 10 hours. 0_0
So, I'm over it. I know that AT&T will be useless to me so I'm just going to try to fix it myself. I've installed Odin3 and would like to get my phone working again. Luckily I saved my pics and contacts, so I can live with a fresh start. The question is, which version do I "flash" (I hope I used that term correctly)? I consider myself tech savvy but there are a million versions floating out there and I don't want to screw up my phone any more than it already is. Apologies if this is easily found somewhere else, but I did read a ton of FAQ pages and am still not comfortable picking out something to download.

thej0nes said:
Hi there,
I have a stock Captivate. I patiently waited for the Froyo update because I didn't want to do anything that might void my warranty that I'm paying for every month.
Very, VERY long story short: I believe my phone is has been "soft bricked" - that's a term I found on here after reading countless hours worth of posts. I've got the phone--!--cpu thing, can get to the download screen, but the Kies Mini won't recognize my phone in emergency recovery mode. My computer recognizes it *sometimes*.
I followed the official Samsung update directions to a T, but Kies is garbage and it booted me out of the installation and left my phone screwed up. I've tried using two different computers (Win7, a 32-bit and 64-bit) and three different stock USB cables. I've turned off firewalls and uninstalled IE9; basically, I've tried everything I could find while searching for about 10 hours. 0_0
So, I'm over it. I know that AT&T will be useless to me so I'm just going to try to fix it myself. I've installed Odin3 and would like to get my phone working again. Luckily I saved my pics and contacts, so I can live with a fresh start. The question is, which version do I "flash" (I hope I used that term correctly)? I consider myself tech savvy but there are a million versions floating out there and I don't want to screw up my phone any more than it already is. Apologies if this is easily found somewhere else, but I did read a ton of FAQ pages and am still not comfortable picking out something to download.
Click to expand...
Click to collapse
What you will need to do is use Odin to flash back to stock 2.1 and then load a custom rom. To be honest you cant do anything here that cant be reversed for your warrenty. Now as for Odin that is the tricky part as some work for some and not for others. Do you remember what version was on your phone? JF6 or JH7? What build number is it? I have a odin one click that I use and would be willing to post a link but I dont want you to wind up in a worse spot then you are now. I would search for how to unbrick a captivate and if non of that works let me know and I will give you a link to what I have. Or you could call ATT and tell them what happened and return it to warrenty

Thanks for the reply. I didn't know any of the pertinent details regarding the version I had.
I ended up going to an AT&T DSC Center during my lunch break. They took one look at it and swapped it out under the warranty; it took about five minutes. The "new" phone didn't have the latest version but I was able to update it with absolutely no problems on Windows 7 32-bit (throwing out all the details in case someone stumbles upon this for help). I guess Kies is just a very fickle program. I'm pretty bummed but at least I have a functional phone and as added bonus, I stumbled upon this kick-ass website that I can browse in the future.

thej0nes said:
Thanks for the reply. I didn't know any of the pertinent details regarding the version I had.
I ended up going to an AT&T DSC Center during my lunch break. They took one look at it and swapped it out under the warranty; it took about five minutes. The "new" phone didn't have the latest version but I was able to update it with absolutely no problems on Windows 7 32-bit (throwing out all the details in case someone stumbles upon this for help). I guess Kies is just a very fickle program. I'm pretty bummed but at least I have a functional phone and as added bonus, I stumbled upon this kick-ass website that I can browse in the future.
Click to expand...
Click to collapse
Ok glad you got it resolved. Enjoy your time here and welcome. Thread closed

[GUIDE]TBH inspired Free wireless tethering hack instructions for Droid 3

Wireless Tethering is one of the main things I miss about not having root. I specifically bought a wifi only Xoom because I knew I could just tether it to my phone. When I switched to the droid 3 believing it would come unlocked it was like a kick in face.
Recently I came across a thread from Team Black Hat describing a way of enabling free tethering on Verizon without root. In their write up they provide a flashable zip. Useless for us as we don't have root, or a recovery, but it got me thinking. All credit for this goes to Team Black Hat. They rock, I really hope they are working on rooting the droid 3 because they are android gods.
The original thread by TBH can be read here.
I'm not going to go too in depth here, because if you screw you have the possibility to brick your pretty new device. Also, It goes against your TOS with Verizon, and who knows one day they might work out a way to tell who is doing this. The more people who know and use this trick, the more likely it is they will find some way of detecting and or closing the hole.
But I couldn't leave my XDA brothers out of the loop! So with the standard disclaimer (I'm not responsible for anything you do, anything that comes of something you do, blah blah, you know the deal) I will outline the steps required to enable free tethering on our wonderful Droid 3s.
Team Black Hat said:
TeamBlackHat is releasing for the public the only permanent 3G Hotspot hack. Please be responsible and do not abuse this release. MyDroidWorld and TeamBlackHat are not responsible for your behavior nor your bills.
Click to expand...
Click to collapse
I did this on a windows 7 64 bit pc. The radiocom software would def be happier with a 32 bit xp system, it will throw a lot of errors, but it will work. More on that in a second.
1st. You need the most recent drivers for your computer so that your computer can see your phone. You can get them off the Motorola website, same as if you were going to use adb or RSDlite. The file I downloaded from the moto support site was called MotoHelper_2.0.49_Driver_5.0.0.exe
2nd. You need a copy of Radiocom. Radiocom is a piece of software thats supposed to be for moto employees only and allows you to read and write data directly to your software radio. You need to search the internet for it, because its a copyrighted file I can't post it for you. You need to find the latest version. The best version I found was RadioCOmm_v11.11.11_Install.msi - You also need the .net framework installed on your computer. You can get that from Microsoft's site for free.
3. You need a USB cable and a droid 3.
Now... crack a beer and lets get down to business.
1. Install the moto drivers and the .net framework. Install Radiocom. It will give you all sorts of errors, but it will install.
2. Next, find it under your start menu. Right click on it, and select "trouble shoot compatibility" I just ran with the suggested settings. Basically what this does is run the application under XP compatibility mode. Now take a sip of beer, you are gonna get some error messages but don't tweak.
a. You will still get the first screen that says do you want ot the following program from an unknown company to make changes on your computer - check yes.
b. it will say motorola datacard drivers 1.5.9 : this installation is intended for 32-bit os versions only.please use the 64bit version on this machine. click okay.
c. Installation incomplete: the installer was interrupted before motorola datacard drivers 1.5.9 could be instaled. You need to restart the installer to try again. hit close.
d. Warning: Motorola Dataard Drier installlation package ersion mismatch. the version supplied with this tool does not match the installed version on the machine. WE cannot guiarantee proper radio enumeration unless you install the latest version. the installation package will start again the next tiem this tool is started. Click OK
e. This version of RadioCOmm is more that 2 months old. This version may be out of date. Please visit the PDO compass webpage and download the latest version of RadioComm. - Click OK.
Radiocom will start! Phew!
you will have to select the chipset at start: I selected CDMA 1x (MSM 7500) w/ Android. I don't know if this is the best or most accurate one. I actually spent 45 minutes trying to search for exactly what our chipset base was... but I decided to be brave (or stupid) and went with this one and it worked. after it boots, Under settings in radiocom, USB, Select PST USB Driver.
3. Now, Connect your droid 3 to your computer and put it in PC mode. If you installed the drivers correctly you should get this cool little screen showing your phone and telling you some info about it that pops up from motos software. in radiocom software in the upper right of the screen right under the RC logo, the lgiht should turn green to show the phone is connected. You can test by pushing the GET button under the SW version. It should return your Android software version. DON'T PUSH ANY OTHER BUTTONS. YOU COULD REALLY SCREW SOMETHING UP.
Now a little background, you can read TBH's awesome explanation, but the quick and dirty one is that moto's software radio uses three different 128 char string identifiers for data requests. Thats how they can tell the difference between your phones web browser asking for data, and a laptop or Xoom connected to your phone asking for data. We are going to use Radiocom to make all three strings match the first string - so all data appears to be just for the phone. After doing so - your verizon installed hotspot app will work and the usb tethering option will too! ta da!
Team black Hat has made a screen shot showing all the steps required it can be viewed here.
I'll also try including it right here but i'm not sure how it will look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. now take a deep breath... use the arrows in the Radiocom program to find the tab marked P2K 1.
Look at the image and in your Radiocom program in the bottom left there is a box called STELEM/ RDELEM. First Select Dec entries.
Rdelem means read, and STELEM means write.
now this is very very important. Do not screw this part up. make sure again you have selected Dec entries, because if you enter the numbers below in hex mode and then hit DEC they will change and you will be reading and writing the wrong values which is BAD.
In Dec Mode
For ElementID: enter 8040
Record # 1
offset 0
length 128
Now Hit RDELEM. the box in the top right should go green, a bunch of numbers should flash through but most importantly right next to where you entered the element ID and record number the box that says Data (hex only) will now have a 128 char string in there. Hilight the entire 128 byte string and copy it.
4. You are now going to change the element ID to 8041 (record, offset, length stay the same) and hit RDELEM. If you compare these two numbers they are different, this is how moto knows you are tethering. You would have to paste both into a word file becuase they both end in a bunch of 00's so in the tiny data box they look the same, but trust me they are different. Select the data in the databox for 8041 and delete it. Paste the number from 8040. Now hit STELEM. Again you should see a bunch of numbers go through that box on the top right and it should be green.
5. Now you are going to do the same things for element numbers 8042, and 8043. Remember each time to hit RDELEM first, paste the value from 8040, then hit STELEM.
6. Now hit the restart button next the text box top center. You phone will restart. it will say something scary at first like SIm card not found. This is normal. Give it a Second and it will be right back to normal, you will have your 3G icon and be able to make calls, send texts etc.
EXCEPT.... Now you can use the verizon mobile hotspot application and it won't send to that verizon website that says "would you like to pay for tethering?" - you have just successfully hacked your radio to make verizon believe all data requests are phone data requests.
Ta [email protected]
We might not have root yet, but now we have free wireless tethering! I have had this running for about 24 hours and everything seems perfectly functional. My xoom connects right away to my phone and the distance is actually pretty good (like from bed to desk.. not just pocket to hand). Speeds are functional, just like you would get on the phone.
I hope I have made the wait for root just a little easier for my fellow XDA'ers... I know despite the fact I'm taking the Bar exam in 3 days I still check the forums every hour hoping against hope for some new news of root .... or hell... even video chat working in talk (gchat/huddle/etc).
Again I take no credit for this, All thanks to Team Black Hat! But if you wanted to press the thanks button it would make feel all warm and fuzzy inside =)
- faylix / local

Frigging awesome I was very strongly considering this phone and the only real drawback for me with lack of root was missing wireless tether and ad blocking. I could live without but having this makes it a no brainer.

hufn said:
Frigging awesome I was very strongly considering this phone and the only real drawback for me with lack of root was missing wireless tether and ad blocking. I could live without but having this makes it a no brainer.
Click to expand...
Click to collapse
I was in exactly the same position.. loved the phone.. could wait for root.. didn't want to give up wireless tether.... but now we don't have too!
Just hit that thanks button, and pledge to donate money to whomever finally roots this beast ;0)
- faylix

Nice job!
There is actually a great deal more to discuss regarding the NVM of the D3 and I will be doing so.
These instructions and screenshots should actually be updated to reflect the MDM6600 global chipset in the D3 and other global Droid models.
I am currently working on a comparison of a dump of the D3 NVM and an unlocked Droid Pro 3.8.7 engineering build to see if its possible to isolate the band unlock and apply it to the new radio.
So far it doesn't look good because there are so many differences in the radio NVM between them, but I have only just started examining it.
Thanks for giving credit where due and i emphasize that this is a very dangerous practice right now if you abuse it and VZW is making a concerted effort to identify and penalize such users.

cellzealot said:
Nice job!
There is actually a great deal more to discuss regarding the NVM of the D3 and I will be doing so.
These instructions and screenshots should actually be updated to reflect the MDM6600 global chipset in the D3 and other global Droid models.
I am currently working on a comparison of a dump of the D3 NVM and an unlocked Droid Pro 3.8.7 engineering build to see if its possible to isolate the band unlock and apply it to the new radio.
So far it doesn't look good because there are so many differences in the radio NVM between them, but I have only just started examining it.
Thanks for giving credit where due and i emphasize that this is a very dangerous practice right now if you abuse it and VZW is making a concerted effort to identify and penalize such users.
Click to expand...
Click to collapse
Means a lot comimg from you guys. I have all the respect in the world for your efforts.
Have you considered looking a the pre release builds of the d3? I know the test units had unlocked bootloaders but when woody tried to flash the sbf with the unlocked bootloader it bricked his d3.
Maybe some analysis there would bear more fruit than the droid pro because of the hardware differences?
Im taking the bar exam this wed and thursday but then im all for attacking this thing head on. If nothing else ill rep you guys for free if anything comes of that c&d letter you got im your jewish lawyer on retainer - just pay me in exploits!
For real, shoot me an email, and ill be first in line to donate when this puppy is finally cracked.
Concerning radiocom, its amazing there is no security in place to keep us from writing directly to the memory space like this... if we could only just pull the bootloader from the test unit sbf and point radiocom at the right memory address that might be all she wrote!
Dunno about you but i thik MIUI would look mighty fine on here....
-faylix / local

cellzealot said:
Nice job!
There is actually a great deal more to discuss regarding the NVM of the D3 and I will be doing so.
These instructions and screenshots should actually be updated to reflect the MDM6600 global chipset in the D3 and other global Droid models.
I am currently working on a comparison of a dump of the D3 NVM and an unlocked Droid Pro 3.8.7 engineering build to see if its possible to isolate the band unlock and apply it to the new radio.
So far it doesn't look good because there are so many differences in the radio NVM between them, but I have only just started examining it.
Thanks for giving credit where due and i emphasize that this is a very dangerous practice right now if you abuse it and VZW is making a concerted effort to identify and penalize such users.
Click to expand...
Click to collapse
This is good to hear, its nice to know some more people are working with this device. I was getting concerned that I jumped the gun buying it.
So now we have TBH working on unlocking the band, and woodyman & birdman working on finding an exploit for root.

This is a fantastic write-up, very well done. I installed all the appropriate software and did a "dry run" just to see everything. Do you know if this will stick through OTA updates?

The NV edits survive a *228 service programming but will be overwritten by a complete radio update like a new version release would usually include.

cellzealot said:
The NV edits survive a *228 service programming but will be overwritten by a complete radio update like a new version release would usually include.
Click to expand...
Click to collapse
Thanks, i'm going to give it a go later tonight.

For some reason whenever I turn on the hotspot app my 3g cuts off then cuts back on and is white and has no access to the net.

Well after cycling it on and off a few times it finally started working. Hopefully it'll work fine from now on. Thanks guys!

When I plug my phone in the icon in RadioComm turns green, but if i do get in "SW Version" i am not getting anything. Anybody have a suggestion?

The software version thing didn't work for me either, but I followed the rest of the instructions and it worked!

Guys,
The most common errors for people having trouble seem to be not using the correct usb setting in radiocom, not putting phone in pc mode, or not having the most current moto drivers.
Im about to go dark for 2 days (bar exam... weee) but I wish you all luck.
- faylix / local

Here is an updated screenshot that should help some of you with issues.
You can read the SW Version and MEID but it will hang reading Flex version so don't bother with that.
Note that the GUI will change dramatically with the correct chipset base and the RDELEM/STELEM module is now on the P2K4 tab instead of P2K1 tab.
Some of the other steps outlined in the OP may also be unnecessary depending on your PC config.
Yes, I am using a newer version of RadioComm than you will find available on the web but this will work with any 11.X.X version.

This is brilliant! Thank you to everyone who helped figure this out and make such an easy tutorial.

I never got the "SIM card missing" error...but complaining about not getting an error makes no sense at all, really.
Especially since it works! Thanks for this, and good luck on the bar exam!

+1. Like Javier78 I never got the SD card error. Thank you sooo much for such incredibly detailed instructions and providing us D3 users with one of the greatest perks of root without being rooted. Good luck on the bar, homie!!!
And a big shout out to TBH for doing what you do and doing it well.

Anyone who is experienced with how verizon does things know if there is any risk of this being detectable by verizon at all? Really want to try this out, but worry that they would detect it and cut off my account or something...

I just did it with my droid 3...thank you so much!
Oddly I had to use the M-link USB rather than PST, but it worked. =)
Sent from my DROID3 using XDA App

[HW][DEV] Internal Pictures Please

I'd like to see some closeup internal photos of the HW inside the Camera.
Something along the line of the "tear apart"-style pictures of the PCB.
Why? I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.

E:V:A said:
I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.
Click to expand...
Click to collapse
How about rooting it and getting a Skyroam Gmate for the SIM card? That should work, I guess...

E:V:A said:
I'd like to see some closeup internal photos of the HW inside the Camera.
Something along the line of the "tear apart"-style pictures of the PCB.
Why? I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.
Click to expand...
Click to collapse
I can't help you with tearing apart the camera since I have no expertise in that matter.
But I assume the phone has the ability to make calls, just disabled by software (no phone/dialer/call logs app), because the phone has IMEI number and can send/receive SMS natively.
But even if we can enable the phone function, i assume it has to be in speaker mode, or using wired headset or bluetooth headset since this device doesn't have speaker in the "right position" for us to make a phone call normally...

Here are some internal pictures from FCC for the following cameras:
Code:
[SIZE=2]FCC PCB Markings RF Hardware PCB Date
--------------------------------------------------
EKGC100 Rev.0.0 XG626 + RF 2012.07.27
EKGC110 Rev.0.3 Missing RF 2012.08.21
EKGC120 Rev.0.* MDM **** ****
--------------------------------------------------
* = unreadable
[/SIZE]
The EKGC100 with full radio capability:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The EKGC110 with no RF capability, except WiFi:
< pictures for EKGC120 missing since the FCC pic quality sucks >

^^
So there is phone module after all.. ?
Sent from Samsung GT-I9082

80000037 said:
^^
So there is phone module after all.. ?
Sent from Samsung GT-I9082
Click to expand...
Click to collapse
/\/\ this?

Didn't want to clog the ROM thread so I moved some stuff over here:
twistedumbrella said:
Nevermind, I think I have them reversed. The 100 should be the one I can mod, the 110 is wifi, and the 120 should be CDMA, which would need a software change instead of a firmware modification.
Edit: Anyway, it's going to require editing the NVRAM with a donor phone to get calling since it is a CAMERA, but I have a tutorial to get it done.
Click to expand...
Click to collapse
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
I had a Bionic when it was determined because of the board you could edit the NVRAM to get it working for gsm. I wasn't too interested in that but did dig into it because I was hoping to use the same process to get an ATT Tab 8.9 I had working on Verizon (using one of MY valid Verizon IMEI's). So I'm familiar enough to be dangerous and a willing victim.

Jiggity Janx said:
...
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
Click to expand...
Click to collapse
Excellent! Yes, I noticed the GC120 pictures were so bad. Impossible to read anything, but I also think they're Qualcomm, but we need to know which! (Actually, if you have the firmware I can check!)
To thread newcomers:
We started this discussion about the possibility of making 3G/4G radio phone calls in this thread: [ROM][PHONE][4way-reboot]Stock Rooted deodexed 4.1.2 XXBMC4 with mods. However that thread is a ROM thread, and is not the right place for this kind of discussion, so let's stay in this thread.
Click to expand...
Click to collapse

If you have an EK-GC120, I would appreciate if you could send me the latest firmware update. The update was an OTA, so it should probably be located in the /cache directory and called something like:
****.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip
Thanks in advance.

E:V:A said:
To thread newcomers:*We started this discussion about the possibility of making 3G/4G radio phone calls in this thread:*[ROM][PHONE][4way-reboot]Stock Rooted deodexed 4.1.2 XXBMC4 with mods. However that thread is a ROM thread, and is not the right place for this kind of discussion, so let's stay in this thread.
Click to expand...
Click to collapse
Ok man, you have my full support. If you or someone else need someone to test stuffs feel free to contact me!

Jiggity Janx said:
Didn't want to clog the ROM thread so I moved some stuff over here:
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
I had a Bionic when it was determined because of the board you could edit the NVRAM to get it working for gsm. I wasn't too interested in that but did dig into it because I was hoping to use the same process to get an ATT Tab 8.9 I had working on Verizon (using one of MY valid Verizon IMEI's). So I'm familiar enough to be dangerous and a willing victim.
Click to expand...
Click to collapse
Actually GSM cannot be converted to CDMA through NVRAM edits. You can switch carriers, enable hardware, bypass hardware, but the hardware is not going to transform. Going 4G SIM to 3G phone is possible by modifying the values IF the 4G still has a 3G fallback, hence using the Thunderbolt as a donor for a 3G connection since the 4G and 3G radios are actually completely separate. I can't take my GSM Galaxy Nexus and make it CDMA, though.

I am not talking about making the gsm gc100 into cdma because the board likely does not have a cdma radio on it.
But in my example of the att tab 8.9 the board already had cdma radio (hardware) that just wasnt enabled so it absolutely could have been enabled to work.
Edit: I was just noting that as an example of my prior knowledge of qpst/nvram.

E:V:A said:
Excellent! Yes, I noticed the GC120 pictures were so bad. Impossible to read anything, but I also think they're Qualcomm, but we need to know which! (Actually, if you have the firmware I can check!)
Click to expand...
Click to collapse
I have the device(s) now so let me know what you would like me to do.

Jiggity Janx said:
I have the device(s) now so let me know what you would like me to do.
Click to expand...
Click to collapse
Unless, you're hip on opening the device (which I do not recommend unless you have some Adam Outler unboxing tools/skills), I suggest you to:
1. Look for FCC ID
2. Connect camera via USB and open Device Manager if using windows to look for some COM port that says "blah blah Samsung Modem". Then use a terminal program to try to connect to the modem and send "ATI" and post the results.
3. If (2) is not working or you're not finding the correct port, we'll have to look around using ADB shell and/or find the correct (Windows) drivers. Do list any associated VID/PID from connected USB devices.
4. This should probably be "0", but try looking in device info for the modem firmware version. Also see if you can access service menu. That should also contain a way to display current firmware etc.
5. If you have the firmware, uncompress it and send me the modem.bin file or just the whole blob, if not possible.
That is just to verify what's inside...

E:V:A said:
Unless, you're hip on opening the device (which I do not recommend unless you have some Adam Outler unboxing tools/skills), I suggest you to:
1. Look for FCC ID - will pull that tonight
2. Connect camera via USB and open Device Manager if using windows to look for some COM port that says "blah blah Samsung Modem". Then use a terminal program to try to connect to the modem and send "ATI" and post the results. - comes up as Samsung Android, will use ADB again tonight to send ATI and post results
3. If (2) is not working or you're not finding the correct port, we'll have to look around using ADB shell and/or find the correct (Windows) drivers. Do list any associated VID/PID from connected USB devices. - can adb while in recovery but still having problems connecting in odin
4. This should probably be "0", but try looking in device info for the modem firmware version. Also see if you can access service menu. That should also contain a way to display current firmware etc. - will look for modem firmware and use outler's method to get into service menu
5. If you have the firmware, uncompress it and send me the modem.bin file or just the whole blob, if not possible. - can't find the firmware. rooted already and can dd through adb. was going to attempt last night but had to merge the partitions twisted notes in another thread with the dd command I found online and just ran out of time.
That is just to verify what's inside...
Click to expand...
Click to collapse
updates in red

Jiggity Janx said:
updates in red
Click to expand...
Click to collapse
I think the "Terminal program" he means is something like "Putty", or "Tutty", right?

Delux9364 said:
I think the "Terminal program" he means is something like "Putty", or "Tutty", right?
Click to expand...
Click to collapse
That would make sense. I work with linux servers at work but use windows at home. Is there a good way to come up with the same result.
Btw worked a long day today so wont be able to pull this stuff until tomorrow.

Jiggity Janx said:
That would make sense. I work with linux servers at work but use windows at home. Is there a good way to come up with the same result.
Btw worked a long day today so wont be able to pull this stuff until tomorrow.
Click to expand...
Click to collapse
You would simply use PuTTY for linux.

Right. But windows at home. So what do I use at home on windows to get the requested info?

Putty
RealTerm

Nexus 6 no longer recognising PC (and PC no longer recognising phone) in Fastboot etc

Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.
When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.
It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.
On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.
In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.
And in the notification shade (again, while plugged into my PC) no option is given. It just charges:
I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).
In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?
As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.
I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.
Any help would be greatly appreciated because I'm just sick of this problem at this point.

Zenamez said:
I'm just sick of this problem at this point.
Click to expand...
Click to collapse
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.

NLBeev said:
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
Click to expand...
Click to collapse
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!

Zenamez said:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Click to expand...
Click to collapse
Wish you luck.
W10-updates are causing issues on my PC

If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.

Strephon Alkhalikoi said:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Click to expand...
Click to collapse
Tried 3 different USB cables and no luck.
I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.
Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).

Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself

I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.

Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?

electricpete1 said:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
Click to expand...
Click to collapse
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.
My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.
Dvoraak said:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Click to expand...
Click to collapse
Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).
Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.
Dopamin3 said:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
Click to expand...
Click to collapse
I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.
It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).
I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.
I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.
Thanks to everyone who's replied though! I'll see how the USB replacement works out.

Hello all, long time lurker 1st time poster....
I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.
I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.
My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.
I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.
So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.
I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.
NOW...........................probably a silly question but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.
Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me .
CHEERS

Some quick thoughts.
1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.
2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.

Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)
1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk
2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.
As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.
Many Thanks once again

**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*

qprjim said:
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
Click to expand...
Click to collapse
SBE repaired my nexus 5, when it was rooted/unlocked.
Is there any damage to the usb port? Never tell the customer service rep that your device.

Cheers for the reply JonesL
As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.
I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.
Oh well....