Hi guys, i really need help here.
i wanted to flash and install TWRP.img on my redmi note 8 today, but i accidentally used the cmd command fastboot flash boot TWRP.img .
my phone then only boots to TWRP instead of my usual MIUI. so i tried flashing the whole note 8 rom using MiFlashTool. However, there is a error (error:Mismatching image and device), and now my phone only shows me that "the system has been destroyed".
when i tried to flash another boot.img to the phone, it shows "FAILED (command write failed (unknown error))"
{
"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"
}
anyone know what i should do to fix this phone? will really appreciate any help... :crying:
I don't know if you can enter to fastboot mode (power + vol down button). If you can, you can try fastboot flash recovery TWRP.img and search for boot.img at Google I think....
---------- Post added at 23:41 ---------- Previous post was at 23:36 ----------
I think this may helps: https://c.mi.com/thread-2542493-1-0.html
I think that the key is to get boot.img (miui or custom rom) from installation zip and flash it again to the phone via fastboot
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
I got the same message even when trying to boot into recovery, even flashing the recovery again didn't work, so I downloaded The stock rom uncompressed and flashed each img manually with fastboot
Leeban Joseph said:
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
Click to expand...
Click to collapse
This is the right solution
Dont worry you phone isnot destroyed ,just fellow these instructions
Hello Community!
I unlocked my 7 days old REDMI NOTE 8 with MI UNLOCK. All fine.
Then I Boot into Fastboot-mode and flashed TWRP.IMG (twrp-3.3.1-0-ginkgo.img) and started into TWRP (Recovery). On internal drive i copied new XIAOMI.EU, deleted all data. Take a reboot into Recovery, too.
But now I get "Message THE SYSTEM hat been destroyed".
MI UNLOCK SAYs UNLOCK no Nessesary. Is unlocked.
I COULD NOT BOOT INTO TWRP after Flashing TWRP.IMG
Devicecheck:
d:\platform-toolsfastboot devices
130fd5f2 fastboot
Writing TWRP is possible:
d:\platform-toolsfastboot flash recovery twrp.imgSending 'recovery' (65536 KB) OKAY [ 1.673s]
Writing 'recovery' OKAY [ 0.287s]
Finished. Total time: 1.980s
Command CONTINUE:
d:\platform-toolsfastboot continue
resuming boot FAILED (status read failed (Too many links))
Finished. Total time: 30.073s
Can Someone help me, please?
Many Thanks!
I tried to flash with MI Flash (Fastboot.rom)
ginkgo_global_images_V11.0.3.0.PCOMIXM_20191119.0000.00_9.0_global_a8923e1765.tgz
Now I am back to Stock!
Thank you!
Related
A friend of mine has a CID 044 and still got ICS since his Bootloader is already unlocked and he doesn't get OTAs
So, he tried to install the Jelly bean firmware from here: http://forum.xda-developers.com/showthread.php?t=1957376
and while writing the commands he ran into a problem, thats what he said happened:
After he wrote the first command [fastboot oem rebootRUU] the phone rebooted into the HTC logo and got stuck there, so he rebooted it again and it rebooted as usual
Then he got it back to fastboot USB, wrote the second command and this is what he got:
{
"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"
}
Anyone knows whats wrong?
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
hopscotchjunkie said:
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
Click to expand...
Click to collapse
Hey, im his friend with the firmware problem.
I did as you said (did it more then twice) and got the next problem:
I cant post photoes here so i'll just copy it
c:\fastboot>fastboot flash zip firmware.zip
sending 'zip' <12875 KB>...
OKAY [ 1.672s]
writing 'zip'...
<bootloader> adopting the signature contained in this image...
FAILED <remote: 99 unknown fail>
finished. total time: 2.281s
Click to expand...
Click to collapse
Any chance you know whats the problem is?
Thanks alot
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
hopscotchjunkie said:
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
Click to expand...
Click to collapse
1. copyed from where i downloaded
x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
Download:
firmware.zip with hboot 1.36
2. I didnt relock my bootloader before starting,
Now it finnaly worked, but it stuck on the black screen with the htc logo, and it added like a green loading bar that showed that it had finished loading but still stuck on this screen.
Should I wait for something to happend or reboot manually?
Reboot manually (use 'fastboot reboot-bootloader' to get back into the bootloader and unlock it again)
I faced a strange behavior of HOX (tegra). It stuck in bootloops - complete boot, starts apps, then black screen and reboot, and all over again till battery drain.
But strange thing is that i can't do anything - all changes that i do disappear after reboot. Deleted files has returned. Disabled wifi|bt are working again. But there is more! About a year ago i has unlocked bootloader, flash cwm recovery. Now, if i flash other recovery (even stock) through fastboot, i still see my old cwm. If i do full wipe in recovery - phone still boot and all apps and files are there. fastboot oem lock has no effect - phone reboot and have "unlocked" message.
When i flash other rom from recovery, of course, nothing changed, however this process goes without any errors. But it does it too quickly, so i think it don't actually writes anything, only "simulates".
Maybe it hardware problem? Or some wicked setting that i've miss?
Arrgh! Looks like a hardware failure to me...
Post the result of fastboot getvar version-main
May b running a ruu or restoring a nandroid might fix this... However, if the Bootloader isn't getting locked... Then I'm afraid running a ruu would be useless...
-Sent from my IceCold One X!
vin4yak said:
Post the result of fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 1.29.707.11
finished. total time: 0.008s
SonicGD said:
I faced a strange behavior of HOX (tegra). It stuck in bootloops - complete boot, starts apps, then black screen and reboot, and all over again till battery drain.
But strange thing is that i can't do anything - all changes that i do disappear after reboot. Deleted files has returned. Disabled wifi|bt are working again. But there is more! About a year ago i has unlocked bootloader, flash cwm recovery. Now, if i flash other recovery (even stock) through fastboot, i still see my old cwm. If i do full wipe in recovery - phone still boot and all apps and files are there. fastboot oem lock has no effect - phone reboot and have "unlocked" message.
When i flash other rom from recovery, of course, nothing changed, however this process goes without any errors. But it does it too quickly, so i think it don't actually writes anything, only "simulates".
Maybe it hardware problem? Or some wicked setting that i've miss?
Click to expand...
Click to collapse
What was the last thing you changed before the bootloop started?
You said you cant flash recovery, is the bootloader relocked?
tony_76 said:
What was the last thing you changed before the bootloop started?
You said you cant flash recovery, is the bootloader relocked?
Click to expand...
Click to collapse
Phone isn't mine, so i don't know what exactly happen, but owner said, that phone's batter just drain, so he attach charger, phone boot and start looping.
Bootloader said it's unlocked:
{
"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 can flash recovery:
Code:
fastboot.exe flash recovery endeavoru_recovery_signed.img
sending 'recovery' (5786 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.557s]
finished. total time: 1.425s
But after that recovery still cwm, whatever i flash - stock, twrp or other cwm version.
So i've managed to load RUU mode with "adb shell reboot oem-78". When i try to flash firmware.zip in stops at "adopting the signature contained in this image". So, i think, bootloader must be relocked. How can it be done not by "fastboot oem lock"? Maybe there is another way or command? Maybe patch file or so?
I was trying do something more and was found out that i even can't run parted on dev/block/mmcblk0. So, i think, i will return it to it's owner and he will send it to service center.
If I find out what the problem was - I write in this topic
i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
{
"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"
}
nassimxmax said:
i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
Click to expand...
Click to collapse
umm that doesnt really help, whats your fastboot getvar all, whats rom did you try to flash, your flash commands are all wrong but require the other info in order to see what your doing.
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
nassimxmax said:
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
Click to expand...
Click to collapse
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Seanie280672 said:
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Click to expand...
Click to collapse
thank you so much i trying to find that htc fastboot but i didin't find it
i understand now i will try
now it work fine
just waiting ^^
I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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"
}
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
If your rom is not booting you might need to reinstall it.
Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.
Reinstall the stock rom from fastboot
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on
Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom
Hi all,
Just wondering if anyone might be able to lend a hand... Im trying to flash back my Pixel C back to stock (currently running TWRP and build from [ROM][UNOFFICIAL][LineageOS]18.
For some reason, when running the flash-all script or manually flashing the Booloader img, it comes back with "writing 'bootloader' failed (remote 'unsupported command')".
The tablet still boots into the Lineage OS (at least its not a brick... yet..) but really like to try and get it back to stock if I can..
if it helps..
{
"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"
}
When running the flash-all bat file:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
See also:
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command" Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock I used TWRP and SuperSU to root and modify the buildprops to enable and get...
forum.xda-developers.com
bernardomarx said:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Thanks bernardomarx! That seemed to have done the trick!!
Yeah - Luckily TWRP recovery was still accessable, typed in the command within TWRP Terminal. And followed the post you linked to
Essentially after doing the fwtool command in a cmd window:
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
Flashed the bootloader:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
I then had to extract the img zip file and manually flash each img file:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
>fastboot flash vendor vendor.img
Many thanks for entering the details of how you recovered your Pixel C. I had the same problem when un-installing TWRP. I did performed the same steps as you, and the tablet is back up and running!
Many thanks for documenting it here!