Database Develop

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 7 Pro

Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6

Reserved for future.

Thank you for this!!

Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?

LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.

jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:

Can you turn TMobile to int'l with this ?

HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said

When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!

Take out the Chinese characters in the file name and then try

joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s

Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?

uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot

uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,

thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.

Added global and EU packages.

Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)

Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.

[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!

When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.

I think I messed up royally

Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?

Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH

Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?

newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com

Hmm, it didn't work. I get bootloops...

Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH

For Multidisabler just do a google search one for samsung devices will appear

Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.

Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH

Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!

newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.

SHRP Recovery bootloop after flashing a ROM (although rom is fine)

Hello,
As the title suggests, I've flashed a custom rom (EvolutionX to be exact), upon booting it up, mediatek Ims stops working, but that appears only on boot so it's not that big of a deal.
However, Upon rebooting into recovery (through system or via vol up+power) i get greeted by the SHRP logo but it powers off and on.
Fastboot mode works just fine, ROM works too, the recovery doesnt want to work though. I had the phone modded for 2 weeks and this is the first time this happened.
Any idea on i can fix it? I've already tried flashing the same recovery via fastboot but to no avail, i get an error saying:
fastboot: error: cannot load 'SHRP_v3.1_stable-Official_CD6-1630047089': Permission denied
That's weird, because my phone has an unlocked bootloader.
Any help would be greatly appreciated!

Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned

HaroldTech312 said:
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
Click to expand...
Click to collapse
i will try flashing stock xiaomi and then install a custom rom again

NewtonPL said:
i will try flashing stock xiaomi and then install a custom rom again
Click to expand...
Click to collapse
try it I can't guarantee you anything but if it comes back and the same thing happens it means that the rom is not compatible with your mobile and you will have to look for another one
If you still have doubts tell me that I can try to help you

the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now

NewtonPL said:
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
Click to expand...
Click to collapse
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.

Mineplayerminer said:
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Click to expand...
Click to collapse
what zip? this isnt about magisk mate.

NewtonPL said:
what zip? this isnt about magisk mate.
Click to expand...
Click to collapse
I mean the MIUI ROM in zip. But I figured it out, I unbricked mine by installing the MIUI from the SHRP.

Xiaomi Note 9 is still bootlooping even after installing stock firmware

Hello! Just created an account in this forum to seek help because this is driving me nuts.
I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.
So, I tried the following:
- I followed the guide in this forum for hard-bricked Note 9 phones (https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.
- I flashed stock firmware, but still no system.
- I flashed the MIUI version that the phone came with through fastboot, but still no system
- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)
- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.
- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.
I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.
Thank you.

Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data (you did first make a backup of your personal data right?)
Then phone should boot again.
I hope this helps. Good luck!

lebigmac said:
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data
I hope this helps. Good luck!
Click to expand...
Click to collapse
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system

bump

bump - really desperate about this matter

I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!

lebigmac said:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
Click to expand...
Click to collapse
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you!

Question Stuck in fastboot after trying to install PixelExperience :(

Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.

OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D

dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?

I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s

fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!

Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?

I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!

Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.

raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!

Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.

raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.