Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
hellfirehound said:
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
Click to expand...
Click to collapse
i see none TWRP and O.F for camellian, can you post the links +Miflash log?
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
I think I need to flash the original rom before trying to install a recovery rom
hellfirehound said:
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
Click to expand...
Click to collapse
The Mi Flash logs are in the Miflash Log folder (post the last + or - 20/22ko
This twrp seems not to work (closed thread).
Try the command: fastboot boot twrp.img
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP
And what do you want to do with the TWRP, your device has a Mediatek soc and there is little or no development for Xiaomi with a Mediatek soc.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like a mediatek device.
Never Mind, ill keep the phone as is. Thanks for trying to help
Download and extract to the root of the disk.C:/platform....
https://developer.android.com/studio/releases/platform-tools
rename the Twrp to twrp.img
Put it in the Platform tools folder
Execute the command from this folder
Since no custom is available for your phone I guess you want to update or downgrade for these 2 cases use Miflash not TWRP.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
this error
is frequent with certain version of W10.
Disable driver verification.
.
Related
Hello, I am student at my university studying Computer Science. I work in tech support at my school. This is the first time I have modified the android os. The community on xda has been really helpful and knowledgeable. I have created an account to see if anyone else has done the same thing I have. Anyway read below for my post.
I am trying to change the recovery on my phone to twrp. Let me start out by saying I rooted my phone before on build number 130 (KIW-L24,Android 5.1,EMUI 3.1,C567B130,United States, Channel-Others). I used the instructions here and it worked http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190.
I then decided to update through the huawei updater to build number 151 (KIW-L24, Android 5.1, EMUI 3.1, C567B151, United States, Channel-Others). It eventually got to a black EMUI menu with installing 0%. So I powered it off even though it warned against it. So my phone was bricked so I followed instructions at http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308 and my phone worked again.
Okay so now I want to root my phone so I follow the instructions for rooting. Problem is that I can not replace the EMUI recovery with twrp recovery. I am guessing that it may be because 151 is a security update.
I use these commands on adb with the twrp_kiwi.img in my adb folder(named .android by default)
adb reboot bootloader
fastboot flash recovery twrp_kiwi.img
fastboot reboot
adb reboot recovery
So I wanted to see if I could put the old firmware back so I followed the instructions for bricked device. But the fastboot commands don't seem to do anything with the .img files.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yea so I am lost as to why fastboot commands arent working as it says finished and any advice would be appreciated.
Also is it possible to format the phone similar to a pc and use adb to flash the firmware back on.
I want to eventually backup my phone and put cyanogenmod on it.
... I am guessing that it may be because 151 is a security update
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
JT-on said:
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Arobase40 said:
Is this really for a private use unless you are trying to ask us to do your university exercises for you ? LOL
And as you felt need to mention "I am student at my university studying Computer Science. I work in tech support at my school.", you should know first University mission is to teach you to search and exercise by yourself, to do things step by step and to guess by yourself what was wrong. ^^
Just one tip and advice : read up your own post carefully and you should find out what you've done wrong...
Click to expand...
Click to collapse
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
honor5x_student said:
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
Click to expand...
Click to collapse
TWRP works just fine on B151
plug in usb / Shut down the phone
boot to the bootloader (power + vol down)
open command prompt on PC
fastboot flash recovery twrp_kiwi.img
hold volume up + volume down + power till you see TWRP (about 14 seconds)
In TWRP choose reboot / recovery
Say yes to Root
recovery will reload / flash your rom
If you want to return to Stock use this >> https://www.androidfilehost.com/?fid=24459283995315154
instructions are in the zip
My device Mi3 is running on CyanogenMod 13 and latest TWRP recovery. Unable to install weekly updates of CyanogenMod. Recently, got an update cm-13.0-20160516-NIGHTLY when i tried to install that there is an dialog box of "Apply Update" You are about to update bla bla bla... Note: This feature requires a compatible Recovery or updates will need to be installed manually. I didn't get what it means and i thought TWRP is a valid recovery so proceeded from that. After few minutes it rebooted the device top recovery and nothing happened from that. So i rebooted the system again searched over Internet about the issue haven't found any perfect solution (within what i found) but i tried by copying the update file to /sdcard (i mean root directory) and tried to install the update manually by using TWRP recovery but it is showing an error "Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160516-NIGHTLY-cancro.zip' Updating partition details......done"
Can you help me out how to install the update and also tell me what I've done wrong so that i will not do that again.
Thanks in advance.
Dude, the answer to your question is in the first post of CM13 FAQ.
Go in here and follow the guide.
https://jrizzoli.github.io/dotfiles/
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
manideeproyal said:
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
Click to expand...
Click to collapse
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Well I encountered the same problem a while ago.. I just flashed miui 8 through twrp.. and booted and again flashed latest cm13 and it worked.. No problems so far..
Sent from my MI 3W using XDA-Developers mobile app
@ssasin.monish said:
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Click to expand...
Click to collapse
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
manideeproyal said:
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is literally written in the second step. Bootloader=Fastboot mode.
diongdyh said:
It is literally written in the second step. Bootloader=Fastboot mode.
Click to expand...
Click to collapse
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
even I am having the same problem, I nothing happpens on clicking on flash all file.........
manideeproyal said:
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
Click to expand...
Click to collapse
Yes it'd be best that you flash miui 8 with fastboot/bootloader
http://bigota.d.miui.com/6.6.1/cancro_alpha_images_6.6.1_20160516.0000.22_6.0_cn_2231b4fcb7.tgz
It has reached me a Mate 10 Lite with error when unlocking the Bootloader ... once made it sends you to the custom recovery TWRP but it shows in its description that they wipe the system and do not load it, I have tried to recover with backups uploaded by other users but it does not ... someone has gone through this ... and what suggestion they give ... The same does not allow to install the Stock recovery, to use the file update.app ... Nor does it allow to i
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nstall other types of recoverys.
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Thks
KOALAaufPILLEN said:
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Click to expand...
Click to collapse
Thanks for the answer, but it does not allow as the previous message says ... it does not allow to install any type of recovery either stock or custom ...
It does not allow to mount any partition, Boot, Recoery, etc ... from the TWRP Menu
Unlock bootloader install via command
thks
I do not think I'm spying.
1. The Bootlaoder even if it is released ... it sends you immediately to the TWRP ... once inside it says no OS installed, and it does not allow doing anything because it does not load any of the partitions.
2. Even if you release the Bootloader, it does not allow you to install another type of TWRP ... nor restore backup files ... it only allows you to flash the different OEMINFOs as if it were a rebrand.
KOALAaufPILLEN said:
Unlock bootloader install via command
Click to expand...
Click to collapse
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Thks
I managed to install another custon recovery, that allows to see the partitions, and that the team has a system ... but at the time of restart the bootloader error comes out ... and giving low CMD fastboot has the same unlocked ... perfect ... when I send the command fastboot flash (Boot, recovery, recovery2) it says Failed ... and I can not install the recovery stock.
P.S: Thanks for the advice of DC Phoenix ... I had seen it and I will try ...
KOALAaufPILLEN said:
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Click to expand...
Click to collapse
solved?
hi men, please you can solved this?, i have de same problem
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and fastboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
biggestpoyo said:
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and flashboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
Click to expand...
Click to collapse
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Ebebeeh said:
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Click to expand...
Click to collapse
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
biggestpoyo said:
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
Click to expand...
Click to collapse
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Let me know if it works.
Click to expand...
Click to collapse
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Click to expand...
Click to collapse
Try using mi flash tool with the same image file, you will find the tool on their official website.
biggestpoyo said:
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Click to expand...
Click to collapse
You have MTK variant (Nikel) and trying to flash Snapdragon (Mido) TWRP.
updated to 11.0.2 MIUI and root disapeared , using ADB for TWRP installing , everything goes ok, but after command fastboot reboot , when phone reboots, there is no TWRP , only standart recovery, What I am doing wrong?
Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great