Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Edit 3: Okay so new issue, everything is all good TWRP is installed phone is rooted, but im trying to update to the latest MIUI 10 version (on MIUI 9 atm) and i can't install it? It downloads fine but it wont install? Do i have to flash the update file since it wont update through the updater?
JasonBjorn said:
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Click to expand...
Click to collapse
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Robbo.5000 said:
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Click to expand...
Click to collapse
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
JasonBjorn said:
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
Click to expand...
Click to collapse
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Robbo.5000 said:
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Click to expand...
Click to collapse
well heres the weird thing, i bought the EU version of the phone, which i know is supposed to be the 9t pro, but not only did the site call it the K20 pro, but in the settings its model number is also the K20 pro. I got everything working fine.
Related
Hi All,
I hope I am asking in the right area and forgive me if I havent.
I have a Mi Mix 128gb running Niui Global 8.0 Stable 8.0.7.0.0 MAHCNDI which I believe is a vendor rom? I try to go into updates as I see on the MIUI website there is a version 8.0.10.0. and I would like to update to that.
-I tried the update button where it takes a few seconds saying checking and comes back with no updates available.
-I then tried the choose update package in the update app and chose the rom I moved onto the phone (not in a folder as specified) and it says getting info and then comes back 'couldnt verify update package'.
-I then tried the reboot to recovery mode and named the rom 'update.zip' as specified and all I got when I tried to enter reboot to recovery mode from the actual update app was a black screen wth a phone and a cord plugged in and a website address, no graphical selection tool where I was able to select using volume up and down etc.
I had read somewhere it could be due to the fact that when the vendor flashed the global rom they may have left the bootloader unlocked and that is why the phone isnt finding the update or running it from the file on the phone.
Does this make any sense or am I just missing everything and doing something wrong?
If it is the unlocked can I lock it again to so that I am able to update.
I did try the other thread on verifying the bootloader and how to type in the command to relock it but I wasnt able to use the ADB as I am not all together familiar on how to use it.
If anyone out there can give me a hand I would be forever grateful and I would ask that if you can help that it be as detailed as possible as I need all the help I can get
Thanks so much in advance
Dis you get your Mi Mix from a vendor who loaded Gapps for you? I think that 8.0.7.0.0 is a vendor ROM, not the CN Stable or EU Stable ROM.
I suggest you find the ROM guideline thread here and update to the CN or EU Stable ROM
Best
J
It is definitely a vendor rom. To begin with, this phone has no Official Global rom yet. It states it is a global rom but in the Rom name it contains the letter CN, which identifies the rom as the chinese rom. Therefor yes, it is a vendor rom.
I don't have the phone yet so take my advice with a grain of salt, but i'm pretty sure that an unlocked bootloader does not interfere with installing roms/getting ota updates etc. Sorry, with an unlocked bootloader you can't get OTA updates. But you've got a vendor rom so you wouldn't be able to get one in the first place even with a locked bootloader.
I think that if your bootloader is really unlocked, the fastest and easiest way to flash the newest rom would be by using the MiFlash program from Xiaomi. Here's a guide for that:
http://en.miui.com/thread-307744-1-1.html
(Method 3, Step 2)
Let me know if you managed to flash it.
Blackphantom said:
It is definitely a vendor rom. To begin with, this phone has no Official Global rom yet. It states it is a global rom but in the Rom name it contains the letter CN, which identifies the rom as the chinese rom. Therefor yes, it is a vendor rom.
I don't have the phone yet so take my advice with a grain of salt, but i'm pretty sure that an unlocked bootloader does not interfere with installing roms/getting ota updates etc. Sorry, with an unlocked bootloader you can't get OTA updates. But you've got a vendor rom so you wouldn't be able to get one in the first place even with a locked bootloader.
I think that if your bootloader is really unlocked, the fastest and easiest way to flash the newest rom would be by using the MiFlash program from Xiaomi. Here's a guide for that:
http://en.miui.com/thread-307744-1-1.html
(Method 3, Step 2)
Let me know if you managed to flash it.
Click to expand...
Click to collapse
Thanks very much for help. I managed to flash it to the official Chinese rom but now things like the proximity sensor isnt working and a few other things. Still cant get the google movies to download or play either so I will try your guide....will let you know how it goes.
Thanks again!
imapfsr said:
Thanks very much for help. I managed to flash it to the official Chinese rom but now things like the proximity sensor isnt working and a few other things. Still cant get the google movies to download or play either so I will try your guide....will let you know how it goes.
Thanks again!
Click to expand...
Click to collapse
If by "google movies" you're referring to movies downloaded from google play, then make sure you disable download manager in the Miui appstore settings. It connects to a chinese proxy and therefor is buggy and really slow.
Thanks to everyone on this forum as I now have a EU rom running on my mix and everything is working. I can download and watch movies from Google Play, I can watch and download Netflix and Google Contacts (the app not sync) now installs and works. Now this is the phone I wanted it to be and I am thrilled.
Thanks again
imapfsr said:
Thanks to everyone on this forum as I now have a EU rom running on my mix and everything is working. I can download and watch movies from Google Play, I can watch and download Netflix and Google Contacts (the app not sync) now installs and works. Now this is the phone I wanted it to be and I am thrilled.
Thanks again
Click to expand...
Click to collapse
Glad to hear that it worked out for you.
imapfsr said:
Thanks to everyone on this forum as I now have a EU rom running on my mix and everything is working. I can download and watch movies from Google Play, I can watch and download Netflix and Google Contacts (the app not sync) now installs and works. Now this is the phone I wanted it to be and I am thrilled.
Thanks again
Click to expand...
Click to collapse
I would like to know how did you do it, because I need to do the same
TIA
stevm said:
I would like to know how did you do it, because I need to do the same
TIA
Click to expand...
Click to collapse
Just follow the directions here
http://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960
And you shouldn't have any issues.
Did your phone come with the Global 8.0 Stable 8.0.7.0.0 MAHCNDI s that is what mine started with and the only issue was that I had to use the ADL mode to get the phone to recognize and take the TWRP so I could get the EU rom working. Been using it for a few days now and no issues whatsoever. Good luck!
OK so I finally got my dev unlock after one week. I immediately installed TWRP and was in awe as I did my first TWRP 64 bit backup and watch in amazment as I backed up everything. Having a global version is obviously a big mistake if I want to use roms though as I tried XOSP, and Pixel PI and had nothing but errors. I then tried to use the Chinese TWRP version as advised by someone and reflash the rom. This amounted in a big mistake as everytime as it would only reboot to TWRP.
Next I noticed that all files in the File Manager were garbled (encrypted?) so I started panicing and trying different TWRP's and wipes as per different instructions. In the end my stupid ass is stuck with fastboot lock out; no recovery and now I can't even flash recovery from fastboot ?!?
Next : I tried MIflash wont take the latest global rom files extracted to folder (missing flash all .bat) nor Mimanger wants me to log in. Nor latest Miflash.
Have I softbricked ? I feel really dumb right now. Though to be fair to me, the forums are really convelioted with many half way attempts and 3 different varients with people experimenting swapping this for that. I just wanted to get this phone to have the XDA full experience I have had for years and now I think I really messed up ...
HELPP !!!! If you are able to thanks ..
used cepheus_global_images_9.6.27_20190627.0000.00_9.0_global ; this worked... ran the .bat file : Old MiFlash doesn't work, newer ones have windows library stop errors (Java, .net missing ...probably ? ) None of the tools out seemed to work and downloads I assume were only updates (but there wasn't clear indication of this. It wasn't until I found that particular build that I could find the flash_all.bat in root. I guess that is the best option despite all these pretty tools..
Hello there!
I have a Xiaomi Redmi Note 10 Pro, and yesterday I made the grave mistake of hitting that "update" button. What used to be a close to perfect smartphone turned into a pile of trash with about 10 GREAT functions REMOVED. Instead they added 10 new phone-destroying functions which make this phone close to unusable for me at the moment.
That being said, I obviosuly want to downgrade my phone to the version it came with apparently is V12.0.15.0.RKFMIXM (Global). Is it safe to downgrade to this version from the version I'm on now 12.5.1? Even if it's not safe, could you please tell me how likely it is that my phone ends up bricked?
Thanks! I hope this works!
If you have updated it using Official Updater app, then there is a high risk of bricking your phone. It depends on ARB index.
Try flashing Fastboot ROM using Mi Flash tool. If it's not safe to downgrade, Mi Flash will prevent you from flashing it.
Yes, I used the official updater app in settings.
OK so you're there's a chance? Because this 12.5.1 version is complete and utter ****. I REALLY want to downgrade. Please help me out here, this version is SO BAD that I have to buy a new phone if the downgrade doesn't work.
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Have you tried updating to the latest 12.5.3?
I'm stuck on this crappy 12.5.1 as well but I don't want to unlock anything or wait for the update... So my question is can I use the Mi Tool without unlocking the bootloader?
Spudsicles said:
Have you tried updating to the latest 12.5.3?
I'm stuck on this crappy 12.5.1 as well but I don't want to unlock anything or wait for the update... So my question is can I use the Mi Tool without unlocking the bootloader?
Click to expand...
Click to collapse
I have not, because I have not received the update on my device yet. However I don't expect them to fix these god-awful "updates" in the next update, hence I'd rather just downgrade, which I'll probably try to do tomorrow. 12.0.15.0 was absolutely perfect (the version it came with) and I KNEW I shouldn't have updated ((
OSX.Nobody said:
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Click to expand...
Click to collapse
I have another Xiaomi I don't care about which ALSO has the horrible 12.5.1. Since I don't care about this device I'll try downgrading it tomorrow, and if it works I'll do it again with my Redmi Note 10 Pro
I'm really curious about those features you said they remove and why miui 12.5 is so bad, I was just about to update!
Hi! I would also like to know what is wrong with 12.5.1 on the redmi note 10 pro. Mine has 12.0.6 (Russian version I think), and I'm trying my best to figure out how to update it to 12.5.1, but I've read many comments saying it is trash.
Can you tell me your biggest complains? What I don't like about my current version is the 10 seconds always on display, and not being able to select an icon pack for the system launcher. Do you have those features on 12.5.1?
My friend, the uptade to 12.5 did not ad or remove any aplications or funtions.
My be you collect them from any place.
Spudsicles said:
So my question is can I use the Mi Tool without unlocking the bootloader?
Click to expand...
Click to collapse
No, installing a Fastboot ROM requires your device to have an unlocked bootloader.
Little Snevil said:
I'm really curious about those features you said they remove and why miui 12.5 is so bad, I was just about to update!
Click to expand...
Click to collapse
DON'T update! Here's a list of the worst ones:
1) They REMOVED the progress bar from the media players on the lock screen, so now you CAN'T scroll through music and audio directly from the lock screen.
2) The screen automatically shuts off after 5 seconds after receiving a notification and there's NO WAY to increase it, making it impossible to read more than 1 notification.
3) When swiping/deleting the last notification the notification screen automatically closes REGARDLESS if you had a media player or something else you wanted to check out, so now they're forcing you to open it up again every time you close the last notification.
4) The notification screen now has a non-removable "No notifications" text, as if I needed someone to TELL me that. Completely unnecessary and ugly as crap.
Note that these are NOT bugs, but features, so if you update you're never getting these features back.
I use a smartphone when I work and this crap only makes things harder for me! Downgrading today!
EDIT: These are ONLY my main issues, the whole update is super buggy and laggy ALL AROUND, so be prepared to add aother 100 bugs and glitches to that list!
Are you sure that you had that options before, at last 2 one impossible....
OSX.Nobody said:
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Click to expand...
Click to collapse
1 extremely quick question, which one of these is the correct one?
Thank you!
artembazhanov said:
1 extremely quick question, which one of these is the correct one?
Thank you!
Click to expand...
Click to collapse
The recovery rom is for TWRP, fastboot rom is of course fastboot flashing.
artembazhanov said:
1 extremely quick question, which one of these is the correct one?
Thank you!
Click to expand...
Click to collapse
Recovery ROM
OSX.Nobody said:
Recovery ROM
Click to expand...
Click to collapse
I downloaded the fastboot load because it's easier to install. Great news, I downgraded my Redmi Note 7 without issue and it's working flawlessly! Then I tried unlocking my Note 10 Pro, but it's telling me to wait 168 hours. Can I use it during that time? Because I kind of need to.
Thanks!
artembazhanov said:
I downloaded the fastboot load because it's easier to install.
Click to expand...
Click to collapse
I thought you were asking about the method that described in the link I shared, which needs Recovery ROM. If you have unlocked bootloader, you have plenty of possibility.
artembazhanov said:
Can I use it during that time?
Click to expand...
Click to collapse
Yes you can. But don't touch any options in Developer settings related to unlocking procedure. Specially do NOT logout Mi Account.
If you are going to unlock, you should try MIUI EU ROM first, It might solve your problem.
OSX.Nobody said:
I thought you were asking about the method that described in the link I shared, which needs Recovery ROM. If you have unlocked bootloader, you have plenty of possibility.
Yes you can. But don't touch any options in Developer settings related to unlocking procedure. Specially do NOT logout Mi Account.
If you are going to unlock, you should try MIUI EU ROM first, It might solve your problem.
Click to expand...
Click to collapse
Definitely won't be messing with developer mode any more this week, and yeah, I'm not logging out either. Thanks!
I'm waiting a week before trying anything else. According to xda-developers you have to wait if you want to unlock.
artembazhanov said:
I'm waiting a week before trying anything else. According to xda-developers you have to wait if you want to unlock.
Click to expand...
Click to collapse
Sorry I mean after unlocking your bootloader, you should try EU ROM first (before flashing official ROM).
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.
Removed
EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.
Removed
Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.
Removed
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.
Removed
EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.
Removed
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.
Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.
Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
I did the same mistake thinking it would work like it would on A12 and ended up sending it in to oneplus to reflash.
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
unsafe8989 said:
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
Click to expand...
Click to collapse
yes full ne2215. quite sad knowing we don't even have proper access to the tools to recover our own phones yet. luckily i kept my op8 for a situation like this.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
you are sol. i already told you guys that you'll brick your phone if you use magisk method when updating os versions.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
If you did unroot completely you can try to boot into EDL mode, in doing so I managed to flip the boot slot and get mine to boot when I was stuck in crashdump mode.
I updated to C.20 yesterday. The process is to unroot completely with image restore, reboot, then let the the update fully install and reboot. You will update fine but be unrooted. Then you boot a patched boot from bootloader and root directly from Magisk.
Do not forget the reboot after uninstalling Magisk before updating.
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
ltw5ki said:
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
Click to expand...
Click to collapse
I'm genuinely not sure how to flip the slot on purpose, it happened to me while I was trying the button combination for EDL mode. I believe you have hold all three buttons (Power, Vol Up&Down) until it restarts, it should vibrate but be a black screen and you can plug the USB in from there to see a port 9008 on the PC. This is very generalized but there are more details all around the forum here.
I will say I believe when it flipped, it booted and I saw the oneplus screen for a split second, the screen sort of glitched, and it immediately rebooted from black screen back to bootloader. I think the switch occurred then.
Also is that from a powered off state or is it possible to do with the phone being on?
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Quantumrabbit said:
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Click to expand...
Click to collapse
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Prant said:
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Click to expand...
Click to collapse
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Prant said:
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Click to expand...
Click to collapse
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
your jumping around probably screwed up some partition size. I did not restart for the c20 ota and have no issues.
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Appreciate your guys input, I'll make sure to be extra cautious! Phone comes in today, fingers crossed I successfully update to C20 and root! Lol.
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
One last question, do you remove all your modules first reboot then unroot and reboot?
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
Technically that's on you. I gave a warning that you will brick if you don't fully unroot for c19.
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
I posted the c20 boots and how to flip the boot so go try it out.