I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
aero_dreams said:
I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
Click to expand...
Click to collapse
Have you checked out this and tried this?
https://forum.xda-developers.com/oneplus-7-pro/how-to/sprint-msmdownloadtool-unbrick-t3989841/amp/
Sent from my OnePlus 7 Pro using Tapatalk
aero_dreams said:
I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
Click to expand...
Click to collapse
Gm1920 or gm1925? Pm sent.
hi....i'm having the same problem....everything was working until i flashed majick in twrp and then got stuck in fastboot......and nothing will work....thanks in advance.....i have an account but my google account was compromised and lost all credentials.......thanks again for finding a way to unlock the bootloader
Related
Hi all,
My one plus one bricked when updating to CM12s via OTA. Since then, I have tried everything, but I am stuck on the oneplus screen. I cannot get to recovery no matter what. Bootloader still works though
This is what I have tried
1. Flashed cm12s, cm11s via fastboot. Still didnt wake it up
2. Used the color OS+MSM8974 tool to flash color os, still stuck on the red oneplus logo
3. Used the color OS+MSM8974 tool to flash color os, then flashed cm11s, still stuck on the oneplus logo
4. Used the oneplus recovery tool, still stuck on the oneplus logo.
In all this scenarios, I cannot access recovery, I even flashed TWRP, and still cannot access recovery.
Bootloader is unlocked.
Of note, when using the MSM8974 tool, I get the following message when I check the logs:
userdata.img: FAILED
userdata_64G.img: FAILED
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
Click to expand...
Click to collapse
So i was changing roms, and when i did this i accidently flashed the wrong boot image. After that i boot into a green screen with a red and blue squares then a message following it "boot image verify fail, please update to the authorized images. I can boot into fastboot recovery but i have no access through adb, i can preform a few adb amd fastboot commands but cannot flash or access my phone. It also boots into Huawei eRecovery and will let me try to download the latest recovery but fails each time, no matter if its highspeed internet or hotspot i always get a download failed message, can anyone help me out? I miss my x5 already and have tried almost everything i can and have done research on.
My Redmi S2 somehow got stuck on Mi logo this morning. Everything is still stock and locked. I followed a guide somewhere to unlock bootloader through edl mode, seems like it worked (is says "unlocked" under Mi logo).
With BL unlocked, I tried flashing TWRP using fastboot. But I still can't boot into recovery, only Mi logo. Even stock recovery won't boot.
It seems flashing using Mi Flash Tool doesn't worked anymore , unless with auth. So I found another flash tool. Tried flashing Global/China rom with it(edl mode of course), all is well but "cache","cust","vendor","system","userdata", didn't finished flashing. But the tool says the whole process is completed and proceed to reboot the phone. Which still only showing "Mi Logo".
So I tried using fastboot command to flash those few files. First few time the process completed. But still nothing changes. However, when I try to flash using fastboot now, it just stuck at "erasing". Any file I tried to flash just got stuck here.
"fastboot boot recovery.img" also don't worked. Got the same result using another computer. Now I'm stuck. Would appreciate some advice and guide here.
JEDAlive said:
My Redmi S2 somehow got stuck on Mi logo this morning. Everything is still stock and locked. I followed a guide somewhere to unlock bootloader through edl mode, seems like it worked (is says "unlocked" under Mi logo).
With BL unlocked, I tried flashing TWRP using fastboot. But I still can't boot into recovery, only Mi logo. Even stock recovery won't boot.
It seems flashing using Mi Flash Tool doesn't worked anymore , unless with auth. So I found another flash tool. Tried flashing Global/China rom with it(edl mode of course), all is well but "cache","cust","vendor","system","userdata", didn't finished flashing. But the tool says the whole process is completed and proceed to reboot the phone. Which still only showing "Mi Logo".
So I tried using fastboot command to flash those few files. First few time the process completed. But still nothing changes. However, when I try to flash using fastboot now, it just stuck at "erasing". Any file I tried to flash just got stuck here.
"fastboot boot recovery.img" also don't worked. Got the same result using another computer. Now I'm stuck. Would appreciate some advice and guide here.
Click to expand...
Click to collapse
if your bootloader still unlocked..
try reinstalling twrp via fastboot and use the volume up button and power button to enter recovery
Even in the beginning, before flashing anything, it won't enter stock recovery. I already tried flashing twrp, flash succeed, but it won't enter recovery mode, or twrp. And now, I can't flash anything through fastboot. It just stuck at "erasing..."
In last working condition, my phone is the TMO branded device, converted to global 10.5.11 with Magisk and TWRP.
I decided to update to 10.5.12 via Local Upgrade, as I've done previously to update. The OOS update went fine but I encountered an issue when updating Magisk to 21.4. After attempting to install to inactive slot and reboot, my phone went into QualComm CrashDump mode. Attempting to boot into TWRP or the system resulted in being thrown back into CrashDump mode. I could still get to fastboot, so I booted TWRP from fastboot and was able to at least recover my device into a working state; albeit not how it should be working. I am currently on TMO ROM fresh from msm restore, 10.5.7.IN55CB, bootloader unlocked. Phone works, signal good, IMEI good, can receive texts, etc.
From that point on, no matter if I msm back to T-Mobile firmware, flash the Global fastboot ROM, factory reset, etc I'm getting an error I can't seem to find any hits on while searching.
"Unable to mount storage
E: Unable to open /system_root/system/apex
E: Unable to load apex images from system/apex"
I'm assuming I messed up my slot_b because prior to using the msm tool, if I tried to boot from slot_b it would send me to CrashDump mode while attempting to boot from slot_a directly after attempting slot_b would send me into stock recovery mode where I could do a factory reset and successfully boot into the system. After attempting a factory reset (and format data) via TWRP I then was being sent to CrashDump mode by trying to boot from either slot or trying to enter recovery mode. When first attempting to msm, holding vol+ and plugging device in would send phone to EDL mode where it would stay for a few seconds, then reboot into CrashDump Mode. I didn't think I was getting into EDL mode, but once it showed connected in the msm tool I quickly hit start and the restore process started.
While typing this, I tried to update magisk by installing to the inactive slot (which would be slot_b) and upon reboot I went straight to fastboot. I got the message included in the 2nd image attached.
Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!
Nathan.7118391 said:
Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!
Click to expand...
Click to collapse
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists
lordcheeto03 said:
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists
Click to expand...
Click to collapse
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!
Nathan.7118391 said:
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!
Click to expand...
Click to collapse
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?
lordcheeto03 said:
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?
Click to expand...
Click to collapse
OP said sparse magic invalid is fine and won't hurt anything. If you are having trouble booting the phone then I suggest you wipe data. That's what's I had to do in order for it to work. Though the first few times I did it I didn't wipe any data and it worked just fine. I think OP said you can modify the script if you know what you're doing. Happy modding!
Nathan.7118391 said:
If you are having trouble booting the phone then I suggest you wipe data.
Click to expand...
Click to collapse
When you say wipe data, do you mean how, like, when you use msm tool data gets wiped? Or maybe you mean how data gets wiped when you unlock bootloader? Perhaps you mean like the flashall.bat wipes data as well...
I'm almost certain it's slot_b, I just need to know how to repair slot_b
Did you ever figure this out? I have a list of problems that all started with the exact problem your having now here
i'm getting same error again and again, can you help me to troubleshoot this. ASAP
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Hold the power button till it turns off, volume down + power button to get to bootloader. Reflash stock boot.
ALWAYS fastboot boot first before actually flashing in case this happens
Make sure you're using the correct boot image to patch for your build number too
AphoticAffinity said:
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Click to expand...
Click to collapse
What version of Magisk did you use? You must use 24.0 or newer.
As @ctfrommn recommended, you can "live boot" the patched image instead of flashing it:
fastboot boot <patched boot image>
If this fails for whatever reason, it'll reboot with the stock boot image.