Question The current image(boot/recovery) have been destroyed! - OnePlus Nord 2T

I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help.
Edit: The fix for this is to flash the correct boot.img via BROM Mode via MTK Client.

need stock files for flashing oneplus nord 2t from mtk client​
can u provide all the files needed to unbrick my phone as it is stuck in boot image/recovery has been destroyed

The issue is solved. I gave to official service center and they flashed the firmware.

Hi I'm having the same issue as you, is there a way for me to solve this faster than the support ?

r-ichard said:
Hi I'm having the same issue as you, is there a way for me to solve this faster than the support ?
Click to expand...
Click to collapse
What did you do to brick the phone?

After flashing the boot with fastboot I locked flashing with :
`
Code:
fastboot flash lock
`

r-ichard said:
After flashing the boot with fastboot I locked flashing with :
`
Code:
fastboot flash lock
`
Click to expand...
Click to collapse
you flashed the patched_boot.img from magisk and locked your bootloader?

yes exactly

you should not lock your bootloader after flashing patched_boot.img

I solved this by flashing with mtk in brom mode boot.img on both boot_a and boot_b partition !

r-ichard said:
I solved this by flashing with mtk in brom mode boot.img on both boot_a and boot_b partition !
Click to expand...
Click to collapse
Could you please describe how you did this?
I've tried to achieve it according to this method using mtk client but can't get a connection to my Nord 2t.

delete post

delete post

rokkdroid said:
Could you please describe how you did this?
I've tried to achieve it according to this method using mtk client but can't get a connection to my Nord 2t.
Click to expand...
Click to collapse
MTK client method is patched unless you are on older version.

I made progress using mtk client but still got
Code:
.....Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Phone is detected but handshake fails.
MTK client method is patched unless you are on older version.
Click to expand...
Click to collapse
I don't understand this to be honest.

rokkdroid said:
I made progress using mtk client but still got
Code:
.....Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Phone is detected but handshake fails.
Click to expand...
Click to collapse
I also had handshake issue when windows driver issues were not set up right.
rokkdroid said:
I don't understand this to be honest.
Click to expand...
Click to collapse
There was a bug, that allowed unauthorized commands to be sent in "brom mode". Which mtkclient used.
Now, phones like Nord 2 and Nord 2T have had updates that "fix" this bug.
Meaning, unless you're an official repair shop with OnePlus blessed secret keys, you can't use most of mtkclient.
Such as, flashing partitions.

I see. So there is no other chance than going to a shop?

rokkdroid said:
I see. So there is no other chance than going to a shop?
Click to expand...
Click to collapse
Yes, till now there is no other way.

Thanks for the Info!

rokkdroid said:
I see. So there is no other chance than going to a shop?
Click to expand...
Click to collapse
I had a good discussion here, https://forum.xda-developers.com/t/bootloop-after-c10-update.4506117/
And looked around for several days.
Hopefully, either those keys leak out, or some new exploit gets found.
But for now yes. It means the corporate overlords screwed you over.
They never wanted you to be able to unbrick your own phone.
By accident it was possible anyway. And now they made sure it's not possible.
Spoiler: I assume that board meeting at OPPO HQ went something like this.
"Let them keep the tools to brick their phones. And make them pay to unbrick it!"
{
"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"
}
Except imagine him 20 years older, fat, and more Asian ^

Related

EDL Mode on Redmi Note 5 Pro

