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
Related
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
randy6644 said:
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
Click to expand...
Click to collapse
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
charesa39 said:
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
Click to expand...
Click to collapse
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
brando56894 said:
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
Click to expand...
Click to collapse
I think the problem mentioned should be a software issue. As in those two threads , they are not able to boot up the device simply by factory resetting it. And they failed to flash the factory image to the bricked device since it's locked.
randy6644 said:
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
Click to expand...
Click to collapse
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
brando56894 said:
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
randy6644 said:
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
Click to expand...
Click to collapse
In that case, Android Device Manager comes into play and allows you to beef up your security.
Sent from my Pixel C using Tapatalk
I've done just about everything. There's a log cat below. EVERY ROM, EVERY KERNEL STOCK OR CUSTOM, this issue is there after the first reboot. Im only going to answer every question that goes like "have you tried...." With a full rundown of what I did and results. I will remind I've tried every custom nougat rom, stock or custom and I've tried stock marshmallow rom to. Also some roms haven't even had sound on first boot. Some roms will work for a bit then they will do a soft reboot that takes 30-45 minutes to complete. Then have no sound. I'm open to taking my phone apart since my screen is fu*ked up. Im begging at this point I love this phone, I've had it for 2 months, I don't want to have to buy another one.
Tried unbrick tool yet? That may have a slightly different effect than just flashing stock ROM (as it completely nukes the device and installs everything again).
Anyways, you may have a hardware issue. In that case taking the phone apart won't do much ... You can only check the connections, that's about it.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Tried unbrick tool yet? That may have a slightly different effect than just flashing stock ROM (as it completely nukes the device and installs everything again).
Anyways, you may have a hardware issue. In that case taking the phone apart won't do much ... You can only check the connections, that's about it.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
I did actually brick it awhile back trying to solve that damn sound issue. I used the mega unbrick guide to fix it, I can try again. Cause hell who knows it might fix it. Thanks for the recommendations.
Found out it is hardware i narrowed it to the aux port board which is what the fingerprint sensor, microphone, speaker connect to. I'm ordering a new part tomorrow for it
Did you find any solution? Im having the same issue and trying to figure out how to fix tihs
Dlind said:
Found out it is hardware i narrowed it to the aux port board which is what the fingerprint sensor, microphone, speaker connect to. I'm ordering a new part tomorrow for it
Click to expand...
Click to collapse
Please give me the link to buy. Im having same issue too. And i think its hardware
xsetiadi said:
Please give me the link to buy. Im having same issue too. And i think its hardware
Click to expand...
Click to collapse
Well, when I bought the new part and replaced it, it didn't do anything. But I can still give you a link, I need up getting a htc 10 cause I was sick of the phones bs. https://m.ebay.com/itm/OEM-Earphone...%3Ac0cbdf2615e0ab10a81ff986ffd94c65%7Ciid%3A6
Dlind said:
Well, when I bought the new part and replaced it, it didn't do anything. But I can still give you a link, I need up getting a htc 10 cause I was sick of the phones bs. https://m.ebay.com/itm/OEM-Earphone...%3Ac0cbdf2615e0ab10a81ff986ffd94c65%7Ciid%3A6
Click to expand...
Click to collapse
You mean this not rix the problem?
I
xsetiadi said:
You mean this not rix the problem?
Click to expand...
Click to collapse
It could for you, but it didn't change a thing for me. Every phones diffrent.
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
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.
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.
roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.
Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.
verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port
Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.
Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??
liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try