Develop Bugs

Flashed 9.5.6 Global ROM to China Note 5 AI, can't proceed through initial setup

Hello!
Today I finally received permission to unlock my bootloader, after waiting a long 15 days (360 hours). After solving some MiFlash Unlock issues, I finally unlocked my phone. I flashed TWRP and Magisk, and then afterwards I flashed Xiaomi.eu's stable whyred ROM, which worked (including camera sensors), but was terribly slow and clearly very unoptimized. For this reason, I decided to flash the leaked official Global ROM, 9.5.6 from Xiaomi. All was well, and I was presented with the initial set-up screen. After selecting my language (English [United Kingdom]), I was forced to select China as my region on the next page. Seconds after selecting it, my phone reboot and opened the system again, only to reboot within seconds. This process would probably repeat endlessly if I didn't have it in fastboot mode. I can still access TWRP recovery, and my phone still shows that it's unlocked on the boot screen. I've tried doing another clean wipe, and then installation of the global ROM with no success (same error occurs, even when I tried English (United States)).
I've tried to use the MiFlash tool (2017.4.25) but my device isn't detected when I click Refresh, and the fastboot mode displays "press any key to shutdown...". I've tried many different drivers as I thought it was a driver issue, but now I'm not sure.
Any suggestions? Thanks!

Flash with fastboot rom. Follow my thread

devcon69 said:
Flash with fastboot rom. Follow my thread
Click to expand...
Click to collapse
I tried that, same issue. Also tried with the new 9.5.11 global rom update.

FIrst Flash MIUI Nougat Rom
http://bigota.d.miui.com/V9.2.7.0.NEIMIEK/miui_WHYREDGlobal_V9.2.7.0.NEIMIEK_b6ab1f7b5b_7.1.zip
after flashing this Rom and setup complete then flash the leaked official Global ROM, 9.5.6. Otherwise you won't be able to pass the setup screen in latest Oreo Rom.

Trewyy said:
I tried that, same issue. Also tried with the new 9.5.11 global rom update.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.

devcon69 said:
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.
Click to expand...
Click to collapse
Ah thank you, I was flashing through recovery. With that being said, MiFlash doesn't detect my phone in fastboot, even if I can normally flash to it through fastboot if I were to open a terminal. Clicking "Refresh" in MiFlash Tool just disables fastboot. I realize its unrelated to your own tutorial, as its probably some fault on my computer. Thanks for your replies!

Plz help! How to revert partitions back to stock

I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hrvoje007 said:
I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
Click to expand...
Click to collapse
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me

nikoman1987 said:
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me
Click to expand...
Click to collapse
is there any other way than edl mode? Im not familiar with that metod

hrvoje007 said:
is there any other way than edl mode? Im not familiar with that metod
Click to expand...
Click to collapse
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!

nikoman1987 said:
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!
Click to expand...
Click to collapse
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again

hrvoje007 said:
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again
Click to expand...
Click to collapse
it will do the edl flash

I did edl flash but sensors stil not working at all. I really dont know what to do next

hrvoje007 said:
I did edl flash but sensors stil not working at all. I really dont know what to do next
Click to expand...
Click to collapse
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?

SubwayChamp said:
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?
Click to expand...
Click to collapse
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode

hrvoje007 said:
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode
Click to expand...
Click to collapse
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)

SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
i will try that in next couple of days, and i will let you know if problem is solved thank you, i can give any information you guys ask im not very experienced in this stuff like you but i appreciate your help.

SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
I tried these steps but still didnt solve the issue, do you have any other sugestions?

hrvoje007 said:
I tried these steps but still didnt solve the issue, do you have any other sugestions?
Click to expand...
Click to collapse
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?

SubwayChamp said:
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?
Click to expand...
Click to collapse
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.

