Is my axon 7 the global or chinese version? - ZTE Axon 7 Questions & Answers

I have just received my new Axon 7 which is currently running stock 6.0.1. So I thought I would try to update as I already know nougat is available. There are no available OTA's showing though. Of course AxonToolkit needs the variant if I want to root etc...
Hoping someone can shine a light on it for me as according to the model number it's the Chinese variant but the spec is 64gb/4gb. I thought the Chinese version only came with 128gb storage!
Any ideas folks?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017 using Tapatalk

beastobadness said:
I have just received my new Axon 7 which is currently running stock 6.0.1. So I thought I would try to update as I already know nougat is available. There are no available OTA's showing though. Of course AxonToolkit needs the variant if I want to root etc...
Hoping someone can shine a light on it for me as according to the model number it's the Chinese variant but the spec is 64gb/4gb. I thought the Chinese version only came with 128gb storage!
Any ideas folks? View attachment 4392763
Sent from my ZTE A2017 using Tapatalk
Click to expand...
Click to collapse
From what I understand you have the Chinese version according to that screenshot.
A2017G = European / Global
A2017U = US
A2017 = China
The Way to be certain is to check the back of the phone as it should be printed there.
I also found a page that referred to a 64GB Chinese version too, just uncommon

This is what I've got for my G model.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

Yes, seems it's definitely a 64gb Chinese version as on the back of the phone is printed 'ZTE A2017', not what I was expecting.
So can I change the region using AxonToolkit and flashing an alternative rom?
Sent from my ZTE A2017 using Tapatalk

I don't know if it's possible, but I think you should have a problem with the radio baseband.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

beastobadness said:
Yes, seems it's definitely a 64gb Chinese version as on the back of the phone is printed 'ZTE A2017', not what I was expecting.
So can I change the region using AxonToolkit and flashing an alternative rom?
Click to expand...
Click to collapse
You can flash any firmware on any device. I am having A2017 and using A2017U Software.
Use MiFlash thread to flash
Instructions : Download both the EDL packages and extract and copy and replace the Modem Elf file from Chinese to US ROm and just flash US ROM. Good To go

satish.yarramsetti said:
You can flash any firmware on any device. I am having A2017 and using A2017U Software.
Use MiFlash thread to flash
Instructions : Download both the EDL packages and extract and copy and replace the Modem Elf file from Chinese to US ROm and just flash US ROM. Good To go
Click to expand...
Click to collapse
Thanks for that. I am having to learn everything again coming from an S4 and LG G3 but that info is something I may use in the future.
In the end I took the simple route and used AxonToolkit to unlock the bootloader, flash twrp and root. Went custom with RR which I have used for years on and off. Just flashed the universal bootloader and modem along side the rom. Apart from losing some stock functionality like the camera, my Axon 7 is running absolutely fine.
Edit...actually reading the MiFlash thread that seems just as simple if I ever get the itch to go back to stock rom
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
Thanks for that. I am having to learn everything again coming from an S4 and LG G3 but that info is something I may use in the future.
In the end I took the simple route and used AxonToolkit to unlock the bootloader, flash twrp and root. Went custom with RR which I have used for years on and off. Just flashed the universal bootloader and modem along side the rom. Apart from losing some stock functionality like the camera, my Axon 7 is running absolutely fine.
Edit...actually reading the MiFlash thread that seems just as simple if I ever get the itch to go back to stock rom
Click to expand...
Click to collapse
If you want the stock camera just go to the stock camera thread on Themes, Apps and Mods, download the B13V2 camera, flash it. You'll get the latest and greatest MiFavor 5.0 camera
To flash any ROM you have to flash the A2017 modem file. And probably an universal bootstack. If you wanted to switch to a G ROM (say, slim⁴) you can just follow the instructions. But it basically js flashing a bootstack, a modem, then the ROM.
And if you want to go back to stock you can just install one of the MiFavor 5 ROMs, they are basically stock for the A2017. I think there's a flashable one, and there's an older one which is just a TWRP backup.
I always thought MiFlash was more like the last thing to do, but you might as well use it. I wouldn't like to know what would happen if there was a power surge in the middle of a flash.

Choose an username... said:
If you want the stock camera just go to the stock camera thread on Themes, Apps and Mods, download the B13V2 camera, flash it. You'll get the latest and greatest MiFavor 5.0 camera
To flash any ROM you have to flash the A2017 modem file. And probably an universal bootstack. If you wanted to switch to a G ROM (say, slim⁴) you can just follow the instructions. But it basically js flashing a bootstack, a modem, then the ROM.
And if you want to go back to stock you can just install one of the MiFavor 5 ROMs, they are basically stock for the A2017. I think there's a flashable one, and there's an older one which is just a TWRP backup.
I always thought MiFlash was more like the last thing to do, but you might as well use it. I wouldn't like to know what would happen if there was a power surge in the middle of a flash.
Click to expand...
Click to collapse
Yeah I have to say I have always been a one for flashing from recovery...it just feels safer to me.
The B13V2 cam file is actually already sitting on my Ax7, I have just never got around to flashing it yet lol
Only thing that I thought would really bother me was the lack of hi-res DAC support on LOS/custom based ROMs but I now have RR with V4A running on it and it sounds great...far cry from the clicks, stutters and hiss I was getting on my S4 and G3
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
Yeah I have to say I have always been a one for flashing from recovery...it just feels safer to me.
The B13V2 cam file is actually already sitting on my Ax7, I have just never got around to flashing it yet lol
Only thing that I thought would really bother me was the lack of hi-res DAC support on LOS/custom based ROMs but I now have RR with V4A running on it and it sounds great...far cry from the clicks, stutters and hiss I was getting on my S4 and G3
Click to expand...
Click to collapse
Actually I believe sound is better on LOS after the AK4490 patch... With it you can get 192KHz/24bit on Neutron, so yeah, there is hi-res on LOS roms. Flash it just in case, but I think that it has already been integrated

