Related
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
redoxy said:
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
Click to expand...
Click to collapse
try install the certificate again to see if works
jgcaap said:
try install the certificate again to see if works
Click to expand...
Click to collapse
tried that again but still same error message
thanks anyway
redoxy said:
tried that again but still same error message
thanks anyway
Click to expand...
Click to collapse
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Heathcliff74 said:
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Click to expand...
Click to collapse
Yep did that also. and not just once but multiple times.
Wonder why this is happening
redoxy said:
Yep did that also. and not just once but multiple times.
Wonder why this is happening
Click to expand...
Click to collapse
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
gfreek said:
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
Click to expand...
Click to collapse
Did Exactly as you instructed and it worked.
thanks
Got my 5X earlier last week, but I haven't been able to get the MDB08I OTA update. Anyone else not getting it? Is there anyway to force it?
Thanks!
You can sideload it if you can download the ota file. Google rolls it out based on some algorithm based on IMEI. You'll get it eventually.
Still waiting for my USB-C to A cable to come in. Just wasn't sure if something else was up with my phone. Didn't know the rollout was based on IMEI; the more you know =)
Thanks!
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Mine was telling me there was an update as soon as I unboxed it and turned the WiFi on. Weird that you aren't getting the update.
On another side note. I've had no problem with getting adb to work.
I've had my 5x since last Monday (19th October) and I don't have it yet either. I'm in the UK.
I'm on MDA89E after getting from cpw yestaday and unboxing didn't get any update yet but loving the 5x so far
Sent from my Nexus 5X using Tapatalk
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
I thought the point of Nexus range was there was no delay due to carriers?
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
Nope. I had no SIM installed when I was alerted to the update. Has nothing to do with SIM or carrier.
Does the bootloader have to be locked to get otas?
nyjumpman said:
Does the bootloader have to be locked to get otas?
Click to expand...
Click to collapse
Probably it's OK to be unlocked, but probably it's not OK to have a custom recovery if you want OTA's. (and want them installed). Best bet is to download B08I and install it via the batch file.
To some other poster in this thread asking about being unable to see phone from adb when recovery is booted up: If it's stock recovery, that makes sense, but if it's custom recovery, you should see adb devices having output.
oxfordmark said:
I thought the point of Nexus range was there was no delay due to carriers?
Click to expand...
Click to collapse
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Like I posted earlier. I was alerted to the update and had no SIM installed.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Oh right, must be for things like wifi calling.
manilaboy1vic said:
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Click to expand...
Click to collapse
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
http://www.droid-life.com/2015/10/21/nexus-5x-receiving-update-today-to-build-mdb08i/
Just followed these instructions and the associated links and 30 minutes later ... updated FTW.
Was having problems, at first, with my phone to being recognized. Either the initial usb 2.0 port was jacked or not, I switched to another port and made sure the cable was seated properly and it was picked up right away.
My N5X on AT&T got this update last Tuesday when I got the phone. My girlfriends N5X on Verizon did not yet get the update OTA. Might have to do with carrier?
I always set my phone up without a SIM. Got the update right away during the set up process.
Jexx11 said:
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
Click to expand...
Click to collapse
thanks.. that cmd worked..
Android is upgrading... (w00t)
was easier for me to get it going on linux ubuntu.. now onto the hotspot tutorial
Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root
Yosh2897 said:
Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root
Click to expand...
Click to collapse
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man
Badger50 said:
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man
Click to expand...
Click to collapse
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk
Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Click to expand...
Click to collapse
Sorry man. KA requires root, so that's not a possibility either :fingers-crossed:
Yeah I made the same mistake , grabbed a XL 2 for 200 and realized it was a vzw variant
Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background
Az Biker said:
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background
Click to expand...
Click to collapse
Please tell me configuration on your greenify, i will enable access user from adb, and how to turn off running in background? Cause it's minimal option, maybe 10 app on check background, not at all
Sent from my Pixel 2 using XDA Labs
And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs
Yosh2897 said:
And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.
Yehudah said:
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.
Click to expand...
Click to collapse
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel
Yosh2897 said:
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel
Click to expand...
Click to collapse
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...
CyberpodS2 said:
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...
Click to expand...
Click to collapse
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?
I feel you Cyberpod...but, looking through this specific thread...I don't believe he's actually stated outright or confirmed that it is in actuality a Verizon variant...
I would say that's first and foremost OP...I know you are rather impatient about it, and tried some things, and intend "...not gonna paying attention about this...", but you really should verify (for sure) if you have the proper variant.
Also, merely reading through this specific thread, he may simply want to talk/contact Google Pixel support but didn't know how... Although, even the smallest bit of effort would easily find the answer; I'll "throw you a bone"... you will find it here: https://support.google.com/pixelphone/?hl=en#topic=7078250&contact=1
But, to be blunt, if you are going to ask for help here on XDA, we at the very least expect the bare minimum of effort (without complaint) and not handing everything "on a silver platter"... this is just not that kind of place...
UPDATE: Post #12 seemed to have been input and came in a minute before this one (mine)... but see! Verifying if it's a Verizon variant was never established and needs to be...
bro, why i make this thread and try to ask you all,
i got command like this
C:\adb>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: -0.000s
C:\adb>fastboot --version
fastboot version eac51f2bb6a8-android
C:\adb>fastboot flashing unlock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash unlock
unknown partition 'unlock'
error: cannot determine image filename for 'unlock'
C:\adb>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
Yosh2897 said:
bro, why i make this thread and try to ask you all,
i got command like this
Click to expand...
Click to collapse
What answer are you expecting? It's not possible. Verizon locks the bootloader and nobody has found away around that. Either live with that or sell your phone and get one that's unlocked.
Yosh2897 said:
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?
Click to expand...
Click to collapse
Constantly repeating a task and expecting the result to change is a sign of insanity. While I don't think you've lost your mind - yet - you're rapidly descending to that level. I've said this before and I'll say it again. If you want root you do not buy a Verizon device!
Since you apparently have a Verizon device, your options are to sell it or live without root, which actually is doable. No exploit has been found to bypass the bootloader encryption, and brute forcing the encryption itself will take a period of time greater than the age of the universe.
I never expect to get bundling device by verizon, but, indonesia doesn't have official store, all of them selling this phone without knowing what type they got and just sell to buyer, to be honest, hard to find a sparepart, warranty for this device, so the option, i just do by myself. I'm sorry if pushing you all, and always ask about this things. Have a nice day mate.
I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
jacobsface said:
I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
Click to expand...
Click to collapse
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
v12xke said:
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
Click to expand...
Click to collapse
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Yeah, I haven't received Dec OTA either. I have a BL unlocked 3XL from Google Fi and normally flash the FULL factory image but I took the OTA last month and like that process better so I'll keep waiting...
jacobsface said:
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Click to expand...
Click to collapse
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Just giving my 2 cents. Stock 3XL. No update here yet either.
v12xke said:
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Click to expand...
Click to collapse
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
jacobsface said:
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
Click to expand...
Click to collapse
Happy to see you were able to get it done. After a couple of times it just becomes routine. As for recovery button press, we can't blame that one on Verizon. That is the how the stock recovery works even on unlocked phones directly from Google. Don't feel bad, lots of people get tripped up on that too. Cheers :good:
Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.