Related
The phone allows you to enable bootloader unlocking in the developer options. So, I was wondering what command is needed to enable it?
I have no clue, I've been searching high and low, trying to figure out a way to root this device and I've hit a wall at every turn. Any help would be appreciated
Zte firmware needed
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
uni-android unlock tool will unlock bootloader so you can root the n9137 and many other devices... it cost 50 bucks and its good for a year of unlimited unlocking. GOOD LUCK!
Any progress on this front? I have a ZTE Tempo X N9137 HW1.0 from Assurance Wireless (Free Gov't phone).
I Just want to root this phone, so I can run rooted apps. I am not interested in installing other ROMs (I am not sure, but my feeling is that I have to leave the original ROM alone in order for this phone to continue to work w Assurance Wireless under the gov't lifeline free cell program - someone correct me if I am wrong and it is confirmed that I can actually ROM better ROMs into this ZTE and continue to work normally with Assurance Wireless.)
Do I need to install TWRP or CWM in order to root the ZTE, or can I use ADB and Fastboot to unlock the bootloader and install Magisk or SuperSU to allow root?
I googled around, but I can't find TWRP or CWM for the ZTE N9137.
Any help or link to guides specifically for the ZTE Tempo X N9137 is greatly welcomed and needed,
Thanks
What is needed?
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
SP6RK said:
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
Click to expand...
Click to collapse
Root ZTE Tempo X N9137 Assurance Phone
sketchscarz said:
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
Click to expand...
Click to collapse
Any luck rooting this phone using KingRoot?
Has the Bootloader been unlocked yet?
If I ever get this phone rooted,. will I be able to replace the ROM?what will happen to the Assurance portion of it? WIll it still work as a free gov't phone, or does it need to have the Assurance software to work as the free government phone?
I need to root this phone so I can run rooted app to expand the very limited built in storage space. I cannot install any new app because there is no more storage space. The solution is to allow App2SD or other app that install apps into the SD card, but this requires root access.'
any help greatly appreciated
Hey guys - I good news to report. I successfully rooted my ZTE X N9137. Running Android 7.1.1 build version N9137V1.0.0B08 which is the most current. My phone came with a Sprint SIM and the phone service is Q-Link I have screenshots of the installed root apps I used and also all the bloatware removed gone from the Apps Drawer. I rooted using KingRoot but not via the apk. I am working on a guide and also going to recreate to verify the steps. I used the combo of scripts that I found from site that I linked below. The requires an account to download but it's free. A couple of things I discovered
Start with the phone in EDL Mode:
The phone needs to be in EDL mode (blank screen but is still powered on).
from adb run this command
adb reboot edl
Or run the edl.bat from the /root/ folder
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
https://www.filehosting.org/file/de...ucion de Desbloqueo 100% TESTED Halabtech.rar
Original script package:
https://support.halabtech.com/index.php?a=downloads&b=folder&id=33472
Stock Firmware Site:
https://combinefile.com/index.php?a=downloads&b=folder&id=15471
I was able to download one from their site before having to pay money. YMMV
https://drive.google.com/drive/folders/1GhQof56lwMZvAsk25J-ONo-DEesXliQ3
This guy has an older version: N9137V1.0.0B04
How to flash ZTE roms:
https://www.leakite.com/how-to-flash-zte-stock-rom-firmware-via/
Service Mode - Enter this dial:
*983*0#
Here are screenshots of my ZTE N9137 without all the bloat! "Kingroot - Remove Bloatware" removed
40 pre-installed apps which most were installed as a service which requires to root to remove.
Everything runs some much smoother now.
Based on the overwhelming response with my previous posts, I am continuing ahead. I was again successful at getting root. Attached a couple of pics.
Since I have been unable to unlock the bootloader, the process is only temp
Unlock hotspot, add to APN internet.. APN type default,dun,mms,hipri. Use by4 setting editor to unlock hotspot
Link to mirror of the script is broken. Anyone have a copy? I have found a copy of the script. I can confirm it works. If anyone needs it let me know
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Nice to see things advancing. Any progress with TWRP yet? Looks like you've been working on it based on your GitHub deadman...
Help Rooting ZTE N9137
Hi! I'm kind of a newb at the rooting process so I was hoping someone had a guide on how to root this phone. My version of this phone is from Qlink Wireless with a Sprint SIM installed. Thank you in advance!
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
CivicObligation said:
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
Click to expand...
Click to collapse
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
deadman96385 said:
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
Click to expand...
Click to collapse
Thank you! Seems so obvious after you explained. Any suggestions or advice on FH loader errors? The log says my device is not on the current port once it tries to actually write to the device.
deadman96385 said:
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Click to expand...
Click to collapse
Can you confirm if this technique will network-unlock an N9137 linked to Assurance Wireless? Or is this not possible yet?
Thank you
---------- Post added at 11:46 PM ---------- Previous post was at 11:10 PM ----------
n2locarz said:
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
filehosting.org link
Original script package:
hablatech.com link
Click to expand...
Click to collapse
Both of the above links don't work. The filehosting.org link is broken or dead and the hablatech.com download is behind a paywall, even if you create a free account on their site.
Does anyone have a link to this script? Also if successful, will this approach network-unlock my phone?
PS. I'm not allowed to post links with a new account so I had to edit them out of the above quote. However you can find them in the original post.
Hello again,
I've proceeded to try Deadman's strategy to install the stock rom he provided. I've implemented the fix to remove references to empty '.img' files in the rawprogram0.xml. The helper files and the rom have been unzipped to the same folder, such that Deadman's rawprogram0.xml and patch0.xml have overwritten those provided in the firmware image folder, which I believe is the correct method.
When I reboot my phone into EDL mode using adb, the QFIL application recognizes the phone as "Qualcomm HS-USB QDLoader 9008 (COM6)" and I can begin the flash.
However, the flashing hangs or stops when it reaches the following stage:
Code:
2019-04-15 12:42:34.015 12:42:33: INFO: {percent files transferred 2.78%}
2019-04-15 12:42:34.016 12:42:33: INFO: In handleProgram('recovery.img')
2019-04-15 12:42:34.016 12:42:33: INFO: Looking for file 'recovery.img'
2019-04-15 12:42:34.017 12:42:33: INFO: =======================================================
So it appears that there is an issue with the recovery.img file. However this file is both present in the same folder and non-empty. What could be the issue here?
Cheers.
After many searches for the best help on my new Asus ZenFone V V520KL, I have no way to unlock the bootloader. Asus doesn't provide any support for this 2017 model, nor does Verizon, the company the phone was made for.
It comes stock with Nougat 7.0 OS, 32 GB ROM & 4 GB RAM. It's got a decent size screen and runs not too too bad.
I'm wondering if one of the tech people here would be so kind as to help me with not only unlocking the bootloader so I can then install a custom recovery image, preferrably TWRP, since I have used this type of program before on my other ZenFone 3 Zoom.
I already have ADB tools on my Windows 7 notebook (32-bit). I used it to install the last root on my other aforementioned phone so it will work.
What I'm wondering about is the bootloader unlock tool, custom recovery image (TWRP), and a way to root the bastard. Hopefully we can relock the bootloader after the job's done because it's annoying on my other phone to always have to bypass the "Can't check for corruption." screen before the phone actually boots. Again this is for the Asus ZenFone V V520KL model. There is really no information anywhere right now I know of that gets this job done.
Having a custom Pie 9.0 ROM upgrade would be the best if possible once we root the device.
My name is Andrew, S.D. from Canada.
Thanks and blessings.
Root
Did you find a way to root it?
No, I still need help with the original post. I can root the ZenFone 3 Zoom ZE553KL but they already tell us how to do that in another forum.
the Bootloader for v520kl is already unlock by ENG Firmware
Just serch it in forums
You're talking to a noob. Give me the location of ENG firmware.
Hi friend, in the other post de link for downloading de ENG Firmware is broken
[email protected] said:
Hi friend, in the other post de link for downloading de ENG Firmware is broken
Click to expand...
Click to collapse
This is the link
http://www.mediafire.com/file/lc17b75qbvy018z/Asus_Zenfone_V_V520KL_All_WW_ENG_T3.3.15.zip
I tried to flash it did not work for me..
---------- Post added at 10:55 PM ---------- Previous post was at 10:43 PM ----------
Doctor Andrew said:
You're talking to a noob. Give me the location of ENG firmware.
Click to expand...
Click to collapse
Here is the link:
https://forum.xda-developers.com/showpost.php?p=78833735&postcount=52
Hi friend,
It's de the same rom for this page
https:
www
hardreset.info/devices/asus/asus-v520kl/faq/firmware/ because, the size of this rom is 813MB
and the size of the rom of the link that you provide is 775.53 MB and the files is the same name.
or this rom has been updated.
someone know what version of android have this rom
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Doctor Andrew said:
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Click to expand...
Click to collapse
To flash the ENG rom, you do not need to unlock the bootloader. Just the Asus flash tool.
Once you flash it, you can reboot to fastboot mode(adb reboot bootloader) and use fastboot oem unlock to unlock bootloader. Be warned though the ENG firmware is very basic. No web browser, no google play, you can't pull down the notification bar etc. (Great battery life though with about 7-10 days since I am not using it at all).
As of right now, there is no TWRP for it that i know of. In fact, I can't even boot into recovery atm. I also am unable to get boot.img file form the .raw file so the various methods to root it seem to be out of reach for the moment.
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Doctor Andrew said:
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Click to expand...
Click to collapse
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
oh my god - rooooot
faericia said:
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
Click to expand...
Click to collapse
Good time of day, Faericia, this is just great news. You can share the experience of getting root with magisk?
Regarding Google Play and all that, where you need Google, using a bunch of microG and Aurora store.
MicroG is the core of Google services, which allows you to pass authorization through Google, synchronize and do it all without any garbage code, according to my observations, the expense is not much spent.
Aurora shop, as an analogue of Google Play, the application, the ability to save apk.
Due to the lack of binding to your Google account.
I think this connection may be relevant and rooted.
The initial partition should appear as root, it intends to resolve all the problems that I have in my phone. for asus applications, after I have done my best, several attempts have already been made.
It was possible to look in read mode using root explorer.
Perhaps you can somehow remove the protection of verizon on the bootloader.
PS the most hardcore variation of raw firmware, a hex editor, search in that between code, boot, recovery, system, etc. Very large empty spaces. previously there were 100 miles earlier.
I think this is part of verizon jokes.
This article should be cut and placed in img.
Thanks so much in advance.
hello when you finish you could share through a tutorial what you did I have my asus v with verizon rom and only data but if I can make it functional with the rom eng then better
Okay, Here are the steps. Before anything else though, I should warn you that I have not been able to get safetynet to pass. So if you have apps that require safetynet to pass, this may not be the way to go.
First you will need the ENG firmware:
https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/
Also Asus Flash tools v 1.0.0.72:
https://drive.google.com/file/d/11rcjOgdpJhpK97GzbhYK6cYEIWOtzKE9/view
I am assuming you know adb and such. If not, search the forums and get the adb tools.
Using adb, Reboot to bootloader. ( adb reboot bootloader )
Load the .raw file in the asus flash tool, select v520KL and flash.
Once flash is done, unlock bootloader by going into bootloader (adb reboot bootloader) then type (fastboot oem unlock.)
Here is the patched_boot.img I used if you want to just try to flash that and see if it will work. This is for the eng firmware.
https://drive.google.com/file/d/1fUxGc27lrodR3ro9MIspde73G8Xg9VlW/view?usp=sharing
Go into bootloader and flash. (fastboot flash boot patched_boot.img)
Install magisk manager and test it out.
If you wish to patch the img yourself, the steps are below (still working on it):
So now we have the phone unlocked, and the software is very basic. We also need the boot.img file to patch since we do not have TWRP. Since I couldn't get it from the raw file (the extracted file is invalid with a size of 0 bytes) I decided to extract it from the phone. But to extract from the phone we need root. So for this next step, temporary root will have to do.
You can get temp root by using KingoRoot. Use the PC version and you will get root. This is just so we can extract the files from the phone itself.
I need to find the steps for the next steps again, but the basics is, extract boot.img from the phone. Patch it using magisk manager and then flash the patched_boot.img in bootloader mode. I had google play working(chinese version) but once i removed kingoroot it kept crashing. I currently have magisk and it gives me the root permissions but safetynet fails. I will retry this tomorrow and see if I can fix the safetynet issue and update this post with the steps.
Also I seem to have borken recovery mode on my phone. That may be because I tried flashing bunch of other stuff before I managed to root it so I do not know if it will be the same situation to you or not. I believe after I flashed ENG firmware, i had access to recovery mode at one point, but I may have just messed it up. Either way, Expect updates in the near future.
asus recovery
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Daniel.Sim said:
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Click to expand...
Click to collapse
I know recovery mode was working with VZW firmware. I know this because I tried installing using adb sideload several times. I might be mistaken on getting there once i flashed eng firmware but again, it has been a month or two since I tried it and all I know is, it won't go into the recovery screen now. Oh well, not my main phone so irrelevant.
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
game #1 said:
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
Click to expand...
Click to collapse
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
faericia said:
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
Click to expand...
Click to collapse
I found out how to stop frameworks from crashing. Just make it a system app. I use link2sd for this.
Now all gapps work nice.
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Julio2019 said:
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Click to expand...
Click to collapse
Sorry, I don't really have the time or the facilities to make a tutorial video, but the Chinese instructions follow the same process, only breaking up the process into a few more steps. Both achieve the same result. My thinking is that you might be able to install the Chinese firmware, but some forum discussions suggest that you will have some modem and IMEI issues if you do. There are ways to back these up using QPSTs software download application. My guess is that it'll probably work, but that it won't work flawlessly. Let me know how it turns out if you try it.
If you want to update your software without rooting, simply follow the process from step 5, using the new L38041_ROW ROM without swapping the boot.img. The link below shows the flashing process pretty well, but you'll need the later versions of QPST since you'll be using .elf programming paths and not .mbn. Once again, that will wipe your phone entirely.
"https://www.youtube.com/watch?v=W9Cz4LwAzLg"
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Julio2019 said:
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Click to expand...
Click to collapse
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
rlb596 said:
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
Click to expand...
Click to collapse
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Julio2019 said:
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Click to expand...
Click to collapse
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
rlb596 said:
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
Click to expand...
Click to collapse
Agree. Hope they focus more in the subject we are talking. By the way, i have checked the club.lenovo's, and they got another new update with more improvements and a fix for their wechat app. , Now they are on zui 5.0.188 st. Could you show me images of the zui 5.0.117 interface, if you could. If not, don't worry i'm going to google it. But leaving this aside, i'm satisfy with the phone, in my opinion, is a great phone!, I like it, has excellent performance, a cool design, is slim, have a nice display, and good cameras. Have a nice day, hope we could talk again soon. If i get any more news, be sure i'm going to share it. Here in xda, i think we are the only ones who are talking about this phone. Hope more people and xda developers join us. Thanks. God blessed you.
Latest .188 st ZUI's interface changes a lot, but is the chinesse variant of the ROM, it comes with chinesse apps and only english and chinesse languages installed. Deleting the chinesse bloatware is easy, there is a folder named "preloaded" or preinstalled (something like that) in /system/ get root rights and delete the entire directory.
please create forum
rlb596 said:
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
Greetings Mr rl596!
So, what order do you recommend, i have downloaded KiiKeEp files, and successfully have receive my unlock image from lenovo, but in with order do i need do thinks. Is the following order correct?
1.- unlock bootloader
2.- Install zui 5.0.117 st ROM
3.- Install TWRP image
4.- Root device
Is this order correct?, I have the CN ROM in hand too, tha latest one is .188 st. But i need to make an EFS backup with the QPST tool, just in case. I have ask KiiKeEp, i'm waiting for his answer too. I want to make a video tutorial, so more K5 pro users could get benefit of this, and use all the potential this phone has. But what benefits does a unlock bootloader have?, Oh, and I almost forgot, for the QPST tool, do i have to install the driver that shows in the Device Manager as L38041 or the one that shows as QUALCOMM?
. Thanks in advanced.
Hi.
Thank you very much for the instruction - I successfully got root on my phone.
The only difference is I didn't use ADB, I just entered Download mode via the buttons: hold the volume + and - and power down until the logo flash.
:good:
Hi guys,
I tried but i have an error "Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable"
log :
13: E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf
00:25:31: Requested ID 13, file: "E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
00:25:32: 622900 bytes transferred in 0.203000 seconds (2.9263MBps)
00:25:32: File transferred successfully
00:25:32: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\denis\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable (The specified file is not found)
Finish Download
do you have any idea ?
thx in advance
I was wondering if there is a difference between CN version and global version regarding future update which device should i get for better support or root
Hi, I have unlokced the bootloader and install magisk via twrp. Is there custom roms for this phone
O meu lenovo apresentar "Qualcum crushdump mode" alguém com isso?
---------- Post added at 05:04 AM ---------- Previous post was at 04:54 AM ----------
O meu lenovo fica no final do processo com "Qualcum crushdump mode" alguém conseguiu resolver isso?
Help! I do the first process but now i can´t enter phone because tell from password on encryption screen.
EDIT: I enter to EDL mode (Press Vol- and Vol+ at the same time and conect to the usb) and flash with QFIL with the original boot.img and the phone turn on normally.
Lenovo K5 Pro ROM
Hi.
Are you have good working ROM for Lenovo K5 Pro?
This is an awesome, awesome phone. I rooted it with Magisk boot image patching on PC, without TWRP and even installed GCam on it to improve the camera massively - can now take photos with Night Sight. The specs of this phone are AMAZING for its price. And the best part is it is without any notches, holes, pop-up cameras and retains the traditional clean design.
I tried the unlock bootloader (official) way to root the device but got stuck here:
Code:
C:\minimal_adb_fastboot_v1.4.3>fastboot flash unlock sn.img
target didn't report max-download-size
sending 'unlock' (5 KB)...
then nothing happens (waited for like 10 minutes).
Tried to install QPST 2.7 (3 different versions, same error) but setup gives me the following message:
Code:
the installer was interrupted before QPST 2.7 could be installed
SOLUTION: Download QPST Portable
---------- Post added at 08:25 ---------- Previous post was at 07:57 ----------
Getting Sahara error but not because I've waited too long! Any solutions? Getting desperate now.
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
Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".（Some Chinese citizens reported a similar situation.）If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
can i flash global rom after unlocked bootloader ?
i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.
Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start
bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy
klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse
Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!
I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks