Hello, newbie here..
Need help!! My phone keeps booting to TWRP whenever I turned it on, connected it to PC, or even when I connected it to my charger.
It happened after I mistakenly uninstalled a system app (it is an app named Freeshare). I thought it was just a sharing app like MiDrop or ShareIt, but clearly that was a mistake.
Now I just can't seem to boot into the system, not even able to enter into the download mode.
I've tried a method that I found in here, like entering a code in TWRP terminal (it was "dd if blablabla", i forgot. Lol), to no avail.
Haven't tried to flash the stock rom or stock boot since I can't find any zip Stock Rom for my phone (my phone is Gome Fenmmy Note).
Does anyone have an idea or know how to fix it?
Thanks in advance
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Or did you flash TWRP to boot partition ??
TWRP needs to be flashed to RECOVERY partition.
If you flash TWRP to boot partition, your device will boot forever to recovery.
If yes, you need to flash the original stock boot.img
VD171 said:
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Click to expand...
Click to collapse
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
disegiooo said:
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
Click to expand...
Click to collapse
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
VD171 said:
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
Click to expand...
Click to collapse
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
disegiooo said:
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
Click to expand...
Click to collapse
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
disegiooo said:
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
Click to expand...
Click to collapse
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
VD171 said:
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
Click to expand...
Click to collapse
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
disegiooo said:
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
Click to expand...
Click to collapse
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script (if available).
Good luck
VD171 said:
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script.
Good luck
Click to expand...
Click to collapse
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
disegiooo said:
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
Click to expand...
Click to collapse
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
VD171 said:
It's same for all xiaomi devices.
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
If you don't know how to flash manually using fastboot, try MiFlash:
Click to expand...
Click to collapse
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
disegiooo said:
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
Click to expand...
Click to collapse
Good job, my friend
You are welcome.
God bless you too
About disabling preinstalled apps, try to perform this in command line:
pm disable-user --user 0 com.android.chrome(Change com.android.chrome to desired package name to disable.)
Related
My Xoom is a 3g that I sent in to have the 4g upgrade. Ive been running different roms for a couple years, decided to go back to stock the other day. I followed some steps I found at xda about how to do that, It was some version of honeycomb.
Anyways, after a reboot of the xoom It is stuck at the red M. I cannot get into recovery, cannon use adb commands. However, fastboot is working. What can I try next? After spending hours googling it, this doesnt seem real uncommon. But most of the links on how to put on a new bootloader with something called avalance 1.35 seem to be broke. Any ideas?
Your Xoom does not have an OS installed, nor a recovery.
Need to fastboot the stock images.
Mjamocha said:
Your Xoom does not have an OS installed. Flash a custom ROM
Click to expand...
Click to collapse
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.
ArXane said:
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.
Click to expand...
Click to collapse
yeah, i corrected my last comment.
hmmm .... odd
Mjamocha said:
yeah, i corrected my last comment.
hmmm .... odd
Click to expand...
Click to collapse
I have done the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I got the files from the Motorola Support site.
I also used the RSD Lite to try and push factory image.
ArXane said:
I have done the following:
Click to expand...
Click to collapse
you forgot the last command
fastboot oem lock
Mjamocha said:
you forgot the last command
fastboot oem lock
Click to expand...
Click to collapse
Sorry, I have done that one also.
are you using the correct stock images for the 4G version?
Mjamocha said:
are you using the correct stock images for the 4G version?
Click to expand...
Click to collapse
Here are the links I have tried:
http://www.randomphantasmagoria.com/firmware/xoom/trygon4g/
HLK75D
I also tried the motorola image: MZ602_HLK75D that I had to request from Motorola.
It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.
Mjamocha said:
It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.
Click to expand...
Click to collapse
WIll try, thank you. Ever heard of everest 1.5 bootloader? It looks like that may be a common fix. All the links I find are broken.
Nope.... flashing HRI66 didnt change anything. Still cannot ADB, still doesnt boot.
no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298
Mjamocha said:
no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298
Click to expand...
Click to collapse
Tried flashing recovery with the stpes agove, same deal, cannot get into recovery. WIll try the LORD tool and will let you know.
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
EDIT: Solved it by using Fastboot and flashing the stock firmware without the -w so far everything is back to normal....know to get that dern kernel again
gears177 said:
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
Click to expand...
Click to collapse
First off, does fastboot recognize the device?
DuckRuckus said:
First off, does fastboot recognize the device?
Click to expand...
Click to collapse
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
gears177 said:
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
Click to expand...
Click to collapse
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
DuckRuckus said:
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
Click to expand...
Click to collapse
Ah nice didnt even realize its recognized under fastboot ive tried flashing the stock recovery but it just gives me an error
gears177 said:
Ah nice didnt even realize its recognized under fastboot
Click to expand...
Click to collapse
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
DuckRuckus said:
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
Click to expand...
Click to collapse
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Nevermind got it flag responsible for deleting userdata thanks alot for the help appreciate your time
gears177 said:
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Click to expand...
Click to collapse
It wipes all your data, that's why you remove it from the flash-all.bat script, unless you need to perform a full wipe. Telperion has an excellent guide for installing the lastest software, if you haven't already read it.
I've heard users having back luck flashing kernels in TWRP, as the kernel has something to do with recovery. I always use the method of booting the TWRP image in fastboot, use ADB to push the files to /tmp, and then do an ADB shell TWRP install of those files. TWRP, kernel, then magisk, in that order. I always reinstall all three, just to be on the safe side, and have never had any issues. Takes a little while, but not as long as redoing the whole freaking thing:silly:
Looks like you figured it out, before I finished my reply
So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?
xiaomi.eu_multi_POCOX3NFC_V12.0.8.0.QJGMIXM_v12-10
MilanTom said:
So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?
Click to expand...
Click to collapse
Don't worry dude. You can still take your phone to fastboot mode. Download a FASTBOOT rom (*.gz or *.tgz) from mifirm.net then flash it via mi-flash (download from mi-globe). Follow the instructions on mifirm.net
adadwa
ndminhdev said:
Download a FASTBOOT rom (*.gz or *.tgz) from mifirm.net
Click to expand...
Click to collapse
Ok I understand that and I've downloaded the ROM but there is this sentence "1. If Fastboot firmware. The ext. must be tgz. If not. Rename it from .gz to .tgz. Extract it by WinRAR" and also these sentences "ZIP. ZIP ROM using Update function in System or TWRP EU. EU ROM flash using TWRP".
I am just completely lost
To be simple : your flash went wrong probably with a bad rom download or a bad flash method.
If I were you I'd reread the post on installing Xiaomi.eu rom and redownload the whole.
Install OrangeFox recovery with the corresponding thread in the forum and ask if you're still lost
By the way, how did you flash that ROM?
Howell said:
By the way, how did you flash that ROM?
Click to expand...
Click to collapse
Well I started on this site https://magiskmanager.com/#How_to_I...Version_220_on_Android_Custom_Recovery_Option and downloaded the stuff that the site said was needed
And which recovery are you using ?
You should be able to reflash stock and recover your phone using the MiFlash tool.
Download fastboot ROM here, and MiFlash tool here.
And also the problem is, that my phone (Poco X3 NFC) isn't being shown in the MiFlash software. I can access the fastboot screen on my phone and yet it still won't show up
Adb drivers are installed ?
Howell said:
Adb drivers are installed ?
Click to expand...
Click to collapse
Yessir
Howell said:
And which recovery are you using ?
Click to expand...
Click to collapse
I don't know If I even have one, because when I hold Volume + and Power button, nothing happens
MilanTom said:
I don't know If I even have one, because when I hold Volume + and Power button, nothing happens
Click to expand...
Click to collapse
But I am pretty sure I tried to install TWRP Recovery
Mate that's just caused by something going wrong. The only times I get that message is the times I have tried to flash a GSI.
I don't know if you can with this unit?
I've fixed that about 5 times with miflash or miflashpro.
Do you have miflash?
It forces a reformat of Miui recovery rom an then you can start again. Just pay close attention to the bottom right hand corner an make sure it is off default. Default is 'relock bootloader'.
MilanTom said:
So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?
Click to expand...
Click to collapse
If drivers are installed an
Howell said:
Adb drivers are installed ?
Click to expand...
Click to collapse
everything is up an running you should be able to get it into fastboot mode (picture of little rabbit fixing his android) an use miflash to reformat an force a flash of miui recovery rom.
I had that happen once with me an it turned out it was my type c cable. Pulled it out an plugged in a wala. PC could connect with my Poco
Bryceicle1971 said:
I had that happen once with me an it turned out it was my type c cable. Pulled it out an plugged in a wala. PC could connect with my Poco
Click to expand...
Click to collapse
The problem is that my computer can't find my phone. Nothing happens when I plug in the USB-C Cable. It doesn't work on the Fastboot screen nor does it work on "the System has been destroyed" screen. I am pretty sure I downloaded the neeeden drivers. And also, the phone was being found/recognized in the working state.
You need to extract then extract again. You double extract with a fastboot image. Then in miflash you find where you extracted that image to. Then hit refresh in miflash an your device should show in miflash. Miflash can be a tricky beast till you have practiced using it a few times
Hi. If you haven't fixed it yet you can try this: Download stock ROM from here (make sure it's the right one for your device!), choose Recovery ROM download link. Put it in your ADB folder. Do the same with recovery. Download this version of recovery as well. Enter fastboot mode on your device and connect it to your PC. Make sure it's detected. If not, try a different USB port on your computer. Open ADB using Open CMD.bat file in ADB folder.
Type in:
fastboot flash recovery OrangeFox-R11.0_6_Alpha-Unofficial-surya.img (hit Enter)
Type in:
fastboot reboot recovery
You should now be able to access your device internal storage from your PC. Copy the downloaded ROM file and OrangeFox-R11-Unofficial-Beta-surya-10-01.zip to your phone (put them in "Download" folder so they're easy to find).
Using Orange Fox recovery file manager find OrangeFox-R11-Unofficial-Beta-surya-10-01.zip and flash it then REBOOT TO RECOVERY.
Using Orange Fox recovery file manager find your ROM file and flash it. Do not reboot! Hit BACK and choose WIPE in Orange Fox menu (Trashcan icon, second from the right) and switch to Format Data at the top. Read the instructions and follow them by typing YES. Reboot to system. You should now have a working device with a clean stock ROM and a custom recovery installed and keep messing around with it
MocnePifko said:
Put it in your ADB folder.
Click to expand...
Click to collapse
Just two more question.
Where does one get the ADB folder? I may have downloaded a few but I don't know if those were good/correct for my device.
And what can I do when the device is not being detected by my computer? Like should I download and install some new drivers?
But can you reach the fastboot splash in your phone?
I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.
Which magisk did you flash? 23 is not working for 9A
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.
Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard
Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.