Database Develop

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

Bootloop

Hello all, i unlocked the bootloader on the xiaomi mi A2 , and i was trying to follow this guide :https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475 to install the gmcam, but after the point 5. i just rebooted the phone from the recovery, just cause i wanted to try it, after that is stucked in android 8.1 animation, but i have access to the recovery (even if the tool shouldnt have installed it), but dunno what can i do from the recovery, and the device can go in fastboot mode but is not recognized by adb, what can i do?

What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

minnuss said:
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?

fuffy841 said:
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
Click to expand...
Click to collapse
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.

I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
---------- Post added at 06:16 PM ---------- Previous post was at 05:31 PM ----------
rt1279_isBITW said:
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
Click to expand...
Click to collapse
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option.

Daniesz said:
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
Click to expand...
Click to collapse
Nono i want to keep the bootloader unlocked, that's why I asked ! Thanks man.
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option
Click to expand...
Click to collapse
I used the same option, cause it didnt work with the other ones.. I didnt have any issue so far tho, and I dont know about hardware differences, but I dont think a bad flash can cause this kind of problem, not sure tho. Maybe now that everything is working try to flash again a stock rom.

Bootloop with no recovery or fastboot options

Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks

Did you flash anything?

Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.

VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?

jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com

jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.

Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything

Question Stuck in fastboot after trying to install PixelExperience :(

Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.

OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D

dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?

I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s

fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!

Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?

I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!

Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.

raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!

Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.

raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.