Database Users

New and Easy way to ROOT and CWM 5.0.2.7

New simple way to root by GALAXY TAB HACKS (THANKS)
not sure if this method has been mensioned in 10.1v forums but i noticed a few people still having trouble with root
so when i came across this i tried it on my 10.1v before posting
required windows computer and tab drivers, best way is to install kies software.
bootloader should be unlocked before rooting see chainfire's post.
1- download the attached required files.and extract
2- move the file "galaxy_tab_root_10.1.zip" to the tablet
3- start tab in download mode with powr+vol down combo,
4- start odin on pc and wait till the box goes yellow (means connected). select "recovery ...." file in PDA and flash.
5- after tab restarts making sure that usb debug is checked go to cmd prompt and type "c:\adb reboot recovery"
now tab will reboot into recovery, go to install files from sd select the above copied file and hit it and youre
ROOTED.
AS FOR CWM 5.0.2.7 (DROIDBASEMENT THANKS)
follow steps 3 and 4 using cwm 5 file and you will have latest (blue) recovery.
hope this comes in handy for people that are still struggling.

not easy enough for me
I fail to boot into recovery.
i assume this is in windows: cmd prompt and type "c:\adb reboot recovery"
then windows replies c:\adb is not recognized as an internal or external command, operable program or batch file.
Should I first install adb manually? Is there another way to boot into recovery?
Bjorn

That means you need to install drivers.
2nd thought do u have adb/sdk installed on your computer.
Sent from my GT-I9100 using Tapatalk

I don't think the drivers are the problem. I understood it is sufficient to install kies to get the drivers.
I do not have android adb/sdk on my computer and rather not install it. I am in Uganda and it is really difficult to install large software components with crappy internet connections.
It would be great if there was a way to boot into recovery from the tablet, without the need of a computer?
d

You can with rom manager, but you have to be rooted first, you can install the basic components of sdk,personally I haven't tried any other way.
Sent from my GT-P7500 using Tapatalk

dragonflyFZX said:
I don't think the drivers are the problem. I understood it is sufficient to install kies to get the drivers.
I do not have android adb/sdk on my computer and rather not install it. I am in Uganda and it is really difficult to install large software components with crappy internet connections.
It would be great if there was a way to boot into recovery from the tablet, without the need of a computer?
d
Click to expand...
Click to collapse
Or you could try adb wireless.....
Worked for me
http://www.mediafire.com/?t3d0ab3635c52u8
Sent from my GT-P7500 using XDA App

thanks
this was what I needed, thanks

problems with the last step
hello, i'am trying to root my galaxy 10.1v, i managed to follow the guide till the last step, but when i give the cmd command, the tablet reboots and it appears a green android logo with a yellow exclamation point in a tirangle in the middle... i tryied also other guides but they are to complicated for me, could someone please help me?

seems like it didn't install cwm
so...i followed every step but after entering recovery mode i noticed that it still has the original 3e recovery....i did it with odin over and over again...but still nothing. and however...which one should i install? the one you get after unziping tabrooteasy.zip or the one you get after unziping recovery-cwm_5.0.2.7-sam-ta.....?(i tried both and still showed 3e recovery but which one has to be installed?)
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
and...just to be sure...the .tar file(s) work for 10.1V too, right?

[REF] [ROOT] [RECOVERY TWRP BETA1] Metro PCS lg K7 LGMS330

