I was trying to return the phone to stock after using the CalyxOS beta, I used MSM tool and it worked fine, I booted into OxygenOS and was like "great, it worked, no issues!" yeahhh I spoke too soon
Obviously the version of OxygenOS installed by MSM tool is very old, so I went to update. It downloaded, prompted me to reboot, the phone restarts, I open it up annd "Update failed, please try again"
Nothing I do works, although interestingly when I unlocked the bootloader I was able to update fine. But relocking the bootloader bricked the phone and I had to use MSM tool again. Does anyone know how I fix this? I searched but couldn't find this issue anywhere, obviously people have had update-related issues before, but nothing to do with MSM tool
Edit: the phone is model LE2115 btw
which msm tool did you use?
Index of /list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R
Following this guide https://community.oneplus.com/thread/1541327
I reflashed with MSM tool, and without connecting to internet I sideloaded updates, I am able to update to 11.2.10.10, but it's everything after that will fail. It must be a problem with ColorOS. I'm going to connect to the internet and try a regular OTA update.
Still nope...
{
"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"
}
Maybe I just need to talk to OnePlus support..? I thought it was MSM being broken because I had never used it before, but now it looks like it's just the switch to ColorOS breaking things
I talked to OnePlus support, useless. They were just telling me to wait for a new update, but it will still have the same issue
Related
Hi guys.
Is there any possibility of rooting Xperia M2 Android 4.4.4 18.3.1.C.1.15? I can't seem to find anything available. Previous method doesn't work anymore. Updated to the version mentioned through PC Companion.
I am desperate!
Later Edit:
There are people who will encounter this issue as well. Fixed it by letting BOOTBUNDLE unchecked in FlashTool both when you flash 4.3 and 4.4.4 back then use RootKitXperia and EasyTool.
Now the phone is rooted with the latest update.
{
"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"
}
Yeah, it's an issue with the installation of 18.3.1.C.1.15 via PC Companion/Sony Bridge for Mac. The new bootbundle doesn't allow to flash anything via FlashTool, unless one reflash the old bootbundle as well (thus not excluding it. What a stupid setting). I never bothered to update the guide. I'll do it now using a link to your post.
Miche1asso said:
Yeah, it's an issue with the installation of 18.3.1.C.1.15 via PC Companion/Sony Bridge for Mac. The new bootbundle doesn't allow to flash anything via FlashTool, unless one reflash the old bootbundle as well (thus not excluding it. What a stupid setting). I never bothered to update the guide. I'll do it now using a link to your post.
Click to expand...
Click to collapse
First time I tried without the BOOTBUNDLE, imagined it would work like the last time, but encountered some weird errors. Started again and let BOOTBUNDLE unchecked and it worked normally.No error or whatsoever. :fingers-crossed:
Hi,Guys~
I can't get the bootloader unlock, Cause it keep saying like the picture shows.. Whatever fimware I use or official Unlock Device Tool(9.1.0.8-9.1.0.11) app. It can't be done. Including android P(16.1220.1909.194 &a lot of P version) to Q(17.1810.2005.153).
"An unkonw error occurs, which may be a network connection issue.please wait and try again later"
Actually network can surf totally no problem, but just can't unlock.I had try both of cyanogenmods unlock method can't work.
{
"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"
}
There is any way back to the older(older than 16.1220.1909.194) or the first fimware? I think maybe it's the fimware 16.1220.1909.194 newer than the unlock apps...I tried the ADB but cant wrrote the older fimware...
Sry for the image...looks like it can't show out by google cloud drive.
Plz help me guys.
Thx a lot.
same problem here. i tried the 1st firmware that came with it 2019 april .still same problem. this happened after i gave it service regarding a problem which is taking too much time to open gallery. they have reflashe the phone and gave to me with AndroidQ. i tried to unlock with the asus tool. it says network issue. then i downgraded to 16.1210.1904.75
and tried with no success. any help
Did you finally solved this problem?
I saw somewhere people saying to remove device pin before you try unlocking bootloader. I guess you can try that.
Anyone found a solution for the bootloader unlock?
Hi there
I'm having a serious problem with my sm-g532f, which went OFF forever after trying to flash a new ROM.
Here is what happen:
I rooted the phone in April of 2019, granted to use super user rights but the malfunction started in the midst of 2020, it started simulating back button clicks on its own. By that time I was used to flashing it with original and custom ROMS. But as I was not ok with its malfunction, I downloaded an original update which is of 2019, trying to overcome the problem i flashed it using Odin (as usual). Unfortunately, the download was interrupted by the USB cable, so the process failed. From that day it has never displayed anything.
it does not respond to charger connection nor power button press.
I tried to follow some advices from various sites from which they told me to flash it with SP Flash Tool using MTK USB Drivers. They said it would be detected but it wouldn't remain stable, they meant i would hear Windows reporting device connection and disconnection in less than 45 seconds. Yes, that happened and even now it does the same. They said the 'preloader' has been wiped, so their procedure told me it flash the preloader file first before all the rest of the files. I did it but the flashing tool asked for the 'authentication file', i searched it all around the Internet and found one with this name 'auth-sv5' in a ZIP file. But here is what the Flash Tool says back:
{
"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 don't know if there is any way do recover this device, Help please!!
Hi.
I cannot recover the OS. Msm tool runs 18 seconds and shows Sahara ....
Tried Global, EU, India versions
I have Win 11, Qualcomm drivers installed.
I will add that on the second computer with the same win 11 system in the device manager (ports and LPT) the Qualcomm device appears from time to time and disappears.
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"
}
Thread 'MSM cannot recognize your phone aka. Sahara Connection error? Check this.' https://forum.xda-developers.com/t/...a-sahara-connection-error-check-this.4308601/
Gotta look around. 2 posts from yours. This works. Then use correct variant of msm tool from https://onepluscommunityserver.com/list/Unbrick_Tools/
If the correct variant doesnt work, try the OP9 Pro - India MSM tool. Its the only one that has worked for many people with the OP9 5G Global/NA model.
mattie_49 said:
Thread 'MSM cannot recognize your phone aka. Sahara Connection error? Check this.' https://forum.xda-developers.com/t/...a-sahara-connection-error-check-this.4308601/
Gotta look around. 2 posts from yours. This works. Then use correct variant of msm tool from https://onepluscommunityserver.com/list/Unbrick_Tools/
Click to expand...
Click to collapse
It works.
I used MSm EU OP9P unfortunately didn't see the sim. Then the flash msm Global OP9 and it started without any problems.
If I check for an update it shows there's an update to android 13. I've tried several times to update and it always says there was a problem installing the update. I start the installation and then says it's paused. I resume and it says the installation will continue when the device isn't being used. I again hit resume and it says there was a problem. Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
{
"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"
}
Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
Rooted is the issue. Flash back the stock kernel or just flash 13 manually
You're trying to take an OTA while rooted and asking why it doesn't work? If you want to run a rooted phone, you have some learning to do before you brick your phone.
If root is the problem, it's not a big deal. Taking the OTA and then using Magisk to flash to the inactive slot has always been the easiest solution. The Oneplus never cared about root. Pixel 2 XL was my last pixel device I used but I always had a rom installed. So this is new to me.
Be careful...if/when you DO get updated and reboot into 13, make sure u flash the new bootloader to the other partition.