I tried installing custom rom in mi a3 it is saying system is destroyed. I tried installing new global version, it is not working .When checked the bootloader it is false,Please help me anyone, this is my phone i have purchased.I will be very thankfull if anyone can help me out..
You are seeing the ‘System has been destroyed’ message after installing TWRP, correct?
My guess is you have to flash BOOT/SYSTEM imgs to restore your device, and RECOVERY also if it's not an A/B device what I don't know because I don't have that device.
The related Fastboot commands are
Boot:
Code:
fastboot flash boot boot.img
System:
Code:
fastbooot flash system system.img
Recovery:
Code:
fastboot flash recovery recovery.img
This won't work, because the oem in not unlocked. Again flashing the europe file worked. I was able to fix the issue.
Related
I was using cm13 sprout 4 and twrp recovery. Was getting error unfortunately ---- apps stopped again again from different apps.
So simply thought of wiping cache and dalvik from twrp . It gave error e: can't mount /cache. So thought of formattig data but by mistake instead of factory reset, i formatted my android. Now i have no os installed just a twrp and unlocked bootloader with me.
now it gives error also E: can't mount/ system also.
pls help, i have only this night to fix it , tight schedule ahead
Try to flash 4.4.4 (posted here) with SPTools. Then install TWRP and update to 6.0.1.
thanks for reply bro!!
but is their any alternate to sp flash tools.
As my sp flash tool does not detect my device. I have tried it many times on different pcs.
MihaiSG said:
Try to flash 4.4.4 (posted here) with SPTools. Then install TWRP and update to 6.0.1.
Click to expand...
Click to collapse
thanks for reply bro!!
but is their any alternate to sp flash tools.
As my sp flash tool does not detect my device. I have tried it many times on different pcs.
i have tried before on this thread also.
http://forum.xda-developers.com/sparkle-v/general/stock-firmware-t2889509/page5
#41
today i tried these commands in fastboot :
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
all commands finished successfully but strangely their no change in my device.
then i tried flashing cwm recovery
fastboot flash recovery cwm.img
but when i boot in recovery it was twrp only.
so i think the flash command from fastboot is not working.
pls help...
Now i managed to get my friends pc and flashed stock rom using sp flash tool , everything went smoothly without any error but strangely nothing happened in device. It remains same without any os . Is my device completely damaged?? :'(
i am attaching logs
please someone reply....
ghanta said:
i am attaching logs
please someone reply....
Click to expand...
Click to collapse
I used sp flash tool format+download option and flashed stock rom. Now its not even booting or charging anymore. Went to service center they simply said its dead buy a new one...
It is being detected by sp flash tools even now also.
Is their anyone who can help me out here???
i don't want to loose my device
please,anyone help
ghanta said:
I used sp flash tool format+download option and flashed stock rom. Now its not even booting or charging anymore. Went to service center they simply said its dead buy a new one...
It is being detected by sp flash tools even now also.
Is their anyone who can help me out here???
i don't want to loose my device
please,anyone help
Click to expand...
Click to collapse
Hi.. i am also facing the same problem. Did you solve it?? Or what did you do?
I have to buy a new phone.
It is still lying in one corner waiting for any solution if you can find
Karbonn Sparkle V
I have the same issue of mounting system as well as cache and data partition shows error and does not mount.
I did use below commands which completed successfully but does affect my device:
fastboot oem unlock (Press Vol+)
fastboot flash preloader preloader_sprout.bin
fastboot flash protect1 protect_f.img
fastboot flash protect2 protect_s.img
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash secro secro.img
fastboot flash para para.img
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot oem lock (Press Vol+)
fastboot reboot
Rajesh Jakhal
Got a solution!
This is kind of late but I hope this helps other people who have the same issue and are viewing this thread!
Take the battery out of your phone and connect it to your computer. Use SP flash tools and flash the stock rom, using the option, "Format All + Download"
You may have to press a button or button combination to get SPFT to recognize your phone. My phone's volume rockers don't work so I cant help you with that, it was pure luck for me!
Once you let it flash, let the phone boot. It will take some time, longer than usual but it WILL boot. And the bootloader will be locked, so be prepared to start tinkering from scratch!
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.
So i goofed up and wiped everything under advanced when I was switching Roms. I was able to get the original recovery image installed (nv-recovery-st-wx-na-wf-5.2.0.zip) but if i reinstall TWRP and attempt to install any rom, the device name is still "" instead of "ShieldTablet". Is there anyway to restore the device name? I have been digging around on the forums (Including other device forums) but installing recovery is all I have been able to find. (Note: There was some guides advising removal of the device name check from the script within the image file, then re-zipping it. But this seems to always fail with a bad image error.)
Recovery was installed manually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Recovery image pulled from https://developer.nvidia.com/shield-open-source
More info to issue.
Boot into bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Boot into OS. (everything works.)
EnableUSB debug
adb shell settings get global device_name (Gives back "SHIELD Tablet")
Reboot into bootloader
fastboot flash recovery twrp-3.5.1_9-0-shieldtablet.img
Reboot into twrp
Copy on Rom and attempt to install.
Error text:
E3004: This package is for device: shieldtablet; this device is .
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Lineage-14.1-20210312-unofficial-shieldtablet.zip'
Note: above error text occurs when trying to install any ROM.
I am trying to figure out where "E3004: This package is for device: shieldtablet; this device is ." is pulling the device name. That is the part that I need to fix somehow.
Hi did you try to use a older version of twrp ? I also had my issues with the 9.5.1 version as it doesnt recognize my sdcard so i reflashed the version 9.5.0
You beautiful person! Downgrading from twrp-3.5.1_9-0-shieldtablet.img to twrp-3.5.0_9-0-shieldtablet.img allowed the img to install!
Checking in with the same problem. Thank you for the solution listed of downgrading to 3.5.0_9-0.
Currently flashing!
Hi, I am running the latest MIUI on my redmi note 7 pro. I unlocked the bootloader and tried to flash both orange fox and twrp recoveries. The flashing process completes fine but when I try to boot the device to recovery mode or system it says this device has been destroyed. I tried to boot into recovery using fastboot boot recovery_name.img but that doesn't work either. Please help.
check out Technobuzznet's video on Youtube regarding system has been destroyed. I had followed his steps and came out of it victorious.
You should flash stock ROM using Mi flash first then flash a custom recovery you want and afterwards flash vbmeta file.
I would recommend to connect device to fastboot mode first and then flash the vbmeta file using command fastboot flash vbmeta vbmetafile, then try to reboot to recovery, if this doesn't help then you can try the flashing method mentioned above.
Here is how I fixed it.
1. Flashed the vbmeta.img from pixel experience plus rom zip by
fastboot flash vbmeta vbmeta.img
2. Rebooted into fastboot mode again and flashed latest orangefox.img
3. Booted into orangefox deleted system, dalvik, cache,
4. Formatted data partition (cause it was encrypted)
5. Flashed PE plus rom.
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2