*******thread is dated, i do not own the device any more*********
Thank you Senior Member: starkly_raving for a break through with a working TWRP recovery and of course Team Win Recovery Project (TWRP) for there awesome recoveries! PLEASE READ, READ AGAIN AND WHEN YOU THINK YOU'VE GOT IT, READ AGAIN! And remember kiddies no one is responsible FOR WHAT YOU DO BUT YOU! Ill be trying to update this opening post as new info comes about, 2nd post will be dated info for reference.... starkly_raving has also mentioned that when a source built TWRP is complete development on this one will stop.
ROOT
Copied from post #22 Senior Member: starkly_raving
Disclaimer!!!
This is the method I used for the Metro PCS variant running 5.1.1 LMY47V. I can't verify this process for any other model or firmware use at your own risk.
All commands are without quotes.
First you have to unlock your bootloader and root...assuming you haven't here are the steps...
Requirements:
1. SDK installed with fastboot. (Minimal adb and fastboot will work also)
2. ADB/USB drivers
1. Enable developer options.
(a) Enable USB debugging
(b) Allow OEM unlock
2. Boot your device into bootloader mode.
(a) Open a cmd prompt in SDK or minadb fastboot.
(b) Connect device via usb
(c) In the cmd prompt type "fastboot devices" this will show if your device is connected.
(d) Then type "fastboot oem unlock" this will wipe all data including internal storage so backup to your PC or cloud.
(e) Once complete type "fastboot getvar" this will give you confirmation that your bootloader is unlocked.
(f) Finally enter "fastboot reboot" this will reboot you back to Android and you you will be greeted with the "bootloader unlocked" splash screen.
Rooting...
Requirements:
Reenable & Keep USB Debugging On!
Reenable & Keep OEM Unlock On!
Enable Unknown Sources!
Install the Kingroot apk from here...
http://www.kingroot.net/wap
Replace Kingroot with supersu:
http://www.w0lfdroid.com/2015/05/How...perSU.html?m=1
At this point you can update SuperSU binary if needed and install busybox.(always helpful)
Now for you (Boost users) to supply the needed files here's what to do.
1. We need the build.prop...
(a) Use a root explorer and copy system/build.prop to your SD card
(b) Via ADB "adb pull /system/build.prop"
2. We need your fstab and partition info... "cat proc/partitions" this will spit out your partition info.
3. We need your stock recovery.img and boot.img
(a) Use a GUI based app like flashify and backup your stock recovery and kernel.
(b) ADB method..
1.If you are using ADB, connect your device to your computer via USB, launch a command prompt window on your computer and enter the following command:adb shell
2. Enter the following command:"cat proc/mtd" You will get an output similar to this. Note that your result may differ from this one and you must proceed according to the output that you get, rather than the example that you see example here.
dev: size erasesize name mtd0: 000a0000 00020000 "misc" mtd1: 00480000 00020000 "recovery" mtd2: 00300000 00020000 "boot" mtd3: 0fa00000 00020000 "system" mtd4: 02800000 00020000 "cache" mtd5: 093a0000 00020000 "userdata"
To dump the recovery image to your SD card, make note of the first word of the line which says “recovery” in the end. It is ‘mtd1’ in case of this example but may be another entry for you.
3. Now use this command, replacing ‘mtd1’ with the term that applies in your case, if different: "dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096" Similarly, to dump the boot image to your SD card, make note of the first word of the line which says “boot” in the end, which is ‘mtd2’ in our case but may differ for you. Use this command now, replacing ‘mtd2’ with the term that is applicable in your case, if different:"dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096"
That’s it – you now have recovery.img and boot.img backed up on the root of your SD card.
RECOVERY
partial copy from post #42 Senior Member: starkly_raving
Prerequisites:
1. root
2. unlocked bootloader
3. knowledge of fastboot commands.
cmds
To test and not replace your recovery
fastboot boot twrp-image-new.img
If you feel its safe for daily use....
fastboot flash recovery twrp-image-new.img
DOWNLOADS:
Beta1:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha2:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha1:
https://drive.google.com/open?id=0B4...WNfMm9sQy1RVmM

dated info for reference only. Original opening post....
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/show...php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching. Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.

