I messed up my Yoga 2 1050 by trying to load an unlocked boot image from here (http://forum.xda-developers.com/thi...-tab-2-unlocking-daaa-deee-daaa-dooo-t3241260), I have tried using the Phone flash tool with the correct file but it fails at 50%, here is the log attached if anyone can help.
When I first power on a message EFILINK ERROR(image -start-partition 596This partition does not appear to contain a boot image shows up.
Thanks
corasman said:
I messed up my Yoga 2 1050 by trying to load an unlocked boot image from here (http://forum.xda-developers.com/thi...-tab-2-unlocking-daaa-deee-daaa-dooo-t3241260), I have tried using the Phone flash tool with the correct file but it fails at 50%, here is the log attached if anyone can help.
When I first power on a message EFILINK ERROR(image -start-partition 596This partition does not appear to contain a boot image shows up.
Thanks
Click to expand...
Click to collapse
so you got your un-repairable tab back from lenovo
as a reminder, when you attempted to unlock the bootloader instead of the correct fastboot flash ESP 1050f-esp-patched you did a fastboot flash boot 1050f-esp-patched so instead of flashing you ESP partition you flashed the boot one with a (incompatible) ESP image, resulting, of course, in a bricked tab (as now the boot partition contains no valid image to be booted)
as advised, what you did to fix is fine (ie flashing back a stock rom), but you must use this Intel Phone Flash Tool (uninstall your existing one then install the new one) because the one you are using will not complete to flash a lollipop stock rom
Thanks ionioni
I did as you said, removed the old phone flash and installed the "lite" version.
I have run the new one and unfortunately it failed, it seems when the command for 25 second sleep is issued the tablet is taken out of fastboot as the screen shows the android system recovery page then.
I have enclosed the log file.
corasman said:
Thanks ionioni
I did as you said, removed the old phone flash and installed the "lite" version.
I have run the new one and unfortunately it failed, it seems when the command for 25 second sleep is issued the tablet is taken out of fastboot as the screen shows the android system recovery page then.
I have enclosed the log file.
Click to expand...
Click to collapse
when installed the new intel phone tool you must leave the dnx driver checked, install also the other file intelandroiddrv....exe, reboot and try again
if still not working try to flash a kitkat rom (have you restored the bios somehow?)
ionioni said:
when installed the new intel phone tool you must leave the dnx driver checked, install also the other file intelandroiddrv....exe, reboot and try again
if still not working try to flash a kitkat rom (have you restored the bios somehow?)
Click to expand...
Click to collapse
O.K. I'll do as you say
No I have not touched the bios
corasman said:
O.K. I'll do as you say
No I have not touched the bios
Click to expand...
Click to collapse
yeah, i read both logs and you should focus on (re)installing the Phone Flash Tool and drivers (first uninstall the existing and the drivers related and reboot)
ionioni said:
yeah, i read both logs and you should focus on (re)installing the Phone Flash Tool and drivers (first uninstall the existing and the drivers related and reboot)
Click to expand...
Click to collapse
Thank you for your help ionioni, it seems that I have really messed this one up.
I'll try again in the morning and see if I have better luck then.
corasman said:
Thank you for your help ionioni, it seems that I have really messed this one up.
I'll try again in the morning and see if I have better luck then.
Click to expand...
Click to collapse
it's not that hard, come on...
1. uninstall the existing Phone Flash Tool(nvm that you already installed the new one) and the drivers associated from Add/Remove programs and reboot
2. install the new Intel Phone Flash tool and the driver from the zip file linked (unplug the tab from usb before installing), to be sure also install at the end the DnX driver attached (this step is normally not needed as it should be automatically installed when the new Intel Phone Flash tool installation is run)
3. flash using the lollipop stock rom (the one you used so far with (L) at end is ok)
10 minutes for all these operations
I can confirm that information. Today I was installing new rom, and have problem with uploading data. I've installed newer version of Phone Flash Tool LITE instead of classic PFT, and DNx driver and it works good for me
O.K you talked me into it.
Just to be different I tried to do it on my Daughters laptop,and it still failed, it just seems to take it out of fastboot within a second or two of starting.
corasman said:
I tried to do it on my Daughters laptop,and it still failed, it just seems to take it out of fastboot within a second or two of starting.
Click to expand...
Click to collapse
if it fails again, attach the log from the Intel Phone Flash Tool and also detail what is the tab doing during these operations
O.K
I have fresh installed the "lite" tool and all the drivers including the DnX one.
The yoga is put into fastboot by pressing volume up and down together while powering on, this shows fastboot starting,then connect to laptop(tried on two different ones)start "lite" tool and load XML (also tried starting tool before connecting Yoga) file from same folder as files are in, press start to flash and within a second or two the screen on the Yoga change to the Android System Recovery screen and thats how it stays.
The attached log is from my Daughters Laptop.
corasman said:
O.K
I have fresh installed the "lite" tool and all the drivers including the DnX one.
The yoga is put into fastboot by pressing volume up and down together while powering on, this shows fastboot starting,then connect to laptop(tried on two different ones)start "lite" tool and load XML (also tried starting tool before connecting Yoga) file from same folder as files are in, press start to flash and within a second or two the screen on the Yoga change to the Android System Recovery screen and thats how it stays.
The attached log is from my Daughters Laptop.
Click to expand...
Click to collapse
try and start your tab in normal fastboot mode (from the recovery console select 'reboot to bootloader' or use from power off the combo keys Pwr & Vol+ or Pwr & vol- one of these two should bring you to the Fastboot/Droidboot menu) and from there tell me what the ifwi entry says... BLADE_21....
ionioni said:
try and start your tab in normal fastboot mode (from the recovery console select 'reboot to bootloader' or use from power off the combo keys Pwr & Vol+ or Pwr & vol- one of these two should bring you to the Fastboot/Droidboot menu) and from there tell me what the ifwi entry says... BLADE_21....
Click to expand...
Click to collapse
BOOTLOADER VERSION -
IFWI VERSION- Blade_21.86c.004.R23.1504091154 FFD8_IA32_R
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
corasman said:
BOOTLOADER VERSION -
IFWI VERSION- Blade_21.86c.004.R23.1504091154 FFD8_IA32_R
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
Click to expand...
Click to collapse
ok, somehow your bios is (still) a kitkat version (sure you didn't restored the bios using the restore bios tool? or lenovo did? nvm anyways)
you need to flash the kitkat stock rom, use this one (you can use the already installed lite flashing tool, no need to reinstall anything, just download and extract the stock rom and flash from dnx mode). after that remember to configure your region code and then you can update to lollipop using OTA's (don't flash the lollipop rom as this is only to be used after you have already updated to lollipop using OTA's and you need a fresh lollipop over your existing one)
ionioni said:
ok, somehow your bios is (still) a kitkat version (sure you didn't restored the bios using the restore bios tool? or lenovo did? nvm anyways)
you need to flash the kitkat stock rom, use this one (you can use the already installed lite flashing tool, no need to reinstall anything, just download and extract the stock rom and flash from dnx mode). after that remember to configure your region code and then you can update to lollipop using OTA's (don't flash the lollipop rom as this is only to be used after you have already updated to lollipop using OTA's and you need a fresh lollipop over your existing one)
Click to expand...
Click to collapse
I will do that, the download seems very slow though at the moment, I'll let you know how it goes.
corasman said:
I will do that, the download seems very slow though at the moment, I'll let you know how it goes.
Click to expand...
Click to collapse
will be fine, you had a kitkat bios and everything choked right from the start (remember that the bios must match the rom you re/install, so for eg if you have kitkat on your tab don't flash a lollipop rom or the other way around, as this will not upgrade/downgrade the bios too and you will get unexpected behavior or bricks, to upgrade to lollipop from kitkat use ota's and after you are on lollipop you can flash a lollipop stock rom if needed sometime)
I now have Droidboot Provision OS
with selection of
Reboot
RebootDroidboot
Recovery
SPupdate
Power off
which do I choose
corasman said:
I now have Droidboot Provision OS
with selection of
Reboot
RebootDroidboot
Recovery
SPupdate
Power off
which do I choose
Click to expand...
Click to collapse
what were the steps you performed? normally that one is the screen that the tab is showing during the flashing yet you must see some activity on the Intel Flash Tool log window and in the bottom of your tab screen. if you see it the it's ok and just wait for it to finish, if not then you must start your tab in DnX mode (screen saying "Fastboot starting...") then load flash.xml from the extracted kitkat stock rom in Intel Phone Flash Tool and "Start flashing"
ionioni said:
what were the steps you performed?
you must start your tab in DnX mode (screen saying "Fastboot starting...") then load flash.xml from the extracted kitkat stock rom in Intel Phone Flash Tool and "Start flashing"
Click to expand...
Click to collapse
Something has worked
I am now at a screen to set the Language and region ,but it will not move on.
Related
Hi all,
I've been tracking this thing down all day to absolutely no avail. The main reason I'm after it is I've heard it changes the partition layout to enable a larger /data partition (Essentially turns the phone into a KIS 3).
The download links Comebuy are all completely down it seems, I've even tried using Wayback Machine but that's not coming up with much good either.
Does ANYONE have these tools - as I said, the one for flashing Android to the phone?
Thanks a lot everyone!
Hi.
I have the Open C upgrade tool zip. Is that what you need?
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
KonstaT said:
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
Click to expand...
Click to collapse
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
johnnynmonic said:
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
Click to expand...
Click to collapse
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
KonstaT said:
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
Click to expand...
Click to collapse
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
johnnynmonic said:
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
Click to expand...
Click to collapse
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
KonstaT said:
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
Click to expand...
Click to collapse
Thank you for taking the time to reply. I got it to get to the language selection (where it hangs if I can get it to boot that far). I plug it into the USB, and on the phone select connect to pc via software - then adb was able to detect it as a device. From there did: adb reboot bootloader, and once there was able to use fastboot to install cwm. From CWM was able to flash the EU_FFOS-Android kitkat rom. Works fine now. I see you've spent actually quite a bit of time making different roms and tutorials for theses ZTE phone in various forums. Thanks for sharing your knowledge with the community.
edit: I don't think it had FFOS. vol down+power never seemed to do anything (just perpetual bootsplash). Recovery failed to flash even stock roms (I'm in Thailand, downloaded the stock rom you linked to in another forum, also the stock UK rom. Always returned an error about the footer).
******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!
Where I can I download the stock ROM for this model of Yoga Book? I hosed up my machine trying to root. I can boot into recovery mode, hopefully I can flash a new ROM to recover.
Thanks,,,
This could help ...
Edit: 2017/02/21: Link has expired
You can try this one: http://s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe
yoga-user said:
you can try this one: (http) s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe
Click to expand...
Click to collapse
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.
No - I' ve full access to all features!
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...
yoga-user said:
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...
Click to expand...
Click to collapse
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?
zamzenos said:
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?
Click to expand...
Click to collapse
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!
yoga-user said:
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!
Click to expand...
Click to collapse
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Have you tried the Intel PhoneFlash Tool? So far I've managed to flash the Stock twice, but with the pad/halo problem I described above.
booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps
yoga-user said:
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps
Click to expand...
Click to collapse
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!
Even_xf said:
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!
Click to expand...
Click to collapse
... you have PM
can i get the link as well?
it would be very nice if someone can help with a download link for yb1-x90l complete rom or even only recovery.img
can you please share the link again?
All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
vogemic said:
All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
I find this very strange this site charges to download the firmware that cannot be found from any other reputable site that I have searched on. It may well be legit but I will steer clear anyway.
keybord
zamzenos said:
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.
Click to expand...
Click to collapse
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot
vimalbhimani said:
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot
Click to expand...
Click to collapse
Long time coming. Thanks for taking the trouble to detail the method. However, in order to update to lastest firmware I was obliged to input a cc. I assumed then that I had got the Halo etc working simply by updating the firmware(!). Even so, good to know why I didn't have Halo. This info is sure to be of benefit to others. Thank you.
yoga-user said:
... you have PM
Click to expand...
Click to collapse
Can you please send me the link as well?
wait for new link download
need stock recovery backup
I will try install windows on android version
I think same Mipad2 (android version can install Windows ) install windows
http://en.miui.com/thread-248564-1-1.html
Hey Guys. This guide will help you if
1. If Using Custom Rom and want to revert to latest stock rom.
2. If Stock Rom got corrupted or became laggy.
3. You want to reinstall stock rom.
Warning:
1. Method 1 require unlocked bootloader. If you want to unlock then go Here . Method 2 doesn't. Don't worry.
2. This will clean your phone just like new phone.
3. First read the post twice carefully then proceed.
4. ALL .bat FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2
5. I may change name of files in folder. Use common sense to identify them.
Pre-requisites:
1. Charge your phone atleast 60%.
2. Backup any important data you might not wanna loose to either sd card or usb drive or pc.
3. Copy the rom zip in the sd card of your phone. (The one with size in GB)
4. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
5. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
4. Common sense, patience.
Download Link:
For Method 1
Click here Android Filehost
Download these folders: TWRP, STOCK RECOVERY, STOCK ROM, DRIVERS
For Method 2
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Procedure:
METHOD 1Step 1. Flash TWRP recovery if not installed by using "TWRP.bat" (Given in twrp folder) in fastboot mode or bootloader mode whatever you call it.
Step 2. Go to Twrp recovery then choose "wipe" then choose "Advance wipe" and tick everything except "SD card or external sd card". then swipe to wipe.
Step 3. Go to fastboot/bootloader mode and flash stock recovery running appropriate .bat file. It is given in "Stock Recovery" folder.
Step 4. When the command executes from the above step, Go to "recovery" by pressing volume down button, then press "power" button.
Step 5. You will see a dead android logo. Nothing else. Then go to stock recovery options.
If you don't know how then use following methods
Method 1:
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
Method 2:
Go to fastboot mode. Connect your device and open command prompt there. Then Type
Code:
fastboot erase cache
Step 6: You should see stock recovery options. Then choose "Update from sd card" and select the rom zip you pasted in SD card.
(If you don't have sd card, then paste rom in internal memory and don't tick "internal storage" in twrp in step 2) But micro
sd is preferable.
Step 7: Wait. Your phone may take 20-30 or more minutes. So leave it on charging.
METHOD 2Step 1: Download and Install all drivers given in download folder. Download RAW firmware for your phone. See above in download links.
Step 2: Install "ASUS FLASH TOOL"
Step 3: Go to fastboot/bootloader mode on your phone. Run asus flash tool, select your phone model and browse for the raw firmware. Check wipe all data. And start the process.
Step 4: Wait for program to say successful. If it takes more than 30 minutes. Disconnect your phone and check phone if rom installed or not.
If this process does not work. Then switch methods.
If you have any questions, problems .. Just Comment it.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
MOD EDIT: LINK REMOVED
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
2. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
File Credits:
1. RealYoti
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Click to expand...
Click to collapse
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Kapil Tapsi said:
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Click to expand...
Click to collapse
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Click to expand...
Click to collapse
It is a guide only. Users are free to choose from where to download. Thats it. I only shared my collection.
E: footer wrong
E: footer wrong
Installation aborted
I need your help!
I follow the instructions in Method 1 but the device give me this error message when I try to update via SD-card...
May I know whats the solution?
Rom used: Fastboot Rom WW-4.21.40.327
Thank you very much!
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks, finally got it
Hey...when I get to part 6 I get this Error >>
footer is wrong
signature verification failed
installation aborted
Hey..I also Tried Flashing with the method 2 it was installing but i got an error after
Man, this thread saved my ass. thank you for all your time all!
I have the Asus Zenfone 2 ZE551ML with sound issues, (it's only when the phone rings that the speaker works) and I put it into recovery mode to wipe cache/data, but it got stuck while doing that and I forced it off. But now, it's stuck at the Asus Boot logo with the rotating icon underneath.
Please help!!!!
Hello, my 551ml has stock LP, it's rooted with bootloader unlocked and Xposed installed. If I want to install the latest MM with through the raw flashing tool, should I install the MM bootloader first or it is included into the raw file? Thank
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
stevegtrlmk said:
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
Click to expand...
Click to collapse
use asus flash tool
damn my asus flash tool says error flashing image failure.... (remote not allowed to flash this partion)
ow btw i already bricked it cause it only does boot fastboot lol no more android
how do i flash it back again i need to send the phone back to amazon by 18/05 lol i mean i can just send it back and say also that it wouldnt boot cause i tried to reset it to get my touchscreen to work but yeah lol dont want them to refuse my retour
No way to simple flash the stock rom through/keeping twrp in the device, like I do with other Custom Roms?
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
euphrodil said:
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
Click to expand...
Click to collapse
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Kapil Tapsi said:
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks, i'll look for a thread that explain this.
euphrodil said:
Ok thanks, i'll look for a thread that explain this.
Click to expand...
Click to collapse
did you find any?
i want to remove the lineageos and install latest stock LP but i have no clue how to do it
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