Related
Anyone solved this problem?I cannot flash via fastboot,its not detecting my phoneblue led on but ~waiting fo device~
EDIT : solved. Somehow new windows 10 update messed driver signature so you need to enable it again in terms to use flash tool and reinstall flashtool fastbood drivers again.
Hello All,
Recently I have run into a few issues with my Umidigi F1 rebooting automatically and resulting in a Bootloop, which required me to re-flash the stock rom. There was however a few issues:
1) SPFlash Tool was unable to detect my device until I completely formatted all partitions of the Phone
2) I flashed a older version and tried to use OTA updates to return to my previous state however my Phone apparently has UMIDIGI One Max release keys, instead of UMIDIGI F1, meaning the update would result in error 7.
Since I didn't wan't to format the Phone a 2nd time to go directly to the Latest Update instead I did the following steps:
1) Downloaded the Latest SPFlash Update RAR from the UMIDIGI Website.
2) Rebooted into Fastboot
3) Connected Phone and Opened SPFlash Tool
4) Extract .RAR update
5) In SPFlash load the Android_Scatter.txt, this will list all partitions and the file that needs to be flashed.
6) Open CMD
7) Use "fastboot flash xx yy", where xx is the partition name in SPFlash, and yy is the File location in SPFlashtool.
8) Repeat step 7 for each partition. You can also flash a custom recovery using this method.
NOTE: If you use this update method you may have a stock android logo at boot.
Hopefully this helps others who are unable to use SPFlash Tool, or OTA.
Also could anyone help me resolve the release key issues which prevent me from using OTA Updates?
There's a method on Magisk to let you to revert boot and apply OTA, and install root again.
This method applied to most Moto phones.
1. Check for update. Settings >>> System >>> update.
2. If you found a new version available, go to Magisk and "uninstall" and revert to original boot.
3. Install OTA system update. DO NOT REBOOT!
4. Go back to Magisk and install on "unused partition". Reboot when finished
If there's an error "unable to revert", you need to get ROM matched the build number, and get the boot.img, copy the boot to the phone and let Magisk "install and patch". This method will give an original boot to revert, and run step 2 again.
If the method above didn't work, you need to do the following.
1. Assume you have original boot and updated boot. Reboot in fastbootd (only for models shipped with Android Q, R, S) or bootloader (shipped with Android P or earlier)
Code:
fastboot reboot fastboot
or
Code:
adb reboot fastboot
2. From there, you can flash original boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot into command window, and press enter.
Reboot when finished
3. Install OTA, and hopefully you have updated boot with matched build number. When OTA installation finished, copy updated boot to the phone and patch it with Magisk, and copy back to host computer, and reboot.
4. Once the phone finished post update, reboot to fastbootd
Code:
adb reboot fastboot
, and flash patched boot.
Done
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
noobtoob said:
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
Click to expand...
Click to collapse
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing.
gullzway said:
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing
Click to expand...
Click to collapse
Well, fastest method for me was:
1. Boot to twrp>backup data. Copy backup off phone.
2. Update phone from LMSA.
3. Follow previous root guide to patch the boot.img (extract from LMSA folder on computer).
4. Fastboot flash the patched boot image.
5. Boot to twrp>copy backup to twrp folder on device>restore data.
You don't have to setup your phone for any of this.
Edit: Obviously you have to setup your phone to install magisk and patch the boot.img. I mean minimal, like skipping all the account .
First let me say that I'm sorry about how this is formatted but I'm very frustrated with Oneplus right now. My troubles began when KB2005_11.C.16 downloaded. I could not take the OTA to save my life and it seems that the download disappeared before I had any opportunity to pull it off the phone. The only thing I could think of to do at this point was search the internet or unroot and try it. My searches turned up nothing useful and mostly forum posts from 2020 and 2021 but were unrelated (obviously). Unroot time it is. The phone updated with no problem but root was gone. Tried to boot a recovery through fastboot with no luck. The command rebooted the phone but hung on "Fastboot Mode". Tried other .img files just for grins and "fastboot boot" just doesn't work for me anymore. I updated the SDK Platform Tools, Xiaomi ADB bootloader interface drivers to no avail. ADB, Fastboot, and FastbootD all seem to function. Just not as I need them to. This is what I've done to rule out operator error.
Phone is Oneplus 8T (KB2005)
Restored phone from MSM to version 11.0.7.9.KB05AA (Obtained personally from Oneplus support)
Setup Wifi and only enough to check for OS updates.
Unlocked bootloader. Accidentally. All I really wanted to do was enable USB debugging. Nevertheless, it was done.
Checked for updates. Update to 11.0.11.11.KB05AA shows up.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume.
Installing Security update...
Restart now button appears
I click Restart now
System update available 11.0.13.13.KB05AA. Tapped on notification.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing Security update...
Restart now button appears
I click Restart now
System update available
New version:KB2005_11.C.16_1160_202204222257
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
At this point OxygenOS is on Android 12
System update available
New version: KB2005_11.C.20_1200_202205262304
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
Finally Phone is up to date
Unlocked bootoader and Developer options survived all updates
ADB reboot bootloader rebooted phone to bootloader (as expected)
fastboot reboot fastboot reboot phone to FastbootD mode (as expected)
fastboot boot anyimage.img just freezes the device with a black screen. Booting into a custom recovery this is the only way I know to pull boot.img from the device.
Untill then or until a new way becomes known to me, I'm unable to root my phone.
You should have rooted when you got to C.16. Because that's a full installation zip, you can take the payload.bin from it and use payload dumper to extract the boot image and patch the file with Magisk.
Then you could have followed the process to keep root with an incremental update.
Or, you could have rooted when you were on OOS 11 using TWRP, then kept root at each update.
These are explained in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
Fair enough. It does sound easy when you put it that way but here is what part of my complaint is about ...
i just reflashed with msm, unlocked bootloader, and rooted with magisk. Tested root with ADB shell, su
Checked updates again and updating failed, clicked "try again" and it failed again. This time after I clicked try again it shows that it is now trying to install C.16 so away we go ...
Oh wait. Fastboot boot doesn't boot any of my recoveries or boot.img files. I need a working custom recovery to extract a useable boot.img from my phone. Where can I find a recovery that works with C.16+?
Before you yell at me, I noticed that I left off the step of installing magisk to the other partition after the OTA. In fact, I didn't even try that yet but I have been here before and it didn't work. This time, however, it did work and I now have a rooted C.16 ready to update to C.20. I should say thank you but that doesn't sound like enough. Thank you, BillGoss. Sometimes just asking for help is enough.
My initial complaint was a bit clouded. I am reminded now trying to update to C.20, the truth of what happened. The C.20 incremental dropped and I tried to take it but it just kept resulting in "Couldn't update. Installation problem". It was because of this that I decided to unroot and try it. It did update but now I couldn't fastboot boot anyimg.img. I had no recovery.img or boot.img to further my cause. Then I went ballistic. I couldn't find an .Ota folder anywhere on my device. That just made matters worse.
I did discovery at this point that there is no longer a local update option on the update page. but there is an .apk developed by Oneplus themselves that installs a local update app.
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
It's clearly stated in BillGoss guide, how to install OTA and keep root.
You can pull your image through msm tool readback mode load msm tool press f8 it brings up a sub menu where you pick what you want to pull them you input oneplus all lowercase as the password on main screen press readback button then put phone into edl mode it will pull the img files out into your c:\ drive
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I can zip my copy and pm you a drive link later
BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word
scottlam1 said:
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word
Click to expand...
Click to collapse
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
Ok you don't need the drive link then
BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone
scottlam1 said:
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone
Click to expand...
Click to collapse
No, I didn't make that mistake.
@scottlam1
Apart from struggling to get my PC to connect properly in EDL mode, once it did connect the readback process gave me the boot image. Woo hoo!
I made the mistake of asking for both boot_a and boot_b. But readback only produces files with <partition name>.img and, therefore, I was left with only one boot.img file (the second one).
But this means we can now get a stock boot image without needing a full OTA zip.
Thanks so much for sharing this method to pull partitions from the phone without needing root.
Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
Use the incremental update from oxygen updater apk and get OPLocalUpdate_For_Android12.apk it is a standalone app for local installs that they took out of the normal update in oos12 in magisk you restore images once update is installed don't restart go to magisk and install to inactive slot then you can restart if you had twrp or orange fox in 11 you had to manually restore stock recovery or the update would fail but as of now there is no twrp for a12 available so you don't have to worry about that yet
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
[email protected] said:
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
Click to expand...
Click to collapse
Search online I find it there 2
I'm searching for boot.img of EU version. Could you please share where you found yours?
Method confirmed to work for OnePlus 9 EU (LE2113) and OnePlus 9 Global (LE2115) - Enjoy!
Update rooted C.47 to C.61:
Open magisk, click 'Uninstall magisk'
Reboot
Updated via standard system update to C.61 . (At first it failed at 99% for me, but on second try it completed successfully). Alternatively: try the Oxygen updater to download the C.61 OTA incremental update.
Reboot
Easy way to root C.61:
Download the patched boot.img:
EU (LE2113 - Europe) from Mega
or Global (LE2115) from GDrive or Mega
Place the downloaded boot file in the same folder as your adb.
Open a terminal or command prompt in that folder and execute: "adb reboot bootloader"
Execute "fastboot boot .\C.61_boot_magisk_patched-25100_Bvj5U.img" to temporarily boot the patched boot file.
Download & install Magisk 25.1.
Open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
DIY way:
All files here on a Mega folder if it helps you guys save time
Download C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater give the same download).
Use Payload dumper to extract the stock boot.img and copy it to your phone.
Download and install Magisk 25.1 on your phone, use 'Select and Patch a File' to patch the stock boot.img which creates magisk_patched-25100_4vi6c.img
Copy this file to your desktop and run the following commands to boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
After reboot, open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
(Optional) Way to extract your current boot file from a rooted phone:
Ensure you're rooted
Execute "adb reboot bootloader" on your pc
To check the current active boot partition execute "fastboot getvar all" on your pc and look for "(bootloader) current-slot:a" meaning you'll be using boot_a.img later on or "(bootloader) current-slot:b" for boot_b.img
Execute the following commands on your pc:
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/Download/boot_a.img
dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot_b.img
exit
adb pull /sdcard/Download/boot_a.img boot_a.img
adb pull /sdcard/Download/boot_b.img boot_b.img
Whichever boot partition was active in step 3 is the one you want
xHalt said:
Same here. I can find boot.img for the OnePlus 9 Pro (EU) but not for the OnePlus 9 (EU).
I tried the payload dumper on the incremental update (instructions do tell you it doesn't work on incremental .zip, only on full .zip). I got the boot.img out of it and was able to patch with Magisk 25.1, but when booting it's not rooted yet.
All files here on a Mega folder if it helps you guys save time :
My phone: OnePlus 9 EU - LE2113
Issue I had: Couldn't update to C.61
I was on C.47, rooted with Magisk 25.1. Tried to update through the system pop-up as well as through the Oxygen Update to update to C.61. It kept failing at 21%.
Steps I took to update:
Uninstalled magisk
Updated via standard system update failed at 99%.
I retried with the Oxygen updater and now it succeeded to 100%
Rebooted
Issue: now I'm no longer rooted.
Steps I took to root again:
Downloaded C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater gave the same download).
Used Payload dumper to extract the stock boot.img and copied it to my phone.
Installed Magisk 25.1 on my phone, used 'Select and Patch a File' to patch the stock boot.img which created magisk_patched-25100_4vi6c.img
Copied this file to my desktop and ran the following commands to try and boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
termporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
It takes a LONG time to boot, but eventually it does boot correctly.
Issue: however, Magisk is NOT installed and I'm not rooted yet.
I also tried to install TWRP recovery but keep getting the Qualcomm Crashdump Mode.
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the TWRP recovery: "fastboot boot .\twrp-3.6.2_11-0-lemonadep.img" in terminal
Issue: Qualcomm Crashdump Mode pops up and is stuck there
Anyone able to figure the last step out?
Appreciated!
Click to expand...
Click to collapse
i am in a similar situation. my OP 9 (EU) is (still) on the c47 build with the latest magisk. I never updated to c48 but have now decided to give c61 a try. But iam not able to install the OTA, inbuild system is crashing @ 35%, even with the local install method and the loaded update from the oxygen updater, its still crashing. Today i uninstall magisk, flash the c47 stock boot.img and vendor_boot.img but it still crashing. After some research I tried to reset the phone. Device is now fully wiped, only the bootloader is unlocked. But i still got this crashes What did you do to install the update ? my next try is to use the MSN tool from this forum, but i'm afraid to brick my device.
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
MrMagic said:
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
Click to expand...
Click to collapse
I spent a few hours trying to solve the problem. no chance. I ended up using the msm tool. after that it was possible to update from C37 to C48 and finally to C61.
I just found this in the OP9 Root topic:
Root OnePlus 9
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll...
forum.xda-developers.com
Apparently you can use the boot.img from the C.61 OP9 Pro build on the regular OP9.
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Try the updated instructions above. Can confirm it works now.
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Daeril said:
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
Click to expand...
Click to collapse
Amazing, @Daeril ! Thank you. It works.
Updated the instructions for everyone.
MrMagic said:
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Click to expand...
Click to collapse
I updated from C.47 and only had to reboot.
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Please see the updated instructions above and let me know if it works for you.
xHalt said:
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
Click to expand...
Click to collapse
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
MrMagic said:
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
Click to expand...
Click to collapse
Only way is sadly with data loss/reset afaik.
xHalt said:
Please see the updated instructions above and let me know if it works for you.
Click to expand...
Click to collapse
working!!
thanks mate