Please help
reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(

BeLOWME1992 said:
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(
Click to expand...
Click to collapse
my advice is take it back, while its still under warranty. i wouldnt tell them you rooted it though. as of right now im having driver issues and cannot help.
do you get a security error indicating modification? can you get into recovery? if so try a wipe

Lg k7 metro pcs
Lg k7 metro pcs cant find a custom recovery yet has anyone found one if so please let me know I can't do anything cool on my phone without one

Rooting the device voids warranty i believe.. and theirs no support for this phone at all...

Frustrated.
I rooted mine with KingRoot, then installed Link2SD and moved all of my downloaded apps to the second partition of my external SD. Shortly afterward, all of my applications began crashing, even system ones like Phone, Settings, Contacts, etc. Like an idiot, I performed a factory reset on my device. After the reset, it wanted the original Gmail account that was linked prior to the reset, but LG Keyboard crashes and I can't proceed. Thought maybe I could sideload Google Keyboard but of course USB debugging was disabled after the reset. Luckily, I took it back to the MetroPCS store I purchased it from and was able to get them to order me a replacement. I still have the "bricked" device in my possession, and hopefully I won't have to exchange it to get the new one.
Now that I've explained my situation, is there anyone out there with the KDZ image for this model? I'm thinking that's my only hope to restore this poor thing. I know I've got another one coming, but it'd be nice to have a working backup phone just in case.

mine wont let me reset it need help

Guys I know this is off topic but could you share the stock wallpapers of the K7 please????

reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
Be sure to update when a custom recovery is available i just don't feel safe with my lg k7 rooted without a recovery. i mess things up quite often and custom recovery's CWM or TWRP have always got me out of sticky situations

ermond012 said:
Guys I know this is off topic but could you share the stock wallpapers of the K7 please?
Click to expand...
Click to collapse
All of them?

Atelear said:
All of them?
Click to expand...
Click to collapse
Yeah, if possible...?

I'm not sure how to upload the file where I put them
---------- Post added at 08:20 PM ---------- Previous post was at 08:13 PM ----------
ermond012 said:
Yeah, if possible...
Click to expand...
Click to collapse
There. These are all the wallpapers excluding the live wallpapers.
PM me for the link

Is the tribute 5 the same phone as the lg k7?

Migue9088 said:
Is the tribute 5 the same phone as the lg k7?
Click to expand...
Click to collapse
Yes they are the same. I think Boostmobile just named it something else

I can try to port a recovery to it if someone can point me to the right direction

I don't think there any custom recovery yet

Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.

starkly_raving said:
Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.
Click to expand...
Click to collapse
Can you tell the person if he could make one for the tribute 5 please

Migue9088 said:
Can you tell the person if he could make one for the tribute 5 please
Click to expand...
Click to collapse
Once we have the one for the K7 finished I'll submit the files for the Tribute 5 if some one can provide them.

Error updating via OTA

Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.

Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.

Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...

iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.

tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage

I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what

iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet

iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse

iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse

I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .

iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.

Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate

iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.

ZTE Axon 7 axon7tool failed to connect

Hi there!
I'm newby with android and unlocking the device. My device ZTE Axon 7 A2017G
I want a device running on Lineage os. So I try since 3 days to backup and flash the recovery with axon7tool.
I get always the error message: failed to connect.
I try to install the driver with zadig and now i see the Q...BULK device but still become this error...
I was on android 7.1 B01 and now have downgraded to android 6.0.1 (A2017GV1.0.0B10)
Still the same error.
I changed the computer, still this stupid error.
Can anybody help me, I'm frustrated...

I had this issue and solved it by showing all file extensions in windows. When you rename the recovery.img to recovery.bin you have to make sure that it's actually an BIN file and so you need to have show all file extensions on in the windows settings.

thanks for your answer.
I'm realy shure that I have activated this option, because of other development stuff
Even the first command in each tutorial is not working: "axon7tool -r gpt boot recovery"
When I disconnect my axon and then run the command again I become this error: "Device not connected/found, Failed to connect"
So this means, if I connect the device and I see only the error: "Failed to connect"
the axon7tool see my device but can't connect to them?
p.s. after the downgrad from android 7.1 to 6.0.1 I don't see any updates such as android 7 and I haven't a connection to mobile data (3G/4G). Very frustrated when I want to use whatsapp outdoor

Sorry. I don't know what your issue is then. I'm sure someone else here can help you.

Do you have then Qualcomm drivers installed? If not, try this: QUD.WIN.1.1 Installer-10039.2.zip
If it's still not detected, use the Zadig Tool found here

I had a similar issue. You have to grant admin rights when opening a command window.
Send from ZTE A2017G using Tapatalk

KwesiJnr said:
Do you have then Qualcomm drivers installed? If not, try this:
If it's still not detected, use the Zadig Tool found
Click to expand...
Click to collapse
thank you. What should I select in the wizard when he ask me for the following:
Please choose between WWAN(NDIS6.20) and ETHERNET(NDIS 5.1)
- WWAN-DHCIP is not used to get IPAddress
- ETHNER-DHCP is used to get IPAddress

First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.

KwesiJnr said:
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
Click to expand...
Click to collapse
oh wow! One step further.
The tool waits a second an then I see this error:
C:\Users\bearbeer\Downloads\adb>axon7tool -r boot
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
I dont understand the message.

bearbeer said:
oh wow! One step further.
The tool waits a second an then I see this error:
I dont understand the message.
Click to expand...
Click to collapse
Good, reboot your device into EDL mode once more and try again.

KwesiJnr said:
Good, reboot your device into EDL mode once more and try again.
Click to expand...
Click to collapse
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?

bearbeer said:
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
Click to expand...
Click to collapse
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.

KwesiJnr said:
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
Click to expand...
Click to collapse
thanks again. It works!
What's the next step to become lineageos running on my device? Download and install lineageos or do I need something else before?

If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.

KwesiJnr said:
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
Click to expand...
Click to collapse
Ok I have flashed the TWRP Recovery (not the latest because the latest boot not up) and unlocked the bootloader. What's the Nougat Bootstack and how do I install it?

Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.

KwesiJnr said:
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
Click to expand...
Click to collapse
What's the best way to upgrade the twrp?

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
0. Reboot to TWRP, then copy the desired Recovery Image file you want to upgrade to, (e.g. twrp-3.1.0.0-ailsa_ii.img) to your Internal Storage.
1. Tap Install Image from the lower right corner. Proceed to select the recovery image you just copied to your device.
2. You should now see a radio list. Select Recovery, then swipe to flash.
3. Reboot.
That is all.
Alternatively, you can flash the recovery upgrade file via fastboot, like you did the older version. Just make sure you flash the older version first, THEN the newer. Should work like a charm.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
metpolds said:
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
Click to expand...
Click to collapse
Lmao. I feel you, bro. Pretty convinced he's new to these forums as you guessed, and I'm sure he likely doesn't know about the 'Thanks' system. You know, benefit of the doubt and all.
Ultimately, I just wanted to help out. I know how frustrating it can be with these things so...

Thank you! Ok I'm now on "twrp-3.1.0-0-ailsa_ii.img" and it works.
Yes this is correct. I don't saw the "thanks" button...
I'm so happy that all of you help me. As a newby there are so many threads, tuts, ... an everywhere all goes right. But on my device nothing works at first try. Thank you a lot! :good: :laugh:

Android 7.1.1 Doogee X5PRO

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

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

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

Do the camera and fingerprint work?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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