Youtube link for the complete process at the end
Step to get EDL on Redmi Note 5 Pro
1. Disassemble the phone
2. remove the battery Metal bracket
{
"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"
}
3. Remove Tape from here
4. EDL Pins are just below that
5. Short pins with twizer and insert USB
6. Qualcomm HS-USB QDLoader 9008 (Com7) detected on device manager (driver required)
7. On Mi flash tool tap refresh
Youtube link:
It recognizes usb, but flashing is not possible.
[email protected] said:
It recognizes usb, but flashing is not possible.
Click to expand...
Click to collapse
what error did you get ?
junioreinstein said:
what error did you get ?
Click to expand...
Click to collapse
It looks like an error due to anti-rollback.I will not buy XiaomiPhone.
yes is work...
hi
my phone is brick, there is no connected to my account on my phone, how can I use it again? Will this solution be good for me too?
sorry bad english
Is this working even with anti rollback brick?
Ra2rd said:
Is this working even with anti rollback brick?
Click to expand...
Click to collapse
You'll get PM on your Miui account. But try to flash 2 days after the deadline even if you dont have reply.
waiting for PM
juve60 said:
You'll get PM on your Miui account. But try to flash 2 days after the deadline even if you dont have reply.
waiting for PM
Click to expand...
Click to collapse
Ok thanks! So i'll just wait and cross my fingers :angel:
This method is not needed for anti roll back, it will automatically be detected as 9008 device in com port, no need to dismantle the phone at all !
all you need to do is wait for your account to be authorized after posting your account number in the forums and you will be able to flash !!
bluerichblue said:
This method is not needed for anti roll back, it will automatically be detected as 9008 device in com port, no need to dismantle the phone at all !
all you need to do is wait for your account to be authorized after posting your account number in the forums and you will be able to flash !!
Click to expand...
Click to collapse
Good morning friend, my phone is dead, I already published my ID in a Russian forum, but still do not give me any answer, you know where I got the message or instructions to revive my phone.
The port QDLoader 9008 appears to me but I can not do anything.
It will be that Xiaomi will send me a password for PM or what they will send.
Thank you for responding and greetings from Colombia
...
Flashing an old stock miui rom(not antirollback)
Hi. After I am confirmed to flash my phone by xiaomi. will I be able to flash an old rom(no anti rollback)?
Thanks
eanaranjo said:
Good morning friend, my phone is dead, I already published my ID in a Russian forum, but still do not give me any answer, you know where I got the message or instructions to revive my phone.
The port QDLoader 9008 appears to me but I can not do anything.
It will be that Xiaomi will send me a password for PM or what they will send.
Thank you for responding and greetings from Colombia
Click to expand...
Click to collapse
As long as you sent the account number before the finish date.
You can post here until 24 July, http://en.miui.com/thread-3254707-1-1.html you only need to post the number of the account and then wait a couple of days.
After you need to sign in to miflash too, so that it can verify your account if it tells you that your computer is bound then you can flash the phone !
The instructions will be sent to you in PM in the MIUI account, you must follow every little detail and it will work.
Do not worry if it shows some errors during flashing, DO NOT stop the process , it continues and gives you success message in the end !
Good Luck !!
Please help me
after unlocking my phone i just installed twrp and install custom rom miui 10 on redmi note 5 global and boom it was dead now i came to know that we have to take permission from the develpers and ive submitted my id to this post but today is 26 and i came to know right now after reading this forum
will i be able to have permission to flash because The deadline for collecting Mi ID was July 24th, 2018?
and if yes then how much time it would take?
cant even flash in edl mode
i cannot even flash my phone in edl mode.. it says .."only nop and sig tag can be received before authentication"
Hello,
Take a look to mi6 forum : https://forum.xda-developers.com/mi-6/help/firehose-t3802143?nocache=1
It might work .
If doesn't ask for auth flash last usable rom , unlock bootloader and flash with dummy.img antirbpass partition if you want to downgrade.
Before downgrade antirbpass partition must be cleared (erased).
AngelescuO said:
Hello,
Take a look to mi6 forum : https://forum.xda-developers.com/mi-6/help/firehose-t3802143?nocache=1
It might work .
If doesn't ask for auth flash last usable rom , unlock bootloader and flash with dummy.img antirbpass partition if you want to downgrade.
Before downgrade antirbpass partition must be cleared (erased).
Click to expand...
Click to collapse
did that work for u?
Deleted
Hello,
First of all even if phone is bricked and is in EDL mode EDL mode needs to be restarted using testpoint.
To be able to flash without xiaomi auth account you need in fastboot rom a non auth programmer.
programmer is prog_emmc_firehose_Sdm660_ddr.elf.
Non auth programmers have about 616KB 617KB size. If it's more it contains auth code and will ask for auth account if using latest mi flash tool.
Download last usable miui fastboot version ( version you have used before brick phone).
Download a old fastboot rom as an example 9.5.6.0 or 9.5.13.0 and get from it programmer file.
Overwrite auth programmer file from version you should flash with non auth programmer 9.5.13.0 or from any previous version.
Download miflash tool 2017.4.25.0 and install it.
Get miflashtool portable (latest) 2018.....
Copy programmer to latest miflash tool and test if programmer is compatible with phone and if sahara protocol is launched through COM port.
Restart EDL mode and test sahara http://en.miui.com/forum.php?mod=viewthread&tid=3576914&highlight=sahara+protocol
If protocol was launched Restart EDL mode and flash using 2017 version as soon as possible after restart of EDL mode.
My phone is not bricked but I have flashed in EDL mode via testpoint without xiaomi auth.
EDL mode restart is very important.
Some mi users has already tried this but they have errors about EDL com port comunication with sahara protocol.
Good luck

