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.
Related
Downloads are in the second post.
So what is this?
This is a continuation of Lokifish's work for those wanting a secure, rooted, stock experience beyond the firmware that shipped with their watches. Right now this will only run in Windows or Windows VM.
What am I getting?
I have packaged three separate packages that update your watch to the latest Omate Smart firmware (contains Smart Mode and some battery/bluetooth enhancements) 05/27. The NA package will update your watch to 04/11 and the patch will do the rest.
Will this work on my ______ unit?
As long as your unit is an x201 derivative, yes. This has been confirmed to work on new aluminum units as well as 512/4 units. You will likely have to wipe data after applying the patch.
Anything to watch out for?
There are known bugs on the 05/27 Aluminum watches - namely that recovery on many of the new EU units is not functional and thus a factory reset may not be possible. I'll have to look into a fix to find out why this is happening (it doesn't happen on older units).
Is this firmware official?
Yes. It's not officially supported by Omate, but it is sanctioned to be flashed onto your units.
Instructions READ CAREFULLY
Download the All-Tools package below.
Download the appropriate firmware package for your unit.
Install the Universal ADB and Preloader Drivers for your watch.
Load up MTK Droid Tools and BACKUP YOUR IMEI AND APPS TO YOUR SD CARD OR PC.
Disable Quick Boot under accessibility settings.
Load the scatter file in SP Flash Tool and turn off the watch.
Click Download immediately and allow it to finish.
Turn on the watch and wait for it to finish booting.
Run the Run.bat file included in the Universal Tool folder and follow the prompts.
After the final reboot, you should be all set!
On newer units you may not reboot into recovery when the script completes. You likely will need to reboot using adb or pull the battery if it gets stuck in a bootloop. Usually it will just power right back off instead of going to recovery. If this happens, just turn the watch on and you should be set.
It goes without saying that I'm not responsible if your unit becomes damaged or bricked as a result of your not following instructions. I cannot possibly account for mistakes that are beyond my control.
Also, when you load the scatter files some of the files will not show up - this is NORMAL because the firmware differences only lie in the kernel and system images.
If you appreciate my work, and especially the work of other developers, feel free to donate. It'll let us know whether we should continue to support devices that manufacturers no longer support so that the user has a better experience. I have a full-time job outside of this, so this is all done on my own time. I never ask for donations, but I will not reject them.
CHANGELOG
(v1.3)
Added AOSP Camera to replace the stock camera.
Added MTK HDR libraries.
Added Panorama/Photosphere libraries (although it currently crashes, Panorama is fine).
Restored 5MP function by fixing with newer libraries from Umeox firmware.
(v1.2)
Fixed TWRP 2.7.1.0 for EU units.
(v1.1)
Fixed EU packages to contain correct kernel images.
Added fixed packages for TWRP 2.7 on newer watches.
Sensors should be fixed with a kernel reflash.
(v1.0)
Enhanced battery life through Smart Mode.
Functional sensors.
Applies Lokifish Marz's Enhanced Security Patch (init.d support, APN hosts updated, Kernel tweaks).
Re-establishes user-controlled root privilege on all units without the use of exploits or Framaroot (will likely need to update the binary).
Changes boot animation and logo to something a little less eye-breaking and a little more eye-pleasing.
CREDITS
Dees_Troy (for his work on TWRP for the TS and for helping me figure out the zImage problem)
Lokifish Marz (for his EnSEC script & kernel tweaks)
Koush (Universal ADB Device Drivers)
llp (for the stock factory images and firmware)
BSDgeek_Jake (modified APN/hosts list)
Adam Outler & Ryan Scott (for continued help in teaching me the new ways of coding and development)
CharlesGoodyear (for inventing the vulcanization of rubber)
KNOWN BUGS
Switching to Photosphere will crash the Camera. Please don't do it.
When entering Preloader sometimes the battery indicator will look garbled.
A factory reset for some reason doesn't seem to want to erase userdata. I'm pretty sure I know what's wrong here.
----------------
LINKS
Get the All-Tools package here. Back up your IMEI and apps to an SD *BEFORE YOU FLASH ANYTHING*.
NA Firmware users should click here for the download.
EU 512/4 users or those with non-aluminum, non-May firmware units must click here unless you want to soft-brick your device.
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway). Do not flash any other firmwares unless you want to soft-brick your device.
Get the patch/root only script here if you are already running 05-27 or 04-11 firmware on your watch. I recommend you still flash the boot logo from the appropriate package for the full experience.
If you're experiencing force closes on your Camera module when switching to 5MP, click here. You can also download this if you want to switch to the Stock Android camera and get some HDR libraries out of it.
TWRP Update
Download TWRP 2.7.1.0 for May 0513/0527 units here if you received your watch after May and flashed the May Shipment firmware. Your watch should be able to boot into TWRP if it previously would not.
Common Solutions to Uncommon Problems
I ran the script but it says no device found after I plug it in and hit enter.
Make sure you have developer mode enabled (Settings -> Build Version -> Click until it says "You're a developer!") and USB-debugging enabled.
Make sure you also installed the ADB drivers and that you have a USB connection to the watch.
I'm getting a PMT error thing when I flash, what gives?
You downloaded the wrong version for your watch. Pull your battery, download the correct version, and try again.
Now I'm getting a BROM ERROR.
I told you it was the wrong version. You'll now have to find someone who has a scatter backup of the same unit you own and flash that.
Then do this all over again.
Now I'm getting a BROM ERROR 4032 or 5054!
You flashed the wrong version and will need to pull the battery out (most likely). After resetting the preloader, go ahead and try to flash again using the correct scatter file.
I click Download and the bar fills to 100% and just sits there.
Your preloader has been disengaged and is not communicating with the PC anymore. You will need to pull the battery and try again.
But that voids my warranty!
What warranty?
When I plug the watch in it keeps connecting and disconnecting over and over.
Your preloader has been disengaged. See above.
My computer is trying to install some Alcatel drivers or thinks my TS is a Yun OS phone.
You will need to uninstall all of those drivers manually (and delete if possible). Uninstall your drivers using USBDeview and reinstall the preloader drivers. When you plug your watch in, you will need to flash your preloader backup first before attempting to flash any firmware.
I'm getting some checksum 16 baseband sram error thingy! Now what?!
Check your cradle's pins and your watch to make sure a solid connection is taking place. If none of that solves it, you might actually have a defective watch and there's very little I can do for you short of you sending it to me to fix.
Why does my version number not say 0706?
Because you forgot to run the update batch file in the included folder. Run it and your worries will be gone.
Why did you not include Play Store in this release?
Because it's ridiculously easy to install and most people install through recovery (which I recommend if you have a working one). I may do this in the future if enough interest is there.
My IMEI is gone!
Told you to back it up. Go to your watch's box, write down the IMEI, go into MTK Droid Tools, and restore it. If you did back it up, then go in and restore the backup. Bonus points if you backed your entire firmware up and can restore your NVRAM data as well.
My watch is doing _______! Your script did it!
No, it didn't. The only thing the script does is modify stock apps/settings by adding things that either aren't there or modifying non-essential system processes. If something is wrong with your watch, I guarantee this script is not responsible.
I can't get phone calls anymore! Your script did it!
See above.
Why isn't my watch booting into recovery?
You likely have a watch with the new eMMC revision and thus have a borked factory recovery from the beginning. I don't modify the recovery in any way but I do include a copy of @Dees_Troy's TWRP in case you are lucky enough to not have a borked recovery. You can either flash this through SPFT or through MTK Droid Tools. Droid tools is easier.
So my stock recovery won't even work then?
Nope. I'm currently working on a fix. Stay tuned.
Why is Bluetooth messed up? Fix it!
This is beyond my control. Android 4.2.2 has messed up Bluetooth stacks to begin with, and since this is an engineering build there is nothing that can be done about it.
Why is my GPS/Wi-Fi/Bluetooth signal so weak!?
This is not the firmware. This is your hardware. Your antenna is likely defective. Contact Omate support for details on replacement and hope they can assist you.
I flashed the May Firmware update and now my watch bootloops!!!
Download this file and replace the lk.bin/boot.img in your folder with the ones from the patch RAR and reflash.
After updating to 0706, my watch seems a little laggy or unresponsive. What now?
Have you tried factory reset? If you kept your userdata intact there's always that chance that things could get a bit turbulent.
If you factory restored the watch afterwards and you're still experiencing lag, check system processes to see what's hogging it up and let me know.
Wohoooo! Thank you so much! Will try it! Is Bluetooth tethering possible?
Gesendet von meinem GT-I9295 mit Tapatalk
It's stock, so unfortunately no. Not without xposed and some other apps that cost money.
okay! maybe you could talk to "dees_troy" and ask, if you could merge his fixes (-> http://forum.xda-developers.com/showthread.php?t=2697984 )
Hello
Did anyone manage to do the procedure?
To upgrade the firmware, in SP flash tool, do I need to Select "Firmware -> Upgrade" by default, it's "Download Only"
I have a may shipment EU 2100 1/8 TS
I finally managed to do the first steps (selecting Download Only)
Flashing went good.
But after reboot, I had a bootloop (with the new boot logo so flash worked)
I had to take the battery out for the first time
I flashed my personnal backup the sameway, but now is stucked in bootloop too
I have this message in mtkdroid tools when I connect my phone :
--->>> Connect to device <<<---
--- ERROR : do not install utils
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
--- Reboot ...
--->>> Connect to device <<<---
--- ERROR : do not install utils
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
Which did you download?
Sent from my GT-P5110 using Tapatalk 2
@kuronosan: donation is on the way ( 9W627868S22023323)!
Gesendet von meinem GT-I9295 mit Tapatalk
kuronosan said:
Which did you download?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
I downloaded this one https://www.dropbox.com/s/xuno6uj1hduajd7/TS-EU-0706-May_Shipment.rar
Update : i'm still stuck on boot logo on my personnal update (not bootlooping just stuck)
midafaya said:
I downloaded this one https://www.dropbox.com/s/xuno6uj1hduajd7/TS-EU-0706-May_Shipment.rar
Update : i'm still stuck on boot logo on my personnal update (not bootlooping just stuck)
Click to expand...
Click to collapse
When did you receive watch, and what firmware were you running before?
Sent from my GT-P5110 using Tapatalk 2
kuronosan said:
When did receive watch, and what firmware were running before?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
I received the watch in may, and it was running 0513 firmware
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
My personnal backup doesn't have preloader , could that explain my problem restoring and rebooting it?
Okay, might have a fix for you. Hold on.
edit: https://www.dropbox.com/s/5ujs7kxn2munfcw/TS-EU-0706-patch.rar
Flash those two files.
Your personal backup shouldn't matter because you didn't flash a new preloader. All you flashed were the bootloader, kernel, logo, and system images.
Flash the package I gave you again with the above file in place of the lk.bin and boot.img.
Sent from my GT-P5110 using Tapatalk 2
kuronosan said:
Okay, might have a fix for you. Hold on.
edit: https://www.dropbox.com/s/5ujs7kxn2munfcw/TS-EU-0706-patch.rar
Flash those two files.
Your personal backup shouldn't matter because you didn't flash a new preloader. All you flashed were the bootloader, kernel, logo, and system images.
Flash the package I gave you again with the above file in place of the lk.bin and boot.img.
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Yes ! That did it ! You're the man !
I replaced the 2 files you gave me replacing them in the TS-EU-0706-May_Shipment.rar
And it boots ! wow lot's of thanks!
---------- Post added at 08:58 PM ---------- Previous post was at 08:47 PM ----------
Can you tell us what was the problem? And what was the fix?
Thanks !
midafaya said:
Yes ! That did it ! You're the man !
I replaced the 2 files you gave me replacing them in the TS-EU-0706-May_Shipment.rar
And it boots ! wow lot's of thanks!
---------- Post added at 08:58 PM ---------- Previous post was at 08:47 PM ----------
Can you tell us what was the problem? And what was the fix?
Thanks !
Click to expand...
Click to collapse
Certainly. It looks like it was a mismatch between the bootloader/kernel and the firmware. Someone else had the issue previously and that was the fix. I could have sworn I put the correct files in there when I re-uploaded everything.
Basically the May Firmware uses a new bootloader/kernel combo that has to be flashed along with the May Firmware. This isn't an issue on older units, whose bootloader is still okay. If you use a new eMMC unit (0513 and newer) you absolutely need to use new software.
Unsure on 6 and 7 step
Could someone please clarify the steps
6. Load the scatter file in SP Flash Tool and turn off the watch.
7. Click Download immediately and allow it to finish.
Please?
I'll also post a step by step guide as soon as I'll finish the process myself
---------- Post added at 09:42 PM ---------- Previous post was at 09:35 PM ----------
This is a work in progress. Please feel free to submit your suggestions.
1) Disable quick boot:
1.1) On your Omate TrueSmart go to "Settings" -> "System" -> "Accessibility"
1.2) Scroll down and UNcheck "Quick Boot"
2) Install required software on your PC:
2.1) Download "All Tools" archive and unpack it
2.2) Open folder "All Tools" -> "0 Needed Files"
2.3) Run "UniversalAdbDriverSetup.msi"
2.4) Open VCOM Drivers
2.5) Run DPInst (64 or normal depends on your system)
3) Make a backup:
3.1) Open "All Tools" -> "1 MtkDroidTools"
2.1) Run MTKdroidTools.exe
2.2) Connect Omate TrueSmart to PC (it should be turned on)
2.3) Wait till all drivers will finish setting up (on the lower left corner you should see a green rectangle and text "TrueSmart" when Window will finish installation)
2.4) Tab "Phone Information" -> Click button "IMEI/NVRAM"; Click "Backup"
2.5) Go to "root,backup,recovery" tab
2.6) Click "backup" button (this process will take a while)
2.7) Optional: Agree to pack everything in the archive
2.6) Close MTKdroidTools program;
4) Flash the firmware
4.1) Download corresponding firmware archive and unpack it
4.2) Open folder "All Tools" -> "2 SP Flash Tool"
4.3) Run "flash_tool.exe"; don't mind the scatter file warning
4.4) On "Download" tab click "Scatter-loading"
4.5) Navigate to the folder with firmware (from step 4.2)
4.6) Select file "MT6572_Android_scatter.txt"
Another question.
How do you install su on the rom ?
It doesn't seem to be preinstalled
5/27/14 FW
I'm already on 5/27 rom with my US 1/8 1900 TS. I also have TWRP installed using MKTools, but I don't have root. Can I still install this FW? What would be the advantage other than gaining root? Are there any performance advantages since I'm already on the newest FW?
Thanks for keeping this project alive!
kuronosan,
I've tried to flash my TS but ended up soft bricking it. I've got a back up which I'm now trying to flash. SPF Tool gets to the end of 'download da 100%' but then does nothing else.
Using USBDeview I can see the TS connecting, disconnecting and then reconnecting etc.
Is this why it will not flash ? If so want do I need to do to stop this? If not want else do I need to do?
If you could spare any of your time that would be appreciated.
XiaoMiTool, xiaomi rom changing made easy
This post is outdated, please check out the new XiaoMiTool V2. All the details and download: click here
INTRODUCTION:
Ciao, Xiaomi users!
I want to share with you my rom changing tool, which is called "XiaoMiTool".
XiaoMiTool is a software for Windows that can be used to change rom to your device.
This program will automatically detect your device info, roms which are available to install, which installation method to use and everything that is normally user's job.
For example, you receive a smartphone with seller fake rom and you want to install xiaomi.eu rom? This tool will automatically install official rom (via stock recovery or edl), then it will open MiFlashUnlock to unlock the bootloader, then it will install twrp recovery and xiaomi.eu rom, all by itself! (some manual steps are needed like enable usb debugging or manual reboot form edl).
This tool incorporates also stock recovery installation, which is only available in MiPcSuite, where is very limited, so you might be able to change official roms without unlocking the bootloader (e.g. form china to global)
This tool does not require guides as it's designed as guided itself, just enable usb debugging!
This is an alpha version (the tool it's still being developed and more features are coming), it might contain bugs.
This tool is free, but you can leave a donation if you want to.
I really don't know what can I say more, just give it a try and let me know.
LINK:
I still cannot post outside links (grrr), just copy paste url:
- Download latest: xiaomitool.com/latest
- Donation: xiaomitool.com/donate
REQUIREMENTS:
- Windows 7/8/8.1/10
- Internet connection
- (.NET Framework (included in Windows updates))
FAQs:
- Does it work for my device?
This tool is designed to work with the majority of Xiaomi devices, just try it. It only works for Xiaomi devices!
- Can I install this rom if I have this and this...?
Just try, the tool will tell you which rom can be installed.
- Do I need to download anything apart this tool?
No. Just the tool, if you want to install no miui roms (such as lineageos) you need to download them as well.
- Which languages are available?
English, Italian, Portuguese. More coming
- Does this tool unlock the bootloader?
This tool includes official Xiaomi unlock tool, so you still need to have an authorized xiaomi account and bind it to your smartphone.
- This software is recognized as virus from my antivirus!
No worries, it's a false positive. If it gets reported or blocked, you might want to disable your antivirus before using it.
- This program can be installed but not uninstalled, why?
Uninstaller is not ready yet, if you want to uninstall just delete C:\xiaomi\XiaoMiTool folder.
- English translation is pretty bad...
I know, my English is pretty bad.
- This tool doesn't work...
Sorry to hear that, just go back to old manual modding and leave a comment with error codes please.
- Do I need to backup my data?
YES! All apps and data will be lost. In some cases internal storage (photos and files) may be kept, but backup those as well
- Can my device get bricked?
yes, but with very small probability (if very delicate process like edl/fastboot flash gets interrupted). No reports of bricked device yet.
- Can I share this tool?
Yes, you do a favor to me, you can just copy paste this message or do whatever you want. Just let my donation link
- I need to install lineageos with google services and supersu, how can I do that?
Just select zip file installation and select the files, then make sure they are ordered as needed (rom, gapps, supersu)
Looks promising but i prefer manual process instead of tools but this can be useful when flashing through edl mode IDF some ones device gets bricked
Sent from my iPhone using Tapatalk
Sound very Nice! I will Test It!
Nice job!
I just have time to test it.
As a Chinese, I can't use English well.Please bear with me.
---------- Post added at 01:27 PM ---------- Previous post was at 01:20 PM ----------
Fail to test!
"Unable to connect to the Internet."：
c296149548 said:
Nice job!
I just have time to test it.
As a Chinese, I can't use English well.Please bear with me.
---------- Post added at 01:27 PM ---------- Previous post was at 01:20 PM ----------
Fail to test!
"Unable to connect to the Internet."：
Click to expand...
Click to collapse
Thank you for feedback. That may be because Internet connection is tested using google as test subject, and that might be blocked in China. Next week new version with different internet connection method (and other features) is coming, stay tuned
franztesca said:
Thank you for feedback. That may be because Internet connection is tested using google as test subject, and that might be blocked in China. Next week new version with different internet connection method (and other features) is coming, stay tuned
Click to expand...
Click to collapse
Well,I have a VPN to connect to Google...
I'll be busy after this week, but I'll try to stay focused on the software!
this actually unlocks the bootloader and flashes the rom and relocks again?
Great tool, just got my Mi5 and flashed the Global Dev ROM without unlocking the bootloader. Thanks for your work!
E sì, una birra non te la toglie nessuno
um, where is the download link?
edit: ah i see it
checking for available roms won't work if you use a laptop and a hotspot from the phone.
also, can you please PLEASE do us poor kate/kenzo users a favor and try to solve this issue detailed here? https://forum.xda-developers.com/showpost.php?p=72985705&postcount=92
Can this help unbrick my phone?
My brother has mi5 with vendor rom 7.2.8.0.0
Will he need to get a deep flash cable? Or just normal USB?
When unlocking xiaomi's phone, sometimes I got a message like "Сouldn`t verify device. Current account is different from the account info on the device."
Can you add the current account on the phone? It might help the users to guess which password does they need (sometimes they have multiple mi accounts, dunno why). Or is this not possible?
Created the full guide to use this tool
[with video] http://www.technobuzz.net/xiaomitool/
.
As a new xiaomi user this is amazing!!
With this tool is possible to change global developer to global stable with locked bootloader for example ?
This tool looks like almost Nexus Root Toolkit... still needs work but is a very good idea I think..I hope you will continue to work in this tool
thanks & sry for english
Worked like a charm in a mi5! Thank you!
Thank you
This apps really helps me! So i thank you!
But i feel bad that i cant give donation yet......i'm sorry
For 2 days now...
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.
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