Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Nobic said:
Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot reboot when pressing vol up maybe?
"FAILED (remote: dtb not found).
Click to expand...
Click to collapse
You choose the wrong TWRP for flash to mi4c. Probably TWRP version for nougat rom flashed on lollipop rom.
Here https://forum.xda-developers.com/showpost.php?p=71120584&postcount=9 follow the steps & you'll be fine. Next time doesn't do anything stupid & read all the introductions before mess with your phone.
Ive tried flashing it using MiFlash but the results were just the same.
Click to expand...
Click to collapse
It can't be same if you flash xiaomi official rom using MiFlash. Looks like you are not flashed it properly. do it corrently .
Related
I just received my new nexus 5.
This is what i did:
1. enabled adb in settings.
2. booted in fastboot mode and launched the "fastboot oem unlock" command
3. rebooted end re-enabled adb settings
4. booted in fastboot mode with "reboot bootloader"
5. flashed latest CWM recovery with "flastboot flash recovery ..."
now my recovery is empty with a scary red triangle in the middle. If i reboot the phone all works normally.
I can even flash other recovery images through the fastboot mode but nothing changes.
What can i do now?
Thanks
Red triangle is stock recovery. You didn't flash other recovery.
Not sure what commands you're using for flashing but I wrote a detailed adb and fastboot thread which you can get to via my signature.
Sent from my Nexus 5 using Tapatalk
what command are you using to flash other recoveries?
i renamed the downloaded file as recovery.img then typed "fastboot flash recovery recovery.img"
it said transferring and flashing done
PacManZ86 said:
i renamed the downloaded file as recovery.img then typed "fastboot flash recovery recovery.img"
it said transferring and flashing done
Click to expand...
Click to collapse
Download it again. In fact you should download TWRP not cwm. Also please read the thread I asked you to read.
Sent from my Nexus 5 using Tapatalk
So, i've tried with CWM, TWRP, with different cables, with different computers, it just seems that my recovery is not writable.
Have i received a faulty phone?
Now i'll try to flash stock recovery than again TWRP.
If it doesn't work i'll flash the whole factory image...
i dont have any other idea
Flashing stock recovery didn't work.
Flashing everything stock worked fine. I think something in the bootloader messed up
Backup everything then flash userdata.img with fastboot while in bootloader.
PacManZ86 said:
Flashing stock recovery didn't work.
Flashing everything stock worked fine. I think something in the bootloader messed up
Click to expand...
Click to collapse
I think you're doing something wrong.
Sent from my Nexus 5 using Tapatalk
I said that flashing everything stock and then TWRP worked fine
PacManZ86 said:
I said that flashing everything stock and then TWRP worked fine
Click to expand...
Click to collapse
You didn't. You said "flashing everything stock worked fine" with no mention of "TWRP". ;]
Sent from my Nexus 5 using Tapatalk
you're right
PacManZ86 said:
you're right
Click to expand...
Click to collapse
hehe sometimes I am..
I have successfully unlocked my Honor 6x. And when i flashed tero using fastboot flash recovery 1p.img (I renamed twrp to this one)
Then it went successful
After that I typed
Fastboot boot 1p.img
But it failed saying remote command not allowed
Then i tried booting recovery by pressing buttons
But it was booting default Huawei recovery
I have flashed multiple times using fastboot it went successful but in actually it don't flashed
Emui 5.0 Android nougat
Twrp 3.1
It said remote command not allowed too to me time ago when i flashed TWRP. Try this: after that you just flashed the recovery, don't do "fastboot boot recovery.img", but normally reboot your phone and try to use the 2 buttons combination (vol up+power) and keep it held until you hear a little vibration, then release it and check if you boot regularly to TWRP or not. Sometimes, if you don't reboot immediately to TWRP after the flash, the previous recovery will overwrite the one you just flashed. Are you using OpenKirin's TWRP right?
RedSkull23 said:
It said remote command not allowed too to me time ago when i flashed TWRP. Try this: after that you just flashed the recovery, don't do "fastboot boot recovery.img", but normally reboot your phone and try to use the 2 buttons combination (vol up+power) and keep it held until you hear a little vibration, then release it and check if you boot regularly to TWRP or not. Sometimes, if you don't reboot immediately to TWRP after the flash, the previous recovery will overwrite the one you just flashed. Are you using OpenKirin's TWRP right?
Click to expand...
Click to collapse
now i want to flash stock recovery
i have stock recovery but i dont know how to flash it i have twrp
narshi shukla said:
now i want to flash stock recovery
i have stock recovery but i dont know how to flash it i have twrp
Click to expand...
Click to collapse
Like TWRP, so through adb.
"fastboot flash recovery [stockrecoveryname].img"
Look for the correct stock recovery for your phone model
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
suzook said:
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
Click to expand...
Click to collapse
try this one
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
had the same problem and it helped
redpoint73 said:
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
Click to expand...
Click to collapse
It sends the file...then I get a remote error. I tried fastboot flash too. It completed, but still boots to fastboot. Guess msm tool is needed. This phone is a pita.
I cannot get twrp to boot.....Phone refuses to boot it. WTF???
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
i.Design said:
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
Click to expand...
Click to collapse
LOL...Um, yes.
Use the All-In-One Tool and flash a fastboot firmware zip (you can find downloads in the software itself). After flashing your back on OOS and can use fastboot to boot TWRP again, then install or restore your rom
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.
Whenever I flash any kernel, my phone loses its recovery and boot partition. It can only boot into bootlader mode.
In Bootoader mode I cannot even flash twrp recovery. Trying to do so results in:
Code:
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
Booting recovery from twrp.img works and when I flash the twrp installer from within, I still cannot boot the phone after this. It boots straight into bootloader again. The only thing I can do, is restoring my boot backup taken in twrp before.
Can anyone help?
P.S.
It doesn't matter which kernel I try... Arter, mad, elementalX...
Guido83 said:
Whenever I flash any kernel, my phone loses its recovery and boot partition. It can only boot into bootlader mode.
In Bootoader mode I cannot even flash twrp recovery. Trying to do so results in:
Code:
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
Booting recovery from twrp.img works and when I flash the twrp installer from within, I still cannot boot the phone after this. It boots straight into bootloader again. The only thing I can do, is restoring my boot backup taken in twrp before.
Can anyone help?
P.S.
It doesn't matter which kernel I try... Arter, mad, elementalX...
Click to expand...
Click to collapse
Use msmtool to start over. And you can't flash recovery only boot it
Yes as mentioned use msm tool to get you back to having a usable device. Then when you want to try flashing kernel. Try using FKM (franco kernel manager) should work.
I've conducted a complete reset using MSM Tools and still cannot flash any custom kernel. It always break the hole boot partition
Guido83 said:
I've conducted a complete reset using MSM Tools and still cannot flash any custom kernel. It always break the hole boot partition
Click to expand...
Click to collapse
I've done that reset a couple times and never had an issue. Make sure you update your phone after msm. Then do the process of getting your phone rooted. After that you should be able to install any kernel just fine. Never tried unrooted but I think it's possible just through twrp to install a custom kernel.