Database Users

Fastboot mode - no boot or recovery img **help**

Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?

Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy

since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.

*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)

Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.

I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option

I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).

Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!

No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S

saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?

I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?

it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium

Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"

It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++

saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!

Need help getting recovery option

I got a Google IO 10.1 Tab. I am trying to get the recovery option on my tab other then your basic download option and USB which I get. Can someone direct me to the right place ?

The IO tab's bootloader doesn't allow direct access to recovery like the retail version. You have to boot to it using fastboot. Put your tab in USB mode, and using fastboot: fastboot boot recovery.img.
Recovery.img can be the CWM version or the standard version. It doesn't matter. You just need the respective image to boot from. Look here for the stock image: http://droidbasement.com/galaxy/sys-backup/
I'm assuming you have the fastboot drivers installed. If not, you'll have to download the Android SDK and install them from that. The fastboot USB driver has to be force installed in windows for the Galaxy Tab 10.1. See here for basic instructions:http://scratchpad.wikia.com/wiki/How_I_rooted_my_Samsung_Galaxy_Tab_10.1_(Google_IO_edition)#Files
Or...if your already rooted, flash CWM via RomManager and boot to recovery from the options in RomManager.

FourCrows said:
The IO tab's bootloader doesn't allow direct access to recovery like the retail version. You have to boot to it using fastboot. Put your tab in USB mode, and using fastboot: fastboot boot recovery.img.
Recovery.img can be the CWM version or the standard version. It doesn't matter. You just need the respective image to boot from. Look here for the stock image: http://droidbasement.com/galaxy/sys-backup/
I'm assuming you have the fastboot drivers installed. If not, you'll have to download the Android SDK and install them from that. The fastboot USB driver has to be force installed in windows for the Galaxy Tab 10.1. See here for basic instructions:http://scratchpad.wikia.com/wiki/How_I_rooted_my_Samsung_Galaxy_Tab_10.1_(Google_IO_edition)#Files
Or...if your already rooted, flash CWM via RomManager and boot to recovery from the options in RomManager.
Click to expand...
Click to collapse
What if my Tab is just on the boot screen..... I can't even get in it. Normally I would adb reboot recovery but now I can't even do that. Is there a way to use Odin where it would erase everything and install retail software ?

Simultaneously hold volume down and the power button when you power on. This brings you to a two choice menu, usb on the left and download mode on the right. You choose by pressing volume down again and then volume up to enter the mode. To get out of either mode, press and hold power...eventually the tab reboots.
Flash the file in the first post via odin to turn your tab into a retail version with HC 3.2/Touchwiz etc:http://forum.xda-developers.com/showthread.php?t=1345995
It's completely stock and works well.
Be warned though, it replaces your bootloader with a locked, encrypted, retail version. You can still root by installing CWM recovery through odin and then flashing the root exploit via CWM recovery.

Can't get into recovery mode after changing bootloader

I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?

guitarguy6 said:
I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
Click to expand...
Click to collapse
1. Make sure you have the Android SDK installed to your PC.
2. Boot the tab to fastboot using PWR and Vol+
you should get a menu
Select Fastboot Mode. Should say it at the top center when in fastboot
3. Download your CWM image file and copy it to your C:\Program Files\Android\Android-sdk\platform-tools folder. (might be in Program Files (x86).
in that folder you will see a file called "fastboot.exe"
Wait, plug your tab in.
4. Open a command window in that folder (shift + right mouse click)
in the window, type fastboot flash recovery nameofyourrecover.img (where nameofyourrecovery is what the recovery image file is named.
5. Hit Enter
Should flash your CWM recovery image back. I advise you use the latest CWM recovery. 1.7.2 or 1.7.3 you can get at tegraowners site
MD

If I don't have a recovery image am I SOL? Can I download one from somewhere?

guitarguy6 said:
If I don't have a recovery image am I SOL? Can I download one from somewhere?
Click to expand...
Click to collapse
tegraowners.com is one place.
The other recovery, is PublicRecovery which you can find in the Dev Forum.
Both are good recoveries. Albeit the CWM one is notorious for not revealing source code on his kernels. Non-GPL, which is why he is not allowed to post his kernels or roms at XDA. Might be sending your usernames and login's for all anyone knows,
The CWM "is" GPL compliant. So no needs to worry.
The "search" button, is such an easy thing to use.
MD

Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.

guitarguy6 said:
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
Click to expand...
Click to collapse
Yeah, keep forgetting about that one. But, just make sure the Recovery you installed is a recent one. Not sure how often that app gets updated.
Some of the older versions have issues with ICS sometimes, especially TWRP. So check versions.
MD

Unbricking Zte Open C (Firefox OS)

Hello,
After an unsuccessful attempt to upgrade a firefox OS phone from 1.3 to 1.4, I bricked it
This is the current status :
It is a ZTE Open C. Bought at LDLC. I am not fully sure whether it is a FFOS_EU_EBAYxxx or a FFOS_FR_ZTE_OPENC.xxx
Normal boot: it does not go beyond the firefox logo and gets stuck there
If I boot in FTM mode (volume down and power), I see it when I do fastboot devices.
It does not go in recovery mode any longer, after I did : "fastboot flash recovery recovery-clockwork-6.0.3.3-roamer2.img". Before that, I did manage to go in recovery mode, but none of the zips I tried would work. I would get an unsuccessful signature verification all the time.
In recovery mode - when it was working - I was unable to see the device with adb devices nor fastboot devices.
I do not believe it is rooted.
Help appreciated

If you have bought your device on LDLC (french online shop) it's a FR version.
Try to flash the image provided by ZTE France here (tool is for Windows only) :
http://www.ztefrance.com/downloads/Pack_root_du_ZTE_Open_C.zip
(this is a "rooted" image so that you'll be able to compile & flash your own FirefoxOS afterwards )

[SOLVED] Unbricked (and successful upgrade)
Thanks for your reply!
Actually, we finally managed to unbrick it.
In case somebody else is looking for this, the procedure is detailed here.
In our case, as adb wasn't working, we booted in FTM mode (volume down and power), were we could use fastboot.
Then
fastboot devices
fastboot boot cw_recovery_dp.img
when screen goes black, adb shell /sbin/black_screen_fix.sh. In our case, this does not seem to do anything? we do control c
adb shell /sbin/cw_recovery.sh. This works great.
We get a recovery screen from which we can apply updates without being bothered by 'invalid' signatures
Regards,

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