To anyone who has had the issue of installing the OTA Kit Kat update and ended up with an error, followed by bootloop "No Command" screen, here's the fix and how to save your data. I was unable to successfully get the image flashed using adb sideload, but I will mention it as others apparently have.
When attempting to install over the air update on Nexus 7 2012, Wifi edition, about 25% into the install I received an error screen. Upon restarting device, the Nexus would load the Google splash screen, followed by a "No Command" screen. To those that have encountered this and are worried about losing your data, follow these instructions. I am using Ubuntu so you will have to do a little research on downloading the tools for Windows and how to use them. I have a ton of computers to work on and don't have much time to type out a long guide, and I have never used either of these tools on a Windows machine.
Download the factory image for Kit Kat from here: https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Tools needed:
Drivers for your Nexus (Windows only)
Fastboot
ADB
Fastboot and adb are packed together in the Android SDK, or other sources have them. Using ubuntu, run "sudo apt-get install android-tools-fastboot" and "sudo apt-get install android-tools-adb" in your command line.
If you want to use adb sideload, check to make sure you device is recognized in "70-android.rules" or "51-android.rules" by running:
Code:
adb devices
If you get "?????????" then you better edit your android rules file by typing:
Code:
gksudo gedit /etc/udev/rules.d/70-android.rules
Note that your android file could use the number 51 or 99 also, so I would recommend performing this step 3 times with 70-android.rules, 51-android.rules, and 99-android.rules.
Add the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #fastboot
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #fastboot
Save this file and exit your editor. Now, extract your image you downloaded from Google. You should see a file named "image-nakasi-krt16s.zip." Copy this somewhere easily accessible, such as /home/<your username>/ANDROID.
Open command prompt and enter the following:
Code:
cd /home/<your username>/ANDROID
adb sideload image-nakasi-krt16s.zip
If all goes well, this should install and reboot. If not, you may get errors such as "E:signature verification failed" or something about unexpected files. I had about 4 different errors trying this, so continue reading to fix this using fastboot.
Extract all of the contents of the downloaded image file to the /ANDROID directory we created earlier.
Power off the device. Press and hold on to the Volume down and power key altogether until you see the bootloader screen. This screen is what we know as bootloader mode or fastboot mode. Connect the device to the PC via USB cable
Open your command prompt and head to the /ANDROID directory. In case you forgot:
Code:
cd /home/<your username>/ANDROID/
Next, run the following commands in order.
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Now we need to reflash the bootloader:
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Reboot the bootloader:
Code:
fastboot reboot-bootloader
Flash the 4.4 Factory Image, type:
Code:
fastboot update image-nakasi-krt16s.zip
Now sit and wait while your tablet is updated. It will restart and your apps will be optimized. Good luck!
I have the very same issue after the 4.4 OTA. When I tried to connect, my nexus is only getting listed under the fastboot devices (Drivers installed by the WUG toolkit/in device manager can be seen as Google Nexus 7 BootLoader Interface) and I have no adb connection (probably I had USB debugging deactivated. Is there anything I can do or do you think I'm screwed and have to erase everything?
Update: just executing the fastboot steps worked just fine (without any ADB sideload), many thanks for this solution
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
I did it using windows: I've installed the android sdk for windows and used the wugfresh toolkit to update my nexus 7 drivers - then booted into fastboot mode and executed the fasboot... commands listed
Yeah, there is really no need for the adb, and I had no luck with it. I was thinking fastboot would wipe my user data, but I just didn't run any commands that would wipe my data and it seemed to work fine. On Windows, I would just download the SDK and then get your tablet connected and the fastboot commands are all the same. The problem I have is I can never get Windows to work right with and of my Android gadgets and I am not as good with the Windows command line. But if you have trouble connecting to Windows, just go to the Ubuntu site and throw the live version on a flash drive, run the sudo apt-get android-tools-fastboot command, and you should be good to go.
Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
If you are still having issues, pm me and I would walk you through it.
greg_gorrell said:
If you are still having issues, pm me and I would walk you through it.
Click to expand...
Click to collapse
Thank you very much greg for your kind offer but i have managed to solve the issue
A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?
abobobilly said:
A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?
Click to expand...
Click to collapse
You're welcome! But I have been looking into it and it seems that it isn't just rooted tablets that cause the update to fail. On another site, I believe Android Police, I noticed some had completely stock devices that failed.
This sux...
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.
notfaded1 said:
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.
Click to expand...
Click to collapse
I am not able to do anything as my Nexus is in bootloop, it is constantly rebooting so I have no access to anything. Cannot get into recovery mode at all. Any help would be nice.
Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
greg_gorrell said:
Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.
PCFixYa said:
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.
Click to expand...
Click to collapse
Just boot into Bootloader and reflash the the whole ROM. Start from there.
khaytsus said:
Just boot into Bootloader and reflash the the whole ROM. Start from there.
Click to expand...
Click to collapse
I cannot boot into anything! It is constant bootloop.
PCFixYa said:
I cannot boot into anything! It is constant bootloop.
Click to expand...
Click to collapse
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.
khaytsus said:
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.
Click to expand...
Click to collapse
It doesn't work, every action I tried ended up with this bootloop which you can see few posts above... Thanks for trying to help btw
Related
My current situation:
Recovery does not work, when I try to enter it it gets frozen on the Google screen with the lock at the bottom.
When I try to go into the phone normally I receive an infinite error "Unfortunately, Setup Wizard has stopped".
My device is not being recognized as an ADB device so i cannot reinstall recovery (possibly USB debugging is disabled and cannot get to it).
How I got here, Used the Nexus RootToolkit v1.5 to unlock the bootloader/root the phone which worked fine except recovery was not working and the play market was gone for some reason. Did a variety of things to get it back with no avail and eventually got frustrated and tried a factory reset. Now I am in this perdicament :crying:
I came from a Samsung Galaxy and Odin was the universal tool to get the phone back even if it could not enter recovery or the phone, Is there anything like that that can fix the phone without entering recovery or the phone itself?
If you can get the device to recognize in fastboot you can flash the factory image for nakasi from here
How do you flash without entering recovery though?
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
slifer315 said:
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
Click to expand...
Click to collapse
Yeah I can get into the boot-loader. I'll give this a shot and see if it works. thanks!
slifer315 said:
Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue.
Click to expand...
Click to collapse
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Use my video guide to help you out. http://www.youtube.com/watch?v=-E-EF0QC0Gc
l0aded said:
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Click to expand...
Click to collapse
You need to have the Android SDK installed, open a command prompt, and cd to its directory and the tools folder. In there is the fastboot binary that allows you to run fastboot commands. For ease of execution, you can just install the SDK on the root of your C: drive or just copy the tools folder to wherever it was installed by default (/Program Files/Android/).
Sent from my Nexus 7
Thanks guys! Restored to factory stock and am back from the brick.
l0aded said:
Thanks guys! Restored to factory stock and am back from the brick.
Click to expand...
Click to collapse
Great!
Sent from my Nexus 7
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
HappyTNMom said:
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
Click to expand...
Click to collapse
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Thank You
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Sorry Didn't work
HappyTNMom said:
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Click to expand...
Click to collapse
ok, so I now have SKD and tried the command you gave me with no luck
I also tried SRT again and it looks like it is working on my cmd screen
I did step 1, step 3, step 4, step 6 and they all said they finished but it still reboots then goes straight to the FastBoot screen
Got my Factory Cable Today still stuck on fastboot
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
ok I have tried using this new cable and running SRT with no luck. I am still stuck on FastBoot. It seems to work, but as soon as I do the Reboot to Normal, it goes to the Kindle Fire homescreen, then immediately goes back into FastBoot. I am going to keep trying and hopefully you or someone will see this and respond with more suggestions. Thanks for the help, much appreciated...
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices
That's encouraging. Any idea how to get past the system.img file is too large error?
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?
My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk
htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?
Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.
For what its worth-
I can boot into Android system recovery <3e> for Android 5.1.1 build # A1PV1.0.0B17 by powering off and pressing power and volume up at the same time then releasing when the Android appears. Pressing the volume key down instead takes you to Factory Test Mode. The following options are available in recovery:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply update from cache.
Unfortunately there seems to be no way to get into the bootloader. Hitting "reboot to bootloader" just reboots the phone back to android. One of these days someone will crack this phone. Just hoping we get some people with some development experience on board with this phone.
There was a post that I saw that said that ZTE phones come with the bootloader already unlocked, but I haven't found a way to check it. Has anyone tried to see if the Factory Test is just their fancy way of saying that it's in bootloader mode?
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
http://forum.xda-developers.com/showpost.php?p=48319535&postcount=29
http://forum.xda-developers.com/showthread.php?t=2520309
http://cellphonetipsandtrickss.blogspot.com/2013/10/the-super-secret-codes-fr-zte.html
Sebring5 said:
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
Click to expand...
Click to collapse
I've tried this and it simply reboots my Axon Pro (model A1P). Where are you getting the drivers from? (Besides windows update and Install mode when you connect the Axon to your PC.)
I use a Mac. No drivers needed.
Sebring5 said:
I use a Mac. No drivers needed.
Click to expand...
Click to collapse
That..doesn't exactly help..
Archfeind2 said:
That..doesn't exactly help..
Click to expand...
Click to collapse
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Sebring5 said:
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Click to expand...
Click to collapse
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Archfeind2 said:
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Click to expand...
Click to collapse
Try this: http://www.downloads.techdiscussion.in/smartphones/zte-axon-pro-pc-suite-and-usb-driver/
Okay cool. I'll check it out in a couple of minutes.
Edit:
It didn't work it was the same as the axon installer unfortunately. Maybe I'll have to virtual machine either mac or Linux, again >.<
I really want this phone's bootloader unlocked xD
I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?
These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.
@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.
Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?
LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.
LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.
Yup, flash the .img files individually, the batch command doesn't work.
Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)