Choose an username... said:
Actually I believe sound is better on LOS after the AK4490 patch... With it you can get 192KHz/24bit on Neutron, so yeah, there is hi-res on LOS roms. Flash it just in case, but I think that it has already been integrated
Click to expand...
Click to collapse
I went away from Neutron a couple of years ago because of the janky UI, damn good player for sound though. Might have to give it another go later. Does Neutron not force out 32bit?...I am sure there is a switch in settings which forces 32bit.
Shame that Max can't get the hi-res working natively on Poweramp though...I am a big fan of that player even though the next version has been in beta for ever.
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
I went away from Neutron a couple of years ago because of the janky UI, damn good player for sound though. Might have to give it another go later. Does Neutron not force out 32bit?...I am sure there is a switch in settings which forces 32bit.
Shame that Max can't get the hi-res working natively on Poweramp though...I am a big fan of that player even though the next version has been in beta for ever.
Click to expand...
Click to collapse
I absolutely despise Neutron, but the hi-res thing is a fact. I use Poweramp 704
Why would you force 32 bit when the DAC only processes up to 24? Even if you toggle that switch the output will be 24.

Choose an username... said:
I absolutely despise Neutron, but the hi-res thing is a fact. I use Poweramp 704
Why would you force 32 bit when the DAC only processes up to 24? Even if you toggle that switch the output will be 24.
Click to expand...
Click to collapse
I thought I had read the DAC had a max bit rate of 32 bit...oh well, no need then! lol
Same here Poweramp 704
Edit...OK did some reading up on the DAC... Bit of a heated subject that one! So the DAC itself is a 32bit chip but it is limited to 24bit by android itself...I mean WTF lol!
Sent from my ZTE A2017U using Tapatalk

Related

[REF] [RADIO] OnePlus One Modem Collection