ONEPLUS 8T DEAD

My Oneplus 8T is in edl mode only. Cannot boot to rom, cannot boot to fastboot. Just black screen in edl mode. When using msm tool it showing error of "open serial device failed". Please help me
{
"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"
}
Have you tried holding Volume up and power until it reboots? That is how I got out of EDL mode.
For the error, have you tried different USB ports? I ended up having to use a USB 2 port on the back of my motherboard before it would work. But I got different errors then you.
Qnorsten said:
Have you tried holding Volume up and power until it reboots? That is how I got out of EDL mode.
For the error, have you tried different USB ports? I ended up having to use a USB 2 port on the back of my motherboard before it would work. But I got different errors then you.
Click to expand...
Click to collapse
I've try holding that combination. Still it boots back to edl mode
Tried both 3.0 and 2.0 same error "open serial device failed" and "automatic detection of DDR failed"
That looks like that your Phone is not listed correctly in Device Manager. Look in Device Manager on your PC whether your Phone is listed as QDLOADER 9008. If it is liested as QHUSB_BULK, then you need to update the Qualcomm driver
I am fairly certain the phone is okay but the drivers on the computer you're using are not.
Ayemnaim said:
My Oneplus 8T is in edl mode only. Cannot boot to rom, cannot boot to fastboot. Just black screen in edl mode. When using msm tool it showing error of "open serial device failed". Please help me
View attachment 5177023
Click to expand...
Click to collapse
Install these drivers on your Windows..It worked for me..
I'm having this same issue. I've tried all USB ports including 2.0 as people are recommending. I've installed the Qualcomm USB driver as well. It shows up as HS USB QDLoader 9008 but still I can't seem to get it working. I am trying to flash the global ROM on my sim unlocked T-Mobile OnePlus 7T
Sack206 said:
I'm having this same issue. I've tried all USB ports including 2.0 as people are recommending. I've installed the Qualcomm USB driver as well. It shows up as HS USB QDLoader 9008 but still I can't seem to get it working. I am trying to flash the global ROM on my sim unlocked T-Mobile OnePlus 7T
Click to expand...
Click to collapse
Wrong forum tho.
xocomaox said:
Wrong forum tho.
Click to expand...
Click to collapse
I was focused on the "open serial device failed" issue because that's the problem I'm stuck at. Sorry, nvm my post

Moto One Macro - Bricked Device

Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?
Open device manager and look for Qualcomm
if you see that your Device is in EDL Mode.
Try this tool
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.
KomitaMKD said:
sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.
Click to expand...
Click to collapse
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all
sd_shadow said:
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all
Click to expand...
Click to collapse
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...
KomitaMKD said:
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...
Click to expand...
Click to collapse
Blankflash only works with EDL Mode (black screen)
10 minutes later im still stuck on the Motorola - Powered by Android logo
So, how do I proceed now?
Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/
VD171 said:
Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/
Click to expand...
Click to collapse
Im not sure how to use this
Official Stock Rom by LOLINET: https://mirrors.lolinet.com/firmware/moto/lima/official
{
"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"
}
KomitaMKD said:
So, how do I proceed now?
Click to expand...
Click to collapse
You need to reboot to fastboot mode, unplug USB, and hold the volume button and power, till you see the fastboot screen.
You have
Code:
ro.carrier: reteu
sd_shadow said:
You have
Code:
ro.carrier: reteu
Click to expand...
Click to collapse
Okay that did the work now my phone is off - black after i pressed the buttons...
Now which one should i download? Should i use the Android 10 one or the 9 one you mentoined previously (if its the same). btw before i do anything i had android 9 running with the november patch
I tried that Android 10 and this is what i did.
Extracted Mediatek and the firmware in same folder, did the cmd thing from the xml through the spanish web site, ran the bat file and nothing happened.
Now ill be trying with the android 9 version
Okay guys im not able to successfully run the flashfile.bat
I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!
KomitaMKD said:
I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!
Click to expand...
Click to collapse
Nice job, my friend.
I would like to thank you all who spared some of your
VD171 said:
Nice job, my friend.
Click to expand...
Click to collapse
Thanks to you and @sd_shadow , I really appreciate your quick assistance
KomitaMKD said:
Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?
Click to expand...
Click to collapse
Hi @KomitaMKD this is vignesh , i am also using Moto One Macro device , Lastweek i have thought to flash my mobile due to some reason first time my device became brick... I am not ble to do anything its come startup failure ! Message .... I felt really bad ... Then almost i tried 8 hrs continuously for recovering my phone.. finally i found it. I recovered my mobile. Below i will give a link just go through it , that will help your mobile to become normal.
[RECOVER][UNBRICK][BLANKFLASH] How unbrick your bricked Motorola Moto One Macro
This script was made by Eufracio López (yehison). Thank you very much ! 1. First, you have to download required contents: Minimal ADB and Fastboot Tool: https://androidmtk.com/download-minimal-adb-and-fastboot-tool Motorola Device Manager...
forum.xda-developers.com

