Database Users

X720 bricked, kind of ;)

Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?

Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.

Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?

1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.

Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?

Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.

Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786

trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.

Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda

trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.

trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!

Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.

testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?

trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.

Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode

Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

How to get the stock rom

Hi guys,
I am a total noob with flashing etc.
Can somebody please be so nice to post here the right tutorial for my case? I want the Original Firmware.
I have read so many threads but they all sound different for me. :silly:
I have got an Motorola X Pure Edition from Ebay. It has Android 6.0 installed. I want to update to 7.0 but when it downloads the new firmware it will reboot and TWRP starts. I have downloaded the firmware 7.0 manually and tried to run it with TWRP but I get always error messages.
According to Bootloader:
Product: clark XT1575 32G P3C
Devise is unlocked
Status Code: 3
Software Status Modified
Do you need information about Baseband Version, Kernel and so on?
Appreciate your help :victory:

Nougat firmware for XT1575 is on androidfilehost.com linked to this thread. The linked thread includes instructions on how to use fastboot to flash the update. Updated baseband, kernel and all that are included in the full firmware package.
You'll need a PC setup for flashing too. Assuming you're using a windows PC you'll need to moto drivers you can get from here, and a minimal fastboot installation you can get from here.

Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.

Muffycheeks said:
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Click to expand...
Click to collapse
No, you don't need to worry about returning to stock 6.0 to get an XT1575 to 7.0 anymore. Motorola-Firmware-Team released a leaked full firmware package for clark_retus-user 7.0 NPH25.200-22 linked to that acejavelin thread that I linked to. It isn't an incremental update, it is the whole package. Thanks to that, you don't have to return to fully stock 6.0, take or sideload an OTA, and hope for the best anymore.

Motorola Device Manager - Windows 10
Thanks guys for your comments.
Unfortunately I have already problems with the Motorola Device Manager (MDM). Seems like the drivers wont install.
Fastboot message = waiting for any device
I have run the MDM as an admin, activated USB Debugging and MTP but after installation of the MDM i get the congratulations message but i cant open the program.
I have installed the Media Feature Pack for Windows 10 and tried it again without success.
When i open the Motorola_Mobile_Drivers_64bit file from the Temp folder i can Repair or Remove Motorola Mobile Drivers Installation 6.4.0 but I can`t run it.
Other cable and USB Port does not help either.
Device Manager: Android Device --> Motorola ADB Interface
Any ideas how to fix this issue?

Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson

dzidexx said:
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
Click to expand...
Click to collapse
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found

Jonasson said:
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Click to expand...
Click to collapse
https://youtu.be/3Q8b0SuGvmI
https://www.google.pl/search?q=inst...1ZHYAhVN2aQKHSi7AoIQ_AUIESgB&biw=1056&bih=660
https://www.google.pl/search?biw=10...k1j0i8i30k1j0i8i13i30k1j30i10k1.0.Pe-SF0MQFkc
Go to movies in google results.

Thanks to all of you. I finally understood how it works. :angel:
Android 7.0 on it :good::victory:

Hi guys,
I did the update with above tutorial to Android Version 7.0. (Android security patch level: 1.September.2017)
But now they ask me to download new Android security updates . (New system software: 25.201.1 (8,0 MB)
Unfortunately when it is doing the restart it shows the error message:
Error!
And it shows a dead Android Robot.
Any ideas what has gone wrong. Not sure why I get the Software-update failure after doing the upgrade successfully from 6.0 to 7.0.
Moto X Pure Edition

Probably you forgot something, I think:
fastboot flash recovery recovery.img

dzidexx said:
Probably you forgot something, I think:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks dzidexx..it does finally work

hello . i need NPH25.200-22-1 android for moto x pure;
any idea?

morvarid said:
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
Click to expand...
Click to collapse
No full images were ever released/leaked for anything newer than:
Style: NPH25.200-15
Pure: NPH25.200-22
You either need to get one of those to work for you, or move on to something else or a custom ROM. Sorry, but the version you have was never released as am image (that -1 sub version probably never was a full image internal to Moto either, most likely an OTA only) and no later version has ever leaked out. You can stop asking in multiple threads, the answer is the same.

Axon 7 not bricked but almost.....pls help

Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck

Following this post, you device should be rescued.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
If your phone can not automatically boot into edl mode, then try follow method.
1) Power off your phone,
2) connect your phone to PC with a USB cable while holding hold vol up and vol down at same time.
here2for said:
Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck
Click to expand...
Click to collapse

Thanks for reply but link is 404...pls resend tks
:::::::::::::::::::::

https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

further....
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??

Run command： fastboot devices
If you device show up, then you can flash twrp by command
fastboot flash recovery "path"/"twrp file name".img
here2for said:
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??
Click to expand...
Click to collapse

mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!

....tried to install a couple different roms (placed them on the SD card) twrp....begins to install but then generates the error - "zip signature verification failed" ?? have tried resurrection remix and aokp nougat for axon 7.... get same error. Thoughts please

you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
here2for said:
mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!
Click to expand...
Click to collapse

llaalways said:
you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
Click to expand...
Click to collapse
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck

which model is your phone? A2017U, A2017G, or A2017?
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck
Click to expand...
Click to collapse

I suggest stock rom, you can follow this post to flash it.
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
llaalways said:
which model is your phone? A2017U, A2017G, or A2017?
Click to expand...
Click to collapse

axon 7 almost bricked....
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse

Do not forget install Magisk16.4 after install ROM.
And try factory reset and then reboot disemmcwp.
If there is still problem, try format data again.
here2for said:
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Custom Rom / rooting Options vor TB-125FU (Lenovo Tab M10 Plus 3rd Gen)

Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!

You should just be able to install matiek form my understanding

I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.

holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?

art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.

holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.

peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.

holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.

holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks

el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.

holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)

el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.

holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet

el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.

Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.

el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?

Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized

el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!

I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.

hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW