Related
I have a nubia z7 with rom version 2.05 (Android 5 and Nubia UI 3), with google apps working without problems. Even youtube.
It took 3 days to figure out how to do it, without rooting the phone.
But some tools are needed...
I upgraded my phone rom (which came with version 2.26, a modified 1.26), put rom 2.02 then 2.03 and at last 2.05, which is the last one in nubia chinese site.
I used nubia rom updater, for the roms version 2.02 and 2.03 you have to decompress to each folder and point nubia updater to that folder.
The last one (version 2.05), i used option update of the phone.
Then uninstalled every chinese app. Downloaded gapps micro for android 5.0.1 and copy to the internal storage.
Then rebooted the phone with TWRP and installed the zip file. With TWRP root the phone, in advanced menu.
After that, i reboot into android system and made login into google play and updated everything.
It's a google phone now.
I think this should work for Nubia Z7 mini and Nubia Z7 Max
I hope this help someone
link: https://drive.google.com/folderview?id=0B52DgCiPfqeTYkFmUjNSbm44RDA&usp=sharing
greetings
I managed to get as far as upgrading firmware to v2.05. The files worked great thanks. How do I use the twrp to install gapps? Thanks for the help
helobot said:
I managed to get as far as upgrading firmware to v2.05. The files worked great thanks. How do I use the twrp to install gapps? Thanks for the help
Click to expand...
Click to collapse
hi, i'm Senh0r. I had logged with an old account.
now you can uninstall all chinese apps ,that you don't want.
then copy file gapps to internal storage.
Check if you have port ADB selected, by inserting on dial number *#7678# , if not, select it.
Now run the TWRP, which is in chinese, when the menu show up, choose option 3 and wait for the phone reboot into TWRP.
When you enter in TWRP, on bottom of screen you can choose english language.
After that is only to install the zip file. don't check for signature.
Now it's only need to reboot phone.
To enter on TWRP you need always to run the program to reboot your phone.
Anything ask
greetings
Thanks for that. I got them installed but when I boot the phone I get a google services has stopped and the phone shuts down I'm
Not sure what I did wrong
helobot said:
Thanks for that. I got them installed but when I boot the phone I get a google services has stopped and the phone shuts down I'm
Not sure what I did wrong
Click to expand...
Click to collapse
try to root the phone first and then install gapps again.
it's in advanced options, i think
did you managed to do it?
Hi Guys,
got my NX506J today, so a word of warning, I am pretty new to this
I am a little bit lost at the start,
Some Infos on the phone
Hardware Revision: NX506JMB_B
Build Number: NX506J_CNCommon_V2.26
NUBIA UI: V2.6.3
Rooted with TowelRoot
I'd appreciate it if you guys can point me in the right direction
THanks in advance
Hi,
just follow the first post.
greetings
Senh0r said:
Hi,
just follow the first post.
greetings
Click to expand...
Click to collapse
having the same issue as helobot.
update to 2.05 no problem
But after installing gapps it crashes in the setup phase
any ideas ?
Did you rooted the phone before installing gapps by twrp?
Rooted from twrp, installed gapps, rebooted.
After a few minutes it started, google setup wizard.
It crashes with an exception.
Gonna give it a shot in a few
Call me an idiot, but I didn't make a backup of the delivered stock ROM KitKat 2.26.
Please have you guys an image? I am stuck for good.
And cleaned the cache and dalvik partition too? Mine its working with no problems.
Cleaned cache etc.
I could hit me for being so stupid to forget backing the original ROM up.
I can easily go to a stock Chinese ROM but at least a KitKat Google ROM would be nice.
Señor or anyone, can you provide a image of 2.26?
Unfortunately I didn't backup it either , but soon I will create a zip file with my Rom with Google apps installed.
I will check Nubia site for older roms too.
Getting the hands on an 1.26 is relatively easy, but the googlefied 2.26 seems to be rather hard to find ...
vision0815 said:
Getting the hands on an 1.26 is relatively easy, but the googlefied 2.26 seems to be rather hard to find ...
Click to expand...
Click to collapse
Hi, I have my phone with 2.26, I have rooted it with kingo, if you can provide me a custom recovery I can do a nandroid back up of complete rom.
Hi Steveyknoxville, Señor shared a custom recovery based on twrp and that works very well. I would really appreciate if you could provide us with the 2.26 ROM
The link is in the first posting of this thread.
vision0815 said:
Hi Steveyknoxville, Señor shared a custom recovery based on twrp and that works very well. I would really appreciate if you could provide us with the 2.26 ROM
The link is in the first posting of this thread.
Click to expand...
Click to collapse
Hi, I have read that senor twrp does not work on 4.4.2, are you confirming it does. My biggest question I need answered before I do anything is, if I install twrp how do I go back to stock recovery so I can do Ota updates to get to lollipop. Thanks.
Sorry but I can't confirm weather it fully works or not. I followed señor's guide and updated the phone. But if I recall the thread correctly from nubia cn forums the stock ROM should be a slightly modified twrp anyways.
Try just going into the recovery mode.
You should be able to backup the ROM.
Thanks for the invested time.
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
mrbix said:
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
mrbix said:
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
Click to expand...
Click to collapse
correct driver installation was a bit difficult also for me. good to know you solved the problem
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thank you. I had the same issue as OP, Google found me this thread and using flashtool 0.9.20.0 worked.
Considering this guide was written before the Mi 9T Pro was released, it's time to rewrite it and make it more relevant.
THE BASICS
GETTING PREPARED
-----------------------------------
If you want to tinker with your phone then you'll need some ground work.
If you don't yet have a Mi account, go to https://account.xiaomi.com/pass/register and create a new account. It is important, when unlocking the bootloader, to have your correct phone number registered on your account, so either choose to create the account using a phone number or add the phone number in the security settings of your Mi account afterwards. Make sure the number is verified by the OTP that will be sent.
Make sure you have adb and fastboot tools installed on your PC. These are part of the Android development tools. You can either install the official Android SDK Platform Tools which can be found here https://developer.android.com/studio/releases/platform-tools
Or you can install only adb and fastboot from this xda members project, called minimal adb and fastboot. https://forum.xda-developers.com/showthread.php?t=2317790&p=42407269
If you want to know more about these tools then read the minimal adb and fastboot post, you'll find a couple of links that explain both tools in detail.
Install the Mi Unlock Tool. You can find this in the guide I've linked to in the bootloader unlock section below.
Install the Mi Flash Tool. This can be found in the guide I've linked to in the MIUI fastboot flashing section.
Install the drivers for the phone. This is done automatically the first time you connect the phone to PC, so go ahead and connect your phone to your PC and wait until it says the phone is ready for use. At this point the computer should identify the phone correctly as a Redmi K20 Pro.
UNLOCKING THE BOOTLOADER
-------------------------------------------------------
I'll point to 2 guides, both on the new, official Mi Community Forums.
https://c.mi.com/thread-2262302-1-0.html
This first guide is somewhat incomplete, but it does give some good extra information about the bootloader unlocking and has direct links for the Unlock Tool and previous versions. Sometimes using an older version of the tool will resolve unlocking issues.
https://c.mi.com/thread-1857937-1-0.html
This second guide is more complete, but not so well written. Again there is some useful extra info included.
CUSTOM RECOVERIES
---------------------------------------
If you want to flash a custom ROM or root the phone, then you'll need to install a custom recovery. Your only realistic option here is TWRP, however TWRP comes in many flavours. (Before anyone corrects me and says what about Orange Fox? This is, underneath it all, still a heavily modified version of TWRP) For a brief overview of what TWRP is, I'll point you to the official TWRP page which answers that very question https://twrp.me/faq/whatistwrp.html
I should point out that MIUI will check on every boot whether the recovery partition has been modified. If it thinks it has, then the boot process will automatically restore the system recovery. In order to keep TWRP you will need to either flash a custom ROM, or make MIUI stop restoring system recovery on boot up. The most common way to keep TWRP with MIUI is to install Magisk.
If you are planning on using custom ROMs, then I would recommend the official TWRP, or the current 'dev' version from the official maintainer both are found here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you plan on sticking with MIUI, then there are a number of TWRP options that have additional functionality specific to Xiaomi devices - e.g. MIUI debloat scripts.
Many of these tend to be from Chinese, Russian and Indian developers, where Xiaomi phones are most popular. A selection of them can be found here.
https://forum.xda-developers.com/k2...irmware-10-3-8-0-9-6-13-t3939647/post79726515
Personally I don't use MIUI so haven't used these much, however OrangeFox seems to have some unique extra functions, like being able to survive OTA updates. So I would guess OrangeFox should be the one to recommend for those that choose to stick with MIUI.
ROOT
----------
Magisk has become the main choice for rooting, so use it. If you have problems with root and you're using something other than Magisk, you're going to struggle to get any help.
Magisk also does so much more than root. Check out the very good official documentation here for all you need to know.
It includes flashing instructions, which is the same whether you stick with MIUI or have a custom ROM. https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post68966662
INSTALLING THINGS
From here I will assume you have some basic knowledge. I will not list every single step/command. The instructions won't be high level but at mid level giving enough details for those with basic knowledge. Many links in the previous post should give most of the knowledge needed, so there's no need for me to repeat things too much.
Where fastboot commands are given, I will assume you know how to use them i.e. you will open a terminal/command prompt/power shell window and also navigate to the appropriate directory if required.
I will assume you have checked the phone is connected with the
Code:
fastboot devices
command
INSTALLING TWRP
------------------------------
- Put the phone into fastboot mode (power and vol-) and connect to a PC
- On the PC
Code:
fastboot flash recovery TWRP.img
here you will need to replace TWRP.img with the actual file name of the TWRP image file, including the full path details if necessary.
At this point you have successfully installed TWRP, but if you boot into MIUI it will be lost. From here you need to boot immediately into TWRP in order to perform further steps to persist the TWRP installation.
- Whilst still connected to the PC
Code:
fastboot reboot
- Now as soon as you send the above command press and hold volume up on the phone
- Keep holding volume up until TWRP boots.
Now you are ready to do the next step. Depending on what you are doing this is likely to be flashing a custom ROM, installing Magisk or installing Orange Fox.
Reserved 2 - coming soon ish
Reserved 3 - hopefully not too long to wait
Thanks a lot for your time! New to this, because usually i buy Global phones, first time i buy a 100% Chinese one...
Interested in what ROM's you would recommend!
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Kalp3sh S1NGH said:
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Click to expand...
Click to collapse
Initially that was what many people thought. But after people have flashed the Chinese ROM on an Indian phone, they have found that they've got a working NFC chip.
Sealed Chinese ROM works well after switching the language to English.
1) Update to the latest MIUI
2) Make sure Google Services is enabled
3) Install Google Play from APKMIRROR
4) Install Calendar Sync (make sure set it to autostart)
4) Install Contact Sync (make sure set it to autostart)
5) Install Google Pay, Google, Gmail, Drive, Google Keep, Photos etc
5) Install an English keyboard (I don't think you will like Sogou keyboard)
6) Delete all other bloatwares.
You can almost remove almost all bloatwares without ADB or root, except those of Xiaomi's.
Kalp3sh S1NGH said:
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Click to expand...
Click to collapse
Robbo.5000 said:
Initially that was what many people thought. But after people have flashed the Chinese ROM on an Indian phone, they have found that they've got a working NFC chip.
Click to expand...
Click to collapse
There seems to be conflicting evidence here. Indian users have reported that they got a working NFC after flashing an official China ROM, but there's a new teardown of an Indian phone which appears to show that the NFC chip is missing.
It may be that some Chinese built phones were shipped over to India to cope with the initial demand, but that's a pure guess.
Robbo.5000 said:
There seems to be conflicting evidence here. Indian users have reported that they got a working NFC after flashing an official China ROM, but there's a new teardown of an Indian phone which appears to show that the NFC chip is missing.
It may be that some Chinese built phones were shipped over to India to cope with the initial demand, but that's a pure guess.
Click to expand...
Click to collapse
I just installed MIUI MS because I was facing some deep sleep issues on the stock ROM.
And there is a setting for NFC but if I enable it, it just turns back off. So maybe my particular device doesn't have the NFC chip.
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
NoobRookie said:
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
Click to expand...
Click to collapse
Xiaomi.eu is a custom rom you need twrp to flash it.
NoobRookie said:
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
Click to expand...
Click to collapse
If you are on an official MIUI stable ROM and checking for an update says you have the latest version, but you know there is a newer version, then you can manually update by following that guide, using the section for updating via the updater app.
If you want to install anything that's not official MIUI, then you need to install that with TWRP.
One last dumb question:if I buy the factory sealed version of the phone with Chinese Rom, will I be able to change it to Global official Rom when it comes out? Or will I just get OTA updates and that's it, no possibility of changing official roms?
NoobRookie said:
One last dumb question:if I buy the factory sealed version of the phone with Chinese Rom, will I be able to change it to Global official Rom when it comes out? Or will I just get OTA updates and that's it, no possibility of changing official roms?
Click to expand...
Click to collapse
Yes you can change ROMs. You can flash an official Indian ROM using the Mi Flash Tool. See this post about flashing the Indian ROM https://forum.xda-developers.com/k2...king-flashing-india-rom-t3955129/post80025306
Nobody will know for sure that you can flash an official global ROM until its released, but best guess is that you would be able to.
Well I'm reading this from a galaxy note 4... a sh*t ton has changed, or at least it is very different with non-global phones.
If I understand correctly, the best, most safest way is to buy chinese factory sealed version so you can unlock the bootloader in case you lock it.
Which colour do you guys prefer, I like blue but I watched Frankie Tech video(s) and the red colour looks sick. Oh if you buy blue version will camera light also be blue lol. Gonna check out the other colour in another video.
Btw great guide, will try to stick with this note 4 for one more year as it just works fine!
Can anyone in UK confirm their experience with the signal/bands/carrier.
Windroid-user said:
Well I'm reading this from a galaxy note 4... a sh*t ton has changed, or at least it is very different with non-global phones.
If I understand correctly, the best, most safest way is to buy chinese factory sealed version so you can unlock the bootloader in case you lock it.
Which colour do you guys prefer, I like blue but I watched Frankie Tech video(s) and the red colour looks sick. Oh if you buy blue version will camera light also be blue lol. Gonna check out the other colour in another video.
Btw great guide, will try to stick with this note 4 for one more year as it just works fine!
Can anyone in UK confirm their experience with the signal/bands/carrier.
Click to expand...
Click to collapse
It's more a case of Xiaomi doing things different. They have an awkward bootloader unlock process. It needs to be done through their unlock tool, where you need to log in to a Mi account to use it, and that Mi account must already be bound to the phone you want to unlock, and you must have already registered, on the phone, to unlock the phone, using the same Mi account.
I've got the blue phone and yes the lights around the pop-up are blue.
I've not used it in the UK, but it should be fine on EE, Three and Vodafone.
O2 may be hit and miss depending where you are. Originally O2 only used band 20, which is missing from the phone, but a while back they added extra bands, this was in major cities and large towns. I'm not sure if O2 have rolled out these extra bands across more of the country since then.
Robbo.5000 said:
It's more a case of Xiaomi doing things different. They have an awkward bootloader unlock process. It needs to be done through their unlock tool, where you need to log in to a Mi account to use it, and that Mi account must already be bound to the phone you want to unlock, and you must have already registered, on the phone, to unlock the phone, using the same Mi account.
I've got the blue phone and yes the lights around the pop-up are blue.
I've not used it in the UK, but it should be fine on EE, Three and Vodafone.
O2 may be hit and miss depending where you are. Originally O2 only used band 20, which is missing from the phone, but a while back they added extra bands, this was in major cities and large towns. I'm not sure if O2 have rolled out these extra bands across more of the country since then.
Click to expand...
Click to collapse
Thanks for the reply. I have done a bootloader unlock before with the Sony xperia z3 using the official website, but there was no need to have an account linked to it kind of like apple icloud nightmare. Thanks for the info luckily I don't use O2 only Vodafone and three so far (8gb for £9 with three! Secret/hidden deal, no cashback bull). I would probably also go with blue.
That being said... the only benefit of stock China rom is OTA updates compared to "global" rom? I know there are custom roms but want to try out stock first, least bugs and only fair to give it a chance. Just want to build up my knowledge on this before I decide to say goodbye to my note 4. Also the actual global rom is on its way as far as we know?
Windroid-user said:
Thanks for the reply. I have done a bootloader unlock before with the Sony xperia z3 using the official website, but there was no need to have an account linked to it kind of like apple icloud nightmare. Thanks for the info luckily I don't use O2 only Vodafone and three so far (8gb for £9 with three! Secret/hidden deal, no cashback bull). I would probably also go with blue.
That being said... the only benefit of stock China rom is OTA updates compared to "global" rom? I know there are custom roms but want to try out stock first, least bugs and only fair to give it a chance. Just want to build up my knowledge on this before I decide to say goodbye to my note 4. Also the actual global rom is on its way as far as we know?
Click to expand...
Click to collapse
At the moment there is an official Indian ROM, which is more or less the same as a global ROM, the jury is still out as to whether OTA works OK when flashed on a Chinese phone. It 'should' be OK, but there hasn't been an update to the Indian ROM yet, so nobody has been able to find out for definite.
MIUI isn't without it's bugs. The week I used it there were a couple of issues, and there's a thread just for collating bugs on the Indian ROM.
The global version of the phone, the Mi 9T Pro, should be released in the next couple of months. It's been seen on a Dutch online shopping site in the last week. It was only showing the 2 6GB models, but I've been expecting that, as the Mi 9 never came with 8GB RAM globally. It's €480 for 6/128 GB, so a huge mark up on the Chinese price. Once that's released then official global ROMs will become available
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
You basically have 3 choices to acquire the boot.img:
1. Payload Dumper
2. TWRP and adb
3. Download the stock boot.img for your version of Hydrogen OS (if it exists)
There are "auto root" tools out there, but not sure how they are. I personally used #2, but payload Dumper works quite well too.
Pretty sure the auto root tool on here works on any version of ROMs. But keep in mind that when you wanna perform a OTA update after root using the restore image method, the auto tool backed up the extracted stock boot image on our pc rather than letting Magisk does its normal job and store in our phone the way Magisk wants. What I mean is that we essentially lose root first and need to re-run the auto tool after each OTA update. I'm just lazy to get perform the normal methods, so I just double click on that auto tool each time and let it does its job each time I lose root after each OTA update. I remember it actually worked flawlessly and let Magisk back up the stock boot image at first, but then after some OTAs later when I messed up and reset factory settings in recovery and had to re-root my phone using the tool, magisk acts weird and stopped storing a back up boot image in the phone.
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
S1nPur1ty said:
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
Click to expand...
Click to collapse
I'm Chinese, and I can help you to download last version H2OS.