So I accidently bricked my device for the first time. I think it was TWRP flash on the boot or something, still trying to figure this.
RIGHT NOW. my OP8t is still bricked, after hours of trying everything I came here.
Currently my device is constantly on the "current boot/recovery image have been destroyed and can not boot."
MSN saying there is a problem but I can't find a solution to it.
I can only access EDL so MSN Download tool is my only way to fixing this issue.
Thanks in advance
{
"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"
}
MystikalE said:
So I accidently bricked my device for the first time. I think it was TWRP flash on the boot or something, still trying to figure this.
RIGHT NOW. my OP8t is still bricked, after hours of trying everything I came here.
Currently my device is constantly on the "current boot/recovery image have been destroyed and can not boot."
MSN saying there is a problem but I can't find a solution to it.
I can only access EDL so MSN Download tool is my only way to fixing this issue.
Thanks in advance
View attachment 5721413
Click to expand...
Click to collapse
Try another MSM version.
Rootk1t said:
Try another MSM version.
Click to expand...
Click to collapse
I managed to fix the brick using this answer, thank you.
MystikalE said:
I managed to fix the brick using this answer, thank you.
Click to expand...
Click to collapse
Next time, if you break your boot again and get the "current boot/recovery image have been destroyed and can not boot." error.
Try to boot to bootloader
if you can, then fastboot flash boot, recovery, vbmeta, and vbmeta_system images of the ROM you are trying to flash. On vbmeta and vbmeta_system images, flash them like this. Copy and paste if needed.
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img && fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Once finished, try to boot to recovery using the volume key to select "Recovery" and power button to make it boot.
If you boot to recovery successfully, sideload the ROM using adb sideload command. If you need to format data for a clean flash, I like to do it before I sideload the ROM.
This should help you to avoid using MSM unless you can't get to your bootloader. You can also go back to OOS from a custom ROM using this method, instead of MSM
Related
Hi,
When flashing TWRP through fastboot I don't get an error in the command line so everything goes fine.
But when i try to boot i get the android error log.
But when i try booting to TWRP (fastboot boot TWRP.img) everything works fine?
Extra information:
Stock android 5.0.1 with sideloaded latest update
Stock kernel
Flashing from linux
Fastboot state unlocked
Command line output
HTML:
target reported max download size of 1073741824 bytes
sending 'recovery' (14000 KB)...
OKAY [ 0.633s]
writing 'recovery'...
OKAY [ 1.100s]
finished. total time: 1.734s
Error logo:
{
"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 would like a working recovery before starting to flash. I'm not new to flashing, but can't seem to find the issue here.
fastboot flash recovery recovery.img is what you should be using
You MAY have written over the kernel with what you did. So just in case use fastboot flash boot boot.img after too
Or have i read it wrong what you've done?
I have used fastboot flash recovery recovery.img
And i can still succesfully boot in the os so the kernel is fine.
It's just weird that i can boot the recovery with fastboot boot recovery.img but cannot boot to it when flashed.
aropop said:
I have used fastboot flash recovery recovery.img
And i can still succesfully boot in the os so the kernel is fine.
It's just weird that i can boot the recovery with fastboot boot recovery.img but cannot boot to it when flashed.
Click to expand...
Click to collapse
Try this
fastboot boot recovery.img
Flash supersu in recovery, then
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Free mobile app
Thanks that fixed it!
Still wondering why, never rooted my nexus 5 before, bought it unlocked it flashed cm11 ...
Hey there, thanks for viewing. Before posting here, I have well enough spent 6+ effective hours (whole day yesterday) to find a solution for this. Unfortunately, I was not successful.
I own a Moto G (XT1033) Dual Sim India Version. Initially, I was running an android 5.02 stock (rooted) with unlocked bootloader when I get a notification about a system update (for 5.1.1). Exited, I downloaded the update and tried to install it, but the OTA wouldn't install. Later, I figured it may be because my phone had an unlocked bootloader. As a result, I tried to re-lock the bootloader by installing 5.0.2 stock again from this guide: http://forum.xda-developers.com/showthread.php?t=2700502 .
Everything was successful and the bootloader was locked again . But this time instead of OTA, I pasted this file Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip which I found in some webpage I don't remember. The update was successfull. Now due to some stupid reason, I wanted to do the whole thing again and and do the OTA udpate this time. This is where the problem begin.
In the bootloader I typed the exact same commands and used the exact same files, but this time, this is what I got:
HTML:
C:\Users\Prasannjeet\Desktop\TWRP\Fastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.103s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.425s
Attaching the screenshot, please have a look.
{
"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"
}
Also adding a pic of my phone's bootloader screen for the error message it receives.
Note that I get the same error for sparsechunk command which comes later. I have tried 10-20 guides, most of them from XDA for the same "Preflash Validatin Failed" error, but none of them fixes my problem.
Bottomline, whatever on earth I do, whatever recovery, stock ROM's, fastboot's I download and install, as soon as I type the command "mfastboot.exe flash partition gpt.bin", I get the same preflash validation failed error message again and again and again!!! :crying: I get the same error for the rest of the commands.
Note that if I try to flash any other custom ROM's via TWRP or any other recovery, I am easily able to do it, but that way I won't be able to lock the bootloader ever again. The only way we can lock the bootloader is something which is not working.
Is it really impossible for me to downgrade now?
Few posts which I have went through already but didn't work:
http://forum.xda-developers.com/moto-g/help/gpe-pre-flash-validation-failed-gpt-t2836073
http://forum.xda-developers.com/moto-g/help/bootloader-preflash-validation-failed-t2834023
I have tried more, but can't find the links now.
Please help :crying:
Thanks!
Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.
thuybang said:
Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.
Click to expand...
Click to collapse
Thanks for replying! Can you share the link of 5.1 ROM, if you have?
I tried to OTA when bootloader unlocked, but it didn't happen
Link ROM :http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
OTA fail because root or you modified system. You only flash stock ROM then update OTA ok. No need relock B.L
Hi,
i tried to downgrade CM 13 to the Stock Android 5.0.2 and relock it (I know that Motorla has the unlock indicator, but this doesn't matter here).
So I tried the following steps as descripted in a lot of posts, but every command failed:
Code:
fastboot oem lock begin //success
fastboot flash partition gpt.bin // Preflash validation failed ->version downgraded for primary gpt
fastboot flash motoboot motoboot.img // Preflash validation for tz -> version downgraded for tz
fastboot flash boot boot.img // Preflash validation failed -> version downgraded for boot
So how can I solve the problem? I think it has something to do with downgrading
You may need to use mfastboot.
However, if you have updated your Bootloader; you may no longer be able to flash a firmware image older than Android 5.1. If that turns out to be the case flash the latest 5.1 Factory Firmware Image for your model using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Unfortunately it makes no difference, same errors.
I already flashed this stock image some time before and it works. And the bootloader is on 41.18.
{
"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"
}
Try with the firmware files in the same folder as mfastboot.exe.
mfastboot flash partition gpt.bin
Nope, same error
You could simply skip that command. And there is always the option to flash the Stock ROM via TWRP.
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection[ROM][FALCON][6.0][STOCK] Identity Crisis 6
The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.
Waishon said:
The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.
Click to expand...
Click to collapse
Flash ROM via TWRP, then relock via fastboot. I would expect it to work.
Does relocking work with a custom recovery? Interesting
Waishon said:
Does relocking work with a custom recovery? Interesting
Click to expand...
Click to collapse
I'm not aware of any relationship between recovery and relocking - but I have no personal experience. If you did need to flash the Stock Recovery, this can be done via TWRP.
Hello Everyone !
unfortunately I Bricked my POCO X3 NFC (Surya)
Now my phones shows this message that "the system has been destroyed" and I can only go to fast boot mode.
I've tried flashing official MIUI 12.0.8 Global version but my phone does not accept any data. I have used miflash tool and XiaomiADBFastbooltool.jar to flash the firmware but both are failed. miflashtool kept showing the status of "Flashing" till 2 hours even I tired waiting and I pulled cable from phone. then I decided to try command prompt. but with every image flash command same error is received " Target didn't report max-download-size "
I'm attaching screenshot.
{
"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"
}
Now my brain can't suggest any stupid thing next. kindly help me recover my phone.
Thanks in Advance
why dont you try a different recovery image? 3.4 for example
[RECOVERY][3.4.0-15][surya]TWRP Xiaomi Poco X3
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
if you cant flash it directly try just booting without flashing
`fastboot boot twrp,img`
then use TWRP to flash a custom ROM see if that works
I have seen solution for system destroyed from a telegram group here it is,
"System destroyed fix
1. Boot to fastboot mode(Hold power+ vol down)
2. Flash vbmeta (#vbmeta)
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
3. Flash recovery img
4. Reboot to recovery and flash rom"
Also I've attached vbmeta.img file here never tried it though, proceed at your own risk and best of luck getting your phone running again.
Also TWRP has been know to cause system destroyed issues so i would suggest orangefox recovery instead its better than TWRP in many ways.
Mak.b said:
I have seen solution for system destroyed from a telegram group here it is,
"System destroyed fix
1. Boot to fastboot mode(Hold power+ vol down)
2. Flash vbmeta (#vbmeta)
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
3. Flash recovery img
4. Reboot to recovery and flash rom"
Also I've attached vbmeta.img file here never tried it though, proceed at your own risk and best of luck getting your phone running again.
Click to expand...
Click to collapse
My Poco x3's System Destroyed itself as it showed a glitch screen and turned off, So now I am trying to flash my phone but never unlocked my bootloader before so Mi flash tool showing can't flash as the bootloader is locked
Moto G stylus 5G Denver build I had TWRP installed and majisk installed I wanted to install a ROM during insallaion i was having issues and needed 2 set my device down for a few minutes and take care of like regular life problems. Anyways my kid get ahold of my phone and did god-knows-what but he had enough time to wipe everything but my external USB drive. i have the full stock file i downloaded to pach wih magisk i have the twrp file as well.i had my backup on my sd card which was erased. so my question is his, where do i go from here? how do i use files in the picture recover back to I guess a stock
{
"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"
}
. Version of Android
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome
tommy2tones1990 said:
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome
Click to expand...
Click to collapse
In my opinion I would just restore back to stock. Basically, using bugjager, make sure you have the stock rom downloaded and unzipped. Now you'll want to probably copy and paste these commands but you'll reboot your Stylus 5G into fastboot mode and once its connected to the second device with bugjager on it, start going down the list of flashing the partitions back... Here are commands you can copy and paste:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
I basically spent a hour trying random things on bugjaegar I honestly have no ideal how I didn't brick this phone seriously but then I flashed vbmeta boot and vendor boot and restarted. It took a long time to start then a msg popped up for half a second and the phone rebooted and then I went thru the whole Google startup process and when I got there I rebooted back to bootloader and flashed the magisk patched img and so far everything seems to work
.. thanks for your help.. I'll probably go ahead and wipe everything and start over using your guide. Then go get everything back to how I had it before and and make multiple backups on at least 2 different micro sds then retry the to install ROM
No worries Just saw your post and figured I'd offer some help.. I personally love the bugjaeger app. I use it all the time... it definitely helps if I'm without a computer and got my tablet lol.. and my handy dandy USB-C to USB-C cable lol...