HI all,
I had a MIUI 12.5.5 Stable and decided to install custom ROM.
I have unlocked the bootloader, waited 7 days. Then installed TWRP, flashed Crdroid 12 ROM and it had a lot of errors on the installation log- but I can see it tried to install to drive A. I have now found out there are 2 partitions on this device (A and B). In TWRP I tried to reboot to another partition but am now stuck at the fastboot mode. Holding Power, Power + Down, Power + up + down keys just trigger the device to go back into fastboot mode. Can anyone provide some advice about my next options.
Benzened said:
HI all,
I had a MIUI 12.5.5 Stable and decided to install custom ROM.
I have unlocked the bootloader, waited 7 days. Then installed TWRP, flashed Crdroid 12 ROM and it had a lot of errors on the installation log- but I can see it tried to install to drive A. I have now found out there are 2 partitions on this device (A and B). In TWRP I tried to reboot to another partition but am now stuck at the fastboot mode. Holding Power, Power + Down, Power + up + down keys just trigger the device to go back into fastboot mode. Can anyone provide some advice about my next options.
Click to expand...
Click to collapse
1/flash the rom which corresponds to the firmware for the Crdroid rom
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
select CLEAN ALL
2/flash TRWP
3/Format data(write yes)
4/reboot Twrp
5/flash Cdroid rom according to the instructions of the OP.
My advice would be to go back to MIUI using MiFlash. Don't lock the bootloader, use the clean all options only. Once you and your device were all set because errors like these would get you into a panic mode. In that situation, you'll do several mistakes which might lead you to do some mistakes while flashing. Therefore, go back to MIUi, take some days and then try flashing stable custom ROMs first. My advice would be to go with the Pixel experience.
Cheers and don't stop trying new things just because they don't work out.
Related
Hi guys,
I just recently bought a Z2 Force EU model (XT1789-06) and thought i better get it unlocked and rooted a.s.a.p.
The first order of work was to boot it up and perform an update to the latest updates available (November 2018, IIRC).
Following the update and after making sure there weren't any more updates, i proceeded to unlock the bootloader using the official Motorola method and it was successful.
I then copied over SuperSU-v2.82.zip to storage and downloaded twrp-3.2.3-2-nash.img to my PC.
I followed this guide in order to run TWRP and root: https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669
After installing SuperSU and rebooting the phone, the Motorola logo was displayed and stayed there for a while. I remembered the verbose logs after installing SuperSU syaing that first boot could take a long time.
I didn't risk rushing anything so i left the phone and planned on picking up where i left off the next day. It has now been 14 hours since the phone rebooted and it is still stuck at the Motorola logo.
I have tried to power it down by holding the power key but that does not work. I could only force it to react by holding down vol down + pwr button, then doing the same again to enter the bootloader.
I then tried to do a factory reset by performing the following:
vol down + pwr button > select recovery mode > hold pwr 2 seconds then vol up > Wipe data/factory reset > reboot
I am now back to a stuck boot procedure at the Motorola logo I did some more reading and found many threads explaining the procedure and what to look out for.
It seems like my safest bet now is to avoid SuperSU and install Magisk instead. However, before I attempt to root again, I would like to have the phone boot up normally again.
Would a kind sould please point me in the right direction of a guide that can help me out of this mess?
Please note, I am already using the latest software update version.
EDIT: Software is 8.0.0/OPXS27.109-34-17
fastboot --set-active=other
fastboot reboot
Take the update again then flash magisk after rebooting from the update.
What happens? You are swapping slots back to a working bootable slot, then updating to the latest update to fix the broken slot. Once it is fixed, follow the rooting procedure and flash magisk 16.7 or higher in TWRP and reboot. (Be sure to fastboot boot TWRP and not flash)
Hey, so i have been using this phone for almost 10 months now . i unlocked the bootloader almost within a month inorder to flash stable miui global roms since ota updates were taking longer time. Now i have been on stock miui rom for a while and i get ota updates normally. Now i want to flash a custom rom so i pressed volume down key + power button and every time it reboots normally instead of boooting into fastboot mode.
Things i tried
1. power button + volume down key.(Reboots normally)
2. Tried to boot into fastboot by using adb commands but when i typed adb devices, my device dint show up in the list of devices
If anyone has faced or know anything about this please help!
any fix for this? I was on 10.3 xiaomi.eu global stable and bootloop after updating to 10.4 xiaomi.eu, any hints will be appreciated
Are you able to enter recovery?
Same problem here...it stucked when I used a dark theme...bootloop with 3 choices 1)reboot, 2) wipe datra and 3) connect with mi assistant. First choice always goes to the 3 options, second choice never selected because of the consequences andd third choice I connect the phone but mi pc suite doesn't connect with it, only the Pc connects. Any help out there?
RamonXick said:
any fix for this? I was on 10.3 xiaomi.eu global stable and bootloop after updating to 10.4 xiaomi.eu, any hints will be appreciated
Click to expand...
Click to collapse
I had the same problem and i fixed this way:
1) extract the ROM fastboot you had before, downloaded from en.miui;
2) connect your device to PC in fastboot mode;
3) go to the extracted ROM and select only batch files;
4) double click on flash_all.bat, if you want to wipe all your device leaving bootloader unlocked, or flash_all_except_data.bat if you want wipe all exept data with boot loader unlocked, or flash_all_lock.bat if you want to wipe all with bootloader locked.
I tried everything...I wiped all data...but the problem that was putting my hpone always in recovery mode 3.0 was that the volume up button is always pressed....so power and volume up, always recovery mode 3.0
So after installing with mi assistant 3.0 chinese version(most of the times I didn't know what I pressed) I installed global stable 10.4.2.0 and after making the phone the rebooting I was pressing volume down so it flashed the rom and opoened the phone.
Now when I try to charge it I have to press the down volume cause otherwise it enters recovery mode 3.0 (because I suppose connecting the cable with mi 6 acts like power button)
I will try to open the phone and see if it is broken volume up or software problem.
in my case phone back to twrp after stay bootloop for like 15 minutes, stuck in V10.3.1.0 even today
RamonXick said:
in my case phone back to twrp after stay bootloop for like 15 minutes, stuck in V10.3.1.0 even today
Click to expand...
Click to collapse
Time for you to move to EU MIUI 11
It's already out
Hey
I installed the recent upgrade to my OP 5T and now the phone is not getting switched on, only the 1+ logo appears on pressing the power button and soon after it gets switched off.
I have tried the 'Volume Up + Power' button combination and fastloader screen appears, i tried to enter recovery mode but it just gets switched off after the 1+ logo when i select recovery mode.
OP5T_Unbrick_tool_dumpling ... not working:
The battery is getting charged normally and this is an android upgrade issue. I am a newbie, any help would be appreciated.
Thanks
A possibility could be that you tried to do stock update local method through twrp or custom recovery... That's similar to what happened on mine when I did that on the first beta 10 update. If so I flashed latest stock recovery through the fastboot menu by plugging into computer and using ADB fastboot command "fastboot flash recovery" minus brackets and dragged the recovery over and pressed enter.
It appears to do it as the update launched some sort of boot script but can't be carried out without stock recovery leading to a sort of boot loop.
Also I found while trying to fix this if I updated from a ROM where it didn't have treble support or wiped the vendor (I did when panicking lol). I had to firstly install the stock ROM that introduced treble then install the beta 10 update.
Sorry if that was all pointless or irellivent but hope you get ur problem fixed soon.
Hey everyone. I'm a novice at this, but I've gotten tired of Xiamoi's updates and decided to try Pixel Experience I downloaded the latest version of TWRP and flashed it per the instructions on the website. I know that unless I boot straight into it, it'll be overwritten by the stock recovery, but that doesn't seem to be possible. Both power + volume up, and adb fastboot reboot recovery just take me into a boot loop until I hard reset. And then of course, the stock recovery is back.
I tried Orange Fox, and various other versions of TWRP, and the same thing happened. This phone really does not want to boot into a custom recovery.
This has been a difficult question to google as everyone just gives obvious solutions like "reboot straight into recovery!!" I'm hoping someone else has experience with this.
Alice! said:
Hey everyone. I'm a novice at this, but I've gotten tired of Xiamoi's updates and decided to try Pixel Experience I downloaded the latest version of TWRP and flashed it per the instructions on the website. I know that unless I boot straight into it, it'll be overwritten by the stock recovery, but that doesn't seem to be possible. Both power + volume up, and adb fastboot reboot recovery just take me into a boot loop until I hard reset. And then of course, the stock recovery is back.
I tried Orange Fox, and various other versions of TWRP, and the same thing happened. This phone really does not want to boot into a custom recovery.
This has been a difficult question to google as everyone just gives obvious solutions like "reboot straight into recovery!!" I'm hoping someone else has experience with this.
Click to expand...
Click to collapse
If you install PE successfully it won't overwrite your current recovery. As far as I know only stock MIUI removes custom recovery when it boots into system.
To boot into TWRP with the phone off press and hold volume up + power button. When the Redmi logo appears release only the power button (keep volume up pressed). When the TWRP logo appears you can release the volume up button.
Ignore the root part if you don't want it.
Compass.
Compass Linux said:
If you install PE successfully it won't overwrite your current recovery. As far as I know only stock MIUI removes custom recovery when it boots into system.
The video mentions using the button combo if you're on MIUI 12. Press and hold volume up + power button. When the Redmi logo appears release only the power button (keep volume up pressed). When the TWRP logo appears you can release the volume up button.
Ignore the root part if you don't want it.
Compass.
Click to expand...
Click to collapse
I don't have PE yet, I'm still on stock MIUI. I'd like to switch to PE but I can't get into TWRP or any other custom recovery.
Also I have tried this several times-- as stated in the post, volume up + power just sends me into a bootloop, and the next time I restart, MIUI is able to remove the custom recovery.
Alice! said:
I don't have PE yet, I'm still on stock MIUI. I'd like to switch to PE but I can't get into TWRP or any other custom recovery.
Also I have tried this several times-- as stated in the post, volume up + power just sends me into a bootloop, and the next time I restart, MIUI is able to remove the custom recovery.
Click to expand...
Click to collapse
Watch the video.
It covers both MIUI 12.0.x and MIUI 12.5.x.
Compass.
Compass Linux said:
Watch the video.
It covers both MIUI 12.0.x and MIUI 12.5.x.
Compass.
Click to expand...
Click to collapse
Sorry, I mistook your post for the same couple suggestions I'd been given, and was way too quick to write it off. Using the downloads in the video description worked like a charm. Thank you so much!