Hello,
I'm probably not posting this in the right section, nor the way it should be posted. This is my first post, and I'm sorry if this is the case.
I'll try to provide as much information as I can concerning my problem.
I have an OP7 (GM1900) that was rooted with TWRP recovery and magisk. I upgraded to OOS 10.0.3 through normal system upgrade. As I have done this many times before, I figured it wouldn't be much different. Upgrade done, everything's working but I lost the root and magisk as expected. Went back to fastboot mode, tried to boot to a temporary TWRP image, which failed (only showing fastboot logo in center of the screen). I googled, and ended up flashing both boot_a and boot_b (big mistake I know...)
Now, I'm stuck in a fastboot loop, with no access to recovery whatsoever. Nevertheless, I can still use fastboot and adb to execute command.
I figured I should download a global ROM and flash it again? I'm not sure which one to download since I didn't take note of the build beforehand and have access to nothing right now.
Is there no way to factory reset through fastboot in any way?
Thanks in advance
Update:
I made it worse by trying to flash a ROM I found on internet and totally bricked it to Qualcomm crash dump screen.
NEvertheless, everything is now solved using the MSM tool that can be found here:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Hopefully, this will help someone with the same problem
This is MSM tool "Hydrogen" Version...
There is msm unbrick tool for OxygenOS (European & International firmware, android 9 & 10)
https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
daitalos said:
This is MSM tool "Hydrogen" Version...
There is msm unbrick tool for OxygenOS (European & International firmware, android 9 & 10)
https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Thanks a lot ! I'll definitely download this one just in case, it could save the time going back to OOS with a local upgrade.
I was trying to install OOS 10.3.2 but it didnt really work as expected so it did boot to the fastboot.
I can't boot in to the recovery because thats not working, OS either because I did wipe Data/System before I did flash OOS10.
I was trying in powershell ADB devices, it did find my OP6. But when I do : Fastboot boot twrp.img it says Failed to load/authenticate boot image: Load Error
Fastboot flash twrp doesnt work either.
Can someone help me out ?
Ghost123NL said:
I was trying to install OOS 10.3.2 but it didnt really work as expected so it did boot to the fastboot.
I can't boot in to the recovery because thats not working, OS either because I did wipe Data/System before I did flash OOS10.
I was trying in powershell ADB devices, it did find my OP6. But when I do : Fastboot boot twrp.img it says Failed to load/authenticate boot image: Load Error
Fastboot flash twrp doesnt work either.
Can someone help me out ?
Click to expand...
Click to collapse
If you search there is a version than can be flashed from fastboot / ADB.
Otherwise I'd look at wiping the device using the MSM tool and flashing back to 9.0 (only version that consistently works for me).
Amos91 said:
If you search there is a version than can be flashed from fastboot / ADB.
Otherwise I'd look at wiping the device using the MSM tool and flashing back to 9.0 (only version that consistently works for me).
Click to expand...
Click to collapse
Do you have a link or something I downloaded MSM tool but when I hit start it says "Waiting for devices"
Which twrp is it ?
I tryed twrp-3.2.1-0-enchilada.img
Ghost123NL said:
Do you have a link or something I downloaded MSM tool but when I hit start it says "Waiting for devices"
Which twrp is it ?
I tryed twrp-3.2.1-0-enchilada.img
Click to expand...
Click to collapse
With msm tool did you follow all the instructions? Windows 10 in test mode installing the Qualcomm drivers etc?
Amos91 said:
With msm tool did you follow all the instructions? Windows 10 in test mode installing the Qualcomm drivers etc?
Click to expand...
Click to collapse
Got it working by reinstalling the qualcomm drivers.
But the windows 10 test mode keeps failing however at the end the MSM did work.
Im gona unlock the bootloader in the next hour.
Let's see if fasboot twrp will work this time.
Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.
p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?
VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.
Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.
Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Fuwlz said:
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Click to expand...
Click to collapse
Hello, did you follow the instructions here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3954325/
?
Yes, MSM tools just doesn't work
Me too, I can't start this EDL mode, it just goes straight to fastboot.
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
WookieTookie said:
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
Click to expand...
Click to collapse
Hi,
Just experiencing the same. I would like some help pls !
Tried LineageOS. Not stable enough on OP7 so I want to go back to OOS.
Got OnePlus 7 - 1903 model EU, so I believe it's GM57BA that I have to deal with.
Tried fastboot methods, not successful. I followed this post. Tested this on linux.
Encountered "Flashing is not allowed for Critical Partitions" even though I got :
Code:
❯ fastboot flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
❯ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Device was stuck during boot (left it about an hour to try, nothing happened).
At some point I faced Qualcomm Crashdump Mode Screen.
Now I think the only option is to go for MSM method but not available for linux, so I switched on windows.
Instructions on this post seem pretty clear but when I plug the phone on PC, device is not recognized, don't know why I can't install phone driver properly (but probably not important at this stage).
Qualcom drivers are installed but I can't get my phone to boot on "EDL mode" ?
vol - and vol + while shutting down/powering on the device, plugged/unplugged to PC (tried few combos).
So device is not recognized and I can't run MSM Enum.
I have probably missed something... if anyone could give a hint on how to do that, I would greatly appreciate it.
Ok so I finally found a way to solve my issue.
Followed instructions from this video.
Basically I had to disable driver signature enforcement on my pc. This allowed me to properly boot on EDL and detect the device using MSM.
Hope this will help