Background
This is a list of radios for the OnePlus One (bacon). With the new OTA release, some people may have better signals with the old radio or want to tinker with the new one so here is a list that will be updated to allow users to switch to their preferred radio/modem.
Radios are independent of Android version, use the radio that provides you the best signal. It varies from user to user, there is no best radio/modem Why? Different carriers, different locations, and more. There are so many factors that play into cellular signal so just because a particular radio is the best for someone doesn't mean its the best for you. We can obtain a consensus on which radio performs the "best" for the largest % of users though.
However, see @Vonnegut 's experiences here on modems.
How to Flash?
Simply flash the .zip below in your preferred recovery. If you prefer flashing via fastboot, extract the .bin file out of the .zip file and flash it by typing,
Code:
fastboot flash modem <name-of-modem>.bin
The MD5 hashes for the files below are MD5 hashes of the zips and not the radio image themselves.
Download (newest on top)
CyanogenMod 11S OTAs
XNPH05Q (02/09/15):
XNPH44S (11/07/14): https://www.androidfilehost.com/?fid=95784891001607675
XNPH33R (08/20/14): https://www.androidfilehost.com/?fid=23622183712462756
XNPH30O (08/10/14): https://www.androidfilehost.com/?fid=23622183712462755
XNPH25R(07/02/14) + XNPH22R (06/05/14): https://www.androidfilehost.com/?fid=23622183712462749
CyanogenMod 11 Nightlies
11/28/2014: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
CyanogenMod 11 Snapshot
M11(10/07/14): Same radio as ColorOS 09/18/14.
M9 (08/05/14): Same radio as XNPH30O (See XNPH30O)
M8 (07/09/14): https://www.androidfilehost.com/?fid=23622183712464203
MD5: 54e0c2bc7104f7e111df37a2f458c48d
ColorOS
09/18/14: https://www.androidfilehost.com/?fid=23622183712473371 (thanks to @fards) This is the same radio as the ones provided in the latest CM11 Nightlies.
To get a feel of what modems are identical and what are not (thanks to @funCrash93 for having the time to display this -- http://forum.xda-developers.com/showpost.php?p=55590762&postcount=163 )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------------------------------------------
It should also be noted that in Settings -> About Phone, all the versions are listed as MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1.
Confirmed by armitage, they are indeed different with the same baseband version. See here.
thanks, great
thank you this is a good thread with direct collection just out of curiosity , are there any improvements ? I don't have any issues with call etc. do you think its good idea to update to latest ? currently on mahdi rom latest build..
This is great thanks.
How would I know which modem I am using now ? In case I want to revert to stock ?
Is one of these the original stock one ?
Am on mahdi 0823 stock modem that came with the phone.
Thanks in advance
captiv123 said:
This is great thanks.
How would I know which modem I am using now ? In case I want to revert to stock ?
Is one of these the original stock one ?
Am on mahdi 0823 stock modem that came with the phone.
Thanks in advance
Click to expand...
Click to collapse
You can check the phone info for baseband version. Thats the modem. But remember the stock cm11s modems use the same name. So i would ask the dev of the rom (in this case mahdi rom) , or you can check the modem in your rom.zip and compare checksums to find the same.
But you dont even need to bother with these. Just keep a backup of your rom.zip, it has a modem, its probably called NON-HLOS.bin, you can flash it through fastboot anytime, with the command stated in the OP:
fastboot flash modem <filename>.bin
captiv123 said:
This is great thanks.
How would I know which modem I am using now ? In case I want to revert to stock ?
Is one of these the original stock one ?
Am on mahdi 0823 stock modem that came with the phone.
Thanks in advance
Click to expand...
Click to collapse
You'll just have to use your own judgment and keep track of what radio you're on. Theres no way to distinguish because CyanogenInc / OnePlus thought it was a good idea to be doing baseband/radio changes while keeping the same version. Which in my opinion, I believe is a bad practice because then users will not remember what radio they're on if they're using radios other than the latest.
Mahdi ROM does not include a radio in their flashable zip.
dayanandgp said:
thank you this is a good thread with direct collection just out of curiosity , are there any improvements ? I don't have any issues with call etc. do you think its good idea to update to latest ? currently on mahdi rom latest build..
Click to expand...
Click to collapse
I can't really answer that question for you as I don't live in your area. For instance, I'm in New York City, if I get the best performance using the XNPH30O radio (just saying as a example) it doesn't meant that you will get the same performance because you're in California (as an example) on AT&T. In my post I explained it, there is no best modem/radio. You will have to just flash it, use it for a couple days (or 1 day) and conclude it for yourself. I'm hoping that people will be more active in this thread and personally lay out their opinions on what is the best radio for them as well as include their location so people can get a general idea/consensus on the most popular radio/modem.
Ask yourself the questions.
- How is my battery life? Did it improve or did it worsen due to a weaker/stronger signal?
- Am I getting dropped connections?
... etc
zephiK said:
You'll just have to use your own judgment and keep track of what radio you're on. Theres no way to distinguish because CyanogenInc / OnePlus thought it was a good idea to be doing baseband/radio changes while keeping the same version. Which in my opinion, I believe is a bad practice because then users will not remember what radio they're on if they're using radios other than the latest.
Mahdi ROM does not include a radio in their flashable zip.
I can't really answer that question for you as I don't live in your area. For instance, I'm in New York City, if I get the best performance using the XNPH30O radio (just saying as a example) it doesn't meant that you will get the same performance because you're in California (as an example) on AT&T. In my post I explained it, there is no best modem/radio. You will have to just flash it, use it for a couple days (or 1 day) and conclude it for yourself. I'm hoping that people will be more active in this thread and personally lay out their opinions on what is the best radio for them as well as include their location so people can get a general idea/consensus on the most popular radio/modem.
Ask yourself the questions.
- How is my battery life? Did it improve or did it worsen due to a weaker/stronger signal?
- Am I getting dropped connections?
... etc
Click to expand...
Click to collapse
thank you ! Flashed the 33R radio yesterday. I live in Germany and will give a feedback.
Offtopic : Mahdi Rom + Vomer tweaks + Franco Kernel = 1% Overnight drain in 9 Hours ( Wifi and cell network)...
dayanandgp said:
thank you ! Flashed the 33R radio yesterday. I live in Germany and will give a feedback.
Offtopic : Mahdi Rom + Vomer tweaks + Franco Kernel = 1% Overnight drain in 9 Hours ( Wifi and cell network)...
Click to expand...
Click to collapse
Its weird because I get better idle time when I'm on cell data than having airplane mode on. Probably because the phone continues to work on finding signal when its in airplane, probably a bug. xD
zephiK said:
Background
This is a list of radios for the OnePlus One (bacon). With the new OTA release, some people may have better signals with the old radio or want to tinker with the new one so here is a list that will be updated to allow users to switch to their preferred radio/modem.
Radios are independent of Android version, use the radio that provides you the best signal. It varies from user to user, there is no best radio/modem.
How to Flash?
Simply flash the .zip below in your preferred recovery. If you prefer flashing via fastboot, extract the .bin file out of the .zip file and flash it by using,
Code:
fastboot flash modem <name-of-modem>.bin
Download
XNPH33R (08/20/14): https://www.androidfilehost.com/?fid=23622183712462756
MD5: d26bd9382afbfdcb7daabca9ff89ecfd
XNPH30O (08/10/14): https://www.androidfilehost.com/?fid=23622183712462755
MD5: 95e9b63832ffa8e5a553b5a4d8ba9230
XNPH25R (07/02/14): https://www.androidfilehost.com/?fid=23622183712462749
MD5: d5b67d0cf419fba567862fe92fb4caed
XNPH22R (06/05/14): https://www.androidfilehost.com/?fid=23622183712462759
MD5: 33b05edf27bfbea64a54a2e07fad766b
---------------------------------------------
It should also be noted that in Settings -> About Phone, all the versions are listed as MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1.
Confirmed by armitage, they are indeed different with the same baseband version. See here.
Click to expand...
Click to collapse
I guess you could also add radios from CM Snapshoots like M8 and M9, 'coz for example there are people that run better with those than CM11s ones.
personally running M9 radio (of course bacon one ), and for me as well Snapshot radio is better.
btw, the is a thread on this (fixing connectivity issues by using CM11 M# radios and not CM11S.
but never the less the idea is good to gather all here.
Sent from my bacon.
OP. I can make a flashable zip file of these pm if interested
funCrash93 said:
I guess you could also add radios from CM Snapshoots like M8 and M9, 'coz for example there are people that run better with those than CM11s ones.
personally running M9 radio (of course bacon one ), and for me as well Snapshot radio is better.
btw, the is a thread on this (fixing connectivity issues by using CM11 M# radios and not CM11S.
but never the less the idea is good to gather all here.
Sent from my bacon.
Click to expand...
Click to collapse
Good point. I'll add CM M# radios. I won't support nightly radios though, there'll be too much
gavin-phelan said:
OP. I can make a flashable zip file of these pm if interested
Click to expand...
Click to collapse
They're already flashable zips....?
Many Thanks for the zip in the Op.
Gesendet von meinem Oneplus One
funCrash93 said:
I guess you could also add radios from CM Snapshoots like M8 and M9, 'coz for example there are people that run better with those than CM11s ones.
personally running M9 radio (of course bacon one ), and for me as well Snapshot radio is better.
btw, the is a thread on this (fixing connectivity issues by using CM11 M# radios and not CM11S.
but never the less the idea is good to gather all here.
Sent from my bacon.
Click to expand...
Click to collapse
Yeah, I'm using the m9 radio on my Chinese OPO running cm11s and u get stable signal, stable data and stable calls.
As a side note, does anyone know if updating cm11s via OTAs will overwrite the flashed M9 modem?
Sent from my OnePlus One
devilsshadow said:
Yeah, I'm using the m9 radio on my Chinese OPO running cm11s and u get stable signal, stable data and stable calls.
As a side note, does anyone know if updating cm11s via OTAs will overwrite the flashed M9 modem?
Sent from my OnePlus One
Click to expand...
Click to collapse
It will override as the OTA includes a radio in there. For some reason, I can't upload to AndroidFileHost right this second. I've contacted them.
Edit: M9, M8 Radios added
Thanks ! This thread was needed
Testing 33R. I travel weekly from West to East, and use AT&T on StraightTalk.
zephiK said:
It will override as the OTA includes a radio in there. For some reason, I can't upload to AndroidFileHost right this second. I've contacted them.
Edit: M9, M8 Radios added
Click to expand...
Click to collapse
That is so strange. I haven't noticed any differences between the M9 radio and the radio that came with the latest CM11S OTA (33R I think). Maybe they use the same one?
devilsshadow said:
That is so strange. I haven't noticed any differences between the M9 radio and the radio that came with the latest CM11S OTA (33R I think). Maybe they use the same one?
Click to expand...
Click to collapse
Sometimes the basebands are close enough that you don't notice a difference. Thats why originally I didn't want to include the snapshot radios but /shrug.. someone suggested it so I went for it. Its hard to tell whether or not there is a difference since its closed source and that the baseband version is the same.
More or less, I would personally follow the OTA basebands. The only time, I'd look into the snapshot is if M10 gets released tonight and its the newest radio, but once the next OTA comes out. I'd stick with the OTA basebands.
Although on other phones, the same thing could be said. Two radios could have the same results as well.
zephiK said:
Sometimes the basebands are close enough that you don't notice a difference. Thats why originally I didn't want to include the snapshot radios but /shrug.. someone suggested it so I went for it. Its hard to tell whether or not there is a difference since its closed source and that the baseband version is the same.
More or less, I would personally follow the OTA basebands. The only time, I'd look into the snapshot is if M10 gets released tonight and its the newest radio, but once the next OTA comes out. I'd stick with the OTA basebands.
Although on other phones, the same thing could be said. Two radios could have the same results as well.
Click to expand...
Click to collapse
Only reason I flashed the M9 modem in the first place was because I got the chinese OPO and people were reporting issues with 3G and dropped calls with it. But now I'm gonna stick to whatever the OTAs use and only flash nightly radios if I notice any issues with the OTA radios. This thread is still great for quick access to said modems tho', so thanks for that.
Thanks for the kind words. The thread will remain updated as the new radios come about
Nice thread much needed one.? Anyone from India Airtel network here using the latest radio what is your feedback? Which radio do you feel is working great with the Indian network?
I am on the latest radio that came with the OTA of cm11s. But from the last radio also I had issues of signal drops w when I switch it to 3G it's not as great as the 2G signals which is very strong feel on my device.
It would be nice to know any Indian users feedback on this topic.
Thanks for this thread.
Oneplus one/PA 4.5 beta 3/AK

P10 Firmware on the Mate 9, Android O, and other recent experiments

Over the past month, although I haven't been able to post to XDA, I've gotten a lot of interesting information which I think can be discussed here. I'd also like to report the results of some experiments.
1. Flashing P10 firmware to the Mate 9
Surprisingly, it is possible to flash P10 firmware to the Mate 9, and it boots. A Mate 9 can even be rebranded as a P10. Unfortunately, there is something different about the Wifi driver, and Wifi does not work. It seems the mobile radios, bluetooth, etc. do work, though. I wasn't able to test this very thoroughly, and I don't recommend anyone else does, as it's impossible to recover it even with offline firmware, but it would be possible in the future for someone to build a ROM based on P10 firmware, I'm pretty sure.
2. Android O
Huawei has an internal Android O build for the Mate 9. This build comes pre-rooted for Huawei's internal development use, which opens up the option of rebranding without ever unlocking the bootloader, and doing other such tricks. Apart from looking at it and seeing the Android O features, the build is pretty useless as a daily driver. Things like the play store can't be installed easily. The recovery which comes with the build has broken Wifi, and I needed to use a HiSuite exploit to get it to restore to previous versions.
With both of the above mentioned firmwares, the recovery system is different. The TWRP which we currently have for the Mate 9 does not work. Rebuilding the recovery image with the tools available also does not work. Something's different about the way the recovery image is made, but I can't figure out what it is. So it's not possible to have TWRP yet in either of these environments, which makes them much less useful.
Even more interestingly, the P10 recovery images which do not work when flashed to a Mate 9 running EMUI 7.0, do work if the Mate 9 is running Android O build, or if it's running the P10 roms.
It's very easy to tell which environment it's in, as the EMUI 5.0 Recovery has a light blue theme, while the Android O / P10 builds, and so on have a dark blue theme.
It should also be possible to flash Mate 9 ROMs on the P10, which would let P10 users access TWRP (but they would lose Wifi in eRecovery, making it very, very hard to revert to P10 ROM)
--What from here?--
Eventually, these updates will be released for the Mate 9, and we'll need to rebuild TWRP. A nice side effect is, if we build a working TWRP for the P10, it will also work with future Mate 9 builds. I'm hoping that the next internal EMUI 5.1/Android O build will have Wifi working in eRecovery to make it possible to do more research on this with an easier recovery method.
For the sake of research, I will upload and link to the recovery img from the Android O build. Feel free to poke around with it! Note that just flashing this to your Mate 9 running EMUI 5.0, it will not work. Hopefully TWRP based off of this can be made. I've tried and have not been successful building something which will boot, despite it being easy for EMUI 5.0-based recovery.
Link for Boot, Recovery, Recovery2 from EMUI 5.1 / Android O build for MHA-AL00:
https://drive.google.com/file/d/0B6ox6M5Lb2JYRVZSNnB1YmpNX1E/view?usp=sharing
Hey buddy, welcome back. :good:
Sent from my MHA-L29 using XDA Labs
That's good news. Let's see what our great minds can do with this.
I am glad to see you here @duraraa.
All the best,
AB
duraaraa said:
Over the past month, although I haven't been able to post to XDA, I've gotten a lot of interesting information which I think can be discussed here. I'd also like to report the results of some experiments.
1. Flashing P10 firmware to the Mate 9
Surprisingly, it is possible to flash P10 firmware to the Mate 9, and it boots. A Mate 9 can even be rebranded as a P10. Unfortunately, there is something different about the Wifi driver, and Wifi does not work. It seems the mobile radios, bluetooth, etc. do work, though. I wasn't able to test this very thoroughly, and I don't recommend anyone else does, as it's impossible to recover it even with offline firmware, but it would be possible in the future for someone to build a ROM based on P10 firmware, I'm pretty sure.
2. Android O
Huawei has an internal Android O build for the Mate 9. This build comes pre-rooted for Huawei's internal development use, which opens up the option of rebranding without ever unlocking the bootloader, and doing other such tricks. Apart from looking at it and seeing the Android O features, the build is pretty useless as a daily driver. Things like the play store can't be installed easily. The recovery which comes with the build has broken Wifi, and I needed to use a HiSuite exploit to get it to restore to previous versions.
With both of the above mentioned firmwares, the recovery system is different. The TWRP which we currently have for the Mate 9 does not work. Rebuilding the recovery image with the tools available also does not work. Something's different about the way the recovery image is made, but I can't figure out what it is. So it's not possible to have TWRP yet in either of these environments, which makes them much less useful.
Even more interestingly, the P10 recovery images which do not work when flashed to a Mate 9 running EMUI 7.0, do work if the Mate 9 is running Android O build, or if it's running the P10 roms.
It's very easy to tell which environment it's in, as the EMUI 5.0 Recovery has a light blue theme, while the Android O / P10 builds, and so on have a dark blue theme.
It should also be possible to flash Mate 9 ROMs on the P10, which would let P10 users access TWRP (but they would lose Wifi in eRecovery, making it very, very hard to revert to P10 ROM)
--What from here?--
Eventually, these updates will be released for the Mate 9, and we'll need to rebuild TWRP. A nice side effect is, if we build a working TWRP for the P10, it will also work with future Mate 9 builds. I'm hoping that the next internal EMUI 5.1/Android O build will have Wifi working in eRecovery to make it possible to do more research on this with an easier recovery method.
For the sake of research, I will upload and link to the recovery img from the Android O build. Feel free to poke around with it! Note that just flashing this to your Mate 9 running EMUI 5.0, it will not work. Hopefully TWRP based off of this can be made. I've tried and have not been successful building something which will boot, despite it being easy for EMUI 5.0-based recovery.
Link for Boot, Recovery, Recovery2 from EMUI 5.1 / Android O build for MHA-AL00:
https://drive.google.com/file/d/0B6ox6M5Lb2JYRVZSNnB1YmpNX1E/view?usp=sharing
Click to expand...
Click to collapse
Welcome back ?
mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...
Nilezcode said:
mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...
Click to expand...
Click to collapse
Source of this information?
What new features did you notice in the Android O build?
Nilezcode said:
mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...
Click to expand...
Click to collapse
No, it'll be 5.1. It already is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MishaalRahman said:
What new features did you notice in the Android O build?
Click to expand...
Click to collapse
The only thing I noticed was a new files app, and some new developer options. I'm pretty sure it's just targeted for Android O development, and not for bringing any new features. It's missing all languages except Chinese and English, for example, it's missing a System Update app, eRecovery doesn't work, very incomplete.
Still, interesting, and I'm not an expert with what's new with Android to the point where I know what to look for, so if there's something I should be looking for, let me know.
duraaraa said:
The only thing I noticed was a new files app, and some new developer options. I'm pretty sure it's just targeted for Android O development, and not for bringing any new features. It's missing all languages except Chinese and English, for example, it's missing a System Update app, eRecovery doesn't work, very incomplete.
Still, interesting, and I'm not an expert with what's new with Android to the point where I know what to look for, so if there's something I should be looking for, let me know.
Click to expand...
Click to collapse
Can you look for Android O specific features to see if they work, such as Picture in Picture? If you know how to use ADB, enter an ADB shell, then open up the YouTube app and start a video.
While the video is paused type:
input keyevent 171
This would be definitive proof that this is indeed Android O. We can try other stuff too.
Any built in apps from P10 that can be installed on the Mate 9? Is there an apk list?
I seemed to remember reading in reviews of the P10 that the camera hardware is the same as our Mate 9/pro, but with upgraded software. Is this something you can verify based on the firmwares you have? When can we Mate 9 users expect this upgrade?
Cheers!
Willyman said:
I seemed to remember reading in reviews of the P10 that the camera hardware is the same as our Mate 9/pro, but with upgraded software. Is this something you can verify based on the firmwares you have? When can we Mate 9 users expect this upgrade?
Cheers!
Click to expand...
Click to collapse
Sorry, can't verify one way or the other. Although I did get P10 software running on the Mate 9, I didn't get the Camera app.
glad to see you here
ive also found that TWRP breaks the phone when you try to recover some partitions (/product i think)
hopefully things can change in the future, the partitions are a pain in the rear to play with
ive also read huawei wont name emui 5.1 on the mate 9 but will have the exact same features when upgraded (and will have the same 5.0 version)
Would you be able to share more screenshots of what you found?
MishaalRahman said:
Can you look for Android O specific features to see if they work, such as Picture in Picture? If you know how to use ADB, enter an ADB shell, then open up the YouTube app and start a video.
While the video is paused type:
input keyevent 171
This would be definitive proof that this is indeed Android O. We can try other stuff too.
Click to expand...
Click to collapse
I finally got a chance to try this. It worked.
Judging by your screenshot, you also got the Play Store and Wifi working, correct?
MishaalRahman said:
Judging by your screenshot, you also got the Play Store and Wifi working, correct?
Click to expand...
Click to collapse
Wifi always worked on Android O, since it's for the Mate 9. It doesn't work when running P10, P10 Plus, or other newer EMUI 5.1 phones' builds on the Mate 9. The issue seems to be the kernel.
I sideloaded google services and managed to get play store working, yes.
Many are doubting that this is actually Android O. Can you show a screen recording of picture-in-picture mode being started from the YouTube app?
1) Start a screen recording
2) Open up YouTube
3) Start a video
4) Send the input keyevent 171 ADB command
5) End recording
That should put any doubt to rest.
MishaalRahman said:
Many are doubting that this is actually Android O. Can you show a screen recording of picture-in-picture mode being started from the YouTube app?
1) Start a screen recording
2) Open up YouTube
3) Start a video
4) Send the input keyevent 171 ADB command
5) End recording
That should put any doubt to rest.
Click to expand...
Click to collapse
Perhaps next time I install it, I will. The picture in the previous post is the result of sending keyevent 171 ADB command while running a youtube video. The video continues to run regardless of what you do with the phone, but I couldn't find a way to close it.
Who, exactly, is doubting that it's Android O?

