Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone
Unlock bootloader, should be easy
fastboot boot twrp.img
(If you just want TWRP flash TWRP-installer, might need to erase Data and/or Internal Storage)
Change to Slot B
Wipe System, Dalvik, (Don't know if it needs to be on every ROM change) Data and Internal Storage
Change to Slot A
Flash copy-partitions-AB.zip (Seems like it's needed every re-flash, or at least every ROM change)
Flash ROM, TWRP-installer
Change to Slot B
Go to bootloader
fastboot erase userdata
Go to recovery
Change to Slot A and boot
Flash Magisk and Gapps
Boot phone
Yes you'll need to flash TWRP installer alongside other ZIPs when changing ROMs, as each come with its own recovery for some reason.
If your OEM unlocking option is greyed out just wait a few days and it'll be available. Disregard, I haven't been successful in installing a ROM after that first time, go to CrDroid's for the best shot at it. If mods can delete this post please do.
dear all, after flashing Xiaomi.eu 20.3.19 update I am stuck in a bootloop to the recovey or to the boot loader.
after the second attempt to flash the zip file I was not able to enter my my so the interal sd card is vlocked.
I have access to the otg drive but.
I tried additional the following:
Format data, caches and system
Install 20.3.19 via OTG
install 20.3-12 via otg
install fresh magisk 20.3 via TWRP
updarde to the newest TWRP
downgrade to an older TWRP
all without success
Does anybody have an idea to solve this issue?
Thanks in advance
If you want to flash xiaomi.eu you shouldn't wipe system when flashing from miui. It won't boot if you wipe system. So now you must flash miui with miflash. Then twrp and xiaomi.eu (wipe cache, dalvick)
Thanks alot for the swift reply.
This is the first time that I had this issue and now I am totally stuck, is there no other way than mi flash?
If I well remember flashing the factor< image will erase everything?
I made a backup but due to the locked internal sd card I have not access on this data.
Thanks for the support
Now I have another problem,
As soon as I start the Mi flash tool or the Mi unlock tool the device shuts down from bootloader mode.
I´m Stuck
Thanks for support
Maybe you have some driver problems?
@baltes: ...or try another cable or another USB-port
Thank a lot,
Ich changed the cable and the USB port as well. No change
I downloaded the standard ADB and Fastboot drivers ver 1.4.3.
I don´t hope the the devise is not toally bricked
@baltes: uninstall ADB/fastboot, Mi tools and Mi drivers. Reboot, install MiFlash again and let it install the needed drivers.
rp158 said:
@baltes: uninstall ADB/fastboot, Mi tools and Mi drivers. Reboot, install MiFlash again and let it install the needed drivers.
Click to expand...
Click to collapse
Thanks,
I uninstalled everything, and reinstalled miflashtool, no change as soon as I select refresh the 9SE shuts down (from bootloader)
I managed to erase the internal storage in TWRP, Im able now toto copy MIUI zip on the interal storage and install it successfully. but reboot is then still again innTWRP
So flash some aosp based Rom. Wipe cache, dalvick, data and system before. Do not flash magisk or other mods. Just Rom and gapps. That kind of Rom should boot. Then you can try flash latest global miui Android 10 with miflash and start over to xiaomi.eu.
@baltes: I wouldn't use AOSP to get MiUI runnable. If you do so,
* format data
* reboot to recovery
* wipe system, vendor, data, both caches
* flash ROM, no GApps
Better make a clean base by MiFlash: now you first say, that Fastboot only aborts when clicking Refresh. I don't remember this tool, but are there other options besides Refresh?
coolek33 said:
So flash some aosp based Rom. Wipe cache, dalvick, data and system before. Do not flash magisk or other mods. Just Rom and gapps. That kind of Rom should boot. Then you can try flash latest global miui Android 10 with miflash and start over to xiaomi.eu.
Click to expand...
Click to collapse
Hello, i don´t know wy but after several formats and installations it worked and I´m running now on 20-3-19
Thanks all
Hi everyone
yesterday i receveived the android 10 update OTA for my redmi note 8 global and i updated it
i ve been using OrangeFox recovery since months and everything worked fine until yesterday
i can no more upload files to phone using recovery it shows 0 MB space i reinstalled ginkgo_global_images_V12.0.3.0.QCOMIXM_20201226.0000.00_10.0_global using fastboot then installed again twrp but after every reboot no more custom recovery only MI recovery 3.0 i have to install it everytime now and anyway in twrp or orangefox i can do anything there are strange files names it just seems it can t decrypt data to work properly ( i have no password set btw ) i formated data and same thing
Anyone can help please
be sure that ur phone is unlocked and enable USB debug
here are talking about an issue about installing a custom recovery or an issue in phone storage
I use fox too but I flashed the TWRP 1st using TOOL ALL IN ONE installed it without any issue then flashed fox from a flashable zip
for the memory issue I had it too it started with no being able to copy files that are 4Go or more to the internal memory so I flashed a the stock rom again and the memory become 0 and not accessible
but in my case fox was working so I went to wipe tab and wiped everything after ejecting the memory card in the reboot it said the system was destroyed I flashed the rom again and the issue was resolved
but before u do that make sure the phone is unlocked if not u wont be able to flash anything
Requirements: miui 12.0.3 china stable fastboot rom.
Orangefox recovery;
Custom rom of your choice;
Example xiaomi .eu 12.0.3 stable
Device: gingko(redmi note 8)
Note: make sure your bootloader is unlocked;
Backup your data before doing anything.
This guide is working and tested .
*If anything goes wrong i will not be responsible*
*Its your choice*
Make sure to check clean all button on mi flash tool.
(Do not check clean all and lock)
Flash miui 12.0.3 stable china fastboot rom using mi flash tool in fastboot mode;
After rom flashed complete the setup;
,boot phone in fastboot and flash twrp
Next boot to twrp ,allow modification.
Next move orange fox recovery to phone storage while connected on pc .
Flash orange fox ,
now your phone will boot
Into orangefox
Move custom rom of ur choice to phone storage while connected on pc.
Next
,wipe delvik
, system ,
data
cache,
vendor.
Flash any custom rom of your choice .
If phone reboots to orangefox itself just got to wipe and choose format data and type yes;
The after wiping done,
Reboot
complete the setup
Download magisk 21.3 stable
Move to phone storage
Reboot to orangefox recovery
Flash magisk ;
Reboot
Install magisk manager if manager is not showing,
Now your will be rooted
,your done.
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Start fresh by flashing stock MIUI rom through fastboot and proceed from there
1 Boot once into MIUI and reboot into fastboot
2 fastboot boot twrp.img (from platform tools folder)
3 Flash custom rom like ArrowsOS with inject twrp option checked
4 Reboot recovery
5 Format Data by typing "yes"
6 Reboot to system
7 Done
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Use "fastboot boot TWRP.img" to temporarily boot TWRP.
You can install TWRP by using "Install to Ramdisk" inside TWRP and selecting TWRP.img
Cvenda said:
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Click to expand...
Click to collapse
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
pedrowood said:
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
Click to expand...
Click to collapse
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Cvenda said:
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Click to expand...
Click to collapse
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Milan-XDA said:
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Click to expand...
Click to collapse
reason for slots
Robert314 said:
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Click to expand...
Click to collapse
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
EDIT: after sideloading ArrowOS and booting TWRP using "fastboot boot twrp.img", I can access internal storage, so I uploaded twrp.img into /sdcard/Download folder, installed it into ramdisk, rebooted to Recovery and now successfully flashing CrDroid ROM that I uploaded to /sdcard/Download
Cvenda said:
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
Click to expand...
Click to collapse
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Robert314 said:
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Click to expand...
Click to collapse
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Cvenda said:
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Click to expand...
Click to collapse
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Robert314 said:
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Click to expand...
Click to collapse
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Cvenda said:
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Click to expand...
Click to collapse
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
dreamytom said:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Cvenda said:
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Click to expand...
Click to collapse
Go into TWRP and press wipe then format data (type yes).
regedit12345 said:
Go into TWRP and press wipe then format data (type yes).
Click to expand...
Click to collapse
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Cvenda said:
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Click to expand...
Click to collapse
Doesn't matter. Just select format data > yes > reboot to system
regedit12345 said:
Doesn't matter. Just select format data > yes > reboot to system
Click to expand...
Click to collapse
sooo what seemes to work for me now is, that I formated data, then flashed PE ROM from OTG and booted into it without any problems