Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end
Related
So I tried to change the ROM of my phone because the vendor's one had malware but it was worse, my phone is stuck at boot screen and can't do anything with it.
First I tried to install a ROM with TWRP, it installed but it was just a black screen, you could only see the battery status.
Then I tried to install the global ROM that is on the official xiaomi site but it didn't work and it locked my phone.
Now I can't use TWRP, please help me. I am desperate.
Miflash isn't detecting the phone, but the PC does cause it listed under Android Phone->Android ADB Interface on device manager.
1st:
http://en.miui.com/thread-277276-1-1.html
Once you rebooted it into download mode, use this:
http://en.miui.com/thread-254606-1-1.html
My PC is no longer detecting the phone, only detects Qualcomm 9008
Ok, it is working till the miflash step it says "receiving hello packet" in red
You will need to flash a ROM using fastboot.
First install fastboot on your pc: http://www.theandroidsoul.com/how-to...t-setup-75174/
Second Download a flashable Rom: http://en.miui.com/a-234.html (make sure to choose the right one)
Unzip the rom and navigate to the 'images' folder
Put the phone into Fastboot mode (volume down and power button together until fastboot appears)
Connect the phone to pc with USB
Shift Right click on a blank space in the folder and choose 'open command window here'
run the following commands. one at a time
fastboot devices
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Feriol said:
You will need to flash a ROM using fastboot.
First install fastboot on your pc: http://www.theandroidsoul.com/how-to...t-setup-75174/
Second Download a flashable Rom: http://en.miui.com/a-234.html (make sure to choose the right one)
Unzip the rom and navigate to the 'images' folder
Put the phone into Fastboot mode (volume down and power button together until fastboot appears)
Connect the phone to pc with USB
Shift Right click on a blank space in the folder and choose 'open command window here'
run the following commands. one at a time
fastboot devices
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
After that I use miflash?
Failed after second command
Hello guys, i have a redmi 3s china version, so i try to find global version, i installed all driver and try to use with miflash that:
land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global_470b843c10.tgz
(if i use xiaomiflash i get error) meanwhile with miflash i see device and i flash it but something wrong , i restart the phone i stuck on the logo MI
I try also to download land_global_images_V7.5.4.0.MALMIDE_20160523.0000.23_6.0_global_dc5d804271.tar
seems is the right firmware
So i try again to flash in fastboot mode with miflash but i get error like i have no permission.
So i extract the whole firmware on a dir where there is ADB files , same problem...the device is locked
I try online the procedure with sms to unlock the bootloader ( i think is the only way, right?) or there are any other solution?
Maybe there is a stock rom to replace the original rom and put the global rom in another way?
Thanks in advanced
Bye
Benz83 said:
Hello guys, i have a redmi 3s china version, so i try to find global version, i installed all driver and try to use with miflash that:
land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global_470b843c10.tgz
(if i use xiaomiflash i get error) meanwhile with miflash i see device and i flash it but something wrong , i restart the phone i stuck on the logo MI
I try also to download land_global_images_V7.5.4.0.MALMIDE_20160523.0000.23_6.0_global_dc5d804271.tar
seems is the right firmware
So i try again to flash in fastboot mode with miflash but i get error like i have no permission.
So i extract the whole firmware on a dir where there is ADB files , same problem...the d: evice is locked
I try online the procedure with sms to unlock the bootloader ( i think is the only way, right?) or there are any other solution?
Maybe there is a stock rom to replace the original rom and put the global rom in another way?
Thanks in advanced
Bye
Click to expand...
Click to collapse
Try this: https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
or this: http://en.miui.com/thread-290959-1-1.html
andrespm said:
After that I use miflash?
Failed after second command
Click to expand...
Click to collapse
After you run 'fastboot devices' is anything listed? Usually a string of numbers. If not then the computer isn't seeing your device.
Try rebooting the computer, and trying different USB leads and ports if possible and try again.
Using this method you don't have to use MiFlash, and is for when MiFlash doesn't work.
Once your phone is working again you can try again to install another ROM using traditional methods.
andrespm said:
Try this: https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
or this: http://en.miui.com/thread-290959-1-1.html
Click to expand...
Click to collapse
Hello, i try the steps you give for EDL, after it the screen is not black but i see again the logo MI, i can go on fastboot mode but if i try to flash anykind of rom i get error "FAILED: remote: Critical partition flashing is not allowed)
other solution?
I think the only way is the unlock bootloader, but sincerally i dont know how it work. i did the steps online and the sim is on another device not xiaomi. I will get a sms from xiaomi with some kind of code? and after it how can use for bootloader?
There is another solution? I thinking....but why i cant use the original rom ?? always about the bootloader lock?
___
now i see another post ...use both volume to enter in download mode and on the miflash i saw port com 49, load a rom and start to flash it ...but....another error : The system can not find the file specified (0x80070002: Max buffer sector is 256)
___
This Morning i received the unlock code. When i use the tool stuck on 50℅
Hey there,
I wanted to install twrp on my google nexus 5x.
Therefore I've unlocked the bootloader, entered fastboot mode and flashed the new recovery file.
I did this with adb fastboot tool.
No errors occured during the process, but after restarting the bootloader and entering the recovery mode, twr opens for a few seconds
and then gets closed again. Now I get an errormessage everytime (device software can't be checked... please lock bootloader) and I'm unable to do anything in the twr menu because it keeps getting closed
over and over again.
Now I can't even start my phone "normally" and can't get a connection with adb (no results when using: adb devices )
Some Bootmenu informations:
FASTBOOT MODE
PRODUCT_NAME - bullhead
.
.
.
SECURE BOOT - enabled
DEVICE STATE - unlocked
Does anyone know how to fix this issue?
Have you tried relocking the bootloader?
TechieComputers said:
Have you tried relocking the bootloader?
Click to expand...
Click to collapse
I can't connect via adb, so I can't relock the bootloader
This guide is to help you recover from “The system has destroyed screen” on Redmi Note 7 Pro
I presume the bootloader is unlocked on your device.
The things you need are (Links are provided below):
1: VB meta and Peter’s TWRP (zip)
https://drive.google.com/open?id=1kd9H2cBsjkN-9oa2_6Sj8OlXLTfpRjNN
2: Platform tools (latest)
https://developer.android.com/studio/releases/platform-tools
Install Platform Tools to windows
First turn off the phone, and put it to fastboot mode by pressing the “Power button" and holding the "Volume down button" and release them when the fastboot mode screen appears.
Connect the phone to PC by USB cable, Place the “vbmeta.img” in a folder, hold shift and right click the blank space in the folder and select “Open powershell window here” (command prompt for windows 7)
Type fastboot devices and enter , you will see your device in the list.
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
After flashing vb meta, Its time to flash TWRP to retain the ability to flash rom again. To do that, place the “recovery.img” file in the same folder as “vbmeta.img”. open the powershell again by the method above, enter the command “fastboot devices” to ensure the device is connected. After that, enter the command “fastboot flash recovery recovery.img”, you will get success message below.
Now hold the “Power button” and “Volume up Button” and release the “Power button” as soon as the redmi logo appears while still holding the “Volume up button” till the twrp logo appears.
Flash Rom and you are set.
If you are trying to flash MIUI,
Download latest MIflash tool here and install it on windows.
https://androidfilehost.com/?fid=889764386195900328
Download latest fastboot rom for Note 7 Pro from below link and place the folder on desktop
http://en.miui.com/a-234.html
Open MIflash tool and put device to fastboot (steps to boot to fastboot are above), connect to pc via USB, click the refresh button on the flash tool and start.
The tool takes approx 400-500 seconds to complete , once its finished it will show in a green coloured text that its successfully completed.
Enjoy
DISCLAIMER
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
This Video can also help how to flash Note 7 Pro Using MI flash tool..
https://youtu.be/t8zqIMw-Zsc
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
I recovered from the same issue with a newer fastboot version and LOS Twrp
ustaadg said:
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
Click to expand...
Click to collapse
I got this same issue and then I downloaded the newer fastboot from a third party site. I assume you would had installed ADB and Fastboot systemwide(The one that requires Y as an answer and runs in blue command prompt) That one is like 1.3. You need to install a newer fastboot for this command to work.
I am not sure which one was it that I had but I am adding the link to the same. Newer Fastboot and added vbmeta
Also, I didn't install the Peter's Recovery because I was installing Lineage OS and used the recover_twistloop with wrappedkey for the same
Original Thread Here: LinegaOS16_RN7Pro
One more important thing: I didn't use "fasboot boot <recovery>" for it. I turned off the device and then used "Power Key + Volume Up". At first it didn't work but after one reboot it worked, and this is the only method I am using to go into recovery NOT VIA FASTBOOT or from inside the system. You can try it but it didn't work.
“fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”
P.S: I thought it was verify the first time I saw it.
Also, I really hope you are not going to install MIUI either via Fastboot or Recovery. If you are going to do check roll-back protection. First check your current roll back index and check the rollback in fastboot folder of the Fasboot ROM that you are going to install. More details here. WARNING. MUST READ THIS ARTICLE IF YOU ARE THINKING OF RE-FLASHING MIUI/EUMIUI AT ANY POINT OF TIME.
You will be doomed if you didn't read this. And not in a usual way like a bricked phone. You will need to visit the service center and maybe a month wait for the device to get fixed
Thanks for replying. I downloaded fastboot rom and flashed that with clear all and lock option.
Unlocked again, installed evolution rom and even tried aosipderpfest but whenever I tried installing magisk or after reboot phone stuck on phone is starting and it won't start, I can access settings but nothing else.
Finally wooed everything, installed EU rom then evolution rom. Then magisk now everything is smooth.
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Spleeny97 said:
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Click to expand...
Click to collapse
Xbk eror is related to baseband lock. I saw one video where following was mentioned
Put phone in fastboot mode
In adb use command fastboot oemlock
After that reboot and follow the miflash method with bottom option erase and lock selected. You need to download fastboot rom.
After you set up the device again. Go to developer settings and enable oem unlock and bind the account from there
(bootloader) Device is already locked!
"Flash xbl error"
I tried
violet_images_V10.3.10.0.PFHCNXM_20190725.0000.00_9.0_cn
violet_images_V10.2.5.0.PFHCNXM_20190316.0000.00_9.0_cn
osm bro you just save me thnx alot bruh
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
dineshp953 said:
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
Click to expand...
Click to collapse
did you found the solution??
i am getting the same error
I have two Redmi Note 7 Pro devices. (Global Devices - A.K.A Indian Variant)
first device is unlocked but no custom rom installed like ever
second device is unlocked with lots of custom rom history
While trying to relock my bootloader with MIFLASH (clean all and lock) and Global firmware 11.0.8
First device firmware flash worked perfectly and bootloader is set to lock state - (Widevine status is L1 )
Second device as stated in OP . Flashing success but device showing "SYSTEM HAS BEEN DESTROYED". If i unlock the bootloader of the device then it boots normally but device is in unlock state (widevine status L3)
I think some modifications might have happened to some system partitions which causes the VBMETA - SRCLIST check failure.
ANY DEVS PLEASE LOOKS INTO THIS ISSUE ...
Yeah someone out there I"m trying to relock bootloader bcoz to get access to my corporate mails , netflix HD content and GPAY
(On other hand magisk is having CTS profile check failure as google changed the approach to check the unmodified system)
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing mSpy reviews)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
I am sorry to say that but I guess nothing could be done to fix your tablet. I would be happy to proven wrong and see some solutions in this thread.
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
jwoegerbauer said:
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
Click to expand...
Click to collapse
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
XX_MRBEAN_XX said:
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
Click to expand...
Click to collapse
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
https://devsjournal.com/download-lenovo-usb-drivers-adb.html
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
jwoegerbauer said:
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
Click to expand...
Click to collapse
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
And adb still don't recognize my system.
Thank you for your help
XX_MRBEAN_XX said:
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
Click to expand...
Click to collapse
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
jwoegerbauer said:
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
Click to expand...
Click to collapse
I tried fastboot oem unlock
It's say "unknow commands"
Anyway thank you for your help !
I think we can't do something for this tablet.
Thank you very much
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Yahoo Mike said:
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Click to expand...
Click to collapse
Holy crap. My hero! Can I buy you a beer dude?
-----------------------------------------------------------------------------------------
Start up Failed:
Your device didnt't start up successfully.
Use the software repair assistant on computer
to repair your device.
connect your device to your computer to get
the software repair assistant
ap fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
fastboot reason: Fall-through from charger boot mode
-----------------------------------------------------------------------------------------
is there any way to backup my phone data before flashing ?
only if you installed custom recovery, boot in recovery and exctract /data in SD card/ USB OTG.
as this looks like you screwed up with bootloader unlock, or reflashing stock ROM
indestructible master said:
only if you installed custom recovery, boot in recovery and exctract /data in SD card/ USB OTG.
as this looks like you screwed up with bootloader unlock, or reflashing
Click to expand...
Click to collapse
i didn't tried to unlock bootloader or did anything. my phone was just charging & then this showed up , all other options are disabled (recovery, factory, restart bootoader etc)
adb is not detecting & i can only execute fastboot command ,
is there any way to backup my photos & files ?
niirmaaltwaatii said:
i didn't tried to unlock bootloader or did anything. my phone was just charging & then this showed up , all other options are disabled (recovery, factory, restart bootoader etc)
adb is not detecting & i can only execute fastboot command ,
is there any way to backup my photos & files ?
Click to expand...
Click to collapse
no,
remove SD card, and
at least recover it via fastboot, or via stock recovery (download official, stock ROM and flash in stock recovery, it should work)
or install that software for PC first to check if it can be restored that way, maybe it's faulty boot.img which software can fix (try this first, maybe you get lucky and save data)