Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..
ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Definitely sounding more and more like hardware
ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.
On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.
Related
I formatted my system on Stock ROM. I found another stock ROM for sprint now i can't get the ROM i want on my phone because the PC won't read the phone (in CWM recovery). My question is...is there a way to get the ROM on the phone through ADB? Im not all that familiar with it. If so...whats the command?
adb push rom.zip /sdcard
nhizzat said:
adb push rom.zip /sdcard
Click to expand...
Click to collapse
says error device not found
Prestige_DOPE said:
says error device not found
Click to expand...
Click to collapse
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
DogzOfWar said:
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
Click to expand...
Click to collapse
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Prestige_DOPE said:
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Click to expand...
Click to collapse
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Prestige_DOPE said:
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Click to expand...
Click to collapse
I misunderstood you're original question, sorry. I didn't realize it won't boot at all. I have done what you are asking for my Nexus 7 (which I had messed up). Typically, when you're in the recovery and you plug it into a PC, it will install drivers (separate from the ones when Android OS is running).
Maybe consider trying to use RSD Lite to at least get a functional OS back on there? This page lists drivers to use along with RSD Lite. Maybe that would help get things recognized to the point where you can copy over a ROM?
nhizzat said:
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Click to expand...
Click to collapse
Didnt work...the more things that arent working the more scared i become
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Installed RSDLite and literally screamed "What the hell is this". A little help here on how this is supposed to work?
I bought a Sony Xperia Z1 (C6903) on eBay, and it came installed with Kitkat.
I decided I wanted to root the device and install a custom ROM before I used it much, so I followed a guide on XDA and flashed it with the 14.1.G.1.534 build using Flashtool. (I had to install several drivers to get Flashtool to work.)
After that, I attempted to root it using Vroot, but the program didn't work (the error message was in Chinese, and when I clicked the supplied link, it was something about enabling USB debugging, which I had already done.) I then tried Kingo Android ROOT, which tried to download drivers for the phone, but always failed, so I downloaded and installed them manually as suggested. Kingo Android ROOT then did the same thing as Vroot, and told me to enable USB debugging, even though it was already enabled.
I tried reflashing it using Flashtool and trying again, but same issue.
I finally got fed up and tried to just upgrade to Kitkat again using the Software Updates feature in Phone info, but now the phone fails every time I try to update! It starts, enters the Android update screen, and then reboots a few seconds in. When the phone loads again, it says the update failed and asks me to redownload the file. I tried this several times, including leaving the phone off for a while before upgrading, and making sure it was at full charge AND on AC power, but still nothing.
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
YamiWheeler said:
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
Click to expand...
Click to collapse
Try rooting with this to see if it works
https://www.youtube.com/watch?v=1aq9YTlfCgc
Ahki767 said:
Try rooting with this to see if it works
Click to expand...
Click to collapse
MrMurphysLaw said:
https://www.youtube.com/watch?v=1aq9YTlfCgc
Click to expand...
Click to collapse
I tried this, but still nothing. :/
http://i.imgur.com/JboJ9VF.png
I'm beginning to think this is a driver issue, because I installed several drivers in an attempt to get Flashtool to work, but I don't know how to fix this. I used USBDeview to remove several drivers from my computer. After doing this, I plugged in my Xperia Z1 and it installed "C6903" on my computer, but it also prompted me to install software on the phone screen, but each time I click Install, it doesn't do anything...
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
YamiWheeler said:
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
Click to expand...
Click to collapse
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Ahki767 said:
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Click to expand...
Click to collapse
Not to my knowledge, no. :/
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
YamiWheeler said:
Not to my knowledge, no. :/
Click to expand...
Click to collapse
Well i'm sure if the drivers ain't installed correctly you wouldn't be able to flash anyways so i don't think its a driver problem. try flashing .534 again and turn on usb debugging and plug your phone in with the screen on and see if there's any pop up
Edit: Just saw gregs reply, totally forgot this method but yes try installing nuts dualrecovery
gregbradley said:
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Forgive my lack of knowledge of this, the only thing I've ever rooted was a Samsung Galaxy S3 Mini, and that process seemed a lot simpler than this. :/ At least, before your method.
YamiWheeler said:
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Click to expand...
Click to collapse
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Ahki767 said:
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Click to expand...
Click to collapse
But don't I have to unlock the bootloader first?
no
Thanks for all your help, it's working and all is well.
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
nejo01 said:
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
Click to expand...
Click to collapse
Have you tried Android File Transfer? https://www.android.com/filetransfer/
_MetalHead_ said:
Have you tried Android File Transfer? CANT QOUTE THIS
Click to expand...
Click to collapse
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
same problem here.
In yosemite (mac osx) doesnt work and dont detect the device.
I think the problem is the compatibility between MDM and Yosemite...
nejo01 said:
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
Click to expand...
Click to collapse
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
_MetalHead_ said:
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
Click to expand...
Click to collapse
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
nejo01 said:
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
Click to expand...
Click to collapse
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
_MetalHead_ said:
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
Click to expand...
Click to collapse
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
nejo01 said:
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
Click to expand...
Click to collapse
Ahhh, through Motorola Device Manager? I didn't even know it existed prior to this thread.
And it's not that it's not 100%, it's that the OTA rolls out in stages. Not every phone gets it at the same time. Not quite sure how it'll work through that software though.
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks