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.
Related
I'm trying to unlock my mi max 6gb version I got from tradingshenzen today but I have no success with the latest version of the mi unlock tool. What's the issue here?
zed011 said:
I'm trying to unlock my mi max 6gb version I got from tradingshenzen today but I have no success with the latest version of the mi unlock tool. What's the issue here?
Click to expand...
Click to collapse
Isnt it unlocked already? It should come unlocked if you bought it from Trading Shenzhen...
Only if you get xiaomi eu rom, I did not I stuck with the original china rom
I bought my one at tradingshenzen too. It was locked.
Did you follow all the steps? Try to logout from mi-account on your phone and login again on the same wifi network as your pc is. Did you activate the developer options and set oem-unlock to on? Can your phone be located through https://i.mi.com/#/ ?
When everything goes right, it will say: waiting time 360 hours = 15 days before going to unlock.
If that's to long for you, then try to flash another rom (maybe China developer or stable), but better take an older version, because the new ones have Anti-Rollback activated.
And before you flash another rom, better logout from your mi account on your phone.
I reduced my waiting time to 240 hours by flashing another rom
zed011 said:
Only if you get xiaomi eu rom, I did not I stuck with the original china rom
Click to expand...
Click to collapse
I chose china rom also from trading shenzhen and got miui 10 china developer rom and they had it unlocked. It gets OTA updates every week...
The device is definitely still locked because there's no message when booting up and going to developer options > mi unlock status shows the device is locked.
Device can be located using find device
OEM unlocking is enabled in developer settings
Logged into mi account on the device which is the same on the mi unlock tool
Don't know what to do now. I'm on 9.6.12.0 which has antirollback unfortunately which I updated to when I was still getting the error.
Nevermind solved. I tried another computer that was Intel instead of AMD and I can now see the wait time to unlock. Ridiculous 719 hours...
Okay, this problem got me now. Three different PCs, all of them unable to unlock the new Xiaomi Mi 8.
I have to say, I am royally pissed of with Xiaomi. What on Earth happened? Why do they create this process, and why is it that buggy?
I was waiting to unlock my mi 8 lite and it told me the usual 360 hours and today it was up so I went in to unlock and now it says that I must 'use the phone more before unlock' Please wait 7 days. I'm so pissed I just put the return in to amazon I'm not doing that waiting again just for them to tell me wait again and then I can't return it. Anyone else seen this? Getting a OP6 I'm tired of this ****.
Sörnäinen said:
Okay, this problem got me now. Three different PCs, all of them unable to unlock the new Xiaomi Mi 8.
I have to say, I am royally pissed of with Xiaomi. What on Earth happened? Why do they create this process, and why is it that buggy?
Click to expand...
Click to collapse
I've read somewhere that it could be a problem with a USB 3 Port, use a USB 2 Port if available. But I can't verify that for myself as I'm still waiting for mine to come :crying:
sting12345 said:
I was waiting to unlock my mi 8 lite and it told me the usual 360 hours and today it was up so I went in to unlock and now it says that I must 'use the phone more before unlock' Please wait 7 days. I'm so pissed I just put the return in to amazon I'm not doing that waiting again just for them to tell me wait again and then I can't return it. Anyone else seen this? Getting a OP6 I'm tired of this ****.
Click to expand...
Click to collapse
Well that's interesting, I was planning on letting mine just sit on the shelf until the 30 days have passed. Good to know that that's not a good way to go forward. Thanks for sharing that, even if it made you return your device.
Zacki06 said:
I've read somewhere that it could be a problem with a USB 3 Port, use a USB 2 Port if available. But I can't verify that for myself as I'm still waiting for mine to come :crying:
Well that's interesting, I was planning on letting mine just sit on the shelf until the 30 days have passed. Good to know that that's not a good way to go forward. Thanks for sharing that, even if it made you return your device.
Click to expand...
Click to collapse
Yeah I'm so unbelievably pissed, I noticed the unlock tool just told me no, then it said there was an update to the unlock tool, installed it. Then I get this now, LOL. Yeah ok Xiaomi I don't think so. It's too bad because the hardware is nice but they want to try and trap you into their crappy ad ridden ROM, bait and switch so I'm just going to grab a OP6 tonight and have it unlocked and flashed before this even gets back to amazon. I went cheap because I heard good things about xiaomi but it must have been in the past because this is very very bad business.
has anyone had any success unlocking after the time was up? I can't believe they are doing this.
sting12345 said:
Yeah I'm so unbelievably pissed, I noticed the unlock tool just told me no, then it said there was an update to the unlock tool, installed it. Then I get this now, LOL. Yeah ok Xiaomi I don't think so. It's too bad because the hardware is nice but they want to try and trap you into their crappy ad ridden ROM, bait and switch so I'm just going to grab a OP6 tonight and have it unlocked and flashed before this even gets back to amazon. I went cheap because I heard good things about xiaomi but it must have been in the past because this is very very bad business.
Click to expand...
Click to collapse
Well from what I've heard, this unlocking procedure was introduced because some chinese vendors were unlocking chinese models of their phones and selling them in europe or elsewere and that was not what they had intended. So to prevent them from unlocking the devices they implemented this waiting time. And I guess "not using" is just one of the details of it. As I would understand it, a vendor could still request the unlock of several devices and then just wait but they would probably not pop a sim in every of these devices for a while. And to be clear, that's just a guess I'm making here. But I could imagine that being a "thing" to prove that you are indeed "using" the phone.
yeah I returned it this morning so I don't care anymore and got a OP6 I'm unlocking right now. I popped sim in the first day and then waited their mandated time and it said nothing about keeping sim in or anything and the countdown timer kept moving so I waited but not going to wait until my return period was over LOL. No way.
Zacki06 said:
I've read somewhere that it could be a problem with a USB 3 Port, use a USB 2 Port if available. But I can't verify that for myself as I'm still waiting for mine to come :crying:
Click to expand...
Click to collapse
That's exactly the point. I had to use a very very old PC to do the unlocking. It wouldn't work on any newer one.
There is no waiting time anymore, though. But I guess you have found out yourself by now.
Sörnäinen said:
That's exactly the point. I had to use a very very old PC to do the unlocking. It wouldn't work on any newer one.
There is no waiting time anymore, though. But I guess you have found out yourself by now.
Click to expand...
Click to collapse
What do you mean be "very very old"? My (desktop) PC is just a few years but it still has plenty of USB 2.0 ports. But for the waiting, I'm still waiting that TradingShenzhen is actually shipping the damn thing Ordered it a week ago.
Zacki06 said:
What do you mean be "very very old"? My (desktop) PC is just a few years but it still has plenty of USB 2.0 ports. But for the waiting, I'm still waiting that TradingShenzhen is actually shipping the damn thing Ordered it a week ago.
Click to expand...
Click to collapse
None of my newer PCs did the job, although they all USB2 ports. I had to use a PC that does NOT have a USB3 port, and that was my 6 year old ASUS.
I don't know what Xiaomi is thinking, but my guess is: Not very much. In this case, at least, the phone altogether is brilliant.
Sörnäinen said:
None of my newer PCs did the job, although they all USB2 ports. I had to use a PC that does NOT have a USB3 port, and that was my 6 year old ASUS.
I don't know what Xiaomi is thinking, but my guess is: Not very much. In this case, at least, the phone altogether is brilliant.
Click to expand...
Click to collapse
Ok that is strange, never heard of that, that the PC to use has to have USB 2.0 only. Then also my desktop would be out of the race as it has 2 USB 3.0 at the back...^^
Not sure this is something that they are doing on purpose, although it's not the first time I've read that something does not work with USB 3 and only with USB 2 (other stuff than unlocking).
It seems that there are still some driver issues or perhaps some other stuff that is interfering, because as more and more is upgraded to USB 3 (pc's as well as phones) that would make things very difficult if we were stuck on USB 2 for certain things.
But back to the phone, have you actually tried upping the dpi? I was wondering up to what point this can be done because the default resolution seems a bit like "not using the screen as effectively as you could do".
Zacki06 said:
Ok that is strange, never heard of that, that the PC to use has to have USB 2.0 only. Then also my desktop would be out of the race as it has 2 USB 3.0 at the back...^^
Not sure this is something that they are doing on purpose, although it's not the first time I've read that something does not work with USB 3 and only with USB 2 (other stuff than unlocking).
It seems that there are still some driver issues or perhaps some other stuff that is interfering, because as more and more is upgraded to USB 3 (pc's as well as phones) that would make things very difficult if we were stuck on USB 2 for certain things.
But back to the phone, have you actually tried upping the dpi? I was wondering up to what point this can be done because the default resolution seems a bit like "not using the screen as effectively as you could do".
Click to expand...
Click to collapse
My best guess is that it indeed is a driver issue and the problem was the INTEL motherboard I use in both of my newer PCs. But it's just a guess. Perhaps the motherboard treats all USB ports internally like USB3 or what not...
I haven't upped the DPI. Maybe I should have, I had some trouble adapting my old browser to the much lower resolution of the Mi 8.
At first that put me off a bit - I come from a device with a 2K screen, and it felt like downgrading - but in everyday use there is no difference. The screen might just be FHD, but it's crisp, bright and great.
I will have a look at the DPI thing, I am triggered now.
Sörnäinen said:
My best guess is that it indeed is a driver issue and the problem was the INTEL motherboard I use in both of my newer PCs. But it's just a guess. Perhaps the motherboard treats all USB ports internally like USB3 or what not...
I haven't upped the DPI. Maybe I should have, I had some trouble adapting my old browser to the much lower resolution of the Mi 8.
At first that put me off a bit - I come from a device with a 2K screen, and it felt like downgrading - but in everyday use there is no difference. The screen might just be FHD, but it's crisp, bright and great.
I will have a look at the DPI thing, I am triggered now.
Click to expand...
Click to collapse
Well I've also read that Intel boards are fine but AMD boards are causing trouble... Strange.
Well my phone before the 5x was an OPPO Find 7 (the s, not the a, so the "better" one with a QHD display) and I still use that from time to time like for navigating because its just so much more you see on the screen than on my 1080p Honor 5x. Let me know if you managed to get anything satisfying in regards to the DPI
Hello all
Can anyone tell me why Xiaomi keep moving the 'time period' for unlocking the BOOTLOADER on the Mi Max 3 ?
Initially I was told onscreen (PC Mi software) to try again in 360 hours. So I waited for the 360 hours and now it is saying onscreen, unable to unlock , try again in another 4 days time......
The phone is VERIFIED onscreen , my Mi Account is well established and verified.
Has anyone else experienced this ?
Will the BOOTLOADER ever unlock ?
I am becoming less interested in the Xiaomi brand as every day goes by. At least with a Samsung product there is no waiting nor external company control.
I am curious to know if Xiaomi are collecting personal data or info when you connect your device to their PC software to unlock the device.
Seems like Xiaomi like to control what the end user can and can't do with their products.
Thanks for reading :good:
tsam19 said:
Hello all
Can anyone tell me why Xiaomi keep moving the 'time period' for unlocking the BOOTLOADER on the Mi Max 3 ?
Initially I was told onscreen (PC Mi software) to try again in 360 hours. So I waited for the 360 hours and now it is saying onscreen, unable to unlock , try again in another 4 days time......
The phone is VERIFIED onscreen , my Mi Account is well established and verified.
Has anyone else experienced this ?
Will the BOOTLOADER ever unlock ?
Click to expand...
Click to collapse
I've just read this message in a different thread here that seems related to your problem. How much have you been using the device while waiting for it go get unlocked?
RE Zacki06
Thanks for the link. As for using the phone i.e making calls or texting. I haven't really used it that way. I've installed a few apps on it. Surfed the web occasionally.
I don't want to use or customise it because when the bootloader gets unlocked it wipes the device like in a fresh format.
It seems like yet another bizzare, controlling twist from the Xiaomi manufacturers if they demand the user to use the device. Before allowing the bootloader to be unlocked.
It also seems suspiscious that Xiaomi are keeping tabs on the owner i.e knowing if they are using the device or not. Personally I don't like being spied on when I invest in buying a product.
I am swaying more and more to stay with a Samsung product if Xiaomi keep dangling a carrot then pulling it away at the last minute.
tsam19 said:
RE Zacki06
Thanks for the link. As for using the phone i.e making calls or texting. I haven't really used it that way. I've installed a few apps on it. Surfed the web occasionally.
I don't want to use or customise it because when the bootloader gets unlocked it wipes the device like in a fresh format.
It seems like yet another bizzare, controlling twist from the Xiaomi manufacturers if they demand the user to use the device. Before allowing the bootloader to be unlocked.
It also seems suspiscious that Xiaomi are keeping tabs on the owner i.e knowing if they are using the device or not. Personally I don't like being spied on when I invest in buying a product.
I am swaying more and more to stay with a Samsung product if Xiaomi keep dangling a carrot then pulling it away at the last minute.
Click to expand...
Click to collapse
So as mentioned here this might have to do with the fact that xiaomi wants to prevent chinese vendors to sell their stuff elswere.
But of course I agree that this level of "spying" is absolutely not ok and actually reminds me a bit of windows 10...^^
Thank goodness I'll be switching to the xiaomi.eu rom after unlocking, so this stuff is just for a while.
I mean, it does make some sense from their point of view as a company, but it's still annoying for the average customer.
Chinese vendors or any other seller, will sell any products where ever they can to make money, so it's naive of any big company like Samsung or Xiaomi to think they can sell their products to a selective audience. And prohibit the sales to an unwanted group or country.
Places like eBay are littered with these devices with cheap shipping worldwide.
From a buyers point of view who has trusted and bought a product doesn't expect to be spied upon or had barriers put in place to stop customising a device. It's similar to Apple and they way they control the end user on what they can and can't do with their products.
Tech companies aren't doing themselves any favours by behaving the way they do. It forces customers to look for a better product elsewhere.
Where is the Xiaomi.EU rom found ?
Personally for me if the device cannot be unlocked then I will be getting rid of it asap.
Regards :good:
tsam19 said:
Chinese vendors or any other seller, will sell any products where ever they can to make money, so it's naive of any big company like Samsung or Xiaomi to think they can sell their products to a selective audience. And prohibit the sales to an unwanted group or country.
Regards :good:
Click to expand...
Click to collapse
The point is to miminise the risk for the seller to unlock and flash own shady firmwares on the phone before selling.
tsam19 said:
Where is the Xiaomi.EU rom found ?
Click to expand...
Click to collapse
You can find the stable version of the rom here: Link
tsam19 said:
Personally for me if the device cannot be unlocked then I will be getting rid of it asap.
Click to expand...
Click to collapse
Well I'm quite certain that it can be unlocked but it's rather surprising to me that it is so difficult But yeah, if I can't unlock mine (that hasn't even been shipped since I ordered it almost a week ago ) then I'll probably also have to think what to do with it.
Zacki06 , yes others have unlocked their Xiaomi bootloader. However the process is not as straight forward as rooting or unlocking a Samsung bootloader.
If your not aware you have to register for an Mi account, verify it. Use that login to be able to use the unlocking PC software and at the same time register and verify your Mi account / phone number on the Xiaomi device you have bought . Boot into fastboot mode and connect to the Mi servers who verify your device and that is when the time duration kicks in. Either 360 hours or 720 hours message will appear.
As in my experience I am having to use the device for yet another 4 days before I may or may not be allowed to have the bootloader to be unlocked.
All I want to do is root the device. No bootloader unlock, no root!
dannejanne , As for sellers selling Xiaomi devices with flakey firmware already on them, that is quite widespread on eBay and similar for sales places. And if these sellers have registered that particular handset with their details registered to that device for them to have had the bootloader unlocked. Then you or anyone who has bought that device. The new owner will / could have problems when trying to use that device or register it. There are lots of instances when the Xiaomi device can become Mi cloud blocked ( just like Apple icloud) . :good:
tsam19 said:
Zacki06 , yes others have unlocked their Xiaomi bootloader. However the process is not as straight forward as rooting or unlocking a Samsung bootloader.
If your not aware you have to register for an Mi account, verify it. Use that login to be able to use the unlocking PC software and at the same time register and verify your Mi account / phone number on the Xiaomi device you have bought . Boot into fastboot mode and connect to the Mi servers who verify your device and that is when the time duration kicks in. Either 360 hours or 720 hours message will appear.
As in my experience I am having to use the device for yet another 4 days before I may or may not be allowed to have the bootloader to be unlocked.
All I want to do is root the device. No bootloader unlock, no root!
Click to expand...
Click to collapse
I am fully aware of the process, I asked a ton of questions before buying this phone because I was not sure at first if it was worth the wait. Turns out I still didn't learn everything but I still bought it because it is an amazing phone (screen size, battery, etc.). And I'm not new to android It has just been a while since I flashed a custom rom on a decvice, my Honor 5x is running stock at the moment so I was not familiar with all the recent changes that have happened.
I still hope you will try and keep the phone. And as a personal note, I never had a good hand with samsung phones (no problem with tablets). I can't stand AMOLED screens and my experiance shows, that they also don't like me. So all my phones except for the only samsung phone I had for only a week until it broke had an LCD or another kind of screen, but never an amoled
Cheers
A good result at last
After more messages of wait, wait, wait.
Today, finally, at last the job is done !! :good:
I don't know what information Xiaomi have extracted from my handset in order for their servers to allow 'unlock'.
But for anyone else in the same 'waiting position', there is light at the end of the tunnel! :victory:
tsam19 said:
After more messages of wait, wait, wait.
Today, finally, at last the job is done !! :good:
I don't know what information Xiaomi have extracted from my handset in order for their servers to allow 'unlock'.
But for anyone else in the same 'waiting position', there is light at the end of the tunnel! :victory:
Click to expand...
Click to collapse
Good news, congratulations
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
sliding_billy said:
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
Click to expand...
Click to collapse
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
lpiratel said:
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
Click to expand...
Click to collapse
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
sliding_billy said:
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
Click to expand...
Click to collapse
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Suggestion: Call Google support
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Homeboy76 said:
Suggestion: Call Google support
Click to expand...
Click to collapse
Same suggestion as Homeboy at this point. Sorry.
lpiratel said:
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
Click to expand...
Click to collapse
They will rma it, I had a similar issue on my pixel 2 (slot unbootable load error) and they shipped me once right away.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
This just happened to me yesterday. Plugged my Pixel 3 XL in to the wall charger and it immediately went into a bootloop. Nothing would stop it as if it were a hardware issue. Tried to boot into recovery and fastboot but it would immediately bootloop again. Eventually after the battery died I was able to start it up and get it working again. My issue now is that I'm worried it will happen in the future. Didn't plan on upgrading but might have to move to the 4 XL as I use this phone for work.
holy crap - this happened to my wife's phone last week. We ended up getting a Pixel 3A XL for her.
She plugged in her 3XL at around 10% and it started boot looping. I couldnt' do anything with it. The only way I could try and keep it on is blasting it with a flipped can of CO2. I tried everything from factory reset to reflashing. Finally I gave up, and let it sit for a week. Started the phone, and it stayed on for 3 days and let the battery drain again to 10% - plugged the phone it and it started bootlooping again. I'm wondering if the battery just gave out. I wonder if we can see if there is some manufacturing correlation here, maybe all of our phones came from the same batch. I ended up buying in Nov 2018 for Black Friday sale.
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
This *just* happened to me, too! Happened at 330pm EDT right before I had a meeting, so I had to quickly swap the sim into another phone. I'm also out of warranty, and the fact that there are a number of us reporting this same issue in a quick span of time leads me to think this is something on Google's end
Sam Nakamura said:
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Since my original reply to this post, it has happened a couple of more times on my phone. Both times I've noticed the phone gets extremely hot but as soon as the battery dies and the temperature cools for a while, the phone will power back on. My uneducated guess is that something in the processor or battery connection is causing the phone to overheat. Excuse the layman's terms lol.
I too have been a big fan of the Nexus and PIxel lineups over the years but my reason for upgrading to the newer model was always because my old phone had some sort of hardware defect. Galaxy Nexus microphone died, Nexus 6P wouldn't power on, OG PIxel bootlooped. Pixel 2 XL had screen issues. Pixel 3 XL, here we are now lol. Each one lasted me at least over a year and the software is unmatched in my opinion. I'm proud of how far they've come with software, hardware and camera. I just wish they'd put a little "oomph" in their quality control department.
Google doesn't help with bootloop
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
----------------------------------------
I bought my Pixel 3 XL November 2018 from the Google Store.
The phone has been great, but the bootloop started happening with me 4-5 days ago. I had to buy a new phone (yes, I'm stuck in the modern world, unfortunately. i need a phone)
Recovery buttons get to a menu...and then back to the bootloop within 2 seconds, There was little time to press volume buttons etc and no response when I do so on this screen, other than the dead Android with it's hatch open.
But no matter what I do - it goes back to the bootloop within a few seconds.
I spoke w rep from Google for 40 minutes or so, I was polite. No help; he said he could not send me a new or renewed device. he suggested repair shops. Which....the shop told me they do not deal with bootloops, "probably a hardware issue", he said.
So...idea....use my credit card extended warranty! But....for this purchase, strangely...I used PayPal. ughhhh!
Disapointing. Not quite 2 years out of my Pixel, and I was hoping to capitalize on the resale / trade-in value. Not possible now, even a trade in requires a factory wipe.
I did think of using ADB / fastboot, but I do not have time to futz around right now.
You could try Google, but...if you are out of warranty, it is unlikely they will help. Did you buy it with a credit card w extended warranty?
good luck
this just happened to me google is saying that because the phone is out of warranty (by 8 months)
there is nothing they can do about it
at least I have the extended care
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,
I got my daughter a new phone and planned to send in her s9 as AT&T was offering $800 for trade in... She got her new phone set up, then, somehow, her S9 that's been going strong for years, hard bricked itself. I've been all over the internet trying to dig up a solution, but no luck yet....
**Symptoms**
No blinking LEDs
Power + Volume Up: Nothing
Power + Volume Down + Bixby: Nothing (Boot menu screen never comes up)
Plug into computer:
Hear windows USB connect sound
See device in device manager under "Other Devices":"qusb_bulk_cid:0402..."
Unplug from computer:
Hear windows USB disconnect sound
While plugged into comuter:
Power + Vol Down + Bixby: Usb Disconnect / Reconnect Sound, device disappears / reappears from Device Manager (no boot menu)
**What I've tried so far...
FixPpo for Android: Wasted $40. Does not fix hard-bricked phone. If you can't get to the screen you can't get the firmware image onto the phone.
ODIN 3: Does not see the phone in the ID:COM field. Iinstalled the Qualcomm HS-USB drivers and restarted w/ Driver unsigned mode. Phone shows up under Ports (COM & LPT) but ODIN still doesn't see it.
QPST: Can see the phone, but that's all I could seem to do with it.
QFIL: This started out promising, until I needed "Programmer Path" and "Content XML" files, which I can't seem to find for the galaxy S9 (Or perhaps there's a generic Qualcomm one I can't find)
If someone's out there, anywhere, that's been able to resolve this I'd really appreciate some additionl info / links to the right files for QFIL. Or am I SoL if the screen doesn't come up? I feel like we would have seen some symptoms earlier if the screen was starting to burn out vs. just never coming up again...
Thanks in advance,
Steve in Massachusetts, USA
Display dead or software dead
Thanks for the reply...
That's a good question.... I think it's just the software. The phone has been working fine for years, with no degradation or dead pixels, and it wasn't abused or dropped. I've had no luck qith QFIL... was going to attempt Octoplus next, but I don't want to drop $50 for a license if I'm still going to end up bricked. I think QFIL could work if I could get it into download mode, but with no screen that's proving difficult.
stevenlmas said:
Thanks for the reply...
That's a good question.... I think it's just the software. The phone has been working fine for years, with no degradation or dead pixels, and it wasn't abused or dropped. I've had no luck qith QFIL... was going to attempt Octoplus next, but I don't want to drop $50 for a license if I'm still going to end up bricked. I think QFIL could work if I could get it into download mode, but with no screen that's proving difficult.
Click to expand...
Click to collapse
Hey, you need download software for you model s9 if you want flash again
oli231 said:
Hey, you need download software for you model s9 if you want flash again
Click to expand...
Click to collapse
Thanks - I did download QFIL, Odin and QPST, but b/c I can't get PC to see it as a modem, Odin doesn't work. I can't get QFIL to work b/c I can't get into download mode. I just blew $50 on Octoplus, but am still waiting for my license key...
I've put $150 into a dead phone... I probably could have got a used one for that if I looked hard enough.
stevenlmas said:
Thanks - I did download QFIL, Odin and QPST, but b/c I can't get PC to see it as a modem, Odin doesn't work. I can't get QFIL to work b/c I can't get into download mode. I just blew $50 on Octoplus, but am still waiting for my license key...
I've put $150 into a dead phone... I probably could have got a used one for that if I looked hard enough.
Click to expand...
Click to collapse
For my eye motherboard is dead
My S9+ died similarly. Was watching a video and suddenly it crashed and stopped working. Came back to life 2 days later just to die again after an hour. Turns out it was old liquid damage from a month prior swim. Popped it open and cleaned it with isopropyl alcohol and it's working now. If you're feeling confident you can try to open it and see if it's liquid damage or anything that a simple fix such as an alcohol clean might fix. But most likely it's a hardware not a software problem. Good Luck.