Failed status read failed too many links что делать
Failed status read failed too many links что делать
Указанная тема не существует, или находится на премодерации.
Cookies Preference Center
We use cookies on this website. To learn in detail about how we use cookies, please read our full Cookies Notice. To reject all non-essential cookies simply click «Save and Close» below. To accept or reject cookies by category please simply click on the tabs to the left. You can revisit and change your settings at any time. read more
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
How to fix FAILED (status read failed (Too many links))
In this guide, we will show you how to fix the FAILED (status read failed (Too many links)). Owing to the Android open source ecosystem, there are a plethora of tweaks that you could try out. Once you have unlocked the device’s bootloader, you could then flash custom ROMs, custom recoveries like TWRP or LineageOS Recovery. This in turn will allow you to flash ZIP and IMG files, take Nandroid backups, wipe device partitions, Fix recovery bootloop, etc.
Along the same lines, you could also root your device, via TWRP or by patching the stock boot.img file and then flash it via Fastboot Commands. However, while executing all these steps, a few issues are imminent. In this regard, the FAILED (status read failed (Too many links)) error seems to be among the oldest as well as the most frequently occurring ones.
So whereas there are a few errors that come with a well-defined error message, unfortunately, this one doesn’t belong to this category. The status lead failed and too many links don’t help the end-user in understanding the underlying error. But fret not. If you are facing this issue, then this guide is here to help you out. Today we will list out various methods to fix this issue once and for all. Follow along.
The Reason for FAILED (status read failed (Too many links))
More often than not, the issue seems to occur while flashing a custom recovery such as TWRP. In that case, you may get an error message along the following lines:
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending ‘recovery’ (4760 KB)…
OKAY [ 0.456s]
writing ‘recovery’…
FAILED (status read failed (Too many links))
finished. total time: 0.551s
Likewise, it could also take the shape of the following message:
fastboot boot twrp.img
Sending ‘boot.img’ (65536 KB) OKAY [ 1.541s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
One thing evident from the above two cases is the fact that it isn’t related to A/B partition devices only. This is because in the first instance, the user has an A partition device as he is flashing the recovery to the recovery partition. Then in the second instance, the user has an A/B partition device- since he/she is sending the twrp image to the boot partition (A/B devices don’t have a dedicated recovery partition, all is taken care of by the boot partition).
Furthermore, most of the time this issue occurs while booting/flashing a custom recovery. In some rare cases, it might be due to the execution of some other ADB and Fastboot commands or flashing custom binaries. With this, you might have got a perfect knowledge behind the reason for this error, let’s now turn our attention towards the more important part- how to rectify it. Well, here are the different methods that will help you fix the FAILED (status read failed (Too many links)) issue. Follow along.
How to Fix FAILED (status read failed (Too many links))
There isn’t any universal fix for the aforementioned issue. You will have to try out all the below mentioned workarounds until you are able to achieve success. We will start off with some basic fixes followed by the advanced ones. Fortunately, in this case, the basic fix should do its job more often than not.
Fix 1: Change USB Cable
The most common cause for this error is using an old, unofficial, or teared up USB cable. Therefore, we would request you to switch over to the official USB cable and retry with the steps. On the other hand, some users were facing the issue with the official USB cable itself. Hence they switched over to another cable and the error was fixed. So to summarize this fix you should try using a different USB cable and this might fix the FAILED (status read failed (Too many links)) issue.
Fix 2: Use USB 2.0 Ports
USB 3.0 Ports are known to give out too many issues. In most instances, they break down the ADB or Fastboot communication between your device and PC. Therefore, we would suggest you switch over to the USB 2.0 ports and carry out the desired task. Check if it fixes the FAILED (status read failed (Too many links)) issue.
Fix 3: Use the Google ADB Drivers
Well, as of now there are a plethora of ADB and Fastboot tools available across the web. However, just to claim that they are among the smallest in size, they tend to compromise on the performance front. As a result, they leave out a few important files. Hence we would suggest you don’t install any such tools but rather stick with the one provided by Google. Here is the link for the same: Download Google’s Android SDK Platform Tools.
Fix 4: Use CMD over PowerShell
I personally keep a safe distance from PowerShell and always stick with Comand Prompt. The reason being the fact that the former makes the matter more complicated than it should have been. For example, you might have to use a period and forward slash before executing any ADB and Fastboot command. Not doing so throws up an error or two. So it’s always good to use the Command prompt window only.
Fix 5: Launch CMD inside ADB Directory
Another pretty important point worth discussing is that you should always launch the Command Prompt inside the directory where the ADB and Fastboot binaries are present. Upon installing the Android SDK Platform Tools, you will get the platform-tools folder. And you should always launch the CMD window inside that directory only. There are two different methods for the same, let’s check them out:
The shorter method: Just head over to the platform-tools folder, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt inside the ADB directory itself.
The longer method: This involves manually instructing the Command prompt to head over to the ADB directory. So search for CMD from the Start menu. Then type in CD followed by the installation directory of the platform-tools folder.
Fix 6: Re-Verify the Files
Fix 7: Check device is A/B partition or Single-A partition
As already mentioned, A/B devices don’t have the recovery partition and hence you cannot directly flash TWRP inside it. You will have to make use of the boot partition to boot up the recovery as a temporary installation and then permanently flash it right from TWRP itself. On the other hand, single partition devices still have the recovery partition and they could directly flash TWRP. In short, here’s what needs to be done:
Verify if your device is A/B or A Slot:
The easiest way of doing so is to download the Treble Check – Treble Compatibility Checking App from Play Store. Then launch the app and verify the number of slots for your device.
If A/B Device
If your device comes out to be an A/B partition, then you will have to use the following command:
Once booted to TWRP, you could then flash the TWRP ZIP for the permanent installation.
If A only Device
if your device just has a single slot, then you could directly flash it as follows:
In both these cases, make sure that you have renamed the recovery to twrp, transferred it to the platform-tools folder and the command is being executed right from the CMD window that has been launched inside the platform-tools folder only. Keep these points in mind and see if the FAILED (status read failed (Too many links)) issue has been fixed or not.
Fix 8: Restart, But After a Pause
Well, I can’t really explain the logical explanation behind this fix, but in my 8+ years of custom development experiences, there have been a few instances where a complete restart of the entire process was able to fix the underlying issue. As far as this issue is concerned, completely shut down the PC. Likewise, then turn off your device and keep it in that mode for around 5 mins. Then power both the devices on.
With this, we conclude the guide on how to fix the FAILED (status read failed (Too many links)) issue. We have shared eight different fixes for the same, any one or a combination of two or more should work out for you. Do let us know in the comments which of the above-listed methods spelled out success in your case.
About Chief Editor
Sadique Hassan
A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”
Failed status read failed too many links что делать
Новые темы необходимо создавать только в корневом разделе! В дальнейшем они будут обработаны модераторами.
При установке Android 10 крайне рекомендуется ставить TWRP с поддержкой Quota, чтобы избежать проблем.
По вопросам обновления и актуализации шапки, обращайтесь к Владимир Евсеенко в QMS
herrfelix, извиняюсь, забылось, что это спарсе файлы и нужно симг2имг
что бы не забывалось
sdat2img system.transfer.list system.new.dat system.new.img
Народ, у меня все установилось с 1 раза. Работает отлично, раза в 2 быстрее, чем миуи
Камера, гпс, звонки, инет, сенсоры вроде все работает. Батарею тоже держит лучше
Добавлено 31.12.2016, 13:17:
Только никак не могу включить нав бар, может кто поможет?
tolyy, это ведь о циане?
Failed status read failed too many links что делать
В теме нет куратора. По вопросам наполнения шапки обращайтесь к модераторам раздела через кнопку 
под сообщениями, на которые необходимо добавить ссылки.
TWRP 6.0 от Cofface (beta)
Нужен разблокированный загрузчик
установить через adb командами:
fastboot flash recovery cofface_recovery_redmi4A_test.img
fastboot boot cofface_recovery_redmi4A_test.img
Поставил викли от xiaomi.eu 6.12.1
отписуюсь
перевод нормальный
гаппсы есть
ставил начисто в кастомном рекавери
брать тута
рут прошить в рекавери 
SuperSU-v2.78-201609011115.zip ( 4.77 МБ )
пост будет дополняться впечатлениями. автономность и тесты батареи завтра. спасибо мне
пока не могу маркет открыть. мб сам косячу, или йота которую раздавать приходится
проблему решил
тоже поставил. Все отлично. маркет работает. темы, обои онлайн не скачиваются
То есть чтобы ее прошить надо в начале на китайский кастом поставить официальную китайскую прошу, посмотреть в свойствах разработчика разлочен ли загрузчик, и только потом через МиФлэш я смогу прошить «вашу» «чудо-прошу»? Или я не правильно понимаю?
только читай внимательно
этот способ работает всегда если все правильно делать
отключить подпись драйверов в винде отключить и драйвер поставить https://yadi.sk/d/qDufr6EPxgoK9
4ку прайм я с трудом, но разлочил на 3ем по счету аккаунте после включения опции OEM Unlock. С этим пока не получается ничего сделать.
короче ребята усложняют анлок. помимо переключателя, в 8.2 добавился раздел с добавлением девайса к аккаунту и анлоку. первый раз вроде ничего не выдало, сейчас выдает 10008 ошибку и что то про API
разблокировал кое как без этой опции, перестало писать что аккаунт на девайсе другой. накатил TWRP и multirom, грузится.
[Q] fastboot FAILED command too many links Help!
Breadcrumb
DaMightyTom
Member
I just rebooted my Nexus and now it sits still at the Google logo.
I’m in desperate need of help.
I did install CWM and a custom ROM.
When I try to boot in recovery the device locks up and I have to pull the battery.
I have tried the Galaxy Nexus Toolkit, Fastboot commands to restore an stock image and do a factory reset.
I’m out of options here. Anyone can give me a helping hand? its 02:30 AM and I need my alarm to go off at 6:30.
DaMightyTom
Member
cancerouspete
Senior Member
definitely read up through the stickies on fastboot use & adb use
ogdobber
Inactive Recognized Developer
I just rebooted my Nexus and now it sits still at the Google logo.
I’m in desperate need of help.
I did install CWM and a custom ROM.
When I try to boot in recovery the device locks up and I have to pull the battery.
I have tried the Galaxy Nexus Toolkit, Fastboot commands to restore an stock image and do a factory reset.
I’m out of options here. Anyone can give me a helping hand? its 02:30 AM and I need my alarm to go off at 6:30.
it seems you flashed the wrong recovery. they are gms and lte specific. so go to the appropriate developer forum and get the right one.
next, fastboot only works when you are in the bootloader screen. adb is for when the phone is on or in recovery mode.
but, it looks like you don’t have the right drivers for abd..
no matter, everything can be done in fastboot for now.
DaMightyTom
Member
Flashed the wrong recovery?
I dont think so, I get this error no matter what I do.
I have tried flashing the recovery, flashing 3 different versions of the GSM stock firmware. flashing CMW recovery and manually flashing bootloader, radio from google stock firmware.
Nothing works. Too many links and the phone freezes in bootloader mode.
DaMightyTom
Member
When pulling the battery I get a faint burning smell inside the device?
Could it be a hardware malfunction rather than a software?
DaMightyTom
Member
I just installed ADB drivers on my laptop to no avail.
Same problem.
I can get into the bootloader, something It’s frozen at start but sometimes I get contact and PDA recognises it, if I press the popup to connect Pda to the phone I get a Failed command inside the phone.
After any fastboot command like recovery or flash the phone returns unknown command or too many links and freezes.
DaMightyTom
Member
I just tried booting the phone up and it was standing on the startup graphics for a LONG time.
But then I got this message:
Encryption unsuccessfull.
Encryption was interupted and cant resume
bla bla
To move forward i have to press this «reset» button. Im trying but pressing wont do anything.
Anyone have any ideas before I return the device?
Goat_For_Sale
Senior Member
DaMightyTom
Member
jhuynh
Senior Member
DaMightyTom
Member
Goat_For_Sale
Senior Member
DaMightyTom
Member
DaMightyTom
Member
I have odin and the nexus in download mode.
Now before I do anything, is there a nice neat guide how to install factory settings with everything?
Goat_For_Sale
Senior Member
DaMightyTom
Member
Okey so i found this.
Original firmware for the nexus. Seems to be an Exe file with implemented odin or something.
Anyways I ran it. It got stock on Write Nand or something. I googled it and someone suggested I would pull the battery and try it again.
Actually when I plug it in it spazzes out like something is plugging it in and plugging it out all the time. The device manager is flickering since its updating.
DaMightyTom
Member
Plugging it in the computer then putting the batteri in seems to made Odin find it again.
Goat_For_Sale
Senior Member
DaMightyTom
Member
No. recovery havent worked since the start of the problem. Only bootloader and download mode.
Now I am stuck with the triangle.
Found this picture its very similiar to the one I am having.
Similar threads
Breadcrumb
Top Liked Posts
No. recovery havent worked since the start of the problem. Only bootloader and download mode.
Now I am stuck with the triangle.
Found this picture its very similiar to the one I am having.
FWIW, I had this same problem and am pretty sure I resolved it on my end.
When trying to flash a new recovery, I would get something like:
I also experienced constant issues accessing my phone via Windows Explorer when connected by USB. Sometimes it would just hang, other times I’d try copying files to the phone and get a ‘File Transfer Aborted’ error from Windows. Sometimes it worked, sometimes it didn’t.
My motherboard (Gigabyte H67A-UD3H-B3) has 2 USB controllers. My USB2 controller is reported as an Intel 6 Series/C200 chipset. My USB3 controller is by Renesas.
For those with this problem (this is the #1 Google hit for «galaxy nexus fastboot failed (too many link)»), I suggest updating your USB controller drivers, if any are available. When that fails, see if your system has a secondary USB controller and throw the phone into that port and give it a try.
DaMightyTom reported issues on 2 separate computers, but it’s possible both computers had the same USB chipset (or two different ones with the same fundamental issue).