Where to download International firmware?

I bought for my wife from Geekbuying, it has multi language, but looks like Chinese firmware, and no Google anything. Other website selling the same phone with International firmware and with Google services.
I hope an OTA, or a custom rom for this soon. Or someone can point me out to where that International firmware is.
Thanks,
Gran
Gran Mastah said:
I bought for my wife from Geekbuying, it has multi language, but looks like Chinese firmware, and no Google anything. Other website selling the same phone with International firmware and with Google services.
I hope an OTA, or a custom rom for this soon. Or someone can point me out to where that International firmware is.
Thanks,
Gran
Click to expand...
Click to collapse
Your rom is multilanguage as every other rom. Sadly Google play isn't working on any of that. There is no international firmware at the moment. The advertisings on the shops are false.
Hello
There is no international firmware for the Z17.
The vendors are putting custom ROMS with multilanguage with or without google services but they have a great inconvenience, you will not be able to receive updates by OTA.
XoanCarlos said:
Hello
There is no international firmware for the Z17.
The vendors are putting custom ROMS with multilanguage with or without google services but they have a great inconvenience, you will not be able to receive updates by OTA.
Click to expand...
Click to collapse
Very disappointing. Such a great looking phone, and specs. Premium feel, way better looking than my Oneplus 5, and water resistant, nicer camera (although video at night time shooting was better with my Oneplus 5). It's nice to have both phone in hands and compare, fortunately for me I have no Jelly issue with the 5. Right now I have downloaded apk of certain droid apps she wants. I can't install Youtube with no Google, so I installed Opera browser and have her access Youtube that way.
Hoping the Nubia people will release Global/International ROM/Firmware soon, or some very capable XDA members here make a custom rom.
Nubia Z17 bought in Aliexpress, unofficial ROM, is a custom ROM with Google services and google store installed. Fake! Impossible to upgrade to not being the official ROM of Nubia. Open dispute in Aliexpress, I ordered with the original Chinese firmware and the seller stated that it would be so. Lie.
Enviado desde mi MHA-L09 mediante Tapatalk
Neomicina33 said:
Nubia Z17 bought in Aliexpress, unofficial ROM, is a custom ROM with Google services and google store installed. Fake! Impossible to upgrade to not being the official ROM of Nubia. Open dispute in Aliexpress, I ordered with the original Chinese firmware and the seller stated that it would be so. Lie.
Enviado desde mi MHA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Hi, what's fake? Them mentioning that it comes with Google services pre-installed and functioning or that you'll not be able to do OTAs latter, since it's a custom ROM.
IMO it's more important to have a functioning Google framework for the time being, until an International/Global ROM is officially released. In a near future, I guess it will be possible to unlock easily the bootloader and install from the recovery whatever ROM you want, Global or, hopefully, mainstream custom ROMs from the wonderful developers here in xda.
Exactly, custom ROM, it is not possible to upgrade to the latest firmware that Nubia took out. For me Google services are not indispensable. When I buy an original Chinese mobile, I always ask that the ROM be the Chinese (Meizu, Xiaomi ...) Problem: System update does not appear, does not support SD, does not recognize OTG. That is, I have a good mobile full of bugs (wifi, button back, battery, performance that improves the first OTA) and for now with no possibility to install its original firmware. Disappointed.
Photos: custom ROM on my phone vs official ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
csabreu said:
Hi, what's fake? Them mentioning that it comes with Google services pre-installed and functioning or that you'll not be able to do OTAs latter, since it's a custom ROM.
IMO it's more important to have a functioning Google framework for the time being, until an International/Global ROM is officially released. In a near future, I guess it will be possible to unlock easily the bootloader and install from the recovery whatever ROM you want, Global or, hopefully, mainstream custom ROMs from the wonderful developers here in xda.
Click to expand...
Click to collapse
No, them say... chinese firmware. Google Store it does not work.
http://cloud.tapatalk.com/s/595d33b331fb0/IMG_20170705_204437.png?
Gran Mastah said:
Very disappointing. Such a great looking phone, and specs. Premium feel, way better looking than my Oneplus 5, and water resistant, nicer camera (although video at night time shooting was better with my Oneplus 5). It's nice to have both phone in hands and compare, fortunately for me I have no Jelly issue with the 5. Right now I have downloaded apk of certain droid apps she wants. I can't install Youtube with no Google, so I installed Opera browser and have her access Youtube that way..
Click to expand...
Click to collapse
Does it have EIS for video recording?
Would OGTube work for YouTube? It's on xda
Neomicina33 said:
Exactly, custom ROM, it is not possible to upgrade to the latest firmware that Nubia took out. For me Google services are not indispensable. When I buy an original Chinese mobile, I always ask that the ROM be the Chinese (Meizu, Xiaomi ...) Problem: System update does not appear, does not support SD, does not recognize OTG. That is, I have a good mobile full of bugs (wifi, button back, battery, performance that improves the first OTA) and for now with no possibility to install its original firmware. Disappointed.
Photos: custom ROM on my phone vs official ROM.View attachment 4202593
Click to expand...
Click to collapse
Now I understand your frustration. Until it's possible to unlock the bootloader you're pretty much hopeless
ı contacted support they saıd we have no plan to make ınternatıonal rom in present.
sewkanteam said:
ı contacted support they saıd we have no plan to make ınternatıonal rom in present.
Click to expand...
Click to collapse
Hi,
I do not understand...
When I bought the phone (~= 15 or 20 days ago), it was clearly mentioned ( the text was at the beginning the of detailed specifications) on the GeekBuying web page the Gaps are not available.
I'd a look today (that night ), this text is removed.
I suppose there is a new release ?
I sent an email to GeekBuying to have more information.
Best regards (from France)
There is NO official International Firmware for the Z17. The Z17 ist not meant to be sold outside China (any may never be). There ARE alot custom firmwares with GAPPS like Gearbest is selling.
You wan't to have smartphone, where everything is working out of the box? Don't buy a Z17, buy a Z11 or someother.
dragon-tmd said:
There is NO official International Firmware for the Z17. The Z17 ist not meant to be sold outside China (any may never be). There ARE alot custom firmwares with GAPPS like Gearbest is selling.
You wan't to have smartphone, where everything is working out of the box? Don't buy a Z17, buy a Z11 or someother.
Click to expand...
Click to collapse
hi,
I've bought many phone from China which are not selling here (Europe), Jiayu, Cubot, etc. And they work.
I think you like give lessons and there is no debate on that point.
Thanks for your constructive answer.
Cheers
Gran Mastah said:
Very disappointing. Such a great looking phone, and specs. Premium feel, way better looking than my Oneplus 5, and water resistant, nicer camera (although video at night time shooting was better with my Oneplus 5). It's nice to have both phone in hands and compare, fortunately for me I have no Jelly issue with the 5. Right now I have downloaded apk of certain droid apps she wants. I can't install Youtube with no Google, so I installed Opera browser and have her access Youtube that way.
Hoping the Nubia people will release Global/International ROM/Firmware soon, or some very capable XDA members here make a custom rom.
Click to expand...
Click to collapse
Could you do a bit of a comparison review of your OnePlus and Z17?
I'm tossing up between Z17, Z17s & OnePlus 5 and would really appreciate your input on the differences between them since you own both models!
Hi Bunta126, have a look to the ROMS. If Oneplus has an international one, take it. For now, no international ROM for the Z17.
Nubia Z17 NX563J
Hello everybody
guys help me with my smartphone after unsuccessful firmware and cleanup twrp the smartphone does not load at all even the logo does not show. I tried downloading the recovery twrp no response to your button: wallbash :: wallbash: already a month without a smartphone on the shelf, please guys who can help all tried except for the firmware of three files QFIL smartphone to see the comp like (Qualcomm HS-USB QDLoader 9008) I really hope for the responsive guys
Qiyas25 said:
Nubia Z17 NX563J
Hello everybody
guys help me with my smartphone after unsuccessful firmware and cleanup twrp the smartphone does not load at all even the logo does not show. I tried downloading the recovery twrp no response to your button: wallbash :: wallbash: already a month without a smartphone on the shelf, please guys who can help all tried except for the firmware of three files QFIL smartphone to see the comp like (Qualcomm HS-USB QDLoader 9008) I really hope for the responsive guys
Click to expand...
Click to collapse
Maybe do it like that
MacLaughlin said:
Maybe do it like that
Click to expand...
Click to collapse
Yes, I know it
ZTE NX563J z17
QFIL the FILES you need ( firmware 3 files ) !!!:crying::crying:
Qiyas25 said:
Yes, I know it
ZTE NX563J z17
QFIL the FILES you need ( firmware 3 files ) !!!:crying::crying:
Click to expand...
Click to collapse
Try contacting nubia support.

