Related
Without checking the forums I went ahead and clicked on the Wireless Update on the P8000 and now it just hangs on the Elephone logo and is not recognized when I try to connect to the PC. Has anyone else done this and has the same problem, any way of fixing?
UPDATE: Decided to mess around with the phone to try and get back to life, found an old laptop, loaded the Drivers (without any security warnings), loaded the SP Flash Tool. Connnected the phone to the laptop, did not register, downloaded the ROM 150907, went to Flash Tool clicked on scatter.txt file, pressed the power button on the phone and somehow connection was made to the phone. Bottom line is that it kicked into life with the new 150907 software, from a non techie, I am well chuffed, certainly will not be doing a Wireless update anytime soon. The new ROM is a lot more stable and even allows me to use my Works email on the Exchange services account where I had previous issues.
I have the same problem. The OTA update got my phone stuck in the Elephone boot animation. I am using Windows 10 currently and I can't install the drivers. What OS did the computer you used run?
UPDATE: I did it!! I used this guide ( http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ ) to allow me to install the drivers in Windows 10, and then used the flashtool. It took me some tries to get the flashtool to recognized the device but it did it.
Unfortunately all data was wiped
emkwrx said:
UPDATE: Decided to mess around with the phone to try and get back to life, found an old laptop, loaded the Drivers (without any security warnings), loaded the SP Flash Tool. Connnected the phone to the laptop, did not register, downloaded the ROM 150907, went to Flash Tool clicked on scatter.txt file, pressed the power button on the phone and somehow connection was made to the phone. Bottom line is that it kicked into life with the new 150907 software, from a non techie, I am well chuffed, certainly will not be doing a Wireless update anytime soon. The new ROM is a lot more stable and even allows me to use my Works email on the Exchange services account where I had previous issues.
Click to expand...
Click to collapse
GroupStudyRoomF said:
I have the same problem. The OTA update got my phone stuck in the Elephone boot animation. I am using Windows 10 currently and I can't install the drivers. What OS did the computer you used run?
UPDATE: I did it!! I used this guide ( http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ ) to allow me to install the drivers in Windows 10, and then used the flashtool. It took me some tries to get the flashtool to recognized the device but it did it.
Unfortunately all data was wiped
Click to expand...
Click to collapse
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
a.cid said:
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
The zip I downloaded is this: "SP_Flash_Tool_exe_Windows_v5.1520.00.000"
Yes it has to be switched off first and then to be connected. As for the last question I don't remember exactly because I tried many times in different ways and I don't remember which worked in the end.
a.cid said:
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
i use the 532 sp tool and its fine for me. maybe redownload it again.
the phone has to be turned off . then press on download in the sp flashtool and connect the phone..
skeleton1911 said:
i use the 532 sp tool and its fine for me. maybe redownload it again.
the phone has to be turned off . then press on download in the sp flashtool and connect the phone..
Click to expand...
Click to collapse
The problem with this one was phone never stayed off. It would just keep switching on and getting stuck at boot screen.
I managed to fix it. Used 532 SP tool. Used an XP computer with anti virus turned off. To keep the phone shut down, I let it run out of juice (took a loooooooong time, not looking forward to doing this again), and then used an older usb cable to just get the phone to stay alive on usb current. Once you get the vcom loader message for mt65xx for usb recognition, that's when you're good to go.
a.cid said:
The problem with this one was phone never stayed off. It would just keep switching on and getting stuck at boot screen.
I managed to fix it. Used 532 SP tool. Used an XP computer with anti virus turned off. To keep the phone shut down, I let it run out of juice (took a loooooooong time, not looking forward to doing this again), and then used an older usb cable to just get the phone to stay alive on usb current. Once you get the vcom loader message for mt65xx for usb recognition, that's when you're good to go.
Click to expand...
Click to collapse
There is an easy trick to turn phone off. Reboot to recovery . (in stock there is the red android then press and hold power , press vol up and it will Boot into stock recovery)
Browse to "turn phone off."
Then its off and dont reboot, you can use the flashtool....etc
Gesendet von meinem Elephone P8000 mit Tapatalk
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Crossvxm said:
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Click to expand...
Click to collapse
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
imurreflection said:
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
Click to expand...
Click to collapse
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up + Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Crossvxm said:
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up +at Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Click to expand...
Click to collapse
Hey, thats great info.. Thanks a lot.. I was able to get the issue resolved. I found that thete was an issue with MTP driver.. I reinstalled it and PC immediately recognized it.. Thanks again for your help
you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)
Modularkarma said:
you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)
Click to expand...
Click to collapse
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.
No
Incogn said:
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.
Click to expand...
Click to collapse
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl
Modularkarma said:
No
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl
Click to expand...
Click to collapse
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash several fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.
Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash roms fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.
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).