Related
So yesterday at school, I logged on to the WIFI network, signed in from chrome browser using my login credentials , few seconds later phone frooze totally.
I have pulled the battery several times, charged the phone for a lot of hours. Gave me nothing
Download mode, seems stuck at the small logo "download mode" it won't go any future.
Hard reset, dosen't progress either. When I hit "Yes" it keeps stuck at "Life's Good LG Logo"
Recover mode, my pc won't recognize the usb driver, it keeps getting "unknown driver" (Phone is otherwise dead? How to solve the USB issue without a boot-able phone) "Perhaps LG's own tool, could recover the phone, if I could solve the driver issue, maybe a manuel .sis file to install the driver?
Phone behaviour keeps staying at boot logo "Life's Good LG" No LG, Life isnt so good.
Solutions are welcome, I will probably call and use my warrenty. Because I had not installed root, messed with bulildprop, anything at all. First phone I ever used totally stock, and then this happens.
The fact it's turning on and the PC is seeing that it is connected is good. My first G3 was completely hardbricked (my fault) Just keep trying different return to stock methods.
Sent from my LG-D855 using Tapatalk
leomd333 said:
The fact it's turning on and the PC is seeing that it is connected is good. My first G3 was completely hardbricked (my fault) Just keep trying different return to stock methods.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply
I have tried almost anything. There's only two stock options for 'back2stock' "recovery, & download mode" neither of them work. My pc won't regonize the usb-driver in recovery mode, so I can't use any firmware flash tools. I have installed driver and so forth.
Seems useless to continue to same two stock options, when they seem to be "corrupt or somehow damaged"
But a big thanks for you optimisme
moblaw said:
Thanks for your reply
I have tried almost anything. There's only two stock options for 'back2stock' "recovery, & download mode" neither of them work. My pc won't regonize the usb-driver in recovery mode, so I can't use any firmware flash tools. I have installed driver and so forth.
Seems useless to continue to same two stock options, when they seem to be "corrupt or somehow damaged"
But a big thanks for you optimisme
Click to expand...
Click to collapse
That is very weird situation... Just can't understand why your phone bricked after logged in WiFi,...
I reckon u should take it back for warranty.
mustang2012 said:
That is very weird situation... Just can't understand why your phone bricked after logged in WiFi,...
I reckon u should take it back for warranty.
Click to expand...
Click to collapse
You are right. My understanding of this issue is that, it's hardware related. I will use my warrenty, and see what happens from there
moblaw said:
You are right. My understanding of this issue is that, it's hardware related. I will use my warrenty, and see what happens from there
Click to expand...
Click to collapse
So I got my phone back from the "repair shop" today. It said on the repair note "Mainboard replaced"
Glad I diden't use to much time trying to flash/whatever. Thanks for your support and reply.
If you experience similar issues as mention in this thread by me. Chances are you'll need to use your warrenty or replace your 'mainboard'
Peace out..
So today I tried flashing android 5.0 on my T-mobile LG G3 D851. I put it into download mode, started the flash and waited. My LG flash tool then crashed and closed. My phone was %6 through the installation however and was just left frozen after it crashed. I tried every way possible to restart it and get out of the screen while keeping it plugged in, but I couldn't...so I took out the battery and put it back in. Now nothing is turning on, I can't put it in download mode and the charging LED doesn't light up, etc. It's completely bricked....what do I do? I've already tried taking out the battery and waiting and plugging in the cord and then battery. Please help! I can't afford the insurance or another phone...
EDIT: Also the battery does have charge...although I don't know how long it will last.
EDIT 2: I just realized this flash was for the 855 variant..not 851. Does this mean that I am just screwed?
It means that you got expensive brick.
You cant enter into download mode or recovery?
Probably only help is jtag. Find someone who can do that.
Sounds like someone has learned a very expensive lesson! Have you tried to factory reset it?
Yeah JTAG is all you got if no download mode
Sent from my LG-D855 using XDA Free mobile app
joshmccoyy said:
So today I tried flashing android 5.0 on my T-mobile LG G3 D851. I put it into download mode, started the flash and waited. My LG flash tool then crashed and closed. My phone was %6 through the installation however and was just left frozen after it crashed. I tried every way possible to restart it and get out of the screen while keeping it plugged in, but I couldn't...so I took out the battery and put it back in. Now nothing is turning on, I can't put it in download mode and the charging LED doesn't light up, etc. It's completely bricked....what do I do? I've already tried taking out the battery and waiting and plugging in the cord and then battery. Please help! I can't afford the insurance or another phone...
EDIT: Also the battery does have charge...although I don't know how long it will last.
EDIT 2: I just realized this flash was for the 855 variant..not 851. Does this mean that I am just screwed?
Click to expand...
Click to collapse
Did you manage to unbrick your G3?
Neurom707 said:
Yeah JTAG is all you got if no download mode
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily. This might work in his situation
http://forum.xda-developers.com/showthread.php?t=2582142
itsbighead said:
Not necessarily. This might work in his situation
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
The linked solution works only if the device shows some signs of life - atleast a boot logo.
i have a D851 that a friend bricked. She tried upgrading to Lollipop and flashed the AT&T baseband on this TMobile version. The result is a hard bricked device which does not even seem to power on. Shows no signs of life, except when connected to a windows pc. It shows up as 'LG Androidnet USB modem' in the device manager. No boot logo, recovery, or download mode. Fortunately she has IMEI and twrp backups for this phone (boot, efs1, efs2, radio, rpm, tz). I did some research on JTag solutions. Unfortunately, none of the boxes support the D851, yet.
Any ideas on how to recover this device would be greatly appreciated.
majesticpark said:
The linked solution works only if the device shows some signs of life - atleast a boot logo.
i have a D851 that a friend bricked. She tried upgrading to Lollipop and flashed the AT&T baseband on this TMobile version. The result is a hard bricked device which does not even seem to power on. Shows no signs of life, except when connected to a windows pc. It shows up as 'LG Androidnet USB modem' in the device manager. No boot logo, recovery, or download mode. Fortunately she has IMEI and twrp backups for this phone (boot, efs1, efs2, radio, rpm, tz). I did some research on JTag solutions. Unfortunately, none of the boxes support the D851, yet.
Any ideas on how to recover this device would be greatly appreciated.
Click to expand...
Click to collapse
If OP at least get QHUSB_BULK when he plugs it in it's better that he tries it
Sent from my iPad using Tapatalk
itsbighead said:
If OP at least get QHUSB_BULK when he plugs it in it's better that he tries it
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Nope. Only LG Androidnet USB modem'
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Redmi Note 8 Pro Hard Bricked
I'm in the same situation.
please help me
Hello,
The same thing happened to me when I installed the Orange FOX recovery, it didn't go into Fastboot mode, so I had to press the 3 buttons and wait for it to turn off completely, open the ADB control console and then connect it to the PC via USB by pressing the volume + button.
The latter I did on several occasions (Turn it off completely and connect by USB). Until I recognized it, when I recognized them, I had to flash the SYSTEM, CUST, RECOVERY. One by one, in total it took almost 5 minutes.
After that the phone started normal, obviously without root, nor custom recovery.
I'm also in the same situation as all of you, the PC doesn't recognize me and I can't go into fastboot
Hey,
I tried everything I could (battery connected/unplugged), my phone seems to have a corrupted preloader and only start the boot rom. That's why it shows up as "Mediatek USB PORT", if the preloader was'nt corrupted, it should be named "MediaTek PreLoader USB VCOM port" or something similar.
The only way to recover it imo is to flash a healthy preloader using SPFlashTool low level flash mode and next flash a full rom when "MediaTek PreLoader USB VCOM port" appears in the device manager.
Unfortunately, xiaomi ask for a certified account for low level flashing. I found one but the guy ask for 40$ for just logging it into my pc with teamviewer.
I buyed a Samsung Note10+ in replacement and i'll just wait someone find a solution to sell my 10-day-used redmi if I can revive it one day.
I got hundreds $ of Xiaomi home automation products in my home, but that was my first phone from this brand. I think it will also be the last.
I'm sad to see that their security policy on the phones is so frustrating to the people who just want to have a full acces on their devices.
Authorise can be done with professional tools
Tools like umt, hydra tool, miracle xiaomi tool, does the authorization. And i think mtk cpu Auth will only be available in miracle xiaomi tool, be aware every Auth cost credit of 4 to 10 u will have but credit separate from the tool.. Hope this will help
MOD EDIT: quote removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
girishjangir7 said:
MOD EDIT: name removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
Click to expand...
Click to collapse
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
djzero86 said:
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
Click to expand...
Click to collapse
It's against forum rules to post paid services
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
petenoni said:
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
Click to expand...
Click to collapse
I Also Had Adguard But I Was Still Not Satisfied
I Wanted My Phone To Be Rooted And Use The Custom ROMs If Build In Future.
Hemant Singh Rajput said:
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Click to expand...
Click to collapse
mine only take 3 hours at the service center in Jaipur
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
hi
does anyone find a solution for this?
please help
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
JuanM2020 said:
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
Click to expand...
Click to collapse
doesn't work
samadsaba said:
doesn't work
Click to expand...
Click to collapse
This is only for unbricked devices.... As I stated. If your device was already bricked it won't help you.
I also faced this problem... I used paid service to unbrick it... I must pay 35USD for the service.. but just wait.. If it works I will post here again. I bricked my phone when flashed anti brick on Android 10.. I forgot downgrade it to Android 9
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).