Database Develop

I Cant Activate My Phone Now Please Help!! Listen!! [solved]

Im new to G1s I switched from an iphone. I had one that I bought off someone, and I put my Dad's sim card in to activate it because he had the blackberry unlimited internet plan. It activated my phone and went through normally. Well, my screen cracked, so I sold that phone and bought another one off someone else. They factory restored it. So I put my Dads sim in again, and now its not activating this phone like it did the last one. I downgraded it and that didnt help either!! Please tell me what I can do to activate it without getting the G1 plan or fibding someone with one because I dont know anybody who owns a G1.
Thnx!

dhester92 said:
Im new to G1s I switched from an iphone. I had one that I bought off someone, and I put my Dad's sim card in to activate it because he had the blackberry unlimited internet plan. It activated my phone and went through normally. Well, my screen cracked, so I sold that phone and bought another one off someone else. They factory restored it. So I put my Dads sim in again, and now its not activating this phone like it did the last one. I downgraded it and that didnt help either!! Please tell me what I can do to activate it without getting the G1 plan or fibding someone with one because I dont know anybody who owns a G1.
Thnx!
Click to expand...
Click to collapse
Here's how!: Use the search button...
Took me all of 10sec to find out how: http://forum.xda-developers.com/showthread.php?t=452316&highlight=wireless next time at least make an effort to find a solution, the people here hate answering questions that we've already answered and written guides for because it means we wrote the guides for no reason.

Yea but I cant get into my phone whatsoever I already tried all that I been searched that thread Im not that stupid cuz

dhester92 said:
Yea but I cant get into my phone whatsoever I already tried all that I been searched that thread Im not that stupid cuz
Click to expand...
Click to collapse
You need to provide more details then you've given. Post EXACTLY what you did and what EXACTLY is happening that its preventing you from activating

B-man007 said:
You need to provide more details then you've given. Post EXACTLY what you did and what EXACTLY is happening that its preventing you from activating
Click to expand...
Click to collapse
Seriously... all you asked was how to activate your phone without using your dad's SIM as that no longer worked...

Ok. I had an old G1, put my Dads SIM in because he had the blackberry internet, it let me activate my gmail account and went through. Now I have a new one that was factory restored, I put his SIM in, and now its telling me ""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."" The other G1 didnt give me this problem. So now I cant even sign into the phone to get to the main menu. Is there ANY way around this??

Either you need to follow the instructions in the link that was provided (many people have used that option) or get a data plan. T-Mobile killed the feature to use other data plans. You need to have the G1/Android Unlimited data plan now.

dhester92 said:
Ok. I had an old G1, put my Dads SIM in because he had the blackberry internet, it let me activate my gmail account and went through. Now I have a new one that was factory restored, I put his SIM in, and now its telling me ""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."" The other G1 didnt give me this problem. So now I cant even sign into the phone to get to the main menu. Is there ANY way around this??
Click to expand...
Click to collapse
From the other post....
"First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry."
Can you confirm youre on RC29 or earlier??

yea I did the [enter] reboot [enter] thing and it reboots

But dont I have to be able to get into the phone and check the debugging option to be able to set up adb on my computer??? I dont have a PC, I have a Mac, and I was up for hours last night trying to figure out how to set up ADB on my Mac, and I never figured it out!!

dhester92 said:
But dont I have to be able to get into the phone and check the debugging option to be able to set up adb on my computer??? I dont have a PC, I have a Mac, and I was up for hours last night trying to figure out how to set up ADB on my Mac, and I never figured it out!!
Click to expand...
Click to collapse
READ THE FREAKING GUIDE!!! It tells you exactly how to set up adb and how to get to the wireless configuration menu...

I read the freaking guide over and over again I got a mac and they dont really say what to do with macs they go by PC like the whole time!!!! Wtf am I supposed to do then???!!!!

dhester92 said:
Wtf am I supposed to do then???!!!!
Click to expand...
Click to collapse
Could go the easy route and get a data plan.

I set it up on terminal but it cant find my device because i cant even get into the home screen

dhester92 said:
I set it up on terminal but it cant find my device because i cant even get into the home screen
Click to expand...
Click to collapse
Set what up in terminal. And you don't have to be on the homescreen for your computer to pick up your phone for adb.

dont you have to check the G1 debugging in the settings in order for the computer to recognize the phone in adb (the terminal) im using a mac

dhester92 said:
dont you have to check the G1 debugging in the settings in order for the computer to recognize the phone in adb (the terminal) im using a mac
Click to expand...
Click to collapse
You're sure you read the whole thing... like this part?:
"If you have an official RC29 or lower phone, type the following command on the phone keyboard to enable adb:
<enter>setprop persist.service.adb.enable 1<enter>"
Notice... It doesn't say anything about using your computer either Windows or Mac...

Ok I got that now.
I did it, and I didnt get any notification that adb is turned on. Should I have got one, or does it turn on but doesnt let you know

Ok I got it! Thnx alot for your help dude

Ok one last question...
can you tell me a more detailed way on how to do this I dont quite understand:
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.

[Q] I want to make sure I have this right

Sooooo I came up on a T-Mobile G1 from a buddy of mine. A little beat up but after 3 and a half years with a t-mo wing it's about time to upgrade my old phone for a not so old phone. Went through the effort and went through my buddy @ likenewcells.com to get the thing unlocked rather quickly I might add.
My scenario, I don't have a data plan... I have scoured the threads about how to register your G1 without a SIM or data endlessly only to be stuck at getting the adb drivers installed. One key thing I have done so far is downgrade myself to RC29 so I can confirm <enter> reboot <enter> works Yet for the life of me I have tried yelling at it, insulting it, even sending it death threats... NOTHING! hehe
Upon further reading it's mentioned that I need to root the thing first to get adb working, is that correct? I have heard the legends of a rooted phone and the fortune it brings. Unfortunately if I am unable to get past the registration screen then what am I to do? Given that all of the guides say you need to do some things on the phone. Mess with this setting, download something from a site using the browser, whisper sweet nothings in it's ear. I've read many guides in the past week on how to get adb working. One similarity is "you need root access" in them all casual like. Not bad mouthing any of the guides and what not hehe.
I appreciate any information anyone is willing to share with me regarding how to get adb working and / or rooting given my situation. I waited a while to make a post here after carefully reading and scouring the many tutorials for a solution to either. My t-mo wing is falling apart literally and I am done with it.
There is one thing that did help me think maybe just maybe is I was able to enable adb by typing <enter>setprop persist.service.adb.enable 1<enter> Unfortunately I still couldn't get the drivers installed.
Now a healthy question I feel would be is there a similar command I can type at the no sim card screen to get into my wifi settings?
Once again I thank everyone here for any info they're down to share with me.
Winmo - I'm quite familliar, Android I am a complete N00b

[Trifecta] Jelly Bean Root

****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.

I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.

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....

HTC One Remix from Verizon, I think it's soft bricked

Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.

bart1822 said:
Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.
Click to expand...
Click to collapse
it seems that you lost your OS for some reason. Data recovery would be a waste of time since you already reset the phone anyway so if you didn't use an SdCard then bad luck.
If you dont wanna send you phone for repair, your best option its to ROOT and install a Verizon software yourself.
NOTE: if you had an SdCard and also got deleted, just use any data recovery program to recover most of the files
NOTE: do a bit of search about recovery programs as they might also access you phone if rooted. maybe one in Google play store?

bart1822 said:
Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.
Click to expand...
Click to collapse
If your primary concern is data, my guess is you would be wasting time even with recovery software, all those I have tried have successfully recovered images half black, half missing etc.