Related
Hi everyone. I hope I'm in the right forum. I need some hand-holding big time. This is the first time writing regarding a mobile phone Unlocker so please be gentile with me. I'm a virgin with phone unlocking matters and anything related to Unlocker issues here in the states.
This was all a bit confusing for me. I donated & obtained Olipro's Rhodium Sec / CID / SIM Unlocker to see if I could get Sprint's service to work on this phone. All went well with the unlocker steps 1 thru 3 until I got to the radio portion for the radio file 2.32.00WU.exe I downloaded from xda-developers.com's website. I ran this downloaded file in hopes that I now could get Sprints US service with my T-mobile phone. Weeeel, unfortunately my HTC T-PRO2 never came back to life after this 4th step. It did have a 90% battery charge when I started this whole process.
I purchased this phone brand new from an eBay seller a few weeks ago which was "supposedly" unlocked. I found out that "Unlocked" only meant it could see both T-mobile and AT&T networks, nothing else, even going manual. Useless...
My HTC T-PRO2 has the Win Mobile v6.5 update.
Did I miss something? Is this what is meant by the term "BRICKED"? Did I do something I wasn't supposed to? Did I just lose $20USD? Do I now have a $500 brick?
Thanks.
suzukii said:
Hi everyone. I hope I'm in the right forum. I need some hand-holding big time. This is the first time writing regarding a mobile phone Unlocker so please be gentile with me. I'm a virgin with phone unlocking matters and anything related to Unlocker issues here in the states.
This was all a bit confusing for me. I donated & obtained Olipro's Rhodium Sec / CID / SIM Unlocker to see if I could get Sprint's service to work on this phone. All went well with the unlocker steps 1 thru 3 until I got to the radio portion for the radio file 2.32.00WU.exe I downloaded from xda-developers.com's website. I ran this downloaded file in hopes that I now could get Sprints US service with my T-mobile phone. Weeeel, unfortunately my HTC T-PRO2 never came back to life after this 4th step. It did have a 90% battery charge when I started this whole process.
I purchased this phone brand new from an eBay seller a few weeks ago which was "supposedly" unlocked. I found out that "Unlocked" only meant it could see both T-mobile and AT&T networks, nothing else, even going manual. Useless...
My HTC T-PRO2 has the Win Mobile v6.5 update.
Did I miss something? Is this what is meant by the term "BRICKED"? Did I do something I wasn't supposed to? Did I just lose $20USD? Do I now have a $500 brick?
Thanks.
Click to expand...
Click to collapse
can you enter boot loader..? and i dont think you can use a t-mobil on sprint?
suzukii said:
Hi everyone. I hope I'm in the right forum. I need some hand-holding big time. This is the first time writing regarding a mobile phone Unlocker so please be gentile with me. I'm a virgin with phone unlocking matters and anything related to Unlocker issues here in the states.
This was all a bit confusing for me. I donated & obtained Olipro's Rhodium Sec / CID / SIM Unlocker to see if I could get Sprint's service to work on this phone. All went well with the unlocker steps 1 thru 3 until I got to the radio portion for the radio file 2.32.00WU.exe I downloaded from xda-developers.com's website. I ran this downloaded file in hopes that I now could get Sprints US service with my T-mobile phone. Weeeel, unfortunately my HTC T-PRO2 never came back to life after this 4th step. It did have a 90% battery charge when I started this whole process.
I purchased this phone brand new from an eBay seller a few weeks ago which was "supposedly" unlocked. I found out that "Unlocked" only meant it could see both T-mobile and AT&T networks, nothing else, even going manual. Useless...
My HTC T-PRO2 has the Win Mobile v6.5 update.
Did I miss something? Is this what is meant by the term "BRICKED"? Did I do something I wasn't supposed to? Did I just lose $20USD? Do I now have a $500 brick?
Thanks.
Click to expand...
Click to collapse
"Bricked" means you've rendered the phone useless, and generally unrecoverable, through a bad flash...that's one that either gets horribly corrputed, or when you use the wrong type of ROM, which is what it sounds like you've done. First, you can't use a GSM version of the TP2 on Sprint's CDMA network. Secondly, trying to flash a CDMA ROM on a GSM TP2 can indeed brick the phone.
I hate to say this, but if you had carefully and throughly read and understood all the instructions provided in both the HardSPL and the Rhodium ROM flashing threads, you would have seen the warnings against flashing the wrong type of ROM.
It's possible that you haven't totally killed your phone, but that's definitely a potential outcome here. While you're waiting for someone else to chime in with steps on how to possibly recover it, you might want to go back and read the guide to flashing ROMs on the Rhodium one more time.
sirphunkee said:
"Bricked" means you've rendered the phone useless, and generally unrecoverable, through a bad flash...that's one that either gets horribly corrputed, or when you use the wrong type of ROM, which is what it sounds like you've done. First, you can't use a GSM version of the TP2 on Sprint's CDMA network. Secondly, trying to flash a CDMA ROM on a GSM TP2 can indeed brick the phone.
I hate to say this, but if you had carefully and throughly read and understood all the instructions provided in both the HardSPL and the Rhodium ROM flashing threads, you would have seen the warnings against flashing the wrong type of ROM.
It's possible that you haven't totally killed your phone, but that's definitely a potential outcome here. While you're waiting for someone else to chime in with steps on how to possibly recover it, you might want to go back and read the guide to flashing ROMs on the Rhodium one more time.
Click to expand...
Click to collapse
Hi & thanks sirphunkee for the quick responses guys. I thought I was following the instructions by simply following the downloaded file's, RhodiumUnlocker.exe, simple three steps, the 3rd step requiring me to check the two boxes on the screen and committing the changes. That part all went well. Then it was the radio flashing part which is actually the 4th step. After that step completed & and it stated that my phone would now reboot/restart. It never came back. I now get absolutely nothing coming up on the screen, not even a power light. I plugged the wall charger in & I noticed that the orange power charging light comes on for about 2 minutes then goes away & then nothing for another 1-2 hours.
Any further suggestions are kindly appreciated.
In the meantime I've ordered the HTC HD2 T-mobile, supposedly "Unlocked", too. I'm definitely not going to try anything on that one until I see if this HTC T-PRO2 can be revived if it's not already dead.
djteotancolis said:
can you enter boot loader..? and i dont think you can use a t-mobil on sprint?
Click to expand...
Click to collapse
Hi & thanks djteotancolis.
No. I can't see anything on the screen. There is just a black display.
As for Olipro's Unlocker, they state they can. Or am I reading it wrong?
suzukii said:
In the meantime I've ordered the HTC HD2 T-mobile, supposedly "Unlocked", too. I'm definitely not going to try anything on that one until I see if this HTC T-PRO2 can be revived if it's not already dead.
Click to expand...
Click to collapse
You ordered a t-mobile HD2 to use on Sprint...? That's not possible to do either, it's still a GSM phone, not CDMA.
sirphunkee said:
You ordered a t-mobile HD2 to use on Sprint...? That's not possible to do either, it's still a GSM phone, not CDMA.
Click to expand...
Click to collapse
No. I ordered the T-mobile HD2 for my girl who is quite happy with her T-mobile service. But I would've tried f-ing with it when she's not looking, especially since I'm buying it for her. I know, I know, " If it's not broke, don't fix it". But if I stuck with that theory I would never learn anything new nor buy any new gadgets.
if u want a tp2 with cdma and gsm capabilities you want a sprint tp2 has a simcard slot and all
If you can put in bootloader then try to reflash original rom...
Others have said this fixed for them.... Can't say, never flashed wrong rom...
ultramag69 said:
If you can put in bootloader then try to reflash original rom...
Others have said this fixed for them.... Can't say, never flashed wrong rom...
Click to expand...
Click to collapse
OK this is dum, dum again. I mentioned that there is no screen on this phone now. My PC tries to recognize it for about 1 minute or two, then the phone's hardware signature disappears from my hardware list in Windows 7's Device Manager listing. It didn't do that before.
Now, how do I boot it into a bootloader? Is this another thing I have to buy or is this some magic mode/functionality built into the phone itself?
Thanks.
PS: I wasn't kidding when I said I'm a virgin at this stuff.
suzukii said:
OK this is dum, dum again. I mentioned that there is no screen on this phone now. My PC tries to recognize it for about 1 minute or two, then the phone's hardware signature disappears from my hardware list in Windows 7's Device Manager listing. It didn't do that before.
Now, how do I boot it into a bootloader? Is this another thing I have to buy or is this some magic mode/functionality built into the phone itself?
Thanks.
PS: I wasn't kidding when I said I'm a virgin at this stuff.
Click to expand...
Click to collapse
bootloader is built into the phone, nothing to download or buy.
hold the volume down button while pressing the power button up top when the phone is off.
If you can get this you might be able to flash the appropriate Rom and radio for the phone.
scariola said:
bootloader is built into the phone, nothing to download or buy.
hold the volume down button while pressing the power button up top when the phone is off.
If you can get this you might be able to flash the appropriate Rom and radio for the phone.
Click to expand...
Click to collapse
Thanks for the suggestion.
Nope. That didn't work. The orange LED comes on when I press the power button without pressing any buttons with or without pressing the Volume-Down button. Then every 2-3 minutes the phone tries to register itself in Windows' Device Manager showing up as "Qualcomm CDMA Technologies MSM" with an exclamation point under "Other Devices". This state lasts for about 1 full minute then it disappears from Device Manager in windows.
suzukii said:
Thanks for the suggestion.
Nope. That didn't work. The orange LED comes on when I press the power button without pressing any buttons with or without pressing the Volume-Down button. Then every 2-3 minutes the phone tries to register itself in Windows' Device Manager showing up as "Qualcomm CDMA Technologies MSM" with an exclamation point under "Other Devices". This state lasts for about 1 full minute then it disappears from Device Manager in windows.
Click to expand...
Click to collapse
if your have any friend i your area who knows aabout flashing...they could help you
i have the same problem like you i'm got a job in a company and they use sprint...so now i need a phone thats sprint and i need to trade my tilt2
djteotancolis said:
if your have any friend i your area who knows aabout flashing...they could help you
i have the same problem like you i'm got a job in a company and they use sprint...so now i need a phone thats sprint and i need to trade my tilt2
Click to expand...
Click to collapse
Nope. OK, then I'm bricked!!!! Thanks though.
djteotancolis said:
if your have any friend i your area who knows aabout flashing...they could help you
i have the same problem like you i'm got a job in a company and they use sprint...so now i need a phone thats sprint and i need to trade my tilt2
Click to expand...
Click to collapse
Thanks for trying to help dude.
suzukii said:
Nope. That didn't work. The orange LED comes on when I press the power button without pressing any buttons with or without pressing the Volume-Down button. Then every 2-3 minutes the phone tries to register itself in Windows' Device Manager showing up as "Qualcomm CDMA Technologies MSM" with an exclamation point under "Other Devices". This state lasts for about 1 full minute then it disappears from Device Manager in windows.
Click to expand...
Click to collapse
Did you try running the flash file anyway? It isn't neccessary for the pc to recognise the phone, the flash file will still run.
ultramag69 said:
Did you try running the flash file anyway? It isn't neccessary for the pc to recognise the phone, the flash file will still run.
Click to expand...
Click to collapse
Yep, tried running the STEP-1/Hard-SPL app again & now the app. just freezes. I left it running for about 30 minutes & it never came back with any visual response even thought the PC doesn't recognize it.
I even tried the following Hard reset Steps from the wiki.xda-developers.com section for this phone:
* With the device turned off, press and hold the TALK/SEND and END/HANG UP buttons, then the press and hold the POWER button until you see this message on the screen.
* "This operation will delete all your personal data, and reset all settings to manufacturer default. Press ?VolUp to restore manufacturer default, or press other keys to cancel."
* Release the TALK/SEND, END and POWER buttons.
* Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
If you have a Telus or Verizon TP2 (Sprint not tested but likely the same), the combination is different.
* Power off the phone using the 'end' key.
* Hold 'volume down' and 'send', the press 'end' till you see blue text. Follow hard reset prompts.
N-A-D-A...
I think it's a dead duck.
You took a CDMA radio and flashed it to a phone that was made for GSM.
GSM - T-Mobile & AT&T
CDMA - Sprint & Verizon
You don't need to use Hard SPL again.Try to install a GSM radio and see what happens. When it's reading for that first minute, run the GSM radio installer.
If you can't get into bootloader you may be F-ed.
For kicks try to install a GSM rom if all else fails and then try the GSM radio again.
FYI - From my knowledge you can't cross over phone's using the opposite technologies.
SeanGotti said:
You took a CDMA radio and flashed it to a phone that was made for GSM.
GSM - T-Mobile & AT&T
CDMA - Sprint & Verizon
You don't need to use Hard SPL again.Try to install a GSM radio and see what happens. When it's reading for that first minute, run the GSM radio installer.
If you can't get into bootloader you may be F-ed.
For kicks try to install a GSM rom if all else fails and then try the GSM radio again.
FYI - From my knowledge you can't cross over phone's using the opposite technologies.
Click to expand...
Click to collapse
Well that's not what the guys over at rhodium.htc-unlocks.com's SIM Unlocker says. I tried it, now I have a fried phone HTC TOUCH PRO2. ...and I'm out $20US. I did write them before I purchased their Unlocker, but I am still awaiting an answer which is now kinda too late for a response for me.
Moving on, though. They don't have a GSM Radioooo unlocker for me to be able to reflash this dead puppy. Oh, well. Poor me.
hi there.
i have pb like u
phone tp2 just detecting @cdma system in winxp
Ports(com<p)----> Generic HS-USB Diagnostics(com2)
what it means?
br Komi
Hi,
I first posted this help request on Nokia Support Discussions on August 13, but amazingly I received no reply to date (I can't insert the link since I have no privileges for that as a new user).
I am experimenting a very weird and annoying problem with my Lumia 900. Some weeks ago, the volume level during the phone call became suddenly very low and barely noticeable. I can hardly hear the other speaker both calling and receiving a phone call. Apparently this behaviour is restricted to the phone call feature in normal mode. If I press the loudspeaker button, for example, I can hear the conversation perfectly as usual. Same using my earpiece: I can hear and talk without any problem. Moreover, the audio output appears to be OK outside the phone call itself: when using apps, music, games or any other feature except the phone call, I can't spot anything abnormal in the volume level, everything appears to work properly.
I would like to point out that:
1) the volume level during the call is set to the max. level as usual (10/10)
2) the master volume of the device, as set though both right-hand buttons, is set as usual to the max. level (30/30).
3) I turned off and on the device, I removed and reinserted the SIM card many times since then, unfortunately the problem persists
4) I did not notice any other problem before this happened, nor the device suffered any "catastrophic" event (such as drop, water or similar).
Basically, I can only hear a speaker during a phone call either keeping the loudspeaker always on or using the earpiece. It's like my call volume were set to 1 or 2, while it is actually set to 10.
Can you help me determine whether this issue may be software or hardware related in first place? Unfortunately bringing it to the Nokia Customer Care is not the first option for me at the moment. I bought my device in Europe, but I am currently in South America. I may consider using the local Nokia Customer Care and paying a fee, but first I would like some clarifications from engineers or advanced users.
Finally, a guy on another forum suggested me a hard reset. I confess I never did that before, is there any step-by-step instruction for this? Or does it make sense to wait for the next software update through Zune (currently I have 8779.12201, a new update however has been already released and should be available for my language within days or weeks).
Thank you very much in advance for any useful information
You can wait for the update or try a hard reset. A reset will restore you phone to factory fresh, so you will lose everything currently stored on the phone; photos, apps, messages, settings, etc. So be sure to sync with Zune to backup photos and videos first, and sync with your Live ID mail account to sync contacts. Restoring email accounts, contacts, apps and media are all easy, but could take a few hours (depending on how many apps you have). If you prepare for the reset (as you can) it makes things easier.
If your other option is to send you phone out for service, that could take weeks. So while painful, rh hard reset is the "quick" fix. If your volume problem persists after the hard reset, then you know its hardware related (be sure to check before and after installing any apps to eliminate any possibilities). If so, and after telling Nokia Care that a hard reset didn't solve the problem, it might just get you a replacement. Quicker than sending it out for an inspection. Hope you get it worked out.
Sent from my Lumia 900 using Board Express Pro
It makes no sense to wait. I assume you are still under your initial warranty, so do the hard reset...after, as jimski says, you save off any pics or music specific to the device. You will lose SMS and SMS history , and any game scores.
Use reinstalled to reinstall apps after the reset, to get or apps installed more quickly.
Hard reset is a harsh way to test this out. However, if you test the phone before reinstalling apps, you cut to the chase real quick. If this is a hardware issue, do NOT wait for a fix. Replace the device and be done with it.
Good luck
First of all, many thanks to you both for your kind reply. It is refreshing to finally have someone listening to you when you really need.
It appears that a hard reset should be the first step to do in any case. While I have no idea when the next update with Zune will be available for my language, I can try to solve the problem alone. Is there any tested step-by step procedure for flashing Lumia 900 or Lumia devices in general? If yes, would you please point me there with a link?
Both your replies convinced me that bringing the phone to the Nokia Customer Care here in South America is definitely not a good idea. Yes, I am still under my initial warranty, I bought my device end of June, the problem is that I bought it in Europe, so my warranty is not supposed to cover me here. If the issue is at hardware level, there is very little they can do here for me without to exburse a lot of money, not to talk about the waste of time. Should the hard reset not work, I guess I'll have to wait for my next travel to Europe or having someone bringing it there for me to have my device replaced.
Anyway, I will let you now about any progress.
Many thanks for your help.
barrel owl said:
First of all, many thanks to you both for your kind reply. It is refreshing to finally have someone listening to you when you really need.
It appears that a hard reset should be the first step to do in any case. While I have no idea when the next update with Zune will be available for my language, I can try to solve the problem alone. Is there any tested step-by step procedure for flashing Lumia 900 or Lumia devices in general? If yes, would you please point me there with a link?
Both your replies convinced me that bringing the phone to the Nokia Customer Care here in South America is definitely not a good idea. Yes, I am still under my initial warranty, I bought my device end of June, the problem is that I bought it in Europe, so my warranty is not supposed to cover me here. If the issue is at hardware level, there is very little they can do here for me without to exburse a lot of money, not to talk about the waste of time. Should the hard reset not work, I guess I'll have to wait for my next travel to Europe or having someone bringing it there for me to have my device replaced.
Anyway, I will let you now about any progress.
Many thanks for your help.
Click to expand...
Click to collapse
I'll start by saying, the Hard Reset will not force you to re-flash your phone. It just resets it back to stock settings. This is in fact the easiest and best way to try to resolve problems with your phone. To do so, go into your settings menu. Go to About, and scroll down to 'reset your phone', tap that, and follow instructions. This will delete all your data and messages, so be sure you've backed up first.
If you Absolutely NEED to flash your phone back to OEM Stock, you can use my link here: http://forum.xda-developers.com/showthread.php?t=1605144
One other thing to check (and what I suspect to be the problem) is the speaker itself. It sounds to me like you either have a failing speaker, or something is in the speaker hole. Look closely at it and see if there is dirt/lint/chocolate/peanuts/earwax/etc packed in the speaker grill. It's pretty easy for this to happen. Try blowing it out with canned air and see if that helps. Otherwise, it's probable that the speaker is going out or the connection is failing.
Good Luck, and be sure you decide before your warranty is gone. Send it off ASAP if the above items don't help. PS: Flashing back to stock may void your warranty, so decide if you want to take that chance, rather than wait for repair to return it.
Thank you very much again for your time. And yes, I had found that link in this forum and was already duly reading it. I just did not post this because I still have no privileges to post links.
SuperSport said:
One other thing to check (and what I suspect to be the problem) is the speaker itself. It sounds to me like you either have a failing speaker, or something is in the speaker hole. Look closely at it and see if there is dirt/lint/chocolate/peanuts/earwax/etc packed in the speaker grill. It's pretty easy for this to happen. Try blowing it out with canned air and see if that helps. Otherwise, it's probable that the speaker is going out or the connection is failing.
Click to expand...
Click to collapse
One last question. Would you please clarify whether Lumia 900 has one or more speakers? The speaker grill on the bottom of the device has apparently no noticeable dirt or other foreign material inside it, anyway I will try blow it with air, maybe it will help. One thing I can't explain to me is why everything appears to be OK with the volume level except during phone calls. As I mentioned in my first post, the audio output with music, apps, games etc. is normal. When I use the loudspeaker in phone calls, no problem. So the question: is there any other speaker in Lumia 900 which is used for phone calls, for example on the top of the device? I don't think so, but if yes, this would definitely point to a hardware problem of THAT speaker.
Anyway, I will let you know about any progress.
Kind regards
barrel owl said:
Thank you very much again for your time. And yes, I had found that link in this forum and was already duly reading it. I just did not post this because I still have no privileges to post links.
One last question. Would you please clarify whether Lumia 900 has one or more speakers? The speaker grill on the bottom of the device has apparently no noticeable dirt or other foreign material inside it, anyway I will try blow it with air, maybe it will help. One thing I can't explain to me is why everything appears to be OK with the volume level except during phone calls. As I mentioned in my first post, the audio output with music, apps, games etc. is normal. When I use the loudspeaker in phone calls, no problem. So the question: is there any other speaker in Lumia 900 which is used for phone calls, for example on the top of the device? I don't think so, but if yes, this would definitely point to a hardware problem of THAT speaker.
Anyway, I will let you know about any progress.
Kind regards
Click to expand...
Click to collapse
There are in fact two different speaker outlets. There's the one at the bottom which is speakerphone, games, apps, etc... Then there is the one at the top in that little slot. That's the one I suspect is either clogged, or going bad.
EDIT: Do you have a case installed that might be blocking that speaker?
SuperSport said:
There are in fact two different speaker outlets. There's the one at the bottom which is speakerphone, games, apps, etc... Then there is the one at the top in that little slot. That's the one I suspect is either clogged, or going bad.
Click to expand...
Click to collapse
Got it. That makes (unfortunately) perfect sense. Chances are then that the issue is actually at hardware level
SuperSport said:
EDIT: Do you have a case installed that might be blocking that speaker?
Click to expand...
Click to collapse
No case.
Thanks a lot
Same issue with my lumia asian rom...
Sent from my GT-I9300 using xda app-developers app
Wow! I thought I was going crazy....'cause I've had the same issues for the past few months. When I got my Lumia 900, I was pleasantly surprised that my in-call volume actually DIDN'T need to be set to max (10/10), and I usually dialed it back to 8/10. Nice...but it began to get quiet so that even on 10/10 it was difficult to hear callers -- especially if I was standing outside. I thought it had to do with a ROM or firmware update, but so few people noted the same problem that I just assumed my phone was faulty.
<sigh>
Anyhow, I found this thread just 30 minutes ago, read through your story, and (for whatever reason) thought it thru more fully. I realized that since I keep my phone in my pocket, maybe the thin ear speaker grill (just above the screen) is full of lint?!? I grabbed a soft, dry toothbrush and took about 30 seconds to brush it out. I could actually see the debris clearing away. Made a test phone call and voila.........my earpiece volume is loud once again! Easy fix. Almost too easy
I hope this helps.
did you ever resolved the problem?
Hi guys love the forum finally joined !
So i recently bought ebay Lumia 900 they are going for cheap =) loving it!
In my case the speaker was working great actually the first week it was way too loud kept it under 7/10 all of a sudden now
i cant hear almost anything below 8/10 and when i go all the way to 10/10 it sounds muffled like a blown speaker already tried cleaning the grill
very carefully it had dust but that didn't help and also erased averything from the about settings
.
Anymore suggestions? Im in the latest update and obviously no warranty .
Thanks :cyclops:
Hi
Are there any updates on this problem,because I am also experiencing this and I think it happened after I did an update with Zune .
Thanks
Hard Reset to Nokia Lumia to address low volume during calls
How do you to a hard reset of the phone. I am ready to try that to solve the low volume problem. I literally took the phone out of the box on Thursday last week. I am getting very frustrated.
Thanks
Hello guys,
This is my very first post in this really nice forum. It helped me alot to understand more about my WP mobiles.
I fully unlocked and installed a custom rom on my lumia 710 and im really amazed by my phone right now so i would thank you guys so much for the amazing work u have been doing.
Now im trying to do the same for my wifes lumia 900 At&t but whenever i try to volume up + power and plug in it wont show anything if its qualcom or Dload, im using Win 7 and it keeps making the beep as its trying to find new device but wont find anything and will just keep beeping like that, i would really like to know at least if this phone is fully unlocked or not , if someone knows what my issue is please help me out since wife wont let me in peace after she saw my lumia 710 :laugh: .
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 tool​Konfuzion for directing me to his thread​Much 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.
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.