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.
Hey guys, I need your help. I'm unable to unlock bootloader. I downloaded everything I need, I got my unlock number from huawei site etc. When I run adb it detects my phone, I write down adb reboot bootloader, it switches my phone into that white screen where it says LOCKED. Then I run this command - fastboot oem unlock (my unlock number from huawei site) and it replies with- Waiting for any device and nothing happens. Phone is still locked, I cannot write more commands and even if I wait for some period of time, nothing changes and I am forced to reboot without unlocking
Do you guys have any suggestions?
PS: another problem...probably week and half ago my wifi stopped working..it detects different wifi routers, but I am unable to connect and if I connect, the internet is not working. I've read on other forums it could be hw issue. I've also tried every possible step to solve this problem but flashing new ROM, since I haven't been succesful with unlocking bootloader.
Thanks.
sainG said:
Hey guys, I need your help. I'm unable to unlock bootloader. I downloaded everything I need, I got my unlock number from huawei site etc. When I run adb it detects my phone, I write down adb reboot bootloader, it switches my phone into that white screen where it says LOCKED. Then I run this command - fastboot oem unlock (my unlock number from huawei site) and it replies with- Waiting for any device and nothing happens. Phone is still locked, I cannot write more commands and even if I wait for some period of time, nothing changes and I am forced to reboot without unlocking
Do you guys have any suggestions?
PS: another problem...probably week and half ago my wifi stopped working..it detects different wifi routers, but I am unable to connect and if I connect, the internet is not working. I've read on other forums it could be hw issue. I've also tried every possible step to solve this problem but flashing new ROM, since I haven't been succesful with unlocking bootloader.
Thanks.
Click to expand...
Click to collapse
In fastboot(white screen with Android logo saying locked) type fastboot devices.
If it displays YOUR phone serial no of your phone then everything is fine. If no serial number appears then your phone isn't connected to minimal adb. Also it can be a driver/cable issue.
EDIT: I know a way of getting out of the bootloader but it requires me to unlock it (even though I left it unlocked after initially doing it). Unfortunately, though, I think I'm left with a £150 paperweight since I need an OS on the device to enable OEM unlocking and the device literally has no OS or recovery after the hard brick. Motorola have been very "supportive" about my situation even after sending them a 10 paragraph email explaining everything which obviously, they didn't read because I wrote on the first line that the device has been rooted so they knew beforehand. I wrote 10 paragraphs, they replied with six lines, so... Yeah.
I installed LineageOS 14 on my Moto G4 months ago with TWRP and I've never had any issues until today. Literally, just updated to a new nightly build for LineageOS and my phone screen went black and didn't turn back on. I plugged it into my computer and it showed up as QHSUSB_BULK. Obviously, at this point, my device was hard bricked but I found a way online of using Qualcomm's recovery thing they have to get my phone working again, which I did. But now, I've sorta ended up soft bricking the device now.
The device boots up into the bootloader (or what I think is the bootloader). What comes up is just white text at the bottom which basically just tells me information about my phone (product/variant, serial number, CPU, eMMC, DRAM etc.) The menu for the bootloader is just one string of text that only reads 'Start' and when I press the volume buttons, it will show up with more options but they're all highlighted in red and they all lead to the same error message, as follows:
Bootloader logs
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect your device to your computer to get
the Software Repair Assistant.
I've looked around Google for the Software Repair Assistant and it appears to only be for Verizon Wireless and since I'm in the United Kingdom, Verizon Wireless doesn't even exist over here, nor do I even have them as my phone carrier. I'm with O2.
Also, I've tried a few things with Minimal ADB and Fastboot but every time I enter a command, it fails and say's 'FAILED (remote failure). My phone is detected in Fastboot, but not in ADB.
Hopefully, I can get this fixed.
Thanks,
Gabriel.
Guys, i am having the same issue too. I am getting the same issue. Since verizon is not available in india, unable to repair the phone since soft bricked. Kindly help.
did you try to enter fastboot>recovery and get the robot? if you can get that try holding the the power key and tap the up volume. that should give you a drop list with a factory reset option. click it and see what happens?
same problem here.
my phone is rescued.
llaalways said:
same problem here.
Click to expand...
Click to collapse
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
TheEthanMaverick said:
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
Click to expand...
Click to collapse
I am having similar problems with my Galaxy S7. In order to make any significant changes, the bootloader MUST be unlocked FIRST. Hence, the dilemma, if you can't make changes without an unlocked bootloader, and you can't unlock the bootloader, what can be done.
As far as I know Samsung devices simply don't have no fastboot support. Refer to Odin flashing tool instead.
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above
How's the progress so far?
Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!