Related
[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"
SOLVED!
So I went ahead, tried flashing the stock recovery, no joy (no recovery menu at all - just a bad-android image). After a while, tried flashing CWM touch (via Toolkit) - and now it's working. So, everything seems good now.
----------------
UPDATE 5 - PARTIALLY SOLVED:
So, after the last couple of things, I began to suspect bad hardware, as I alluded in those updates. And I was right.
But... it wasn't the hardware you might have thought.
It was...
(this is embarrassing)
The USB cable.
Yes, the USB cable. It was the wild variations in recognizing the fastboot mode that made me suspicious. Replaced the USB cable with another one and... stability, achieved. Unlock, root, recovery program and SU program all went without a hitch. In fastboot mode, for the first time, the device serial number shows.
HOWEVER - things are not perfect. The recovery mode from the bootloader still gives the bad-android icon.
I just used the toolkit to reflash stock recovery back to the device. This completed rapidly, without error. I then tried the recovery option in the bootloader, but again, no joy.
So at this point, I point a finger partly at the tools used to flash this - they claim there is no problem, yet the flash doesn't take at all, and no error is given. As a sometimes firmware developer, I'm used to flash being followed up by a checksum or other test to verify success of the flash. Is that not being done (shame, if not). If it is, then apparently the flash works, but the software being flashed doesn't? The stock recovery???
Any ideas on how to get this back? I just did the full unlock, which wiped all user data, and proceeded from there. I now have a solid connection, but don't really know how to get things back.
Perhaps I need to manually reinstall 4.2.2?
----------------
UPDATE 4:
So, on a lark, from fastboot in Android, I selected the "Recovery" option - it starts to boot that, then gives the Android with red triangle and exclamation point. So, looks like the recovery was toasted.
This was a brand new device earlier today. It has been completely wiped twice, and none of this has gone away. Seriously: bad device?
-----------------------
UPDATE 3:
So, I thought I'd try the direct approach, as outlined here:
http://forum.xda-developers.com/showthread.php?t=1741395
Device is in Fastboot, Device Manager shows it as ok.
I run fastboot flash recovery <file> -- and IMMEDIATELY get "fastboot has stopped working" - that's right, a hard crash in fastboot. And this is repeatable.
Am I wrong in thinking this looks more and more like a driver problem? I note that fastboot is recognized as a device maybe half the time - the other half, it gets an exclamation point in Device Manger. All I do then is restart the bootloader using the bootloader menu, and usually it fixes right up. But that's obviously a huge red flag, as the device should be recognized every time.
Is this a defective Nexus? The only thing that seems dicey is anything relating to fastboot/bootloader (which is, however, unlocked - or at least it says it is).
----------------
UPDATE 2: Using the "restart bootloader" in fastboot results in slightly worse non-recognition of the device. When I do that, I get a straight "USB Device Not Recognized" from windows - the device manager doesn't even show "Android Phone" as a class of device in this case.
---------------------
UPDATE 1: I found the thread talking about missing entries in the INF file. I added these, and got a somewhat, but not entirely, stable recognition of the Nexus 7 when in fastboot mode. Basically, sometimes it is recognized, other times it is not. By "recognized", I mean that the Windows Device Manager shows the device as "Android Bootloader Interface", with no indication of a problem (which it only does in fastboot mode - it shows as a composite ADB device when booted normally).
However - it seems it fails to recognize fastboot about half the time, although it seems that that is related to reboots - that is, a fresh boot, then going to fastboot through adb seems to work. But restarting fastboot manually fails to be recognized (Windows shows a bang by the "Android Bootloader Interface", and says the device "failed to start").
So, using 4.3.5 Nexus 7 toolkit, I tried to unlock the bootloader. Windows recognized fastboot mode, but the process errored out anyway, after maybe 15 seconds, saying "Too Many Links" - the same error as before.
Again, brand new 32gb wi-fi-only Nexus 7, with 4.2.2 update and the most basic configuration only (dev mode, usb on, etc.)
Any ideas?
-------------------------------------------------------
ORIGINAL
So this is a new, out of the box nexus 7. The only setup has been to connect to wifi, update to 4.2.2, and enable developer mode and USB debugging.
Running latest paid-for toolkit - Update 29 Feb 13, version 4.3.5
Just about everything requires the insecure fastboot, but every time I try any operation that attempts it, I get:
Booting into fastboot mode
downloading 'boot.img' ...
FAILED <status read failed <Too many links>>
I basically can't do anything - in this case, I was trying to backup.
It is being done on 64-bit win7 system that had drivers, and worked for another nexus 7 a couple months ago. But, just to be safe, I uninstalled the drivers, rebooted, and installed.
However, I see this on the home page of the toolkit:
FASTBOOT MODE [If serial shows, drivers are installed]
List of Devices attached
ADB Mode
List of devices attached
<numeric code> device
From this, it seems I should expect the word "serial" to show up if the drivers are installed?
I then unplugged the Nexus, refreshed the menu, and both Fastboot and ADB show no devices.
I then plug in the nexus - I get the usual two tone "device attached" sound, no warning or error message from Windows.Checking the Windows device manager, I see a section "Android Phone" with the entry "Android Composite ADB Interface". There are no unknown devices, which would seem then that drivers are working.
So, another refresh of the main menu, and again, I see, under ADB MODE, a single device ID number, and the word "device".
I don't know what to make of this. Apparently, per the "if serial shows" message in the main menu, drivers a NOT installed. But according to Windows, they are.
This perhaps matches the fastboot failure.
Should I see "serial"?
In any case, what do I do to get the drivers to work properly if they aren't?
And if they ARE working, then what is wrong with fastboot?
At this point, I think the toolkit is broken, and worked a couple months ago.
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Erik.Leach said:
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Click to expand...
Click to collapse
I've since figured that out. There was nothing at all, when in fastboot mode, only ADB. But then I found the thread describing two missing INF entries. I added those, updated the driver, and now the fastboot mode (which wasn't even recognized by windows) is now ok in the Device Manager. However, in the main menu, it shows, literally, "??????????" instead of a serial number - that is, there are question marks instead of serial number, Following that, a few spaces and then "fastboot".
Apparently, there are still inadequacies in the driver as relates to very, very new models running 4.2.2 (which this is).
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Erik.Leach said:
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Click to expand...
Click to collapse
Interesting. I did re-flash the stock recovery, and could get that without the android image.
stickplayer said:
Interesting. I did re-flash the stock recovery, and could get that without the android image.
Click to expand...
Click to collapse
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Erik.Leach said:
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Click to expand...
Click to collapse
Thanks! Next is trying to put 4.x on a Samsung Vibrant.
Hi,
I have a Nexus 4 with a damaged LCD and digitiser - the touchscreen won't respond at all. I'm hoping to recover data from the phone (e.g. SMSes etc.).
The bootloader is *not* unlocked, and it does not have a custom recovery installed. It has stock Android 4.2.2.
If I try to go boot into recovery mode, it says "No command".
Using ./adb devices or ./fastboot devices lists the device but it's marked as "offline" - I'm thinking that might be related to the new "feature" in 4.2.2, where you need to keysign each computer that you try to use adb from?
From memory, Android Debugging was enabled on this phone - however, it was subsequently upgraded to 4.2.2, which I'm guessing caused the RSA keysigning to kick-in, which is why ./adb now doesn't work.
Obviously I can't do that if the touchscreen doesn't work (and if I try ./adb from recovery, there's nothing to add a new RSA key either).
Any thoughts on how I can get ADB working, or recover data from this phone?
(I'm assuming ./fastboo oem unlock will blow away the phone and wipe everything - including SMSes).
Cheers,
Victor
If you do an OEM unlock it will wipe out the phone. So don't do that your current situation.
You need to get the updated phone drivers for it to show up in the adb devices output. The offline device that you are seeing isn't your phone. I can't remember right now what it is, but it probably says something about an emulator. I ran into the same problem after the 4.2.1 to 4.2.2 upgrade. It's a driver issue keeping the phone from showing up.
Unfortunately I can't remember where I got the driver to get my phone to show up after the 4.2.2 upgrade, otherwise I would give you a link.
Edits:
This thread may help:
http://forum.xda-developers.com/showthread.php?t=2150614
Or this:
http://forum.xda-developers.com/showthread.php?t=2150447
After researching this a bit I realized that it was probably adb that I updated, not phone drivers. Here is another link:
http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
Sent from my Nexus 4 using xda app-developers app
Hi,
Hmm, I've just downloaded the latest SDK bundle from here (adt-bundle-mac-x86_64-20130219.zip):
http://developer.android.com/sdk/index.html#mac-bundle
and tried again with the adb from there - still no luck.
Also, I'm on OSX, so I don't actually need to install any drivers.
I'm pretty sure the offline device is this Nexus 4 though - if I don't have anything plugged in, and I use ./adb devices:
Code:
Victors-MacBook-Air:platform-tools victorhooi$ ./adb devices
List of devices attached
However, if I plug in the Nexus 4, it comes up:
Code:
Victors-MacBook-Air:platform-tools victorhooi$ ./adb devices
List of devices attached
004217aa9f10f0d1 offline
If it is the stupid RSA key thing - is there any way to force it to accept without needing to use the touchscreen? Or if it's not that, what other possibilities are we looking at?
Cheers,
Victor
Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
bump...
anyone?!??!?!
I'm having a problem that is a little similar to yours. I have a nexus 7 2013 wifi. It won't boot up all the way it gets stuck on the X screen. Bootloader is locked and usb debugging is off. I've been trying to figure out if I can do a pull or backup over the adb sideloader.
Does your nexus have that capability?
I did come across a method that would unlock the bootloader. You need to install a nexus 7 toolkit.
I don't know if that will help you but let me dig up the link to the instructions.
If you would take the time to actually read the guides around here you would know that USB debugging is not a requirement in fast boot or recovery mode. USB debugging only applies to a booted os. Why don't you follow the guides and manually install your drivers? Use fast boot commands to flash a stock image. This isn't difficult to do. Stop messing with toolkits and learn something. You're here on XDA, utilize the resources we have.
happyfuntimes7 said:
Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
Click to expand...
Click to collapse
Use Nexus root toolkit and folow Full driver instalation guide for correct driver instalation
After this use Flash stock to repair, then you can continue to unlock/root or anithing else.
Hello,
I've had my Nexus 4 for about six months now and have never had any issues with it until two weeks ago. I've been using TWRP and multirom on it to try out Firefox OS, CM11, LuneOS, Sailfish OS, and Ubuntu Touch (running with 4.2.2 as base per requirements for Sailfish and LuneOS). I installed the latest LuneOS build about two weeks ago which involves installing via MultiROM and then switching it to be the primary ROM for the device (temporarily moving Android 4.2.2 to a secondary ROM going back into recovery and reversing it when I'm ready to use my other OS's again).
Anyways I started up LuneOS as usual with no issues and messed around with a bit before deciding to reboot (still into LuneOS not recovery) for whatever reason but the phone never did turn back on. I set the phone down for a few minutes not paying attention so I'm not sure if anything (visibly) unusual happened.
I'm not able to get it to go into recovery mode no matter how long I hold volume down + power (or any other combination of the volume/power buttons) and Nexus Root Toolkit does not detect any ADB devices. I've managed to get it to show up in Device Manager twice under Other Devices as "Jellybean on Mako" but still can't do anything with it.
When I plug the device in I can see the backlight turn on but nothing ever displays on the screen. I've been trying for two weeks now and have tried charging it for hours plugged up to my PC, original wall charger, QI charger, and have even taken the device apart to unplug the battery for a while which didn't help either.
Any input would be appreciated as I'm pretty discouraged at this point.
Does phone respond to fastboot commands?
audit13 said:
Does phone respond to fastboot commands?
Click to expand...
Click to collapse
It doesn't appear so. In Nexus Root Toolkit I get the error message that FASTBOOT device was not found.
Just to update I bought a new battery and replaced it and still have the exact same issue with the device so I can safely rule that out. Does anyone else have any suggestions please?
Maybe some info in this thread will be of use: http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
You said it finds "Jellybean on mako" did you try doing adb reboot recovery or adb reboot fastboot? Might work if you had debugging on. Also what shows up on the screen when you shut the device down and attempt to go to bootloader?
After spending 2 days on the forums and softbricking my device for several times, here's my 2 cents about on how to do the upgrade from Andorid 10 to Android 11 or even to downgrade ... on the HA units from Dasaita.
First of all, a small disclaimer:
This worked for me, it might not work for you.
You might end up in bootloop, blackscreen, softbrick, be aware of this risk
My device is a Dasaita Max11, I wanted to downgrade to A10, in order to get Magisk and Hal9k v5 mod installed.
After purchasing modinstaller 3pro, and trying to install Andorid10 I ended up in a blackscreen. Hopefully @Hal9k_ will be able to fix this in his further releases.
Remember, this was ONLY tested and worked on a MTCE_HA device. A rather new model sold by Dasaita last december. If you have a HTC or other device this has no or litlle importance to you, since the images atached are ONLY for HA devices. Also, if you have an older Dasaita model, it might not work as described bellow:
What you'll need:
- a USB A to USB A cable (as short as possible)
- the purple usb plug cable (labeled carplay/android auto) that comes out of the back of de divice (this is the only one that recognized my device in bootloader mode. Feel free to try the others, in function of what configuration your device might have.
- driver assistant (see google drive link)
- flash tool (see google drive link)
- full system image of Android 11 or 10 regarding what you want.
- a pin or paperclip to push the reset button.
The procedure is rather simple:
1. Download and install the driver assistant (google drive link at the end), run it to install the drivers on your windows machine
2. Unpack rkdevtool and run the exe (google drive link at the end). At this point the program will display a huge message in the bottom part saying: "no devices found". That's good.
3. Connect the Usb cable to the HU and to the PC, while the device is turned off (like no power, not in sleep mode)
4. Push the reset button and keep it pushed. While doing this turn on the device. At this point if everything is setup correctly you should hear a notification sound from windows and RKDevTool should say: "Found one bootloader device".
4a) If you only hear the notification and the device is not found in boot loader mode by RKDevTool, check Device Manager and try to reinstall the drivers / install other drivers, try another USB port. (at this point, the usbA to usbA might be to long if the device manager shows: unrecognized device)
4b) If you hear no sound, RKDevTool still shows no devices: Turn off the HU, (really of, no power). After 10-30 seconds turn it on, while it is on, press the reset button and keep it pressed (even after side leds flashing) until the device enters bootloader mode and it is recognized by the RKDevTool.
4c) If none of the above work, switch the usb port on the HU, or try another combination of reset pushing (like trying to enter recovery)
4d) If the PC won't recognize the device in bootloader mode, it might be a situation in which the device is not capable of this, and you might need to take it apart and use the direct SOM flash method ... search the forums.
During step 4 the HU display should remain black, so the only indication of being in bootloader mode and connected to the PC, is the windows notification sound and the messege displayed by RkDevTool.
5)With the device in bootloader mode, connected to the PC, in RKDevTool go to the tab that says: Upgrade firmware. Click on the line(empty rectangle) that says firmware and browse for the desired android img. (10 or 11). See drive link. Attention: the zips from the drive MUST be unpacked and the update.img must be loaded in RkDevTool.
6)After selecting the desired update.img, click on the ERASE FLASH button, wait until the process completes. If everything goes well, the device should reboot in maskrom mode.
7)After the device enters maskrom mode, RkDevTool shoul display the message: "Found one MASKROM device". At this point, just click the UPGRADE button. The new android is flashed on the HU. When the process is finished the HU reboots ITSELF. If that doesn't happen after 1-2max, cut the power and power on.
It should boot in the new android.
Final thoughts after 2 days of thinkering:
This worked for me to downgrade from 11 to 10, and also to upgrade from 10 to 11. Be aware it might NOT work for you!
In theory, if one can get the device in bootloader mode it should work also to upgrade from andoid 9 to 10. This is just a theory and I did not test it.
The advantages of Android 10 over 11 are (for me):
- root access via Magisk (for the time being I could not root 11 with any of the tutorials found online)
- less crap and restrictions imposed by the growing Google censorship..
- the possibility to install the Hal9k v5 mod, one of the greatest and customizable mods ever made for MTCD/MTCE devices.
- using both 11 and 10 I could very certainly tell you, that (from my point of view), 11 has no advantages over 10, nor in stability nor in sharpness.
The images from the google drive are vivid for android 10 and max for android 11. Again, this are FULL images, not just OTA. I put them here after endless hours of searching the net. I respectfully thank to those that took the time to upload them on xda and dasaita forums.
Once you install the base 10 or eleven you can easily switch from vivid to max via update.zip flashed from an usbstick.
Also: there are many tutorials that involve a sdcard, sdcardtool and different combinations of zip images. I tested them ALL using the side sd card slot of the device. NONE OF THEM worked for me. I found the OTG flash method to be the fastest and most reliable, once I figured out how to connect de HU to my pc in bootloader mode.
PX6 MTCE_HA Android 10 full image, Android 11 full image, RkDevTool, Driver Assistant link: https://drive.google.com/drive/folders/1eigYrCKl8Z34KQxBoX3Q91Foy2K15CGm?usp=share_link
Nice! Do you perhaps know where to find the files for other headunits? I have a MTCE_HT and have no idea where to look!