Related
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
1st off, it's "taboo" not tabu. Secondly there is already a pretty good amount of threads that have covered this in detail, I'm certain because I have posted in them. Lastly, please SEARCH the existing threads before creating a new one; the answers to all your questions are already there.
1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.
Michael.fri said:
1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.
Click to expand...
Click to collapse
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium
Do you know what caused the brick?
Sent from my SGH-T989 using xda premium
Searched, and yet no result. Sending the phone to the U.S is quite risky. I have no idea how they're intended to pack it before sending it back. I would rather doing this in Israel.
I saw on ebay several devices associated with Jtag. the price starts from 10$ for a simple usb dongle, through 30$ devices, which is the price of most of the jtag devices I found, to the 150$ riff box that is associated with phone unbricking.
By what I know Jtag is a simple serial protocol. I just need sort of "bridge" to translate the logic 1's and 0's with the right voltage level and certain clock speed to a usb interface or even RS232. How expensive can that be?
I also contacted several ebay sellers which offer a jtag repair service. they all answered this model is not supported.
I would go to Samsung labs in Israel and see what they can do to get it working.
I just thought to invest 20$, get that sort of device and to get it done by my own.
Another issue is the pinout. The pinoput of the Jtag connection is not shown in any website, so I have no way of knowing how to connect on this specific PCB.
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
About the reason for bricking the phone, I have no Idea. As I said, last time I've installed new rom was more than a week prior to the incident. I've used some overclocking app mostly to underclock my phone, cause it drained the battery like hell before, even while it was running on stock and after changing the rom several times.
I also used some usb otg device which worked normally, but was not plugged to the device even few hours before it was bricked.
Hopefully we can figure out the cause of these permabricks so we can prevent it from happening to more people.
Sent from my SGH-T989 using xda premium
I gotta say, this is quite alarming. That the phone can just hard brick itself like this spontaneously.
I've had some scary experiences with the phone myself. Like a couple of random reboots that required the long power press for the phone to power back on. At least it always came back on.
I'm also from Israel myself so a similar scenario can bring me to the same situation as you.
Good luck with getting any kind of solution.
Sent from my SGH-T989 using xda premium
parusia said:
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Troll for advising to follow the posted rules of membership ? WOW
I just contacted Adam and still no jtag for this device .
Sent from my Galaxy Nexus using XDA App
did you look for a service manual?
- the manual may cover schematics for jtag device.
Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.
reocej said:
Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.
Click to expand...
Click to collapse
I recommend splurging on the $2-3 for a jig, I have had moments where I thought I was SOL & the jig saved my arse.
Michael.fri said:
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
Click to expand...
Click to collapse
Did you solve your problem?
I was looking at using QPST
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it. This has tools for building and installing bootloaders and partition tables. Our device after a hard brick (and still serviceable by JTAGing) has a com port open still and if you load the driver in windows you will see a port number as others here on XDA have said. The driver allows ODIN to see the device but not connect. QPST does connect, but I have not attempted to flash anything to it since I have not built any files to load. I'm kind of stuck creating the needed xml that makes the partition table and headers and file that are to be loaded to partitions. This is really a softbrick, in my opion, but nobody has the knowledge for this level of building and coding, with this tool, here at XDA. If somebody does, it may make those selling JTAG services mad, but that would mean we could fix our phones on our own. On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days.
By the way, this is a multi-device solution in the long run. We get one fixed and we can start on the others with this same issue, where the only life left in the device is the Qualcomm download mode driver showing in windows device manager.
Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
Mobile Tech offers the JTag service. There is even a discount for XDA members. They offer the service for all variants of the S2
Here you go!
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
daxxone said:
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it.*snip* On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days..
Click to expand...
Click to collapse
Any word on a fix using QPST?
Hey guys,
Just signed up to ask a few questions, a very good friend of mine had her phone (T-mobile Samsung Galaxy SII SGH-T989) run over the other day. Needless to say she is not very tech savvy. She has a new S4 now. Now the problem is, that being she is not so tech savvy she didn't back up (ever?) So i am looking to somehow recover lost pictures and contacts if possible.
Now I have a small background in building computers and taking stuff apart so I agreed to take a look at the phone. The screen is shot. but besides that the other internals look fine. Nothing is broken as far as i can tell. When I plug the phone in with the battery nothing comes up at all, except when i leave it plugged in for a little bit the LED under the camera will flash about once every minute or so.
So i guess the question i have is did the motherboard somehow short circuit when it was run over? Has anyone had experience with a situation similar to this before?
And is there a way to get the phone on long enough to recover the lost info?
Help would be much appreciated if possible.
Justin
As phones don't have an actual hard drive, I doubt you can recover anything from a phone that isn't running.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
This is not easy, but can be done. I have done similar recoveries several times…
You’ll need:
1) The equipment & ability to remove a surface mount soldered chip, and re-solder it onto another board *without* damaging it.
2) Another identical phone to host the transplanted chip.
3) A service manual, or someone with intimate knowledge of the device, to identify the correct chip…
Note that if the pix were encrypted this will not work…
My phone got hard bricked by only disabling OEM and rebooting the phone.
Can't load bootloader or Recovery mode and even if I wanted to fastboot it I'm also unable to do that, as fastboot/adb unable to find device, so what now ? I pay the price of trusting "the people's company" which is no longer true at all since they are basically charging flagship premium cost with terrible phones that brick within a week of buying ? any suggestions ? because I spent the last two days trying different stuff without it being able to work the only thread I found is of someone who managed to get a hold of them to remotely unbrick the phone for him. However when I attempted to do the same they gave me the most generic reply "we value our customers and bla bla bla and stay tuned .... what do you mean stay tuned... it's not like I won this phone as a gift I paid 1k+ and even more for local and vat taxing only to get the global version which by the way ended up still not working for my local Telecom providers as it seems that 5G isn't supported not sure if it's a lock thing from the phone or what because my previous phone was a Samsung S20 Ultra and 5G worked just fine not sure how come a phone equipped with 888SD can't afford to run 5G and an exynos990 phone that runs out of battery in two seconds is able to do it ?
one of the main reasons why I even tried the OEM Unlocking was in hope to be able to switch to the European stock RoM for it to somehow support 5G N78 even though OP9P Global version is supposedly able to cover all 5G bands (correct me if I'm wrong)
I genuinely loved this phone until I discovered that it can't do 5G NR78 NSA where I live . and to add salt into injury the phone doesn't support Dual-SIM setup which is very crucial to me and doesn't support eSIM (YES NOT EVEN) functionality what the heck ?! how is this a "Global Version"
------------------------------
Special thanks to :
jammin6996 for providing msm toolKonfuzion for directing me to his threadMuch appreciated I managed to get my device back by running the MSMdownload tool and installing the L2 Drivers as well as going through the installation of QDloader for Qualcomm as it was not discovered by windows.
Request a remote session, they fixed mine
Their customer support has been good to me, I've owned the 5 and 6T prior to the 9.
Pretty much the only reason I buy OnePlus is because of their dev support. They easy to mod phones. Cause lately it's not their hardware or features, frankly OP9 has been a huge disappointment, but it's still big upgrade for me. But I can definitely acknowledge the S21 series, Xiaomi 11 series and Oppo X3 series are far superior devices, OnePlus seriously f'd their fans, most expensive phones so far, but removed most features. Definitely most expensive phones for less on the market IMO.
I've never hard bricked either and I was compiling my own roms for a bit. There was always a way to resolve when I thought hard bricked it.
Most importantly, it's your responsibility if the phone doesn't support the bands you wanted, that's easy to find public information.
While i understand you're pissed. I've been with Oneplus since their launch of their original flag ship killer. I've never had a problem. It seems you did little to no homework while buying this phone. I would pissed too if i cant use all of its features (5g for example), but! you should've looked this up prior. I hope you're able to get a refund somehow and get another different phone. Good luck!
Sorry .. but ..
Take responsibility for your own F ups ....
Uh, there are many legit complaints about the OP9 series, but in this case you bought something you didn't understand, and then f'd it up by doing something you don't understand.
But, if it's true what you say and you have a hard brick, I'll buy it from you
craznazn said:
Uh, there are many legit complaints about the OP9 series, but in this case you bought something you didn't understand, and then f'd it up by doing something you don't understand.
But, if it's true what you say and you have a hard brick, I'll buy it from you
Click to expand...
Click to collapse
this right here is the truth.
Well you're in luck someone just posted the MSM tool.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
zymphad said:
Their customer support has been good to me, I've owned the 5 and 6T prior to the 9.
Pretty much the only reason I buy OnePlus is because of their dev support. They easy to mod phones. Cause lately it's not their hardware or features, frankly OP9 has been a huge disappointment, but it's still big upgrade for me. But I can definitely acknowledge the S21 series, Xiaomi 11 series and Oppo X3 series are far superior devices, OnePlus seriously f'd their fans, most expensive phones so far, but removed most features. Definitely most expensive phones for less on the market IMO.
I've never hard bricked either and I was compiling my own roms for a bit. There was always a way to resolve when I thought hard bricked it.
Most importantly, it's your responsibility if the phone doesn't support the bands you wanted, that's easy to find public information.
Click to expand...
Click to collapse
Yikes! Most reviewers I've read the reviews of disagree that those are far superior devices, but to each their own.
Konfuzion said:
Thanks a lot, begging them didn't work I'm glad XDA exists and such a supportive community exist.
Click to expand...
Click to collapse
steve841 said:
Sorry .. but ..
Take responsibility for your own F ups ....
Click to expand...
Click to collapse
how is this my F-up ? enabling and disabling OEM should never cause your phone to hard brick and get you stuck with no recovery or bootloader (you know that debug doesn't work with OEM off right ? meaning you literally can't do anything)... I have owned countless of phones during the last 15 years I have never had such problem happen to me.
moe990 said:
how is this my F-up ? enabling and disabling OEM should never cause your phone to hard brick and get you stuck with no recovery or bootloader (you know that debug doesn't work with OEM off right ? meaning you literally can't do anything)... I have owned countless of phones during the last 15 years I have never had such problem happen to me.
Click to expand...
Click to collapse
So do I understand correctly. You opened bootloader and then locked it, and that caused soft brick? You didnt modify system in any way before locking it or anything?
That sucks, man.
Do you still have the device? What OS do you use on your PC?
I'm using Windows 10 and downloaded the Google USB Drivers from here:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
I installed the drivers (right click the inf file after extracting and select install) and then navigated to the Android (other) device in device manager; right clicked on it and selected "update driver", "Browse my computer for driver software", "Let me pick from a list..." and then "Android" and "Bootloader device (or something to that effect)" from the list.
Driver installed, phone got detected, and a quick "fastboot -w" brought it back to life.
If you still have the device, give it a shot. Good luck, man.
1] You should have checked you could unlock the bootloader on your model first as some OEMs lock that out, posting here would've helped
2] Ask for guidance or instructions first if you're not sure what you're doing
3] The OnePlus 9 Pro DOES support dual sim ( https://www.gsmarena.com/oneplus_9_pro-10806.php ), if memory serves, each sim goes on each side of the sim tray (Not got mine yet, just ordered it today)
4] As others have said, there seems to be an MSM tool available already which is impressive, this will be able to restore the stock rom to the phone as long as you make sure your computer has the correct drivers installed
5] As others have said, you should do some research before buying a phone to see if it will fit your needs, your actions caused your problems.
djsubterrain said:
3] The OnePlus 9 Pro DOES support dual sim ( https://www.gsmarena.com/oneplus_9_pro-10806.php ), if memory serves, each sim goes on each side of the sim tray (Not got mine yet, just ordered it today)
4] As others have said, there seems to be an MSM tool available already which is impressive, this will be able to restore the stock rom to the phone as long as you make sure your computer has the correct drivers installed
Click to expand...
Click to collapse
Unfortunately, dual-sim is not available in the US market, "global" or t-mobile (LE2125, LE2127). Simple ROM flashing does not enable it. Currently, the MSM that's posted applies only to LE2125. No other models would apply to that MSM.
Hi everyone, long time XDA lurker, first time poster here. Hope I'm in the right spot.
I have a 3XL that bricked overnight similar to what I've seen on other posts (for example: https://forum.xda-developers.com/t/...Rj7bE_8k87pI2zaSnIskWwmvsbMpMeVBlmWrHPsqhUY0c)
Long story short, can't get it to boot, isn't recognized by fastboot/adb. I started following this guide https://www.thecustomdroid.com/qpst-flash-tool-download-usage-guide/ and my phone is recognized, but like one user in the xda post (above), I don't know where to get the raw firmware file that I need to move forward (need elf or mbn file with maybe some xml files?). I've been searching high and low and this is where I'm stuck. I've seen some mentions about needing to get these files from someone who actually has a working 3 XL, but I'm not sure if that's the only option. Does anyone have any insight that could help me move forward?
And on that note, if I manage to recover the phone using this method, will it be recovered right back in the state it was, or will it be freshly formatted? Again, I've read lots on this, but I can't seem to get a straight answer. To be honest, while getting the phone working again would be amazing, my priority is recovering the data from the phone, so if this QPST recovery will only end up giving me back a naked phone, then I'm open to alternatives.
Any help is appreciated! Thanks!
Currently in the exact same boat as you, unfortunately...
I'm also mostly interested in just getting to my data, although having a working phone again would be nice.
I can get the serial port to show up in qpst but I'm pretty much at a stand still from there, can't get anything else to work.
Have you had any luck??
I'm in the same position as you guys, pixel 3 XL bricked, bootloader locked, no recovery just Fastboot Mode (With OEM Locked, any command wil not work there.. thank u so much Verizon), I was looking and this seems to be the only way but I can not find any dump from a pixel 3 xl working to flash in EDL Mode, if you guys can find something let me know, I'm gonna try to find it on my side too
Unfortunately I never found a solution. QPST recognized the phone, but could never successfully connect to it. While Googling the issue, I noticed that this has happened to a number of other people too, and it often seems to coincide with updates, so it could be linked although good luck getting Google to admit to that.
I ended up swapping the phone out for an S21. This is the first phone that has even bricked itself so bad that I couldn't recover anything from it, and seeing how it has happened on many generations of the Pixel line, I wasn't very tempted to get another one unfortunately.
Chiming in with a similar story to the rest of you folks.
I'm an experienced user that knows his way around adb/fastboot and flashing custom ROMS and whatnot, but in this case I have a completely stock Pixel 3XL that I woke up to find in this hard bricked EDL state. I am up-to-date with any and all updates for the OS and I usually pull those down on release day or very shortly after. No idea what update could have caused this, but in my case, I am overseas with a bricked cell phone - SUCKS.
Hopefully the QPST files can be located so that we can recover from this bull****.
I know some people with a working 3 XL. Are there instructions on how to extract the necessary files from a working phone to flash through QPST on the bricked phone?
I just ordered a 3 XL for my daughter and I'm getting scared seeing these stories. Is it just aged hardware related? Or is it update related? It's weird that it seems to be happening over the last few months on the 3 series which makes me think its either related to an update that rolled out or just mileage until failure of the chips?
I have had for two years a used one year old 3XL and had no problems. If someone has instructions, I would be glad to extract what is needed. At this phase it has only been unlocked to use DNS66 though I consistently ROM'd all my earlier phones. Age related ;-)
I've have owned quiet a collection of smartphones... Too many to list, but some of my memorable one's are:
1st edition Apple iPhone 3g (still own)
Samsung Galaxy Mega
Samsung pre Knox edition Note phablets
Motorola Razr HD (still own, but died on me)
Google Nexus 6 (still own, but battery is completely dead) loved the clean google experience.
Xiaomi Mi Mix (still own, despite changing several broken LCD screens) my personal all Time Xiaomi favorite phablet.
Xiaomi Mi Mix 2 and 2S (hated the extended waiting time to unlock bootloader)
Xiaomi Mi 9T (still own)
Motorola Razr 5G (own and use, presently in warranty status, but have to keep the bootloader locked to preserve warranty)
Oneplus 8T 5G (purchased it on a trial basis used, and immediately loved the speed and 5G speed even though bootloader locked - T-Mobile Edition)
To my present backup phone (as I wait for my Razr 5G to be returned to me) that I recently purchased the Oneplus 9 pro LE2127 T-Mobile edition (waiting now 7+ days for Oneplus/T-Mobile to unlock bootloader). I was initially crushed that I could not access the blazing 5G speeds in my city, I soon read how to modify the existing policy.xml file to remove the network restrictions that Oneplus put in place??? (or is it T-Mobile put in place???)
This phones best feature is it's worry free blazing charging speeds... I'm mean come on, who doesn't love the Warp speed charging. It's insanely quick and the best part, the technology works in such a way that their is no heat generated while charging at 4000+mAh rate. I know you need to have the Warp Speed Charging plug and a USB-C 6.5A version cable handy, but from home (morning, noon on weekends, or night) you can always grab a quick boost if you feel you need to get through the rest of the day or night. LOVE it. Too bad the block was not included (it wasn't on my smartphone) as standard.
The screen is a thing of beauty (it makes my Razr 5G looks so poor), the refresh rates are insane (can't really say it was a game changer compared to the Oneplus 8T 5G - which is really good on it's own), and the 5G network is pretty good (not as good as my Razr 5G, nor my son's iPhone 13 pro max which is a beast on the 5G network)
I am thoroughly impressed with the Oneplus 9 pro 5g, and look forward to receiving the bootloader unlock .bin file. I only hope it will take less than the two week waiting period. I am thinking and weighing my options when I unlock the bootloader whether to root it and debloat on the LE2127 firmware, or convert it to the global rom and hence turning it into the LE2125. Something tells me to just root it and debloat, since I now have the correct policy.xml modified to access the 5G network up here in Canada.
I can't wait to debloat what little apps are there, and install AdAway root edition to crush the Ads and popups. Looking forward to using this phone as my main phone, as I just might sell off the Motorola Razr 5G (expecting it to be exchanged by Motorola instead of repaired - - - suffering from two burned pixels and poor TX reception.
Cheers,
LormaD
OnePlus 9 Pro Display Technology Shoot-Out
You don't need to wait for the unlock.bin
Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people). ***...
forum.xda-developers.com
People seem to think the EU conversion is better than the global conversion anyway.
LormaD said:
I've have owned quiet a collection of smartphones... Too many to list, but some of my memorable one's are:
1st edition Apple iPhone 3g (still own)
Samsung Galaxy Mega
Samsung pre Knox edition Note phablets
Motorola Razr HD (still own, but died on me)
Google Nexus 6 (still own, but battery is completely dead) loved the clean google experience.
Xiaomi Mi Mix (still own, despite changing several broken LCD screens) my personal all Time Xiaomi favorite phablet.
Xiaomi Mi Mix 2 and 2S (hated the extended waiting time to unlock bootloader)
Xiaomi Mi 9T (still own)
Motorola Razr 5G (own and use, presently in warranty status, but have to keep the bootloader locked to preserve warranty)
Oneplus 8T 5G (purchased it on a trial basis used, and immediately loved the speed and 5G speed even though bootloader locked - T-Mobile Edition)
To my present backup phone (as I wait for my Razr 5G to be returned to me) that I recently purchased the Oneplus 9 pro LE2127 T-Mobile edition (waiting now 7+ days for Oneplus/T-Mobile to unlock bootloader). I was initially crushed that I could not access the blazing 5G speeds in my city, I soon read how to modify the existing policy.xml file to remove the network restrictions that Oneplus put in place??? (or is it T-Mobile put in place???)
This phones best feature is it's worry free blazing charging speeds... I'm mean come on, who doesn't love the Warp speed charging. It's insanely quick and the best part, the technology works in such a way that their is no heat generated while charging at 4000+mAh rate. I know you need to have the Warp Speed Charging plug and a USB-C 6.5A version cable handy, but from home (morning, noon on weekends, or night) you can always grab a quick boost if you feel you need to get through the rest of the day or night. LOVE it. Too bad the block was not included (it wasn't on my smartphone) as standard.
The screen is a thing of beauty (it makes my Razr 5G looks so poor), the refresh rates are insane (can't really say it was a game changer compared to the Oneplus 8T 5G - which is really good on it's own), and the 5G network is pretty good (not as good as my Razr 5G, nor my son's iPhone 13 pro max which is a beast on the 5G network)
I am thoroughly impressed with the Oneplus 9 pro 5g, and look forward to receiving the bootloader unlock .bin file. I only hope it will take less than the two week waiting period. I am thinking and weighing my options when I unlock the bootloader whether to root it and debloat on the LE2127 firmware, or convert it to the global rom and hence turning it into the LE2125. Something tells me to just root it and debloat, since I now have the correct policy.xml modified to access the 5G network up here in Canada.
I can't wait to debloat what little apps are there, and install AdAway root edition to crush the Ads and popups. Looking forward to using this phone as my main phone, as I just might sell off the Motorola Razr 5G (expecting it to be exchanged by Motorola instead of repaired - - - suffering from two burned pixels and poor TX reception.
Cheers,
LormaD
Click to expand...
Click to collapse
I assume you're on OOS 11. To sustain your good impression of the phone, stay there and don't go to OOS 12.
EtherealRemnant said:
You don't need to wait for the unlock.bin
Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people). ***...
forum.xda-developers.com
People seem to think the EU conversion is better than the global conversion anyway.
Click to expand...
Click to collapse
Currently at same point with my OP9Pro as OP, I got screwed and ended up with 2127 thinking I bought 2125... Anyways, I want to do this, but cannot find any info on how to backup persist and modemst1/2.
I read in that thread to use EDL tool but not seeing anything obvious in MSM that lets me back up partitions.
EDIT: Just found it. For anybody searching "how to backup persist or modemst1/2", see this post (#82):
Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people). ***...
forum.xda-developers.com
Not my first rodeo, but my LE2127 is completely bricked. Like, super bricked.
After unlocking the boot loader, I rooted my LE2127 using a boot.img extracted for my build. Magisk created the rooted boot.img for me (have done all this before many times), applied the rooted boot.img using adb. I managed to take a complete backup of my handset now that it was rooted.
My LE2127 was rooted and good to go.
Prior to unlocking the bootloader and rooting my LE2127 I successfully managed to modify my policy for my LE2127 and hence had 5G access on the Rogers Network.
Last night I toyed with the idea of unbloating or programming the LE2125 global image. Followed the direction and did notice in the flash_all.bat file that some of the files being written failed in the write command. And that point onwards from recovery reboot my handset was bricked.
I have bricked (soft bricked if you will) handsets before trying different various builds, but I could always get into fastboot or recovery. This LE2127 is super bricked, no matter what sequence of Volume down + power, or Volume down + Volume Up to enter EML..
I know my laptop Port for the Qualcomm Driver is good, since I could program ADB and access with the MSM Tool. But now, the MSM Tool will see the phone and then after 8 seconds will get the Sahara Communication Error.
After banging away all night reading up and trying various work arounds, I decided to mail in the handset to ONEPLUS warranty. Either way, I have nothing to lose.
Keeping my fingers crossed.
Cheers
You should have worked on here some more to troubleshoot before mailing in!
I guess at least it is under warranty but getting into EDL is odd sometimes.
You have to press & hold vol up+down then plug it into your PC, and as soon as device mgr sees it as a comm port click start in the TMO MSM and let it rip.
cproo12 said:
You should have worked on here some more to troubleshoot before mailing in!
I guess at least it is under warranty but getting into EDL is odd sometimes.
You have to press & hold vol up+down then plug it into your PC, and as soon as device mgr sees it as a comm port click start in the TMO MSM and let it rip.
Click to expand...
Click to collapse
That's exactly what I did... I can get it into EDL, and when I plug it in it is seen by the MSM Tool (for my device LE2127) and acknowledge and proceeds with the "process", but after 8 or so seconds, I get the communication fail error and the device seems to stagnate without any further "action".
What really spooked me is the complete blank and dead screen for the device. There isn't even a gray overtone on the device when trying EDL, or Fastboot Recovery mode. Nothing, no sound, no screen, nothing. Even when I plug it in to charge it seems lifeless. I even left it plugged in overnight to charge, just in case.
I tried it on a Windows 10 machine, as well as my personal laptop on Windows 11. I can get either computer to recognize the appropriate Qualcomm USB driver and both computers react the same way when plugging the LE2127 in EDL mode with the MSM tool. It either had a mechanically failure right after being flashed (the handset is 10 days old) and something other than the Global Rom bricked the LE2127. I wasn't scared, I just did not see any options after looking here and google.
I'm hoping Oneplus comes through for me with my handset "reflashed" if that is the only problem, or a replacement unit (great, You buy a new unit and you get a refurbished one as replacement).
Cheers,
LormaD said:
What really spooked me is the complete blank and dead screen for the device. There isn't even a gray overtone on the device when trying EDL, or Fastboot Recovery mode. Nothing, no sound, no screen, nothing. Even when I plug it in to charge it seems lifeless. I even left it plugged in overnight to charge, just in case.
Click to expand...
Click to collapse
This is because the screen is an OLED. You won't see anything on the screen if it can't boot because it will just be a black image... which on an OLED is, well- BLACK!
Hoping for the best with your oneplus return. You should post here with an update when you get it back.
What did you tell them/who did you reach out for support? You have to pay shipping?
LormaD said:
That's exactly what I did... I can get it into EDL, and when I plug it in it is seen by the MSM Tool (for my device LE2127) and acknowledge and proceeds with the "process", but after 8 or so seconds, I get the communication fail error and the device seems to stagnate without any further "action".
What really spooked me is the complete blank and dead screen for the device. There isn't even a gray overtone on the device when trying EDL, or Fastboot Recovery mode. Nothing, no sound, no screen, nothing. Even when I plug it in to charge it seems lifeless. I even left it plugged in overnight to charge, just in case.
I tried it on a Windows 10 machine, as well as my personal laptop on Windows 11. I can get either computer to recognize the appropriate Qualcomm USB driver and both computers react the same way when plugging the LE2127 in EDL mode with the MSM tool. It either had a mechanically failure right after being flashed (the handset is 10 days old) and something other than the Global Rom bricked the LE2127. I wasn't scared, I just did not see any options after looking here and google.
I'm hoping Oneplus comes through for me with my handset "reflashed" if that is the only problem, or a replacement unit (great, You buy a new unit and you get a refurbished one as replacement).
Cheers,
Click to expand...
Click to collapse
If you have a problem and need to MSM in the future, open the MSM, click lite firehose, and click Start before you connect your device... Then hold volume up and volume down at the same time while plugging in the cable. This way the software picks up the phone immediately because it's already looking for it. I noticed that there are only a few seconds it spends in EDL before trying to reboot so if you're not quick, you get a connection error.
Ah... OLED.... My first time on a smartphone that I was modding with. Still an odd feeling trying to interact with a device that shows no signs of life, other than communicating with the computer usb port.
I basically opened up a repair ticket on the oneplus canadian website. It asks for the IMEI, and then the nature of the problem (there is even an upload for any videos to further explain the problem. I basically wrote on the repair ticket that after upgrading from OS 11 to OS 12, the LE2127 would no longer boot up. It is under warranty, and they will probably note on file that I applied for the bootloader to be unlocked (and successfully unlocked). How they go about it from there, one only hopes they stay true to their warranty that even a unlocked bootloader is warrantied.
As for MSM, I would power it up and ready to receive the LE2127. I pressed down on a flat table the side of the Volume UP and Volume Down with one hand, and after 3 - 5 seconds or so, plugged the USB C into the phone with the other hand. MSM immediately made the connection with the device within 1 - 1.5 seconds and confirmed connected to my Port. The download process would start and then after 5 - 8 seconds fail with the Communication Error. If your saying you need to be lightening quicker than that, then no "I did not attempt it" much quicker than that. I read somewhere about the possible errors to solve the communication error after the initial handshake and confirmed connection, and none of them made mention to time or interval of time required for each step.
Cheers
LormaD said:
Ah... OLED.... My first time on a smartphone that I was modding with. Still an odd feeling trying to interact with a device that shows no signs of life, other than communicating with the computer usb port.
I basically opened up a repair ticket on the oneplus canadian website. It asks for the IMEI, and then the nature of the problem (there is even an upload for any videos to further explain the problem. I basically wrote on the repair ticket that after upgrading from OS 11 to OS 12, the LE2127 would no longer boot up. It is under warranty, and they will probably note on file that I applied for the bootloader to be unlocked (and successfully unlocked). How they go about it from there, one only hopes they stay true to their warranty that even a unlocked bootloader is warrantied.
As for MSM, I would power it up and ready to receive the LE2127. I pressed down on a flat table the side of the Volume UP and Volume Down with one hand, and after 3 - 5 seconds or so, plugged the USB C into the phone with the other hand. MSM immediately made the connection with the device within 1 - 1.5 seconds and confirmed connected to my Port. The download process would start and then after 5 - 8 seconds fail with the Communication Error. If your saying you need to be lightening quicker than that, then no "I did not attempt it" much quicker than that. I read somewhere about the possible errors to solve the communication error after the initial handshake and confirmed connection, and none of them made mention to time or interval of time required for each step.
Cheers
Click to expand...
Click to collapse
No, what I meant is that you just click Start before the device is hooked up, that way it starts the process automatically when you connect it.
I bricked my OP9 multiple times this weekend and I can tell you it was a real pain getting the MSM to work until I figured out clicking Start first, I got the connection error a bunch of times before I finally got it to work the first time. It was a total fluke that I figured out that starting the process before connecting it worked though. I flashed the MSM, rebooted, unlocked the bootloader again, flashed a custom ROM, rebooted, and it went back to EDL (because apparently the flash failed again) and it flashed the MSM automatically because I had never hit Stop or exited the MSM. I bricked it one last time before I gave up and stayed on stock and again, hitting Start and then connecting the device worked the first time. If you had already done this then you had more problems than I did. I would have installed a portable Windows 10 to a USB stick and tried it that way.
Honestly think I'm done messing with the OnePlus though, I'm going to get a Pixel 7 and be done with this temperamental junk with bad software. Just need it to survive until then...
Ah... I don't remember starting MSM Tool, and clicking start without having my Oneplus Pro 9 LE2127 in EDL mode before plugging in the cable to the laptop. Damn.
Be it as it may, the phone is no longer in my hands. When I do get it back, I will probably just:
1) rewrite the Policy File that I modded to accept the Rogers 5G network.
2) Unlock the Bootloader.
3) Root the phone.
4) Debloat some T-Mobile apps.
5) And stick with OS11.
Question for those who unlocked the Bootloader... if you relock the bootloader, do you still on reboot have the phone displaying the information that the handset is running an unlocked bootloader?
LormaD said:
Question for those who unlocked the Bootloader... if you relock the bootloader, do you still on reboot have the phone displaying the information that the handset is running an unlocked bootloader?
Click to expand...
Click to collapse
On my 9pro it doesn't even show this warning when it's unlocked and rooted. My Nord shows the warning, but it is on a custom rom.
My 1st Motorola Razr 5G (when I received the approval request from Motorola to unlock the bootloader - voids warranty) after unlocking the bootloader had this 3 second delay or so as it flashed the fact that the phone was running an unlocked bootloader (I sold it).
My 2nd Motorola Razr 5G I decided not to unlock the bootloader (as much as I would like) because the phone is simply to fragile to own without a warranty. I have it as my main phone (but I think once I get it back from Motorola under warranty, I may regulate it as a backup phone or sell it) but I think I will use my oneplus 9 pro instead (once I receive it back from Oneplus warranty center).
I'm questioning the value of going to a global rom. Do you still get the same number of 5G channels/frequencies (something about, the modem does not get over written when flashing a global le2125 rom to the le2127 t-mobile)?
Is it simply because there are more updates on the LE2125 build?
Cheers
People prefer EU over Global, but yes, both EU & Global receiver more regular updates then T-Mobile
Apparently yes you have to flash the modem if you do the conversion, however I have tried both versions without flashing the modem and I still get perfectly fine coverage without flashing the modem... Your mileage may vary.