Bricked Device but has unlocked bootloader and having access to Fastboot Mode
Before doing the process, make sure you have to remove your SdCard and having sufficient battery power to ensure that the process won't be interrupted and to prevent higher chances to hard bricked your device (Dead)
Requirements:
Accessible Fastboot
Unlocked Pocophone F1 Device
Laptop/PC
Type-C Data Cable (Not Charging Cable because it has no data output and input)
Microsoft Visual C++ Redist 2015, 2017 and 2019 (Please report what kind of error you get when flashing and provide a screenshot)
Fastboot ROM updated to 11.0.6.0 (get it here: https://bigota.d.miui.com/V11.0.6.0...M_20200227.0000.00_10.0_global_983cdd2f82.tgz)
Qualcomm Drivers (Search in Google)
Latest Mi Flasher (https://www.xiaomiflash.com/)
7-Zip to extract .tgz file type (This is more efficient and has fewer errors) https://www.7-zip.org/
Patience and Hope
NOTE: FASTBOOT MUST BE ACCESSIBLE, IF NOT, THIS TUTORIAL IS NOT FOR YOU
{
"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"
}
Code:
While Turned off, Hold POWER + VOL DOWN for a few seconds
1. Install the drivers needed (Qualcomm, Microsoft Redist 2015, 2017 & 2019)
2. Reboot your Laptop/PC to make sure all drivers are working
3. Using 7-Zip, extract the Fastboot ROM (beryllium_global_images...da212305c9.tgz) to any designated directory/folder
4. Open Mi Flasher
5. Click "Browse" and navigate to your extracted folder of Fastboot ROM
6. Select the folder that contains the extracted Fastboot ROM
7. On the bottom right, select "Clean All"
8. Now, reboot your phone to Fastboot Mode
Vol Down + Power Button
Click to expand...
Click to collapse
9. Connect your phone to your Laptop/PC
Mi Flasher should recognize your phone. If not, check your Laptop's/PC's USB Port, it might be broken. Try another port, from USB 3.0 to USB 2.0 If the problem still exists, try reinstalling your drivers. Some users faced problems on AMD system, try it on INTEL based system for more stability.
Click to expand...
Click to collapse
10. After all that, click Flash
The process should take about 5-10 minutes depends on what kind of Laptop/PC you have
Click to expand...
Click to collapse
11. If you see on the results tab "Success", then the flashing is completed
12. Now, try rebooting your device
The booting might take about 5-15 minutes, just be patient
Click to expand...
Click to collapse
Bricked Device but has locked bootloader, you applied for unlocking, and have access to Fastboot Mode
There might be a chance. If you applied for unlocking the bootloader, you can still unlock the bootloader by downloading the Mi Unlock Tool on their website https://en.miui.com/unlock/ and boot to fastboot mode and follow the steps provided on their website.
Bricked Device but has locked bootloader, you didn't apply for unlocking, and having access to Fastboot Mode
Your Device is HARD BRICKED. You cannot Flash your phone with a locked bootloader, if you cannot reboot or your device has bootloop after an OTA update, sideload, etc. you should bring your device via the nearest Xiaomi Service Center for further analysis.
You could do the flashing by using EDL Cable (Deep Flash Cable). Or by Testpoints to access EDL with locked bootloader. Find a guide anywhere in XDA or in YouTube.
Is the EDL mode is the same as fastboot mode? Afaik they're different
DAusRon said:
Is the EDL mode is the same as fastboot mode? Afaik they're different
Click to expand...
Click to collapse
EDL or download mode term is used for samsung devices (uses ODIN). They are alike as fastboot mode (uses flasher e.g MI Flash tool, MTK flasher, qualcomm flasher, etc.)
Edl flashing means using a edl flash cable or hardware test points. It allows to unbrick a corrupted bootloader .
anvesh583 said:
Edl flashing via this method doesn't require permissions or what since I heard edl flashing is locked and requires authentication .
Click to expand...
Click to collapse
Going to edit my post since that someone confuses about EDL and Fastboot.
And yes, only Xiaomi has access to EDL Mode (Emergency Download Mode) to force flash system images or firmware because they are the OEM of the device. Only Fastboot that can user be accessed but it requires an unlocked bootloader.
Theoretically as an user, you can access EDL Mode but it requires such tools and knowledge.
Why when I plugin my phone to miflash it only shows the option to unlock and erase data, rather than the flash function?
pipyakas said:
Why when I plugin my phone to miflash it only shows the option to unlock and erase data, rather than the flash function?
Click to expand...
Click to collapse
Please provide a screenshot so that I can know if what update of Mi Flasher you have
anvesh583 said:
Edl flashing means using a edl flash cable or hardware test points. It allows to unbrick a corrupted bootloader .
Click to expand...
Click to collapse
Darklouis said:
Please provide a screenshot so that I can know if what update of Mi Flasher you have
Click to expand...
Click to collapse
Oh no.. You downloaded Mi Unlocker, not Mi Flasher.
Please search in a MIUI Forum or Google "Mi Flash Tool"
Darklouis said:
Oh no.. You downloaded Mi Unlocker, not Mi Flasher.
Please search in a MIUI Forum or Google "Mi Flash Tool"
Click to expand...
Click to collapse
Ya I figured. The problem though, is that your post is linking to miflash unlock tool while you say you need to download the Flasher
I ended up just googled it and got my flash back to miui successful
pipyakas said:
Ya I figured. The problem though, is that your post is linking to miflash unlock tool while you say you need to download the Flasher
I ended up just googled it and got my flash back to miui successful
Click to expand...
Click to collapse
Sorry, will fix it though.
Wanna thank you for this post first. However I was unable to run the latest MiFlash due the error as seen on screenshot. (Windows 10)
No matter what I was trying to do, MiFlash was still asking to install drivers (including Nvidia drivers, wtf?)
USB drivers were installed correctly as I could see connected device with installed drivers and fastboot devices have also worked fine. I have done several reboots, windows test mode, but without success...
If anybody else is having same issue, I was able to use probably very old version of MiFlash to successfully flash fastboot MIUI image.
Poco F1 again operational
Nexus5-32GB said:
Wanna thank you for this post first. However I was unable to run the latest MiFlash due the error as seen on screenshot. (Windows 10)
No matter what I was trying to do, MiFlash was still asking to install drivers (including Nvidia drivers, wtf?)
USB drivers were installed correctly as I could see connected device with installed drivers and fastboot devices have also worked fine. I have done several reboots, windows test mode, but without success...
If anybody else is having same issue, I was able to use probably very old version of MiFlash to successfully flash fastboot MIUI image.
Poco F1 again operational
Click to expand...
Click to collapse
New and updated Mi Flash Tools needs new drivers (including Visual C++ 2015 or the 2017/2018 one, Microsoft Framework, etc. e.g. just like installing a game, it needs drivers to work)
edl required dfc cable/testpoint and auth mi account, no need ubl,,
and fastboot only need ubl..
Darklouis said:
New and updated Mi Flash Tools needs new drivers (including Visual C++ 2015 or the 2017/2018 one, Microsoft Framework, etc. e.g. just like installing a game, it needs drivers to work)
Click to expand...
Click to collapse
That is correct and I have all of them installed, but still unable to run latest MiFlash properly.
Nexus5-32GB said:
That is correct and I have all of them installed, but still unable to run latest MiFlash properly.
Click to expand...
Click to collapse
Please send me a screencap on the details panel
Darklouis said:
Please send me a screencap on the details panel
Click to expand...
Click to collapse
here you are
Nexus5-32GB said:
here you are
Click to expand...
Click to collapse
Got the exact same problem with new Miflash. Tried the old version but it gives me an error. See screencap. The file it says missing is actually there.
The attachment went wrong. Maybe now
Edit:
Maybe you can see my attachment, ican't i dont get why.
Anyways Miflash sends an error message saying ' can not found file flash_all.bat '
When i open the tar file the flash_all.bat file is there.
pederzen said:
The attachment went wrong. Maybe now
Edit:
Maybe you can see my attachment, ican't i dont get why.
Anyways Miflash sends an error message saying ' can not found file flash_all.bat '
When i open the tar file the flash_all.bat file is there.
Click to expand...
Click to collapse
Bootloader is open but USB debugging was off when the bootloop accured. ADB does not recognise device, older MiFlash does but gives error written above. Any idea how to proceed? Your help is much appreciated
pederzen said:
Bootloader is open but USB debugging was off when the bootloop accured. ADB does not recognise device, older MiFlash does but gives error written above. Any idea how to proceed? Your help is much appreciated
Click to expand...
Click to collapse
Make sure you have the drivers installed.
Check it on "Device Manager" while the device is connected with fastboot mode on.
Related
Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.
Anybody?
{
"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 get this when I hit Apply Update and then use storage as option.
moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?
geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb
geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.
Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
(EDIT) finish the timer for the unlock bootloader, and after that i just flash a stock rom, thanks for everyone who support me
Re-flash Stock ROM
Tell the problem clearly what issues you are facing??
aaashzz said:
Tell the problem clearly what issues you are facing??
Click to expand...
Click to collapse
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
{
"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"
}
Syxnetrax said:
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
View attachment 5198249
Click to expand...
Click to collapse
Yes tha'ts right you can not flash rom with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi. And the with miflash tool you cannot unlock your phone there is an entirely different tool for unlocking the bootloader "miunlock tool" they are entirely different tools the miflash is only for flash mi rom and for lock your phone. And the other side the miunlock tool is for unlocking the bootloader!
aaashzz said:
Yes tha'ts right you can not flash os with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi.
Click to expand...
Click to collapse
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
aaashzz said:
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
Click to expand...
Click to collapse
i can access the fastboot, and the unlock will finish in the time mencioned
Syxnetrax said:
i can access the fastboot, and the unlock will finish in the time mencioned
Click to expand...
Click to collapse
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
jwoegerbauer said:
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
Click to expand...
Click to collapse
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Syxnetrax said:
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Click to expand...
Click to collapse
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
flashing stock rom does not require bootloader to be unlocked.
just flash the rom using adb or fastboot
i will recommend using fastboot because it's reliable but some time it requires unlocked bootloader so just try fastboot after adb has failed.
jwoegerbauer said:
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
adb reboot sideload starts a bootloop of the same screen "ths system has been destroyed"
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Bhanu8082 said:
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Click to expand...
Click to collapse
this happend, idk if im doing something wrong
Syxnetrax said:
View attachment 5198725
this happend, idk if im doing something wrong
Click to expand...
Click to collapse
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
jwoegerbauer said:
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
Click to expand...
Click to collapse
after this the same error repeats and start to bootloop with the system has been destroyed screen
bro problem might be your version of adb just use latest version or try version
Android Debug Bridge version 1.0.32
version 1.0.32 is reliable for me as it works
Syxnetrax said:
after this the same error repeats and start to bootloop with the system has been destroyed screen
Click to expand...
Click to collapse
Fix for "The system has been destroyed" Redmi note 8/8T
Fix for "The system has been destroyed" Redmi note 8/8T This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions...
forum.xda-developers.com
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Hey did you fixed the phone ??
After 6 months from launch date, we finally got bootloader unlock permission on March 2nd 2020 for Realme C12 initially based on Realme UI 1.0. Later Realme gave permission for UI 2.0 too.
Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Unlocking bootloader will trip safetynet. If you want to use bank apps or some apps that use SafetyNet, then you have to pass SafetyNet. To pass it we have to use a Magisk module called 'Universal SafetyNet fix' Or use a custom rom or GSI that uses it if you dont want Magisk.
Also locking bootloader seems to lead 'Red State' in many devices. This can only be solved by going to Service Center. So be prepared for it. To get rid of it flash stock rom once even if you didn't done any modifications.
Prerequisites:-- A PC
- USB Cable(We can use charger cable)
- Platform-tools
- Patience
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool from below
For UI 1.0 https://download.c.realme.com/flash/Unlock_tool/DeepTest_realmeC12.apk
For UI 2.0 https://c.realme.com/in/post-details/1526491339024314368
{
"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"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - Go back. Remove app from Recent apps. Open the app and click on Query verification status which is at top right
Step 6 - You can now click “Start the in-depth test” and the device will reboot to fastboot mode automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and Connect the device to PC using USB cable and ready to unlock it.
Step 8 - Now you are in Fastboot Mode. Type this command
Code:
fastboot flashing unlock
in command prompt of PC and Press enter.
Step 9 - On your phone press the Volume Down key to select "UNLOCK THE BOOTLOADER” (or press the Volume Up key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”).
Step 10 - Now type
Code:
fastboot reboot
. Your phone will reboot and all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
And there you go! Your phone will reboot and you can set it all up again. with the ability to root and you can also install GSIs/custom ROMs/recovery!
After unlocking, flash stock rom once from stock recovery to fix some 'Red state' issue and fastboot errors that may lead to GSI booting issues. See this for flashing stock rom. With this you will also get a idea of flashing stock rom.
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.- Try another USB cable.- Download and install exe for 64-bit and 32-bit- Restart PC- Connect device to PC- Go to Device Manager- Double Click on Unidentified Realme C12(Device with exclamation mark)- Click on Update Driver- Select Browser my computer- Select Let me pick- Select Android Device- Click on NextEnjoy!
Q: I am getting carrier-customized phone?
A: See this
Relock your bootloader
Locking bootloader without flashing stock rom again may lead to 'Red State'(can only be fixed by flashing stock rom with PC). So before locking bootloader, flash stock rom in stock recovery and boot to stock rom once.
Tutorial:
Step 0 - Flash stock ROM in stock recovery.(Don't skip this step even if you haven't done any modification)
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume down button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: fastboot flashing lockStep 4 - Press the Volume Down button to select the “Lock bootloader” option (or press the Volume Up button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Thanks
To this
You are showing relame 6pro device
adityalonkar said:
You are showing relame 6pro device
Click to expand...
Click to collapse
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks
HemanthJabalpuri said:
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks
Click to expand...
Click to collapse
Ok Thanks
adityalonkar said:
Ok Thanks
Click to expand...
Click to collapse
Is there chances for getting twrp image for c12 ?
adityalonkar said:
Is there chances for getting twrp image for c12 ?
Click to expand...
Click to collapse
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks
HemanthJabalpuri said:
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks
Click to expand...
Click to collapse
Thanks a lot
Can you make a full tutorial on flashing twrp image on realme c12 device ?
adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Will try later.
Thanks
adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Just made a guide at https://forum.xda-developers.com/t/custom-roms-and-recovery-for-realme-c12.4250073/
I'm stuck in "fast_boot_unlock verify ok"
HemanthJabalpuri said:
fast_boot_unlock_verify ok
Click to expand...
Click to collapse
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.
ramcadag said:
I'm stuck in "fast_boot_unlock verify ok"
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.
Click to expand...
Click to collapse
See the drivers question in the guide. You need to install drivers for working.
Thanks
I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz
Raqeshpati said:
I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz
Click to expand...
Click to collapse
I guess, there is no support for UI2 yet.
So wait for it or downgrade
Thanks
I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)
Shawmik said:
I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)
Click to expand...
Click to collapse
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks
HemanthJabalpuri said:
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks
Click to expand...
Click to collapse
Thanks a lot. I am facing some problems while trying to unlock bootloader. (Forgive me, I am a noob )
I have successfully installed platform-tools, granted usb debugging permission and rebooted my phone to fastboot mode from depth tool. It's showing "fast boot_unlock_verify ok".
Now if I enter the command "fastboot flashing unlock" in command prompt window, it's showing this message: "waiting for device" and nothing is happening afterwards... Am I missing any drivers? (My cable is ok)
@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks
HemanthJabalpuri said:
@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks
Click to expand...
Click to collapse
I don't know why I am facing these weird issues, sorry for bothering you...
I have installed the driver you mentioned in the questions section, now if I connect my phone while in fastboot mode, my PC detects it but if I give the command "fastboot flashing unlock", the command prompt still shows "Waiting for device"...
And I tried going to device manager and manually update my device drivers (as you guided), still the same
[SOLVED] Please read through, hopefully this helps someone!
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.
LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.
Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12
Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first
Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse
can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"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"
}
LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.
BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.
Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"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 in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...
Looks like USB Debugging isn't got successfully enabled on phone.
xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.
binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?
or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot
binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?