I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone. ☺☺☺
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
if u could access your phone via fastboot / adb then it wasn't a hardbrick , just a softbrick
TahmidZee said:
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
Click to expand...
Click to collapse
You should check first the driver of your computer. Make sure you have the driver of your phone to your computer. After that you can check your device via adb by using commnd on cmd "adb devices".
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Can u please explain it. I am stuck with the same problem. I got success in flashing fastboot rom via miflash tool but it's still stuck in fastboot.
Thanks God Bless You.
---------- Post added at 05:01 PM ---------- Previous post was at 04:36 PM ----------
Deaddo6 said:
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
Click to expand...
Click to collapse
This Helped You guys are angel
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
fastboot boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
dix93 said:
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
flash boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
Click to expand...
Click to collapse
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Wolfcity said:
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
Click to expand...
Click to collapse
Thank you. Actually I was confused in the transcript here, I meant fast boot instead of flash.
But I figured out to use XiaomiFlash Tool to install a ROM via fastboot, and then reinstall a recovery.
The popup camera is not working good with the XIAOMI official rom (It tries to close the cam even if it is already closed). Now I'm trying to install Havoc OS to try to solve those problem, but it demands me the miui v11.0.4 or new (error in twrp), even if I have the miui v12.... trying to figure out why
for the guys whome are stuck on fastboot, you may try "XiaoMiTool V2". this bought my Mi9T from fastboot to life.
make sure all the drivers are installed as well. what's better is install usb drivers, reboot computer, enable usb debugging, connect the phone to computer, select transfer data, wait till the computer completely setup your phone, turn off phone and connect to computer, wait till computer detects and setup, put the phone on fastboot mode and connect, check whether computer shows android device... once everything are confirmed then proceed with flasing.. :good::good:
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
This command - fastboot flash vbmeta worked.
(using a version from Redispade for Grus - mi9se)
Unbricked my bootloop (recovery) after upgrading from miui 12 (android 10) to 12.5 android 11.
thanks!
Related
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
Hey everyone, I just flashed my Moto G5S with a custom ROM (8.1 Pixel Experience).
Everytime I start it, it just goes into TWRP recovery mode. If I hold the Power+Volume buttons, and then select "Start", then it will boot into the Android OS. But if I leave it alone, then it just boots into TWRP Recovery mode.
How do I resolve this? it sounds like the boot order is not correct... but I don't know how to fix this.
EDIT: I have tried running the commands below in TWRP Terminal. They did not help
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Thank you all so much.
Same problem
I'm having exactly the same problem.
I've tried every single thing I can think of so far, including reverting everything back to stock.
Even when I revert the recovery img back to stock, it still tries to boot into recovery and just has a screen with the android logo and one word: "error".
I think that we need the moto G5 plus equivalent of "blank flash". EDIT: I'm not allowed to post links, so replace DOT with . here: cloudDOTEvache-androidDOTcom/Moto/potter/blankflash/
I'll try flashing this and see if it works.
Solved!!
I was finally able to solved this with the following steps:
Download the latest stock rom and firmware. There are lots of links around (sorry, I still can't post links). I used the Feb 2018 version.
Extract the zip file to the same places as fastboot. Boot into the bootloader.
1: Check your device is connected in fastboot mode
Code:
fastboot devices
If your device is listed then proceed.
2. flash bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
This might be enough - I didn't test it but you could try booting back into twrp and reinstalling your custom ROM here.
2. flash stock ROM ( and everything else)
I got a couple of error messages about signing with bad keys here, just ignore them.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
4: Optional: relock bootloader
Code:
fastboot oem lock
5: Reboot and rejoice! (hopefully)
Code:
fastboot reboot
6: Reflash TWRP and then sideload Magisk for root
Reboot back into bootloader.
Download lastest TWRP for Moto G5S plus. Mine is called twrp-sanders-r16.im
g:
Code:
fastboot flash recovery twrp-sanders-r16.img
Get the latest Magisk from their website. Mine is v16.0.
In TWRP go to advanced -> sideload. Then:
Code:
adb sideload Magisk-v16.0.zip[CODE]
And you are done! Good luck :D
Thank you. I will give this a shot when I have a moment. At least I can still use my phone and it's not a brick. I'll come back with an update!
Success!
The previous suggestion worked... thank you so much!
I don't want erase my user data... I'm good with pixel experience rom.. no major bugs.
Help with twrp bootloop.. I use twrp r20 for Sanders unofficial
Hi,
I got the same issue. Can load fine with Start from Bootloader, but after next Restart, it's stuck on TWRP bootloop again.
I installed Pixel Experience, TWRP 3.2.1 r20 and Magisk 17.1
I used fastboot to load each file as you suggested, but still don't work.
Any idea where it might be wrong?
Thanks!
Fix bootloop in twrp MOTO G5 PLUS, works too in G5 s Plus
kevinm2738 said:
Hey everyone, I just flashed my Moto G5S with a custom ROM (8.1 Pixel Experience).
Everytime I start it, it just goes into TWRP recovery mode. If I hold the Power+Volume buttons, and then select "Start", then it will boot into the Android OS. But if I leave it alone, then it just boots into TWRP Recovery mode.
How do I resolve this? it sounds like the boot order is not correct... but I don't know how to fix this.
EDIT: I have tried running the commands below in TWRP Terminal. They did not help
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Thank you all so much.
Click to expand...
Click to collapse
Here the solution: search in youtube "Solucion al Reinicio en Twrp Moto G5 Plus y seguramente todos" i cant upload links because i am a newbbie.
Sorry bad english.
---------- Post added at 12:41 AM ---------- Previous post was at 12:11 AM ----------
stevenhw8 said:
Hi,
I got the same issue. Can load fine with Start from Bootloader, but after next Restart, it's stuck on TWRP bootloop again.
I installed Pixel Experience, TWRP 3.2.1 r20 and Magisk 17.1
I used fastboot to load each file as you suggested, but still don't work.
Any idea where it might be wrong?
Thanks!
Click to expand...
Click to collapse
Here the solution: search in youtube "Solucion al Reinicio en Twrp Moto G5 Plus y seguramente todos" i cant upload links because i am a newbbie.
Sorry bad english.
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Vsider said:
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Click to expand...
Click to collapse
Flash the boot.img of your current firmware version in twrp to both slots and flash twrp installer.zip afterwards then reboot. Now you will be able to boot as normal and have twrp installed also
Vsider said:
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Click to expand...
Click to collapse
Don't use twrp
It'll break userdata partition
Use shrp recovery
For Android 9
https://sourceforge.net/projects/mi...RP_P-v2.2-laurel_sprout-official.img/download
For Android 10
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download
Shrp installer Flashable zip after flashing ROM
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Rajendran Rasa said:
Don't use twrp
It'll break userdata partition
Use shrp recovery
For Android 9
https://sourceforge.net/projects/mi...RP_P-v2.2-laurel_sprout-official.img/download
For Android 10
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download
Shrp installer Flashable zip after flashing ROM
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Click to expand...
Click to collapse
TWRP breaks down? ? Man!! Everyone using it.
All the youtubers.
There is a stable twrp for a3
I have bricked my X3 SZ and worked 1 week to get it unbricked (bricked after update of Android 11) myself, even the service centre not able to restore it and told me that may be Motherboard Problem. Finally by flashing Android 11 Stock images (created using OFP to CMD file converter), I restore the phone. I tried with unlocked Bootloader mode, don't know about locked bootloader state.
Simply download the stock images from the link and boot into bootloader mode, connect to PC, open Minimal ADB Fastboot and flash with fastboot commands. Required USB, Realme, Android Drivers to be installed in the PC. All your data will be lost and do it at your own risk.
Download all the images (userdata, recovery, boot, vbmeta & dtbo) and copy to the Minimal ADB Fastboot folder, run the CMD prompt and run the following commands:
fastboot devices (to check whether phone connected successfully or not)
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot flash dtbo dtbo.img
fastboot reboot
Done.. your X3 SZ must reboot and starts, if not you need to work around or contact SC.. Good Luck
Link Deleted
Thx
EDIT: Very informative and useful!
Cant get magisk_boot.img to work. Going to try orangefox recovery to install Magisk (root).
Tried numerous times to install it (here) took 3-4 hours to get Python to work in windows 7 (cus missing libraries, and newer version dont work). Its bricked the phone 3 times now.
I tried to install TWRP but failed, after I tried Orangefox, successfully installed but not able to boot, rebooting into recovery only, then I flashed only boot image using fastboot and able to boot but lost Custom Recovery. After all I stopped trying anything on X3 SZ
please provide new link
I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.