i ve a problem guys i used to ve root on my phone when i had miui 9
but i didnt do it probably so when i updated miui to 10 the root
is gone and i cant flash twrp again
i tried many time and tried 3 pc's same result
every time i got this errors
C:\Users\Eyon\Desktop\TWRP n ROOT n Redmi Note 5>fastboot devices
4294b69c fastboot
C:\Users\Eyon\Desktop\TWRP n ROOT n Redmi Note 5>fastboot boot "C:\Users\Eyon\De
sktop\TWRP n ROOT n Redmi Note 5\twrp.img"
downloading 'boot.img'...
FAILED (command write failed (No error))
finished. total time: 0.013s
i tried also others command and tried to flash dummy but i got this error
C:\Users\Eyon\Desktop\TWRP n ROOT n Redmi Note 5>fastboot devices
4294b69c fastboot
C:\Users\Eyon\Desktop\TWRP n ROOT n Redmi Note 5>fastboot flash antirbpas "C:\U
sers\Eyon\Desktop\TWRP n ROOT n Redmi Note 5\dummy.img"
target didn't report max-download-size
sending 'antirbpass' (8 KB)...
FAILED (command write failed (No error))
finished. total time: 0.017s
idk what to do guys if some one ve any idea pls tell me
Related
My phone stuck while using so as usual I pulled out the battery and it was his end. From then on bootanimation glitched and the phone restarted all over again. Sth like a bootloop but with complete phone restart. Then I tried to full wipe but with no luck, recovery hung and rebooted the phone. Even now restoring/zip installing etc suddenly restarts the phone. I also tried to flash new recovery/rom via fastboot as well as via Nexus Root Toolkit but everytime I got 'too many links error'
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2308 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.404s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.005s
sending 'radio' (12288 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
archive does not contain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse
I used two different cables that I use for every flashing so far, and different usb slots... I have no idea what else I can do.
Sth has changed, I tried to flash TWRP instead of CWM via fastboot and again, got 'too many links' error BUT it flashed the new recovery anyway . So now I have TWRP, managed to flash cm 10.2.1+gapps. I have a recovery log for sb to analyze. Could you check if my emmc is corrupted telling ftom this log?
i9250 recovery log http://pastebin.com/4Yx0ZwJK
Thanks
EDIT/
A second ago it booted to system in a normal way, then a sudden restart and the phone is stuck while boot animation, like a catch 22...
Hi,
I have Hongmi Redmi1 WCDMA phone, which is in a softbrick boot-loop.
I can get into fastboot , from a Windows (8) comandprompt, so that does look promissing, however...
When I flash the (correct) recovery this is my output:
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (5462 KB)...
OKAY [ 0.181s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.189s
So the writing 'recovery' FAILED (remote: partition 'recovery' not support flash)
- It seems to me I am stuck...
- Is Fastboot the solution to my boot-loop problem?
- Should I try to get adb up and running, and then trying to push a complete ROM to the phone?
Do you have any suggestions?
Thanks in advance,
k03st
After running this command fastboot devices, I get
MTK0123456789ABCDEF fastboot
Does that help?
ko3st said:
Hi,
I have Hongmi Redmi1 WCDMA phone, which is in a softbrick boot-loop.
I can get into fastboot , from a Windows (8) comandprompt, so that does look promissing, however...
When I flash the (correct) recovery this is my output:
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (5462 KB)...
OKAY [ 0.181s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.189s
So the writing 'recovery' FAILED (remote: partition 'recovery' not support flash)
- It seems to me I am stuck...
- Is Fastboot the solution to my boot-loop problem?
- Should I try to get adb up and running, and then trying to push a complete ROM to the phone?
Do you have any suggestions?
Thanks in advance,
k03st
Click to expand...
Click to collapse
see Xiaomi hongmi / red rice by Urich24
All about Xiaomi RedMi 1S / Hongmi 1S by Tarun93
This thread will be moved to Redmi 1S Q&A, Help & Troubleshooting
too bad....
Thanks.
I was unable to get it working .:crying:
hence I have bought a new phone.
My old one is still rebooting, no matter what.....
Cheers,
ko3st
hey my friend!!!
try this:
root your device and install root explorer. go to /system/ and RENAME this file "recovery-from-boot.bak" to "recovery-from-boot.p"
edit:
ooohh sorry, your device have a bootloop :\
Swos said:
hey my friend!!!
try this:
root your device and install root explorer. go to /system/ and RENAME this file "recovery-from-boot.bak" to "recovery-from-boot.p"
edit:
ooohh sorry, your device have a bootloop :\
Click to expand...
Click to collapse
Hello, I have a similar problem, but in a xiaomi MI4, but i have problems to update, the rest is fine, do you think to this can help me solve the problem.
Hello guys, last week I bought a redmi 7. But this i check this cell phone and the MIUI LOCK was unlocked.
I had a brilliant idea to block using adb. And i destroy the system.
I tryed MI PC Suite, I Tryed mi flash is faild (remoite: Update sparse crc list failed), I Tryed in adb fastboot oem unlock, i tryed mi flash unlock, I tryed change the firehose but i won't have a success. I tryed use old versions of miflahs and i was unsuccessful too.
*I tryed install TWRP but have a error:
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
erasing 'recovery' ...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.006s
Did i throw my money in the trash?
Guys, this cell phone have a solution ?
edit3: managed to flash orangefox back(MTP now works in recovery) i should be able to flash a stock rom now
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
edit: i don't have access to an intel machine nor an usb hub(i have a ryzen cpu)
edit2: for some reason i have 3 different errors i can get
Code:
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.911s
You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it
SunilSuni said:
You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it
Click to expand...
Click to collapse
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz
SunilSuni said:
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz
Click to expand...
Click to collapse
that's the file i downloaded and tried
ijheaven said:
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
Click to expand...
Click to collapse
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem
Sidgup1998 said:
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem
Click to expand...
Click to collapse
i'll try that thanks!
or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.
gursewak.10 said:
or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.
Click to expand...
Click to collapse
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
ijheaven said:
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
Click to expand...
Click to collapse
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly
gursewak.10 said:
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly
Click to expand...
Click to collapse
bootloader is unlocked and reinstalled adb still no luck
ijheaven said:
bootloader is unlocked and reinstalled adb still no luck
Click to expand...
Click to collapse
Its working , but khmmm use miui flash tool... stop using adb, becouse you don't know what are you doing..You gonna brick it and than you'll cry again.??
Tip: dummy file. ?
Good luck.
Sent from XDA Labs
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Try this
https://www.getdroidtips.com/twrp-recovery-redmi-note-8-2021-root/
I guess you have used a wrong recovery file, maybe one for another device
The problem is that the command 'flash recovery' does not work, because it says th partition does not exist....
Norah1838 said:
I am using a Redmi Note 8 (2021)
Click to expand...
Click to collapse
wrong forum ! , see Biloba forum
on some devices, boot+recovery are on the same partition, but not for Biloba
boot partition (+dtbo on some cases) is the kernel
i think you should look for official install of miui rom since it has IMG of most partitions ...