hrvoje007 said:
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.
Click to expand...
Click to collapse
It seems that the GSI that you used before is the culprit.
Some things you can try:
- Try other firmware versions, probably a downgrade like v10.0.3.0
- Try to erasing first in fastboot as many as partitions you can in both slot before to flash through MiFlash tool. I know that MiFlash tool overwite them but just to be sure.
- Probably you might try flashing with other tool like QPST or other qualcomm flasher tool, I´m not sure which actually works for our device.
- If you resized some partitions to flash a GSI you have to restore them to the exact size that was before.

I was watching youtube tutorial from iboy editz and something i probably did wrong, but it doesnt matter anymore because i can lieve with this isuse it just iritating and always deleting everything from the phone and instaling again takes to much of my time, but anyways thank you for help

Trying To Recover Data - recovery and system partitions wont boot

Hey all,​
Question: Can anyone offer any help recovering my data partition?
Problem: system and recovery partitions wont boot.
Why: I failed to fix a boot loop problem I was having. I tried to restore my system and recovery partition that I had backed up through TWRP. The restore failed and now I cannot boot into recovery mode (let alone system).
What I've Tried:
1. booting into a TWRP (booting TWRP image via fastboot off my desktop PC). FAILED
downloading boot.img completes ok.
I get an error when it tries to boot the image: "FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)"
my guess is my recovery partition system is broken.
Thoughts:
Can I flash my bootloader and recovery partitions from a stock ROM without interfering with my data?
can i do a partial flash (not a flashall.bat)? How?
I am not super familair with doing a partial flash. I have only ever ran flashall.bat on Google's stock ROMs.
Question: Does anyone have any ideas?
If you can help me out, I would love to buy you a 6 pack of beer!

I am recreating this thread in its proper place.
@XDHx86
XDHx86 said:
Can you boot to bootloader? Does fastboot detect your device?
Yes, fastboot detects the device. It lists my Pixel 3 XL a fastboot device and the Pixel 3 XL properly executes commands like fastboot reboot bootloader.
Other things I just tried:
I also tested the connection and I was also able to fastboot a TWRP.img (sailfish version--Pixel 1) for my Pixel 1 just now. So everything looks good on my desktop end. However, when I boot a TWRP.img (crosshatch version--Pixel 3) on the Pixel 3, the boot fails and gives the error i posted above.
I also tried three different TWRP.img revisions (including the oldest and newest revisions for the Pixel 3XL). None of the twrp.img images will load.

Here is the fastboot command and error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.

pritchfest said:
Here is the fastboot command and error.
View attachment 5254701
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.
Click to expand...
Click to collapse
I used this script when I ran into a similar issue before, you can use it to flash TWRP or sovle your bootloop.

@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.

pritchfest said:
@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.
Click to expand...
Click to collapse
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.

XDHx86 said:
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.
Click to expand...
Click to collapse
oh, no. As in, your suggestion might have worked but I didn't get to try it because I really needed to have my phone working for work. I didn't get to try your suggestion because in my haste I opted to just flash-all.bat and forefit the opportunity to recover my data.
After trying to flash several partitions separately and failing, including just the bootloader--and later just the recovery partition--, I kept getting the same error I wrote about above.

So you still get this error?? Even though you used the script, you still get the error?
Are you sure you have latest adb tools and device driver?
What about setting active partition first?
Try fastboot set_active a
Then fastboot boot twrp.img

As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
I can confirm I had the latest ADB setup.
I did not try your fastboot set_active a command before trying to fastboot into twerp.img. I can't say this wouldn't have worked.
The only other information I have is that on the fast boot screen, The triangle with an exclamation mark in it was colored red. Normally this triangle is a yellow color.
Hope that helps.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.

XDHx86 said:
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.
Click to expand...
Click to collapse
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.

pritchfest said:
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.
Click to expand...
Click to collapse
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.

Y
XDHx86 said:
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.
Click to expand...
Click to collapse
Yeah, it could be worse :/

Cant get back to factory

