hi, ive tried everything just to get my awful z1 C6903 to boot the marshmallow version of resurrection remix, the lollipop version has graphical glitches, most people got it booting but no one will reply in that thread to me on how to get it working, no instructions either in the thread...
i HAVE searched xda but only found mixed answers
google is a absolute joke for researching anything root related...
i dont know the button combo to boot into recovery from power off
if i try "adb reboot recovery" in stock rom, it just reboots normally
ive tried "fastboot flash boot twrp.img" but bootloops after flashing rom, its the only way to get in recovery btw
"fastboot flash boot boot.img(from the rom.zip) bootloop on sony logo
"fastboot flash kernel boot.img" same as above
"fastboot flash recovery twrp.img" does nothing and the phone will not boot into recovery
i dont think there is a recovery partition but guides always refer to a sony tool that doesnt exist
bootloader is unlocked
what the H am i doing wrong, im fresh outta ideas....
do i need to do a different command, do i need a kernel?...
i would even donate to whoever can help get it booting or to refer to any other lp or mm stable rom
never had a problem with samsung/htc/nexus with this sort of thing, if it still dont work, ima throw the z1 away...
latios381 said:
hi, ive tried everything just to get my awful z1 C6903 to boot the marshmallow version of resurrection remix, the lollipop version has graphical glitches, most people got it booting but no one will reply in that thread to me on how to get it working, no instructions either in the thread...
i HAVE searched xda but only found mixed answers
google is a absolute joke for researching anything root related...
i dont know the button combo to boot into recovery from power off
if i try "adb reboot recovery" in stock rom, it just reboots normally
ive tried "fastboot flash boot twrp.img" but bootloops after flashing rom, its the only way to get in recovery btw
"fastboot flash boot boot.img(from the rom.zip) bootloop on sony logo
"fastboot flash kernel boot.img" same as above
"fastboot flash recovery twrp.img" does nothing and the phone will not boot into recovery
i dont think there is a recovery partition but guides always refer to a sony tool that doesnt exist
bootloader is unlocked
what the H am i doing wrong, im fresh outta ideas....
do i need to do a different command, do i need a kernel?...
i would even donate to whoever can help get it booting or to refer to any other lp or mm stable rom
never had a problem with samsung/htc/nexus with this sort of thing, if it still dont work, ima throw the z1 away...
Click to expand...
Click to collapse
If you've read some of the threads here, you would have already figured out your problem. Evidently you haven't.
You need to have flashed the latest .236 ftf at least once. Once you do it, you will get the new bootloader that can boot 3.10 kernels (MM) and also the TA update that enables the recovery partition. This should be done with Androxyde's Flashtool (can be found in Xperia Z1 General subforum). Once you've done that, you can use "fastboot flash recovery" to flash the latest TWRP 3.0.0-0. Using that, you should be able to flash and boot any MM ROM. Be warned, though, MM still does not have a stable camera. The best you can get is from the AICP MM ROM, which is the only ROM atm to use the latest Sony MM blobs.
If, by graphical issues, you are referring to purple artifacts on the screen in random places (does not appear on Screenshots), then it is because you have used an aftermarket screen. I have the same issue too, and it is not present in MM and stock ROMs. If you are hellbent on using a stable AOSP based LP ROM, I would suggest you mess with the screen color settings in Kernel Adiutor. Keep Red at around 212, Blue and Green at around 208. +-5 values. Experiment, and see which value fixes the issue.
EDIT: To boot into recovery, turn the phone off and press power+vol down till you feel the vibration. Then release both. You should boot into recovery. This works only after you have the TA Update.
Related
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
how do you flash the old bootloader? if you don't mind me asking.
I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.
ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus
You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063
I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.
anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.
Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse
Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.
Hey,
i am running cm11 on my phone and everything went well for a few month.
but today i realized, that i couldnt boot into recovery anymore (not via adb reboot recovery, not via vol-up/down on boot, not via reboot-menu) and that the "sony"-logo which appears during boot is gone. it just goes from black screen to cyanognemod bootanimation.
i tried to use fastboot to boot philz_touch 6.41.6 recovery, but no success there. it just tells me:
Code:
[email protected] /tmp> sudo fastboot boot philz_touch_6.41.6-honami.img
downloading 'boot.img'...
OKAY [ 0.423s]
booting...
FAILED (remote: dtb not found)
any ideas?
loads of ideas..
First you may need to do some reading
You cannot install recovery that way on xperia phones
Secondly, if you were running CM11 you would never have seen the sony logo as there is no sony logo on the CM kernel
Thirdly, if you could successfully boot into CM, then you had the CM kernel which includes recovery.
Which ROM are you on now?
Can you boot your phone? (Maybe not, if you tried to fastboot flash that img.)
gregbradley said:
loads of ideas..
First you may need to do some reading
You cannot install recovery that way on xperia phones
Secondly, if you were running CM11 you would never have seen the sony logo as there is no sony logo on the CM kernel
Thirdly, if you could successfully boot into CM, then you had the CM kernel which includes recovery.
Which ROM are you on now?
Can you boot your phone? (Maybe not, if you tried to fastboot flash that img.)
Click to expand...
Click to collapse
Thank you for the fast response!
I was getting the idea to hotboot the recovery from this post: http://forum.xda-developers.com/showpost.php?p=49186518&postcount=3
Are you sure? I could swear that the white sony logo is the first thing i saw the last month while turning on the phone. I dont know, maybe it was a relict from the DualRecovery i installed before, when i still had a locked bootloader?
I am running cyanogenmod11 nightly, the last updated was on may 10th. I can still boot into the system, but just not into the recovery.
ok, just extract the boot.img from the cm download and flash it using fastboot
You should then be able to enter recovery
gregbradley said:
ok, just extract the boot.img from the cm download and flash it using fastboot
You should then be able to enter recovery
Click to expand...
Click to collapse
Thank you very much! And the white sony-logo is back too.
onlyolli said:
Thank you very much! And the white sony-logo is back too.
Click to expand...
Click to collapse
hmm
That must just be the nightlies then, there used to be the freexperia logo before the cm boot animation
Hi everyone! I have a N4 and installed a AEX rom with SINAI kernel firstly. He works great, but some colors was inverted(like orange, red...) So, i asked on forum rom and i knew what it does not support this kernel, and install the kernel on the zip's rom. I do it, his works, but on beauty time he turn off! After i try turn on, he spawn google(with bootloader unlock on down) but don't pass of this. I've installed two times stock roms, but he freeze on boot screen.
Maybe my N4 be bricked, however i can access bootloader and run fastboot commands.
Please, Help me!
Thx!
Download stock lollipop img from google. Flash that using fastboot, the instructions are there in the site itself. Mako is code for nexus 4. After lollipop boots up, u can flash twrp and then flash other roms.
Hey there!
I am trying to flash TWRP 3.1.1-0 into my Xperia SP using ADB and apparently it cannot find the "recovery" partition. I've found out I can flash into "boot" instead but my question is, is there a way ( or should I even try) to fix this? I've tried Emma but my device is not supported. It's bootloader is unlocked and I am using Lineage OS 7.1
As far as I've searched in the forums ( https://forum.xda-developers.com/xperia-z-ultra/help/recovery-partition-xz-ultra-flashing-t3453568 ), at least for Xperia Z, it means the bootloader I originaly flashed used a "boot" partition instead of "recovery", right?
The final goal of this quest is to relock my bootloader so Sony Companion can reinstall the original firmware and get it as original as possible.
I am new here and, I hope I am posting this in the right section and I did my research right. This forum is so big it is a little overwhelming.
Thanks in advance!
flash recovery into boot
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
FuchsXSP said:
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
Click to expand...
Click to collapse
Yeah that's pretty much where I'm at right now. Whenever I flash TWRP into my Xperia SP using " fastboot flash boot twrp****.img" it works but when the phone boots the TWRP is all that is on the phone. It will not boot into the system. But then, when I install the OS using TWRP, the OS overwrites TWRP and I am back to the old cyanogenmod bootloader.
So answering your questions:
FuchsXSP said:
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"???
Click to expand...
Click to collapse
Yeah that's pretty much how it is done. At least on my Xperia SP. ( I love this phone btw XD)
FuchsXSP said:
After I have done this, I can reboot normally and TWRP will start?
Click to expand...
Click to collapse
Yeah it will only boot into TWRP. You probably wont have access to to your system anymore.
FuchsXSP said:
Then I will be able to install LineageOS?
Click to expand...
Click to collapse
Yeah, just press Install, select the file, and swipe that cool looking safety slider and it should be fine. Beware though older versions of LineageOS had some problems with zip signatures, just make sure to have the newest nightly version (07/12/2017 I guess) and you should be fine.
I have to say though, as anything with android modding, do at your own risk =p.
Here is the solution (at least, the one that worked for me)
I had similar problem - my phone was booting either into Lineage or TWRP, but I had to switch these using ADB commands.
Then I found an application in the Google Play store which can repair this. Look for "TWRP Manager (Requires ROOT)" - from Jmz Software. Free version is good enough.
I installed it and then when I tried to select the option to install TWRP, it tried to install, then complained that there is some problem with my configuration and it looks that it has been repaired. (I'm sorry for not repeating exact messages here, I was doing this about month ago, but when you install this application, the rest is quite self - explanatory).
Anyway, try this. Now my Xperia SP is booting flawlessly - Lineage or TWRP, of course "Reboot to Recovery" option in Lineage also is working correctly !
Xperia SP does not have a dedicated recovery partition like most of other Android phones and a newer Xperia variant. To workaround, the developers of this device have been using different ways of implementing recoveries, the latest and working one is by loading the recovery into our FOTAKernel partition, which is a partition that plays an important role during Stock OTA updates.
Since such a partition serve absolute no purpose when you ventured into custom ROMing, the idea of making use of it for recovery is quite neat. This "feature" is Adrian DC's implementation.
To answer to your question, no, you cannot flash a recovery using fastboot (or any other tools that makes use of fastboot). The options provided by the tool is only limited to partition names, not addresses. You can though, download the FOTA zip from the TWRP thread, and then flash them in the recovery (the one that you booted into because it was installed in /boot). Then re-flash the ROM zip so that the boot image of the ROM gets flashed properly.
It works
Hi,
I have success. On my Xperia SP is now LineageOS 14.1
1. Unlock Bootloader via Sony
2. fastboot flash boot twrp-3.1.1-0-huashan.img
3. reboot SP into twrp
4. wipe and install lineagesOS and opengapps
5. reboot
Now, i can access twrp with second recovery mode (FOTA)
Thanks for your help!! :good:
solved !
sorry to need to bump this thread, but i am having similar issues - i have successfully flashed twrp-huashan as shown in the post above, but on rebooting into twrp, wiping and installing adrian's oreo build, i lose access to twrp
attempting to boot to recovery shows a very brief droid on its back, and then tells me to choose to boot to system or recovery, neitherof which get me back to twrp
any suggestions, as i do not understand why this is so
edit : all is revealed !!
[Recovery][OFFICIAL][UBL] TWRP 3.2.1 Touch Recovery for Xperia SP
https://forum.xda-developers.com/xperia-sp/orig-development/recovery-twrp-3-0-0-touch-recovery-t3309938
Xperia z wont go into recoverymode. blue light with black screen
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Blue light indicating fastboot mode on Sony Xperia Z5
Karimano24 said:
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Click to expand...
Click to collapse
Well, that's it. The blue light indicates fastboot/recovery mode on the Xperia Z. You can now connect the Xperia to a computer via USB, then run e.g. 'fastboot devices' and it should list your Xperia. Or run 'fastboot flash recovery <image filename>' to flash TWRP onto the Xperia.
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good