Database Users

Doogee X5 Max Pro Root Recovery OTA

******************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!!!!

Get rid of shutting down after "device corrupt" message - so possibility to gain root

Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.

Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.

Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)

I have bootloop with usb connected, without usb powered off

Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.

I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it

Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?

LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.

Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU

Videotron LG G2 Nightmare

I would like to thank this wonderful community for all the help I have gotten over the years, I think this should be my first post.
For technical details of all I have done and learned on recovering the damn phone, skip to below the line, the rest is more of an introduction + some history.
In the past I have had a Canadian (BELL) Samsung Galaxy S2.5 as I like to call it. Specs similar to the S3 but not quite.
That was fairly easy to root thanks to odin.
Anyways, I have an LG G2 that I inherited from my brother, so I have some emotional attachment given he passed away 2 years ago (Age 36)... Reason why it is critical that I fix it.
I feel it's a great phone with excellent specs, with some flaws.
Hardware wise, this phone's digitizer seems to fail after a few years and stops registering touches.
Failed on my brother after 8 months, he got it replaced by videotron.
8 months after my ownership, same issue. I replaced the screen, which is a pain.
I dropped it a year later and broke the screen, replaced again.
Replaced the battery twice (First replacement battery was DOA) and... The internals of this phone are a pain to work with... to my limited experience at least.
The get to the point line as stated above.
___________________________________________________________________________________________
I wanted to flash my 4 year old never reinstalled phone, give it new life.
Researched a bit everywhere, verified in the phone what version it is, even most google results tell me this and the replacement screen is all the same.
it's a D801
After some work and research being clueless about working with this model, I finally installed
Started with getting Dev powers by spamming a specific key, setting usb debugging...
Using some application manager.
Installed
D801_AutoRec.apk
Towelroot.apk
From autorec, I installed the twrp and... fastboot... had no idea what that was.
Here I learned how to recover my phone.
This guy... super helpful.
Youtube link removed to post
So in short Download all the necessary drivers to get the android device detected.
Download those
codefi re link removed
I erased and flashed so often now that I scripted it in a batch file
Notepad, save as (not as text) flash****.bat or whatever you want to call it.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot erase dbi
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase rpm
fastboot erase stl1
fastboot erase tz
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash recovery recovery.img
fastboot flash laf laf.img
fastboot flash dbi dbi.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash PrimaryGPT PrimaryGPT.img
fastboot flash rpm rpm.img
fastboot flash stl1 stl1.img
fastboot flash tz tz.img
Originally, I only did boot aboot recovery and iaf
After that, my phone rebooted to the LG logo and stuck, but the Download mode is working again.
At that point I did flash a twrp recovery and was able to run it using the command abd reboot recovery
I pushed different roms, but no matter what I do, always back to fastboot.
Found this video later on, originally found a thread here but for the life of me I can't find it anymore (too much history) (How to recover with LG Tools the original kdz
youtube link removed
Now... I could not find the correct firmware
I used this
T-Mobile KitKat D80120A_00
IT worked, my phone restarted as it was before my adventures, but under a tmobile d801
Here I am happy, I get the proper D803_AutoRec.apk
Install the recovery again...
Now I really broke my phone.
Retried the steps above of flashing aboot and so on...
Refuses to work.
So I figured, hey, I recovered it under D801 tmobile... I probably broke it with the D803 recovery.
Back to the download site, made another folder and downloaded all the D801 img's
Ran my script (well that's when I created it from being sick of typing it)
Now I boot Tmobile but it's stuck to All Auto Test - FTM Mode
SUrprisingly on wifi,, shows missed calls and picking up exchange emails...
When I try to Flash as I have before under download, it fails.
SO hey, it found a 300MB tmobile update... why the hell not at this point.
Can anyone link me the proper software I can try to recover the LG Tools ?
csmgdl link removed
and
csmgdl link removed
Don't seem to work
Did I mess it up beyond repair ?
Any recommendations ?
I am hoping for one of the following
If I get tmobile OS working
Retry the D801_AutoRec.apk given it matches the tmobile recovery that somewhat works and then attempt the original goal of setting up CloudyFlex_2.8, CloudyStock_2.7 or cm-12-20150325-UNOFFICIAL-d803
Pretty sure up there, most of those wont work, I just want a working twrp
All I want is this phone wiped with a clean efficient rom to use as a reliable daily.
All I do is phone, text, exchange, camera, some apps... nothing too fancy.
I am off to sleep

Whatever I do, I can't get out of All Auto Test = FTM Mode
Reboot, hold volume up
Down
Up and down
Power up
Power down
Power vol up and down...
Always to all auto test.
Swipe down, get to options, general, do a full factory rest...
Same thing. Grr

Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.

Turbine1991 said:
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Click to expand...
Click to collapse
I have gone to download mode before to recover an oem image.
Now, I can't get to download mode after trying a number of times.
Ill give it another go tonight. Yesterday I got tired from the research, trial and error.
Thanks for your reply

With a calm mind, I fixed my issue.
https://forum.xda-developers.com/showthread.php?t=2613404
Press and hold power + Vol up and tap normal boot.
Didn't understand that at first.
Now let's see if I will break it again.
Still unsure if I should root it using D801_AutoRec.apk or D803_AutoRec.apk
Reason why I hate this phone.
Videotron LG G2 writes that it's a D801 but I read in other sources that it's a D803.
Now however, it's been restored to a Tmobile Firmware...

Okay, take it really slow. I've just completely rooted, put a custom recovery on and am now on Android N. There's many things which can go wrong - requiring you to restart the process.
Treat it as a D801, as the T-Mobile firmware booted. AutoRec does not root the device. Are you on KitKat or Jellybean? If you're on KitKat, do the following.
You must use IORoot to root the device - it does it in such a way it'll accept custom recoveries.
(You already have the phone's USB drivers obviously)
1) Download IORoot V25 from here.
2) Extract the file.
3) We need to unlock USB debugging, so make sure the phone is not connected to the pc. Settings -> About -> Software -> Tap on "Build" like 8 times fast. Go back into settings and you'll see "Developer Options", tick USB debugging. Now if your device freezes up like mine did when tapping build, then download an app which lets you go directly to developer options.
4) Hook the phone up to the PC, make sure it's not in lock screen.
5) Double click "root.bat" normally (not as admin). Keep going through this process until it brings you to the stock recovery area where you can flash over ADB.
6) It'll walk you through the process where it boots back into Android.
7) Open SuperSU, which it installed.
8) In the settings somewhere, make the grant always accept rather than prompt. My device was bugged not allowing root unless it was forcefully granted like this.
AutoRec - Recovery Install
1) Copy the contents "bumpboot-v1.0-blastagator-signed.zip" and "busybox.apk" and "flashify.apk" onto your device. Download here.
2) Download TWRP for T-Mobile 2.8.6.0 from here, extract recovery.img and copy that onto your device.
3) Copy AutoRec KitKat for T-Mobile here.
4) So you should now have "D801_AutoRec.apk", "recovery.img", "busybox.apk", "flashify.apk", "bumpboot-v1.0-blastagator-signed.zip" on your phone.
5) Proceed to install "AutoRec.apk", ticking unknown sources. Let it boot into recovery. Now reboot.
6) As my recovery didn't stick, install and open "busybox.apk", click install in the program itself. Install and open "flashify.apk", flash recovery, browse using flashify to the location of "recovery.img", let it reboot into recovery. This is where I had to flash "bumpboot-v1.0-blastagator-signed.zip", otherwise I couldn't boot into the OS. So flash that file.
7) Reboot back into the OS. Until we flash lollipop, there wasn't any other way for me to reliably get into TWRP recovery without repeating step 6.
8) Copy over the Bootstack and Stock Rom from here. Don't worry about SuperSU or anything else.
9) Repeat step 6 to boot back into recovery.
10) Wipe everything except internal memory in TWRP.
11) Flash the lollipop bootloader.
12) Flash the lollipop stock rom.
13) Reboot.
14) Now you're able to get back into recovery any time by holding the power + volume down combo, releasing when the screen goes on - and holding it down again.
15) Feel free to flash LineageOS 14.1 or anything afterwards. Make sure to backup your EFS partition at some stage before this - just incase you can't connect to cell towers in the near future.
As you can see, I had to improvise a bit. No guide was good enough to just work in 2017 for my D800. These should work fine for your D801.