Nokia 1.4 TA-1322 Help

Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it
optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}
Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?
optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...
S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?
Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)
Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got
Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.

Question Need some help unbricking (solved)

I bricked my OP9 doing some stuff today. It will not turn on, access bootloader, or anything.
When I plug it into my computer, it makes a connecting sound, waits 10 seconds, then disconnect sound, then repeats the process.
I tried using MSM Tool with the tmobile one I found online (this is a tmo device), and when it makes the connect sound it does show up in MSM, but when I hit start it says downloading firehouse binary or something, then this happens... Any ideas?
{
"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 phone is not fully off? I usually fix the error in the first post by holding the power, volume up and down (keep holding sometimes upto 40 secs) until it reboots in bootloader then power off and try fashing again while holdin volume up and down only
If your device is a T-Mobile, did you use this MSM package?
LINK
Maybe check the instructions here ...
t-ryder said:
If your device is a T-Mobile, did you use this MSM package?
LINK
Maybe check the instructions here ...
Click to expand...
Click to collapse
Yes I have done all of that, same issues.
orangekid said:
Yes I have done all of that, same issues.
Click to expand...
Click to collapse
Did you use the original data cable or a good quality data cable (no eBay crap)? Did you try all USB ports on your PC? Cable and port is the same as you usually use for flashing devices or this device?
t-ryder said:
Did you use the original data cable or a good quality data cable (no eBay crap)? Did you try all USB ports on your PC? Cable and port is the same as you usually use for flashing devices or this device?
Click to expand...
Click to collapse
Yes I have literally done all of that. I think I may have figured out a solution using the indian OP9 Pro MSM and modifying the XML for settings.
This appears to be a known issue with very little recourse, hopeuflly this works.
ya the Indian OP9 Pro MSM worked, now just getting back to original firmware.
orangekid said:
ya the Indian OP9 Pro MSM worked, now just getting back to original firmware.
Click to expand...
Click to collapse
Hey! I have a similar problem "Sahara communication failed". At 18 seconds I have the same error. I see that MSM OP9PRO helped you, but I have the same problem with it. Please explain in as much detail as youcan
Use this guy's MSM Tool. Deselect sha256 and select Use Light Firehose. Make sure you have India selected.
It should get you back to stock Global OP9 ROM.
Restore your Global OnePlus 9 LE2115 via MSM
For those with model LE2115 having trouble restoring their device, follow these steps: https://easyupload.io/xgw3x5 NOTE: Link expires April 26, 2022 M1-1) Download the above file in this post and extract it to the same directory as your MSM...
forum.xda-developers.com
I will try it.
Param preload failed...
Pink Knight said:
Param preload failed...
Click to expand...
Click to collapse
Can you give a screenshot?

			
				
Urgent! Help with the MSM tool (stuck in Param preload)
Hi Please help! I have downloaded everything in this link: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 It contains "guacamole_21_O.07_190512_repack" and "L2 drivers" I have followed the mega unbrick guide...
forum.xda-developers.com
IT'S WORKED! JUST INSTALL THE LATEST QUALCOMM DRIVERS. I LOVE YOU GUYS!!!
Pink Knight said:
Urgent! Help with the MSM tool (stuck in Param preload)
Hi Please help! I have downloaded everything in this link: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 It contains "guacamole_21_O.07_190512_repack" and "L2 drivers" I have followed the mega unbrick guide...
forum.xda-developers.com
IT'S WORKED! JUST INSTALL THE LATEST QUALCOMM DRIVERS. I LOVE YOU GUYS!!!
Click to expand...
Click to collapse
Funny that is what I was about to recommend, qualcomm drivers and USB port. Awesome man so glad it worked for you.

Categories

Resources