Xiaomi Mi Pad 2 has been EoL'd

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link:
https://xiaomi.eu/community/threads/7-9-14.41552/
Latest version for Mi Pad 2 can be downloaded from here https://www.androidfilehost.com/?w=files&flid=213123 (MIUI 9) for global* version or from MIUI http://en.miui.com/download-296.html (MIUI 8) for Chinese version.
*Mi pad 2 doesn't really have global version, .EU version comes with pre-installed google services and removed Chinese bloatware.
This is a bad news for Mi Pad 2 owners because they do not have any solid custom ROM support for their device, which is due to lack of propitiatory Intel Atom's source code. So even if developers tried hard to deliver custom ROM they simply cannot. So unlike Mi Pad 1 even if Xiaomi EoL'd the support in a similar way last week, they can still get custom ROMs and patch support as long as developers delivers them. But for Mi Pad 2 it is simply not possible.
Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me
The reason why Xiaomi.eu has dropped support for Mi tablets can be found here "Sorry guys, we have no more free time to take care of tablets and debug them.. " (https://xiaomi.eu/community/threads/is-the-mi-pad-3-is-still-being-updated.41551/#post-386099).
Furthermore, if you paid attention to what @tank0412 wrote, you would know that Lenovo has a Nougat update scheduled and that opens the door for Android N development for the Atom series. Lastly, if you really want Mi Pad 2 development, I suggest you donate a Mi Pad 2 to @KonstaT over at Modaco (http://www.modaco.com/forums/forum/445-other-devices/) - he's the brain behind all Atom custom rom development.
Palm Trees said:
Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me.
Click to expand...
Click to collapse
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.
udaan said:
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.
Click to expand...
Click to collapse
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues
Palm Trees said:
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues
Click to expand...
Click to collapse
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.
udaan said:
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.
Click to expand...
Click to collapse
I asked you for a link, because I couldn't find any information confirming Xiaomi will stop releasing more updates for Mi Pad 2. Spreading fake news is never good. Mi Pad 2 hasn't been EOL'd. Only by Xiaomi.eu, but not by others.
Livedten actually points out that it doesn't matter if you use Xiaomi.eu, Multirom.me, etc. MIRU mod should be compatible with all of them.
multirom_MIPAD2_7.9.14_v5.1_b10.zip can be found here https://multirom.me/index.php?m=app&a=view&id=11&app=roms
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.
Palm Trees said:
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.
Click to expand...
Click to collapse
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp
Palm Trees said:
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp
Click to expand...
Click to collapse
So do I just flash it over to MIUI9?
udaan said:
So do I just flash it over to MIUI9?
Click to expand...
Click to collapse
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.
Palm Trees said:
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.
Click to expand...
Click to collapse
btw, will they release the full ROM in future like .EU folks?
udaan said:
btw, will they release the full ROM in future like .EU folks?
Click to expand...
Click to collapse
Probably, yeah. But beware, you might have to download the firmware zip many times, if you decide to use the MIUI 9 firmware from multirom.me, always run 'test archive' with e.g. 7zip. If no errors show, you're ready to flash, if errors show, you have to re-download. I think it's because of a server issue. I use Ninja Download Manager to succesfully download the .zip. MIRU mod downloads perfectly, since it's hosted elsewhere.
After a few tests I managed to flash MIUI9 with MIRU Mod. You must flash both multirom_MIPAD2_7.9.14_v5.1_b10.zip + MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip at the same time in order to get it to work.
https://androidfilehost.com/?fid=817550096634797955
is there any working download link for the latest multirom and miru mod package?
cant find it anywhere anymore.
i found a yandex folder "MIUI_9_BACKUP" containing:
MI_mod_08.02.2018_для_MIPAD2_UNIVERSAL.zip with 144.2MB
MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip with 336.2MB
But without any instructions or anything and dont know what to do with it
So... I had the Mi pad 2 laying in my house running on MIUI 9 and one day I got curious and tried to unlock its bootloader.
I didn't remember my password and the recovery phone no. is discontinued now. and I couldn't change it or sign out.
So like an idiot, I factory reset it. And now it's asking for a password for the last mi id.
can anyone help me? Will and edl flash do the work?
THANKS

[OFFICIAL] LineageOS 20 for the Nokia 6.1 (2018)/6.1 Plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nokia 6.1 (2018)/6.1 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Nokia 6.1 (2018)/6.1 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Nokia 6.1 (2018)​
PL2 - Official builds​
PL2 - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
Nokia 6.1 Plus​
DRG - Official builds​
DRG - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.​
Find any? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_nokia_sdm660
Is this rom based on Android 13?
ardwivedi16 said:
Is this rom based on Android 13?
Click to expand...
Click to collapse
yes
very excited waiting
worked my phone, yesterday i tried clean flash but not boot, and today i tried update with sideload and worked
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
kazekiri said:
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
Click to expand...
Click to collapse
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
backspace123// said:
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
Click to expand...
Click to collapse
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
kazekiri said:
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
Click to expand...
Click to collapse
on my device worked, i tried update using lineageos19.1 official
schwedenespresso said:
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Click to expand...
Click to collapse
Hello, regarding the camera, it is quite likely that it is the kernel as such, in fact, in previous versions, LOS 18.1, 17.1, the flash worked from the camera application, but now it does not work, at the time it was published Official LineageOS for this device, the flash has never worked correctly as such (other applications were not able to take the picture with the flash on the camera due to failure in its execution) as if it did with the manufacturer's version, it is possible that the manufacturer has kept some hidden details at the code level or that the driver has not been fully released on the devices so that the developers themselves have difficulties to achieve a 100% functional version (without errors so to speak), the only solution to this problem is install a custom kernel, it seems some users with knowledge in programming found a way to solve the problem with the flash in the camera + the zoom failure as such, I have not found out if the developer would have adapted the kernel for the versions of android 13 for this specific device than if it is available for versions prior to the unofficial LOS 20 available.
Best regards
Hello everyone, for all those who have problems with their recovery (nothing is displayed, but it feels like it works internally), I will leave you a post that I made months ago, the recovery options should be the same for the latest versions, hopefully It is useful for you, remember that the installation process of LineageOS can last more than 4 minutes.
LineageOS recovery instructions for use build 2022-08-30 -When starting the recovery, 4 options will be presented, which are these.
Reboot system now.
Apply update
2.1)For this step I recommend selecting the first option with the power button of the device, which is by ADB
3)Factory Reset
3.1)Format data/factory reset
4. Advance
4.1) advanced options, with this image it will serve to guide you in how many clicks you have to press to access the option with the power button of the device to access one of these options.
Best regards
backspace123// said:
on my device worked, i tried update using lineageos19.1 official
View attachment 5763487
Click to expand...
Click to collapse
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
kazekiri said:
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
Click to expand...
Click to collapse
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
npjohnson said:
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
Click to expand...
Click to collapse
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
kazekiri said:
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
Click to expand...
Click to collapse
Figured it out - next build should work. give it like, 4 hours.
npjohnson said:
Figured it out - next build should work. give it like, 4 hours.
Click to expand...
Click to collapse
Yep. Whatever you did worked! Booted on my DRG. Haven't tested everything yet, but so far seems great.
Thanks! You are one dedicated dev!
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
I have the same camera issue, any solution for DRG?
kazekiri said:
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
Click to expand...
Click to collapse
Weird, works on PL2. got logs?

Categories

Resources