Thank you so much for such an amazing and detailed response !!!
After quite a bit more research and work, I got it rooted and got TWRP working.
Once done I uploaded cloudyflex 2.8
Installed it and of course, me being me, chose the wrong install when prompted. It asked Tmobile, other and Canadian 803.
I chose Canadian and after that got back to fast boot.
After that I simply erased boot, aboot and laf, getting ready to restart from scratch but it rebooted on a clean cloudyflex 2.8.
At this point, the phone is running better then stock and I am very happy with it
Your walkthrough is great and I will certainly redo my phone soon again.
For one, practice makes perfect and I certainly like that with your instructions, I will be able to call on the recovery when I want it instead of asking my way into it by adb command.
Thank you again for your time
This community rocks !

Feel free to thumb me. I also have a request for you, I'll PM.

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself

(Needed) ASUS Zenfone Max Plus M1 ( ZB570TL ) Signed Firmware

Needing a Signed Firmware for my ASUS that has the partitionings as i cant boot into the Android System and im stuck at POWERED BY ANDROID screen when powered on and it doesnt load the ASUS or ZenfoneUI screen it just stays at Powered By Android screen and after 30 secs it reboots back to that screen no matter how many different firmwares i flash with SP Flash Tool...
I CANT -
1.Turn on USB debugging in settings as i cant get the system to boot full up after flashing.
2. Cant boot into Recovery Mode to flash update.zip its like Recovery Mode is gone even after flashing
3. Cant Unlock Bootloader, in ADB and Fastboot i can flash .img but at the end of flashing it errors abd says remote failed and then error locked, im sure thats because the bootloader is locked or usb debugging hasnt been enabled in developer settings.
I CAN -
1. Power + Vol+ to get into the menu that has RECOVERY MODE, FASTBOOT MODE, NORMAL MODE, if i select Recovery Mode it just reboots the device back to Powered by Android screen and reboots after 30 secs.
2. I can use adb devices but no adb shell, fastboot works but limited no flashing or unlock bootloader until i figure a way to enable usb debugging in the settings.
3. I can use SP Flashtool and flash all kinds of firmware for the device WW, CSC, but after flash i get the green checkmark that it flashed propperly but when i boot it im vack to powered by android screen with reboot after 30 secs, no recovery mode still just limited fastboot mode.
Im told that maybe the partitions were messed up and it needs to be re-partitioned by usingba signed firmware, or flashing the EMMC using UFI program or Android Toolkit but i cant find any of the .XML file they use or the .mbd flash files i can only find what asus has are the ones for Sp Flashtool and SdCard but cant get into recovery to flash from SdCard an Update.zip....
Any help or if someone has a Signed backup that i could flash using SP Flashtool as that seems to be the only way i can get to flash, i also was told it has to be signed firmware that has the partition files as the device wont let any firmware stick to it unless its signed with keys in the firmware...
Id like to keep trying as i had it given to me and i buy new screen, back cover, vol buttons, battery then after i whiped all the together and turned it on this is whst im left with ( A Pain in the Azz ) device of wonders, all that money spent into it i keep on keeping on Joe Dirt Style with it until something gives hopefully ..
Im going to try using OllyDbg and try finding if theres anything in ADB.exe or Fastboot.exe that i can put a True or False for has the device enabled USB Debugging already or if they asking for Signed Keys to tell it No keys needed or Bootloader is unlocked or any checks if allowed to unlock bootloader if its locked, but this is just dreaming at this point of hackin a ADB or FASTBOOT exe .... anyone know of any good decompiler to modify exe files let me know i could give a try as all i know of that get into them to change things are Reflector and OllyDbg but they kinda hard to use.... anyways the journey continues any help or firmware signed or instructions on partition the main system blocks ill try anything at this point... Thankz Ya'll.....