Related
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Pomaraczowy said:
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Sent from my Honor 9 using XDA Labs
hujialun2002 said:
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Click to expand...
Click to collapse
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Pomaraczowy said:
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Click to expand...
Click to collapse
We have already had a taste of Pie now,so for anyone who dont care EMUI 9 they can simply do with Treble Pie GSIs.Who cares about the ugly UI of Huawei?PE 9.0 and OpenKirin Pie AOSP are both doing quite great.
Sent from my Honor 9 using XDA Labs
Pomaraczowy said:
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
streetu said:
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
Click to expand...
Click to collapse
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Pomaraczowy said:
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Click to expand...
Click to collapse
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
streetu said:
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
Click to expand...
Click to collapse
Probably gonna do it soon.
Thanks for help.
For now, I'm up to B372, and still able to do whatever I want, fyi.
Keep on updating... and supporting the Apple wannabees of the Android world. They learned and stole the ideas they wanted from the community and now will completely lock out the devices, bootloaders, root methods, anti-rollback measures, etc.
Oh, and as for that "spying" part? Just search for "Huawei D.U.B.A.I.". Every single aspect, action, usage and telemetry of your device is logged and sent to Huawei's Big Data Analytics servers, and it's embedded on kernel and can't be disabled. Most i could do on my kernel was disabling it on GPU framework, but the rest remains. If i turn it off on kernel or eliminate it, the mobile comms framework is killed and sim card doesn't even get activated, turning your device into a small tablet at most... so you either accept it or get yourself another phone.
Since using Treble Roms gets rid of the "system" part of EMUI, like their store, services, etc, it's possible that the Analytics part is somewhat suppressed but i can't be sure of that.
My advice is, stop updating EMUI and go Treble. Or just sell your device and get another. Or just resign to the new Huawei's reality and forget this community.
I just got done chatting with Nokia support (both chat and email) about getting the required unlock.key file that you need to unlock the bootloader for the Nokia 8, which they said they would unlock. First, a little background. The process Nokia wants you to go through to get the file is to download an apk of theirs which will analyze your phone a bit and then generate a code which you put into a form on their website to get the file emailed to you. Rather clunky but alright. I do so, but then I get an error when the apk runs. "Error messages: Device not support." Very well. I then talk to support. Chat had no idea how to fix it. Email fared just as well. I will copypaste the entire exchange. (Save for the original email I sent as I forgot to save it. Sorry about that.)
Nokia said:
Welcome to Nokia Mobile Care ,
Thank you for your time writing us and thanks for using our Nokia 8 products. We understand why you came to us thats why we will try our best to assist you !
In order to assist you better and more accurately we would like you to provide us a little bit more information :
- Could you please provide us the screenshot with the error message? Thank in advance!
- How are you unlocking bootloader ? in which step are you at ?
Additionally we will provide you the steps unlocking bootloader below :
1-Go to https://www.nokia.com/en_int/phones/bootloader, accept the terms and sign in
2-Scroll down until you see the phone validation form.
3-Download and install NokiaPhoneUnlockBootloader.apk, there is an included link on the page.
4-You will receive a validation code that must be entered into the form on the website along with the email used, note the validation code is only valid for 30 minutes.
5-You will receive an email containing a link to download a file, the name will contain your IMEI number and have an extension .key, it should be renamed to "unlock.key"
6-Start the phone in download mode.
7-Download and set up ADB
8-Start an ADB shell and run the following commands, unlock.key must be in the platform-tools directory from the ADB setup
fastboot flash unlock unlock.key
fastboot oem unlock
You should then see
Unlock success!
9-then run the command
fastboot reboot
Remember that you are important to us and we're looking forward to your response.
If you have questions or face any difficulties, please contact us at your convenience.
Wish you all the best.
Best regards,
Nokia Mobile Care
-----------------------------------------------------------------------------------------------------------------------------------
© 2019 HMD global All rights reserved.
Nokia is a registered trademark of Nokia Corporation.
HMD global is the exclusive licensee of the Nokia brand for phones and tablets.
-----------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
S5Guy said:
I have downloaded the official apk from Nokia to get the verification code to put on the website form. When I launch the app and put in my email though, it merely shows the error message shown in the attachment.
Click to expand...
Click to collapse
Nokia said:
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.
I can see that you are trying to unlock your phone's bootloader, you have already downloaded the app and you are receiving the message saying that "device not supported".
HMD Global allows the bootloader on certain Nokia phones to be unlocked, allowing for customizations. This feature is intended for developers only.
Once the device is being unlocked, it is no longer covered by the manufacturer's limited warranty provided by HMD Global.
If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message "Device not Supported" this mean that your device is not supported to have the bootloader unlocked.
If you are facing some issue with your phone, you can send it to a repair center, out specialists has the information on how to handle it. Note that Nokia only provides the possibilities to unlock bootloader to developers.
We hope that the above information is useful.
Any other question you may have are always welcome. Please feel free to contact us again.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
S5Guy said:
"If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message 'Device not Supported' this mean that your device is not supported to have the bootloader unlocked."
^ This is not correct at all. At least for the Nokia 8. https://twitter.com/sarvikas/status/1045298106818949120
I have followed the prior instructions rigorously, but since the apk does not work, I must ask you for the needed "unlock.key" file. I am very well aware of the consequences of unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for getting back to us. I'm sorry to hear that the previous solutions didn't make any difference.
I can see that you are not happy about the previous answer you have had. I understand that can be frustrating sometimes.
As explained before the allowing will depend on many factors, as market, for example. If you have the app running well, if you have tried all the steps to have your bootloader unlocked and still receiving the message "device not supported" there is no other reason than that the app itself is saying the device you are trying to unlock is not supported.
Did you tried to uninstall and reinstall the app? did you tried to restart the process?
Note that here we are a customer care for technical issues customer may face with their device, we do not produce the rules or the policy we just follow then. There is no other advise to you at this moment.
If you have any other question not related to bootloader, please feel free to get back to us any time.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
-
So basically, to sum up, if you're thinking of unlocking the bootloader at all for any reason, steer WAY CLEAR of this phone. My phone may for whatever reason have fallen through the cracks perhaps, but a lot more people than me are reporting this issue. On top of that, I've checked my phone's IMEI to be sure it wasn't stolen or fake and it was perfectly fine and legit. Honestly, I hate that I have to post this message because the Nokia 8 actually has some features I like that aren't really on other phones, but because of this software travesty, I can't recommend it at all.
Nokia, if you're out there, this is a disgrace in both software and support. Please fix this.
Hi
I have the Nokia 8 TA-1012 but I have not tried to unlock the BL. I am currently on Pie so see no reason for doing so as I am happy with the OS.
As most people do not buy a phone to modify the OS I see no problem not recommending this phone for normal use.
Sent from my TA-1012 using Tapatalk
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
The only solution that doesn't rely on Nokia might be to tear apart their apk and use a rooted phone or an emulator to fake the properties it reads, so the app thinks it runs on a security patch that is supported.
But this approach requires people to send their IMEI to random people on the internet so there are additional risks.
ironman38102 said:
While I didn't unlock through official methods
Click to expand...
Click to collapse
I have heard someone else mention this as well. How did you unofficially unlock the bootloader?
THMSP said:
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
Click to expand...
Click to collapse
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
frankoid said:
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
THMSP said:
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
Click to expand...
Click to collapse
I'm your man. With nothing left to lose. o_o Will report back with the results ASAP.
I'm back and with bad news. The update process via the recovery menu seemed to run into an error where it complained about the timestamp on the update zip being too old, but for whatever reason, it proceeded anyway. OK, wiped the data (what data?) and did a factory reset, now it's booting up. I check the system information to be sure and it is 8.1.0. Installed the apk. Ran it. AND THEN...
Device not support.
I'm gonna try this with the zip mentioned in frankoid's post and do another update again, but honestly, it looks like Nokia just wants to be an asshole at this point.
!!!!!!!!!!!!!!! SUCCESS !!!!!!!!!!!!!!!!!!
This update zip is what you need: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
Thank you apple boy for this topic.
100% troll.
S5Guy said:
*snip*
Click to expand...
Click to collapse
Great to hear that you got it working! My zip likely not worked because it just throws you back half a year (where official unlock didn't even exist) - you would have to update until you find a security patch that works.
But if November patch worked for you thats great! Since the May OTA worked for you that also means that people could choose to use the unofficial (paid) unlock method so Nokia doesn't know about whether they are locked or unlocked (warranty reasons).
Those OTA zips are model-agnostic btw. Whether they say TA-1004 or TA-1012 doesn't matter, they are the same. Only google makes that distinction on their servers, the software doesn't.
foxbatul said:
Thank you apple boy for this topic.
100% troll.
Click to expand...
Click to collapse
What's less useful...
A detailed set of instructions aimed at helping other forum members
... Or your post?
On mine that option is greyed out...
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
theviking33 said:
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
Click to expand...
Click to collapse
Did you touch the option in the past at all? If you did, it will be greyed out. As long as it's switched on though, it's fine. (I heard it will "ungrey" itself after a week, but there you go.)
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
theviking33 said:
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
Click to expand...
Click to collapse
I'm assuming you have a brand new TA-1004? And yeah, you should have gotten back a code long ago.
Try some of these options. https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
It could be though that it's just been flat out disabled due to region or whatever. If the solutions in the above link don't work, try downgrading back anyway and then using the apk as explained in an earlier post of mine.
It seems to be a case of "flat out disabled". I did a factory reset already and this setting won't change. I actually bought 2 of those phones and on both is the same.
How do I see or find out what region they are for?
And for the booloader, seems I have to go the old fashion way now...
---------- Post added at 11:38 ---------- Previous post was at 11:25 ----------
I have the TA-1004 DS which is International. So wouldn't understand why ist greyed.
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
Mine has same problem and I've also been through similar online-forum attempts to help.
Model: TA-1012
Hardware version: 3.1
Patch level: 1 Jan 2019
Build No: 00WW_5_11A, 00WW_5_110_SP01
Downgrade your phobe and you can unlock, i have the same phone and this is what i did. I downloaded my phone firmware,i place the update file on my external sd card, i reset my phone to factory stock, i shut down my device an while shut down i press vol + and plug in my cable, i wait for the no comand screen and press power while holding vol up and get in recovery where i update from sd card and boom oreo
I ve been trying to unlock the bootloader for a week now.
I am stuck at Developer Options > Mi Unlock status > Add account and device.
It throws up the error "Coudn't add, Device basic data authentication failed"
What could be the issue, any help / pointers will be appreciated.
sonudhillon said:
I ve been trying to unlock the bootloader for a week now.
I am stuck at Developer Options > Mi Unlock status > Add account and device.
It throws up the error "Coudn't add, Device basic data authentication failed"
What could be the issue, any help / pointers will be appreciated.
Click to expand...
Click to collapse
I think you need to turn off wifi and enable mobile data then goto developer option and repeat the process.
Thanks, I tried but still not working.
There is no possible solution for this particular problem. We're constantly checking everyday but apparently its MIUI problem they messed up something in new update. Wait for Aug update.
sonudhillon said:
I ve been trying to unlock the bootloader for a week now.
I am stuck at Developer Options > Mi Unlock status > Add account and device.
It throws up the error "Coudn't add, Device basic data authentication failed"
What could be the issue, any help / pointers will be appreciated.
Click to expand...
Click to collapse
maybe try this, factory reset then again do setup, add your mi account, insert mi registered sim and enable data on it,
Aghora7 said:
There is no possible solution for this particular problem. We're constantly checking everyday but apparently its MIUI problem they messed up something in new update. Wait for Aug update.
Click to expand...
Click to collapse
An update on android 10 Is available for this redmi 8A dual now .. https://www.google.com/amp/s/www.xd...1-xiaomi-redmi-8a-dual-android-10-update/amp/
File link is also available here , I have already updated
What's the change they( Xiaomi) posted
Security patch August
Android 10.
Quick replies added.
What's the change i feel ,
Light sensor works as it should be working now only auto brightness works now .
Dark mode is far more better now
Full screen gesture is available now ( swipe up from bottom and side to navigate ref - Google android 10 updates navigation gesture)
Jiocall app works well no issues ( I am mentioning this because jio call app was not working properly with Android 10 on other brands like realme they are trying to fix..)
And now also the bootloader unlocking not working.. now also the miflash_unlock application shows failed to unlock..
Aghora7 said:
There is no possible solution for this particular problem. We're constantly checking everyday but apparently its MIUI problem they messed up something in new update. Wait for Aug update.
Click to expand...
Click to collapse
Brother , can't be downgrade the miui version with the software updater stock one for the 11.0.7.0 to get may security patch for unlocking is there any problem with that solution does downgrade cause any bootloop or crash.. I want to try reply please
aswath bharathwaj said:
Brother , can't be downgrade the miui version with the software updater stock one for the 11.0.7.0 to get may security patch for unlocking is there any problem with that solution does downgrade cause any bootloop or crash.. I want to try reply please
Click to expand...
Click to collapse
Did you downgraded?
.excalibur said:
Did you downgraded?
Click to expand...
Click to collapse
Its not possible to downgrade with stock software updater app. It says downgrade is not allowed
.excalibur said:
Did you downgraded?
Click to expand...
Click to collapse
Can we flash the lower version of miui roms by this meathod
https://www.google.com/amp/s/wasconet.com/flash-rom-xiaomi-phones-locked-bootloader/amp/
Without unlocking bootloader. (Device is at latest update) so not possible to unlock bootloader.
aswath bharathwaj said:
Can we flash the lower version of miui roms by this meathod
https://www.google.com/amp/s/wasconet.com/flash-rom-xiaomi-phones-locked-bootloader/amp/
Without unlocking bootloader. (Device is at latest update) so not possible to unlock bootloader.
Click to expand...
Click to collapse
This method doesn't work on newer devices, as the edl mode is locked and only accessible by opening the device's back case and shorting the edl flash point. Even after that flashing permission would be needed to flash via official mi flash tool which users can't get.
.excalibur said:
This method doesn't work on newer devices, as the edl mode is locked and only accessible by opening the device's back case and shorting the edl flash point. Even after that flashing permission would be needed to flash via official mi flash tool which users can't get.
Click to expand...
Click to collapse
Super , so the only way is to wait wait wait.. next September update
aswath bharathwaj said:
Super , so the only way is to wait wait wait.. next September update
Click to expand...
Click to collapse
Lol, tbh it's pretty bad.. like how can they give a patch which doesn't even allow unlocking bootloader. Wonder if the other Xiaomi phones are having same issue
.excalibur said:
Lol, tbh it's pretty bad.. like how can they give a patch which doesn't even allow unlocking bootloader. Wonder if the other Xiaomi phones are having same issue
Click to expand...
Click to collapse
Excalibur, leave that bootloader issue first my device IMEI number is not getting verfied with the Flipkart exchange and the device exchange value is also very less its 1,680 without IMEI verified.
and then the mi suit does even recognise this device why I don't know.
And it's a 32 bit device that's a bad issue for gcam lovers too.,
Good things with this device that
Storage space 32 gb I have
(And that too this device doesn't support ExFat file system on as card)
Type C ( but its of no use without fast charging ) may be we can use this type c for audio output (again the audio drivers or hardware is of no best for orginal audio quality) you have to use mausic player like jet plus pro app to tune it .. if it's rooted then V4A viper 4 Android.
aswath bharathwaj said:
Excalibur, leave that bootloader issue first my device IMEI number is not getting verfied with the Flipkart exchange and the device exchange value is also very less its 1,680 without IMEI verified.
and then the mi suit does even recognise this device why I don't know.
And it's a 32 bit device that's a bad issue for gcam lovers too.,
Good things with this device that
Storage space 32 gb I have
(And that too this device doesn't support ExFat file system on as card)
Type C ( but its of no use without fast charging ) may be we can use this type c for audio output (again the audio drivers or hardware is of no best for orginal audio quality) you have to use mausic player like jet plus pro app to tune it .. if it's rooted then V4A viper 4 Android.
Click to expand...
Click to collapse
It supports 18w fast charging, you just need a fast charger to do that which doesn't come out of the box. I've been using a fast charger and it charges as quickly as rn8 pro or any other 18w supportable device.
There isn't anything wrong with the audio quality provided by the inbuilt dac, it's the same as any other phone in this price point or any devices costing even higher than this. And viper4droid does more like tuning the eq which again would be of no use if the device's dac is bad.
any update guys?
sonudhillon said:
I ve been trying to unlock the bootloader for a week now.
I am stuck at Developer Options > Mi Unlock status > Add account and device.
It throws up the error "Coudn't add, Device basic data authentication failed"
What could be the issue, any help / pointers will be appreciated.
Click to expand...
Click to collapse
I also facing same problem brother did you find any solution or not
Hi guys,
So I got the chinese variant of the OnePlus 9 - LE2110. It came with a global Rom already installed. I'm currently on os 11.2.2.2 LE25DA.
I've been reading through the forums and I'm not sure what I need to download exactly to get this over to EU Rom. I think I also saw that I need to let this update first as it's prompting me to install 11.2.7.7. Things are changing so fast with this phone in terms of recent otas and root options that I'm concerned I'll use a dated method that could brick my phone.
Does someone know what file I need to flash on this and how? Also should I upgrade first. At the moment I'm downloading a zip of this but I'm not sure if this is correct :
11.2.6.6
OnePlus9Oxygen_22.E.09_GLO_0090_2105252341
Thanks in advance for any help or pointers
chinbags said:
Hi guys,
So I got the chinese variant of the OnePlus 9 - LE2110. It came with a global Rom already installed. I'm currently on os 11.2.2.2 LE25DA.
I've been reading through the forums and I'm not sure what I need to download exactly to get this over to EU Rom. I think I also saw that I need to let this update first as it's prompting me to install 11.2.7.7. Things are changing so fast with this phone in terms of recent otas and root options that I'm concerned I'll use a dated method that could brick my phone.
Does someone know what file I need to flash on this and how? Also should I upgrade first. At the moment I'm downloading a zip of this but I'm not sure if this is correct :
11.2.6.6
OnePlus9Oxygen_22.E.09_GLO_0090_2105252341
Thanks in advance for any help or pointers
Click to expand...
Click to collapse
Achieved it - as another user posted in another post. Set your device to EU before you update in the oxygen updater app.
But what was not mentioned is If you are just setting up, you also need to allow advanced settings in the updater. Otherwise I was getting a warning message telling me I have selected the wrong device.
Just updated using the updater with the device set to EU and I have BA version
Hey! I'm in the same spot as you were, but I updated it to 11.2.7.7.LE25DA. I also have the CN version. Do I have to wait to the next update to move from global to EU, or is there any option to change it now?
Thanks!
alex7171 said:
Hey! I'm in the same spot as you were, but I updated it to 11.2.7.7.LE25DA. I also have the CN version. Do I have to wait to the next update to move from global to EU, or is there any option to change it now?
Thanks!
Click to expand...
Click to collapse
That was my understanding. However I've been having reception issues that I did not have with a CN huaweii I had before this phone so I'm thinking it might be the EU rom I flashed, which would be odd as I'm in Ireland.
,
Anyway, even though I changed my phone from oneplus 9 (eu) to just oneplus 9 in the updater, I am prompted to download 11.2.7.7 - even though that's what I'm currently on.
Anyone know if this is just the global version of 11.2.7.7? This would mean I would not have to wait for the next update though.
chinbags said:
That was my understanding. However I've been having reception issues that I did not have with a CN huaweii I had before this phone so I'm thinking it might be the EU rom I flashed, which would be odd as I'm in Ireland.
Click to expand...
Click to collapse
Regarding the reception issues, bugs are always possible, or maybe the antenna isn't as strong as your previous phone. From https://www.kimovil.com/ I can see that your Chinese variant should be perfectly fine in Ireland. I would recommend that you reach out to oneplus support, what you've done so far is not breaching warranty restrictions.
Otherwise the "nuclear option" is to use an msm tool to reset your device, including the "modem" (or EFS?) partition which controls certain hardware-related functionality. This is because I'm quite certain they don't change when flashing any of the standard update images (not even a "full" update). Not sure an msm tool is available for your Chinese hardware variant. This is also becoming more risky and not sure how desperate you are.
chinbags said:
Anyway, even though I changed my phone from oneplus 9 (eu) to just oneplus 9 in the updater, I am prompted to download 11.2.7.7 - even though that's what I'm currently on.
Anyone know if this is just the global version of 11.2.7.7? This would mean I would not have to wait for the next update though.
Click to expand...
Click to collapse
You said yourself that you're running EU version but have set the app to check for "global", so I'm a bit confused by your confusion. If you want to stay on eu branch, then tell the app that your device is eu.
laasworld said:
Regarding the reception issues, bugs are always possible, or maybe the antenna isn't as strong as your previous phone. From https://www.kimovil.com/ I can see that your Chinese variant should be perfectly fine in Ireland. I would recommend that you reach out to oneplus support, what you've done so far is not breaching warranty restrictions.
Otherwise the "nuclear option" is to use an msm tool to reset your device, including the "modem" (or EFS?) partition which controls certain hardware-related functionality. This is because I'm quite certain they don't change when flashing any of the standard update images (not even a "full" update). Not sure an msm tool is available for your Chinese hardware variant. This is also becoming more risky and not sure how desperate you are.
You said yourself that you're running EU version but have set the app to check for "global", so I'm a bit confused by your confusion. If you want to stay on eu branch, then tell the app that your device is eu.
Click to expand...
Click to collapse
Cheers, thanks for all that info. I may just live with it, I don't think it's bad enough to warrant messing around with MSM tools. The reception issues seems to only happen when I'm travelling across the county and probably switching towers.
Sorry if my post is a little confusing. What I'm trying to say is I'm having reception issues while on EU rom. So I thought if I change back to global rom this might fix the reception issue. I thought I could only do this if there was an update available. I changed my phone to global on the update and it says there is an update available even though it's the same software version, that's all.
Do you think changing back to Global could fix it?
chinbags said:
Do you think changing back to Global could fix it?
Click to expand...
Click to collapse
I see, I highly doubt it, but it's a low-risk experiment and only a bit of fuss waiting for the download and update, so probably worth a shot. Not to mention the fuss to come back to eu version if it didn't help.
And to be clear about the app, I guess the app was then just telling you about the latest relevant image matching your preference, the "advanced mode" should probably be turned off once you've settled on the region of choice. It's only giving you persistent notifications, so it's not helpful and also quite distracting in the long term.
laasworld said:
I see, I highly doubt it, but it's a low-risk experiment and only a bit of fuss waiting for the download and update, so probably worth a shot. Not to mention the fuss to come back to eu version if it didn't help.
And to be clear about the app, I guess the app was then just telling you about the latest relevant image matching your preference, the "advanced mode" should probably be turned off once you've settled on the region of choice. It's only giving you persistent notifications, so it's not helpful and also quite distracting in the long term.
Click to expand...
Click to collapse
thanks, and yes regarding the app, I thought it was prompting me to install the same version of the software but for the global variant, this is not the case if you try it locally. I saw an option to flash it via the root method but this required twrp. Trying to install twrp at the moment but having an issue with the boot twrp.img command. anyway, if there's an easier way any pointers would be great but thanks for your help.
I'm also thinking if my connection issue persists I will get in touch with oneplus like you said - this is not an issue I should be having with this caliber of a phone.
If I get the global rom on, and make the same journey to test it, I will circle back here to let you know how I got on.
Cheers
What are the differences between the global and EU roms? Are there any benefits to using one over the other?
Superguy said:
What are the differences between the global and EU roms? Are there any benefits to using one over the other?
Click to expand...
Click to collapse
Not a lot, if any. On DA I'm getting the odd one plus notification from the updater or cloud services that I didn't get from EU. Otherwise it's the same rom. I'm testing the different variants to see if it makes any difference to signal strength (which it doesn't by the way).
I'm likely to revert back to EU rom because they say updates are quicker for it and 'should' be better in terms of gdpr issues. But they're basically the same (from what I can see).
So, just to be sure. Now that 11.2.8.8 has been released, I have to switch my phone in Oxygen Updater to EU version and full update? That's it?
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Doesn't exist. Ideally, you would dump the firmware yourself from the phone.
Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?
kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.