Trying to get CyanogenMod on my mums new Amazon Fire HD8 tablet. However, it's faring a little harder than expected. I have downloaded the AmazonFire SuperTool package as well as GoogleApps and the CMM Disc Image, however, when I try to run the .bat file in the supertool, my device shows up fine - the ADB works. However, when I try to boot the device into TRWP through the .bat, the screen simply turns blank on the tablet with no "FastBoot" on the screen. I have tried installing drivers many times, and have used the minimal ADB + Fastboot installer but even that has been to no avail. Trying to manually install drivers has failed too, with this resulting in the error message "The folder you have specified doesn't contain a compatible software driver for your device." Weird.. Could anyone help me out?
Thanks.
Thread moved to proper forum
The Super Tool written by RootJunky is currently only for the Amazon Fire 7" model. The reason why the HD models (8" and 10.1") are not compatible is because there is not a good fastboot screen right now. I am currently working on a root/replace firelauncher currently. Please check it out here:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
******************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!!!!
A friend of mine rooted my phone for me a while back. He's no longer around and I'm still pretty unfamiliar with the process without using twrp. I'm not sure what method he used. I was going to try flashing a stock os via adb but adb doesn't detect my phone. I'm sure it's a driver issue but I can't seem to fix the problem. I also have trouble transferring files with a USB cable. My computer sees the phone but as far as opening it to explore or transfer files, it doesn't work. I downloaded drivers from a link I saw in another thread on xda and installed some file with a weird format and that didn't fix the problem.
Can somebody please point me in the right direction?
First of all, I'd suggest you to try with a different cable. The one shipped with the RP2 is optimized for power and might cause issues when using it for data trasfer.
Secondly, generally speaking you should install adb platform tools (I don't remember installing specific drivers for the adb, to be honest). You probably want to install the google usb driver as well for the fastboot as well.
If you confirm that those solution do not provide a solution to you, we might look at other causes.
Once everything is workin, you can proceed to update (since you have root permissions, I am assuming you see the OTA but you don't know how to proceed). The procedure that I followed is this:
1. Download razer factory images for mr1
1. perform a nand backup with TWRP
3. extract the factory images somewhere, open the "flash_all.bat/.sh":
3.1. make the fastboot variable point to the actual fastboot executable (if you are not familiar with relative paths, use full path and it will work seamlessly)
3.2 remove/comment the line
Code:
fastboot erase userdata
4. run the script
5. reboot your phone and perform the OTA update
6. install arter12 kernel
7. In magisk installer download the zip and flash it with TWRP
So I've been troubleshooting for the past few hours. I'm familiar with the process that needs to be done. The issue I'm running into now is a driver issue. I deleted the Google driver and installed a Samsung driver just for laughs. I can view my phone and transfer files now flawlessly. But it still isn't detected by adb. I was just going to wipe my phone and reflash the stock rom with adb fastboot. I wonder if there's a way to flash the stock rom with the Razer bootloader until I figure out what's going on with adb?
The google drivers are for fastboot (bootloader), not adb. For adb I just let windows do the automatic install (I'm sorry, I just assumed you are using windows, tell me if that is not the case).
Keeping the assumption that you are using windows, try to uninstall all driver (both from installed apps and from installed driver. For the second step you will need to show in device manager, all hidden devices and uninstall all of them).
Reboot windows and reconnect phone, I'd expect it to be automatically recognized as Razer Phone 2.
As per bootloader, in W10 sometimes it's a pain in the ass installing the drivers as you might need to manually install them.
Hi!
I borrowed this tablet from a friend who said I could use it for awhile. I was installing OTA OS updates to the device and I think I inadvertently hit the power button at a bad time while futzing with putting it in a case. Now it won't boot and just hangs on the LENOVO logo screen.
I can hold volume up + power and get to the Android 8.1 Recovery menu. I've cleared all the data and cache, but that didn't fix it. I think I will have to restore the firmware on it, but am open to other suggestions.
Now, finding that firmware has been a real challenge. It looks like a russian "lenovo forums" website hosted the file at one point, and literally everything links to that russian website and file, but all I get is a 404 when trying to download the firmware file. I was able to find the Tab4 8 Plus file, but that doesn't match this tablet.
I already told my friend who said not to worry about it, but I feel bad and want to fix it. I can't find anything useful on the Lenovo support pages, except other people mentioning the russian website and getting the firmware file from there. Thanks for any help you can provide.
This is the site that I keep getting links to: -x--snip--x- I guess I can't post URLs yet since this is a new account.
Some of the OTA incremental updates I can download, but I need to find the full firmware file. Judging by the linking to this file I see in other threads and forums, this file link stopped working sometime between July 2019 and today. Thank you.
I was just in a similar situation yesterday.
https://forum.xda-developers.com/showpost.php?p=81833275&postcount=2055
Lenovo MOTO Smart Assistant downloads the QFIL file and rewrites the internal flash via EDL mode to restore the stock ROM.
https://pcsupport.lenovo.com/jp/en/...er-list/component?name=Software and Utilities
I have the same problem I downloaded the program but it can not install stock rom.When I open the device it enters fastboot and I can not configure anything. I can access fastboot twrp but when. Any help?
giorgakis1966 said:
I have the same problem I downloaded the program but it can not install stock rom.When I open the device it enters fastboot and I can not configure anything. I can access fastboot twrp but when. Any help?
Click to expand...
Click to collapse
I'm just a noob, but i recovered from a similar scenario this morning... I found that pushing volume+ and powering on doesn't enter EDL like it needs to, but rather boots to TWRP, if you can boot into the ROM you can run the command "adb reboot edl" which gets it into the Emergency Download Mode. I would imagine that you could boot into TWRP then run a similar command in the terminal
ROM Unbrick LenovoTAB 4 8 Plus Stock Rom_Rooting File1- BOOT.img RECOVERY.img for Fastboot flashing— File2- For QFIL resulting in Android 7.1.1. which will find the OTA update to Oreo after completing the installation. File3- For TWRP Restore. (use
7.2.5.5/2465-diff-7.2.8.5/2877
https://d1s31zyz7dcc2d.cloudfront.net/ac0bfc6c85b2fa5000fdc568c30eed60/update-kara-diff-PS7255_2465_0021911675268-to-PS7285_user_2877_0023723720068.bin
md5Sum=89f4ee800801eae7eb0c0e5fd537d0aa
7.2.7.3/2625
https://d1s31zyz7dcc2d.cloudfront.net/dc64e6a705f8e840217c98b2217938f2/update-kindle-kara-PS7273_user_2625_0022851240324.bin
md5Sum=0741cd9b3c663ff1d10be80e2b20fd64
As I referenced in the other post with the mantis device getting full.bin updates, I was only able to get the diff updates for kara
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Lukatler said:
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Click to expand...
Click to collapse
who can help with installing new firmware or restoring the previous
Lukatler said:
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Click to expand...
Click to collapse
Right now there's no known way to flash the firmware over the bricked device. You'll need to be unlocked which there is no guide for that due to the encryptions of the system. Only time will tell when we do see an unlock guide which can allow you to flash the firmware.
For any XDA users that have the (kara) device and hasn't updated to the latest firmware. Make sure the firmware (excluding the system components update) that's downloading isn't downloading fast or else it'll be under a diff update which isn't the full update and the command to run is adb logcat as soon as the update is downloading in the checking for updates screen. Report here to post the updated firmware and the URL is different compared to the one listed here.
Copy this and put it in front of the .bin link after the logcat.
Remember to enable adb debugging, adb connect ip/USB adb and allow the connection and type in adb devices. In case the update does download in full type in adb shell pm clear com.amazon.device.software.ota
https://prod.ota-cloudfront.net/
I have two (kara) devices locked on 7.2.5.5/2444 and 7.2.5.5/2465 still and I'm getting the update to the 7.2.8.5 diff instead of the newer 7.6.1.4. Help is appreciated. Thanks again.