i am on PE and been on Linage and then Derp but for 2 weeks now ive tried to go back to factory and for the life of me nothing works ive tried the All N One Tool and MSM Tool and nothing i constantly end up back where i started.
Ive downloaded the latest os firmware from oneplus All N One Tool Downloads the firmware extrasts it the pops up a error saying flash all .bat is missing so dead end there.
could someone lead me in the right direction or explain to me if im doing something wrong.... thanks

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

this will be my last onepluse thatr for sure going back to Pixel 4 XL didnt have no issues going back to stock this is crazy

I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.

When u r stuck on pink TMobile screen, force reboot to bootloader by holding vol+, vol-, & power buttons for 10 sec. Once you see phone rebooting, let go of power button only to enter bootloader mode. Then type "fastboot reboot fastboot" on PC while USBC cable is plugged into phone. This will kick phone into fastbootD mode. Then fastboot flash all stock rom files.
When wifi and 4g not working, u did not enter fastbootD mode, so system did not flash right

SageChrono said:
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
Click to expand...
Click to collapse
Above

HueyT said:
Above
Click to expand...
Click to collapse
i was just coming to edit my post. rookie mistake - i forgot to overwrite adb/fastboot tools everytime i moved the OS files to my adb folder lol... somehow i forgot a bunch of times
phone is booting up without that userspace error, so i may be back in good shape!
edit 2.0: all booted up with wifi/camera working again

well gonna try again for the 4th time this time im gonna use a different computer and see if that works..... UUUGGGG

well the 4th time fail to restore back to stock OOS.. its gotta be something im doing bc i even used a different computer. but gonna keep looking around for another route.

msmdownloaderTool says this (Device Not Match Image) the device seems to time out and disconnects from MSMDownloaderTool every time. any advice i have the global version 7T 1905

HueyT said:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??

scoot0073 said:
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

using the " All in One Tool "
Flashing is not allowed for Critical Partitions
is this normal error when flashing back to stock OOS ? when the flashing starts it says this for the first 4 or 5 flashing parts then it stats flashing as described in OP. then it reboots out of fastboot and boots to stock recovery then it finishes the flashing . then at the end it says to press any key to continue and the phone reboots and hangs at the screen that lets me know the bootloader is unlock screen. i flashed both a \b partitions and still does the same thing. its like the boot image is not flashing or im missing something else in the OP to get back to stock OOS.
anyone can help me please ?

"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts

HueyT said:
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
Click to expand...
Click to collapse
ok that command worked it successfully Flashed all partitions and when it it it finished it said to press any key to continue .... i did and it rebooted into stock recovery and finished the flashing . then it reboots to the Your Bootloader is unlocked warning and stays there . so i went into recovery and factory reset everything and still hangs at the bootloder unlocked warningthat was all on Slot b so i was like maybe i need to flash both Slots so i switched to slot a active and repeated the whole process above and still nothing hangs again at the bootloader is unlocked warning... ggggrrrrr
what gives..... this is all done using the All in One Tool ... i know im getting close to getting it back to Stock OOS as i made progress with your help.
i then downloaded the factory image from OnePlus site but that was a no go as the zip had only something called Payload which wouldn't flash ..
anymore knowledge u might can share and thank you very much for your help

Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot

HueyT said:
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
Click to expand...
Click to collapse
that did it im back to all stock oos thank you so much buddy couldn't have doe it without your knowledge. crazy that none of the tools didn't work mine must have been a rare odd ball that i had to flash everything manually.
again thank you.

Question Poco f3 Error: Sending modem_ab

good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.

Same problem. Don't try more things because you will brick your phone like mine.

Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance

As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz

Thanks you so much I will try that

and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots

Still the Same Error unfortunatelly

nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?

No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?

Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock

Still the Same Error . Can This be because of a Driver or a hardware issue?

i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.

It doesnt seem to make any difference to the error whether i flash it via cmd or miflash

nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...

I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you

You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.

Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.

I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot

nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse

okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?