So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
DakshMiglani said:
So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
Click to expand...
Click to collapse
very good how to! couldn't go wrong.! before step 4 I also check if device is connected via code: adb devices.
if device is not showing up you already know somethin's wrong.
Thank you for the guide. I pushed twrp into my phone without any error and I'm on the OTA 5.8.015S but it doesn't work. I rebooted into recovery and it still gave me the stock recovery screen.
Finally got it to work! After pushing twrp you have to type fastboot boot twrp.img and you will get a screen that looks like it's broken. Leave it alone for about 1 minute or two then the screen will turn off. Then press the power button once only to wake the screen up. From there twrp is working! Thank you to steve mars and jim262 for this tips!
Cannot mount /cust in TWRP
After trying to flash I noticed that after the wipes The failure of /cust cannot be mounted appears.
Can't get adb/fastboot to work on Windows 10
windhoarse00 said:
Can't get adb/fastboot to work on Windows 10
Click to expand...
Click to collapse
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Sörnäinen said:
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Click to expand...
Click to collapse
Were you asking for help or just wanted to help windhoarse00?
Amowagou said:
Were you asking for help or just wanted to help windhoarse00?
Click to expand...
Click to collapse
I don't have the phone yet - a mix of both, as I will be in a similar situation soon.
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Amowagou said:
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Click to expand...
Click to collapse
That's welcome news, cheers.
For me rooting a phone and putting a custom ROM of my choice is essential - not to speak of Titanium Backup to transfer all my stuff to the new phone.
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
nflau said:
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
Click to expand...
Click to collapse
Yep. I ended up with the exactly same issue.
Not working at all, no matter what I do.
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Sörnäinen said:
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Click to expand...
Click to collapse
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
nflau said:
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
Click to expand...
Click to collapse
Gearbest.
I'm already considering to just keep the EUI, but I do not trust their PlayStore installation...
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Sörnäinen said:
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Click to expand...
Click to collapse
Where to download the driver? Thanks!
nflau said:
Where to download the driver? Thanks!
Click to expand...
Click to collapse
No need to download. Just choose the list of drivers on the PC and take the one that's made for fastboot.
this is not real for dummies
this is what you forgot
1) after enable debug mode with tapping 7 times build you must actually enabyle usb debug in settings
2) to install the driver in win10 which dont work automatic unrar the adbsetup and then start in driver dir DPInst_x64.exe
3) after I did manage to adb reboot bootloader I got after reboot into the bootloader but then I am stuck
what is recovery image? and fastboot devices shows nothing
Related
DESCRIPTION:
Today i found the New Root & Installing Custom Recovery(CWM) in KITKAT surely...
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
PREREQUISITES:
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
PROCEDURE:
FOR UNLOCKING BOOTLOADER, FOLLOW THIS
Download the Attached PC Software Named "Huawei Product ID Generator" then Extract this zip file...
Now open it, fill all Info in it and select the device Y300-0000... After this, it will Generate a Product ID for your Phone....
Now go to this site Unlocking Code website
Login to this site using your Huawei id which you made in themes store or in huawei cloud!!
Use the Serial Number Written on BACK OF YOUR PHONE..!!
Fill like, samrtphone>Product Model should be "HUAWEI Y300-0000"
then fill all fields and captcha also.. Click Submit and get the UNLOCKING CODE....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
Now go in your 4C's Settings>About Phone.
Then tap on Build number 10 times,,, you will get the Developers options in Last of Settings app. Open Developers option and Turn On the USB DEBUGGING.
Now connect your device to PC in MTP mode and then install the ADB drivers for it....
To install adb drivers correctly, use the Software Adb Driver Installer from here
LINK FOR ADB DRIVER INSTALLER
Full ADB folder is also attached Below.... put this folder in drive C.
Now Direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
BOOTLOADER UNLOCKED NOW!!
Now You are Ready to install CWM recovery first.... Download the Root and CWM recovery File from here...
This File Also contain Stock Recovery of Kitkat Rom
4C Root+CWM by [email protected]
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in adb to install the Custom Recovery(CWM) in your phone.
fastboot flash recovery cwm.img
Then
fastboot reboot
This will reboot your phone and cwm installed.
Now move the Root.zip file to sd card and using CWM recovery, install it.. and Whoa!
Its done and phone Rooted for sure... wid no bootloop chance..
Now Customize Your Phone Install Viper4Android And Roms Xposed ^_^
If You Want To Stock Recovery After Root Simply Use The Command In Fastboot Mode
fastboot flash recovery stock.img
Then
fastboot reboot
This way, you will have Stock Recovery back.
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01
Version Information:
Status: Stable
Stable Release Date: 2015-09-28
Created on: 2015-05-29
Last Updated on: 2016-02-19
Reserved
I'll try it when i arrive home.
Enviado do meu CHC-U01 através de Tapatalk
I flashed the cwm zip .. But now unable to boot in to recovery .. After doing Vol up + power .. Honor title come n nothing happens .. Normal booting is fine , just recoverys bricked I think :crying:
Nops... keep pressing vol up for 3 sec then keep power button pressed also untill cwm appears... Dont release keys when logo appear... Release when cwm appears... @Srijit
Press thanks if i helped you
Followed all the steps but still not able to boot into cwm .. I have lollipop beta installed .. Is that the problem ? :crying:
Its for kitkat nd has kitkat kernel.....
inshaalmirza said:
Today i found the New Root & Installing Custom Recovery(CWM) for sure,,,
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
Just mail at [email protected] wid subject that unlock bootloader huawei honor 4c and in mail type all info..like imei, serial no. Product number nd model number...they will send you unlocking code....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
download the installer utility ADB and Fastboot and set (if you have them yet);
direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
Now You are Ready to install CWM recovery first.... Download the Root and CWM recovery File from here...
https://drive.google.com/file/d/0B0iMDu5QRxNicU1EalpZeHNUR3M/view?usp=sharing
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in adb to install the Custom Recovery(CWM) in your phone.
fastboot flash recovery recovery_cm.img
Then
fastboot reboot
This will reboot your phone and cwm installed.
Now move the Root.zip file to sd card and using CWM recovery, install it.. and Whoa!
Its done and phone Rooted for sure... wid no bootloop chance..
Now Customize Your Phone Install Viper4Android And Roms Xposed ^_^
If You Want To Stock Recovery After Root Simply Use The Command In Fastboot Mode
fastboot flash recovery recovery_official.img
Then
fastboot reboot
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Credits: Gizdev site...
Click to expand...
Click to collapse
where is for lollipop,,
No lollipop cwm yet...
tested recovery and cannot made a advanced restore. Tried only system but after selection cannor made it to apply.
Anyone knows how?
I backup full... Nd its done
I still dont have the bootloader unlock code
Sent from my ALCATEL ONE TOUCH 7047D using XDA Forums
Lol.... Follow procedure carefully... Nd dont write anything other
Honor 4x I need custom rom and cwm r lollipop update
Sent from my Che1-L04 using Tapatalk
inshaalmirza said:
I backup full... Nd its done
Click to expand...
Click to collapse
Me to.
I tried to restore only system but don't know how.
Everything else seems to work OK.
Enviado do meu CHC-U01 através de Tapatalk
OP! how do you able to get CWM,
does it came from own recovery of 4C? if yes, can you show how
Custom recoveries use the kernel properties of device.... Not the stock recovery converted to cwm.....
Hey. Kingo root android application make tempory root your device. After restart mobile. Back to normal
Sent from my CHM-U01 using XDA Forums
Unlock bootloader... Then it wont come back to normal...
<disclaimer> I take no credit for anything in this guide. A BIG Thanks goes out to @tennear, @Unjustified Dev, @DrakenFX and @Starvirus. They are the ones who figured out the process described below and provided the excellent LineageOS 14.1 ROM. I just wrote this all-in-one-guide because I think the information is way too cluttered and spread over these forums.</disclamer>
<disclaimer> If you're not 100% sure what you're about to do, please first scroll down to the bottom of this post to see a list of DON'T's, a few things you SHOULD ABSOLUTELY NOT DO if you want to keep using your device.</disclaimer>
After having had quite some phones (Moto Defy +, Oneplus One, Nexus 5x,...) and having flashed a lot of ROMs on them, I thought I had quite some experience in these matters. Alas. Unlike Oneplus, ZTE would rather not have users fiddling with their devices. There are also three versions of the Axon 7 called the A2017 (China), A2017G (Global) and A2017U (USA), each with some minute differences from the others. This makes unlocking BL, flashing a custom recovery and installing custom ROMs not so easy on this device.
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution. There's always a tiny chance this process bricks your device. By following this guide, you will lose all your data on your internal memory. Please backup before proceeding. The data on your SD card should be safe.
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4UVMBVpYdVwcnlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
15) Type "Fastboot oem unlock" and hit enter
16) Follow the instructions on your phone and use the volume and power buttons to confirm you want to unlock your bootloader
17) Boot into TWRP by holding both power and volume up button
18) Type "Wipe" and choose "Format Data"
NOTE: If you get a permissions denied issue, try doing these steps while your device is in TWRP.
C) Update bootstack, Install LineageOS 14.1 and update your TWRP to latest version
Q: Why do I need Lineage OS 14.1?
A: It's a custom ROM that's a lot smoother than any available stock rom for any of the Axon 7 versions. Aside from an audio bug (the speakers make a rattling noise when the volume is turned higher than 80-90%) it's perfect. You can however find quite some other decent ROMS here.
Q: Why do I need the latest TWRP?
A: Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone. Update it using the steps below.
1) Download the latest unofficial Lineage OS 14.1 ROM from here: https://www.androidfilehost.com/?fid=457095661767134540
2) Download the A2017G Nougat bootstack from here: https://www.androidfilehost.com/?fid=673368273298930583 (A2017U users: your bootstack is here
3) Download the latest TWRP .img from here: https://build.nethunter.com/twrp/zte/twrp-3.0.4-1-ailsa_ii.img
4) Download a Google Apps version from here: http://opengapps.org/?arch=arm64&api=7.1/ .You must use an ARM64 file since that is the type of the CPU in the Axon 7. You must use 7.1 Gapps since that's the android version Lineage OS 14.1. is based on. Which one you choose is up to you, the "smaller" you go the less google apps will be installed as stock. You can always download the ones you miss via the play store after having installed LineageOS
5) Put the bootstack, the LineageOS and the chosen Gapps zips on your MicroSD card. Also put the TWRP.img on there
6) Flash the A2017G Nougat bootstack: Flash -> select the bootstack file on the microSD card
7) Flash LineageOS 14.1, then flash the Gapps zip file (again via TWRP)
8) Update your TWRP recovery by choosing "Install" and then clicking "Install Image" (bottom right) and selecting the TWRP .img file
9) Wipe dalvik, cache and data
10) Reboot
11) Enjoy your phone
In the unlikely case that you're greeted by a screen that asks you for a password because your system is somehow encrypted, reboot to TWRP and format your data partition to ext4 instead of f2fs (wipe -> advanced)
If your phone doesn't pop up as QUSB_BULK in EDL, you probably installed the driver that came with the phone. The device will pop up below Ports (COM & LPT) on Device Manager as Qualcomm something-something USB device. Uninstall that driver and reinstall winUSB drivers through Zadig.
If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver
Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.
If LOS refuses to install and you get the error axon7.verify_trustzone, install the universal bootloader (A2017X_B15_UniversalBootloader) before the N Modem.
So, the steps after you get access to TWRO are: 1) Install univ. BL (A2017X_B15_... .zip); 2) Install A2017G_N_modem.zip; 3) Install LOS14.1 zip; 4) Optionally, install Gapps; 5) Flash TWRP img
DON'T's:
- DO NOT use the signed TWRP (3.0.2) to backup or restore, it might brick your device
- DO NOT use this guide when you're on locked stock nougat, you need to downgrade to Marshmallow first
- DO NOT flash the wrong N bootstack. There's a different version for G and U devices
- DO NOT use this guide if you're on an A2017 (Chinese) device
- DO NOT unplug your cable from your PC or Axon while axon7tool is doing it's magic
- DO NOT make a mistake or typo, it can be fatal
- DO NOT try flashing random zips or files or formatting this and that when your device doesn't act according to the guide, post your issue instead
- DO NOT wipe anything else than Data, Dalvik and Cache in TWRP
ADDITIONAL STEPS:
- You can opt to root your device by flashing the latest SuperSU zip file
- You can opt to upgrade your unofficial LineageOS to the latest official version to receive weekly OTA updates
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
PsyJoe said:
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
Click to expand...
Click to collapse
Both the aboot.img and the TWRP.img come from A2017U versions. For the moment, we do not know if there is any difference in the aboot file between A2017U and A2017G, but it's highly unlikely. @tennear sent me a tool to read the partitions on my A2017G and the result showed the partitions were the same as those in the A2017U model.
For the moment, there's only one TWRP version, made for A2017U, but it seems to work on all models. I quote tennear here:
tennear said:
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
Click to expand...
Click to collapse
I suspect nearly all bricks on A2017G devices happen when A2017G users use tenfar's tool to unlock the BL. There's a lot of margin for error, for example with the whole COM ports shizzle. I advise not to go down that route. I also advise against trying to flash a rooted image through TWRP without unlocking your bootloader. Especially the command "axon7root.exe -p 4 -b -r" (flashing both boot.img and recovery.img at the same time) seems to kill specifically A2017G devices, that seem to have an extra "DFU" mode, which the A2017 and A2017U devices don't seem to have. A2017G devices get stuck in that mode and there's no way to get them out again.
TL;DR I think the risk isn't in flashing TWRP, but in flashing both boot and recovery at the same time, in the axon7root tool and in flashing a rooted stock rom without unlocking BL.
Thank you for this one thread guide. Should make it a lot easier.
Maybe you can add a few words and links to the B03 files that allow a downgrade from higher versions.
You have a typo in step 14), should be adb not ab
Controllerboy said:
30) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
Click to expand...
Click to collapse
Hi,
So, the backup can be restored, even if we cancel the password? Isn't the backup encrypted than?
Also, when we do swipe to agree to modify the system partition, is flashing SuperSU enough to gain root?
I'm not so much interested in installing a custom ROM (yet) but do want a safe way to gain root.
Thanks for your time and efford,
Edit: And all this is safe (step A) when on B08?
Cheers,
/Cacti
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Znuf said:
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Click to expand...
Click to collapse
Hi,
Thanks Znuf, I'll give it a go then.
Cheerz,
/Cacti
Controllerboy said:
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QDL_BULK"
16) In command, type "axon7tool -r gpt" and hit enter
Click to expand...
Click to collapse
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
le_cactus said:
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
Click to expand...
Click to collapse
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Controllerboy said:
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Click to expand...
Click to collapse
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
le_cactus said:
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
Click to expand...
Click to collapse
I give up. Or at least at this computer.
Just to be sure, the QDL_BULK/QUSB__BULK, shoild it be an unknown device, one with a yellow exclamation mark? Or should I install a driver for it, and if so where do i find it? Google didn't help me out today
I'll try another pc, see if that does work.
Cheers,
/Cacti
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Hi,
i unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Thanks in advance
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Killerdog said:
I unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Click to expand...
Click to collapse
Here's the file from DrakenFX: http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Flash bootstack only once, then flash BO6 stock ZIP. In my experience it doesn't replace TWRP with stock recovery, even when you're not rooted.
DeJe63 said:
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Click to expand...
Click to collapse
Thanks for the tricks. I didn't know you could do all three commands at once. I'll update my guide.
Will this work for B08 or should I go all the way back to "B03 (or others)" ??
Tutorial looks good and simple, big thanks!
In general it works.
For some reason I was not able to update from DragenFX B06 to OTA B08. So I flashed stock recovery, stock B06, OTA B08 and just flashed back TWRP with axon7tool...and it worked. But it may be that I make some mistakes on the way to B08.
I was at BL unlock before.
Controllerboy said:
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Click to expand...
Click to collapse
Hi,
That worked flawlessly on my Win7 box, but I have general USB problems on that device. Got timeouts a few times during the axon7tool -r commands, so I don't dare doing a axon7tool -w command on that machine. So I stepped over to my Win10 x64 machine, but that machine it keeps identifying it as a "Qualcomm HS-USB QDLoader 9008 (COM3) device." :crying: axon7tool -r gives my a "Failed to connect"
Thanks for the help though, much appreciated.
Cheers,
/Cacti
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Controllerboy said:
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Click to expand...
Click to collapse
Thanks for the tips. I'll let you know how things work out.
Cheers,
/cacti
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
It looks good
Applesoap said:
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
Click to expand...
Click to collapse
Some useful tips for rooting MAZE Alpha, perhaps will help you : MAZE Alpha root
Use the method I to patch your boot.img with Magisk-v14 and flash the result image, it must works
Here is the HowTo, have done it 3 times yet:
First, get the correct TWRP Version for Doogee T6Pro ( i dont remember where i got it, i can upload it somewhere if someone have a good location) and the SuperSu Zip.
Then, activate the Developer Options in the Device Settings and Activate the OEM Unlock and USB Debugging in there.
The next Step is to Boot the Device in Fastboot mode. you can either do it by USB with the Terminal Command: "adb reboot bootloader" or you can turn the device of and then reboot it by pressing the Volume Up Button and the Power Button simultanously (quite difficult, didnt Work every Time). You will get to a menue with 3 options: Boot to Recovery, Fastboot and Normal. Switch through these Options with the Volume Up Button and Select it with the Volume Down. Go To the Fastboot Option and Select it.
In Fastboot Mode, plug in the device to an computer and type the terminal command "fastboot oem unlock" (in windows, you have to install the fastboot tools. i dont remember that i had to install them in ubuntu... im not sure). this will wipe the whole data of the device. its important to reboot the device afterwards normaly. otherwise it could happen that you get stuck in an bootloop later ( happend twice to me ) this normal system boot will last much longer then normal, so get a coffee or tea
the next step is do get to fastboot mode again and then send from your computer the command: "fastboot flash recovery twrp-recovery-filename.img". this will flash the recovery.img on the recovery partition.
than go to the bootloadermenue and this time you dont choose fastboot but the recovery option. this will start TWRP
while TWRP is running, you can copy the SuperSU zip to the device with Nautilus or in windows systems with windows explorer. then select "Install" in TWRP and select the SuperSU.zip.
After the installation, reboot to normal system and you are ready with rooting!
if something goes wrong, it can happen that booting to normal system will get you stuck in an bootloop. the last time i could repair the system by booting into recovery (TWRP) and select the Wipe menue and there the Format option. the other time i downloaded the original system from Doogee and flashed all partitions. im not sure if that was necessary.... but who knows :fingers-crossed:
Hello,
Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer..
Thanks
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
OTG and Charge Simultaneously
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
am24901 said:
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
Click to expand...
Click to collapse
Look here: https://www.instructables.com/id/DIY-Cable-to-Use-OTG-and-Simultaneously-Charge-the/
Test
---------- Post added at 08:00 AM ---------- Previous post was at 07:13 AM ----------
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
@Xenograph:
Hi, would you care to specify in detail the rooting process used for your tb-8505F?
That would be very much appreciated!
I aquired the tb-8505X (LTE) model myself, but was surprised by not being able to dig up the rooting method specific for this model from the internet for two weeks now.
So far, my attempts to aquire root have got stuck at the initial stage of having my W7-64bit laptop communicate with TB-8505X via (first) ADB (lists the device) and (second) fastboot (no devices or waiting for devices).
My suspicion is that while ADB has at its disposal the correct W7-driver, subsequently fastboot is unable to operate with that driver.
Internet search shows the <fastboot-waiting for devices> to be rather common, but without coherent solution.
Any thoughts welcome, thanks!
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
How did you actually root it?
I tried patched boot.img, won't work, tried patched recoevery img the M8 is in a bootloop.
Only boot up after I flashed standard recovery again
Cheers
Tom
tom1807 said:
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Click to expand...
Click to collapse
Yes, enabled all three of them.
Then installed the ADB/Fastboot package on W7/X64.
Then the usb driver/drivers (don't know).
Then from the admin CMD adb list devices (returns device name)
Reboot tb8505 into fastboot mode.
adb>fastboot list devices (returns waiting for devices...)
Any other subsequent fastboot command returns the same ''waiting for devices''.
Could be this is better attempted from W10,Ios or linux.
Any thoughts? cheers!
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
tom1807 said:
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
Click to expand...
Click to collapse
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Reboot 8505X from fastboot mode by pressing power button >20 seconds.
Device manager shows Lenovo Android Interface again.
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Q... said:
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Click to expand...
Click to collapse
Haven't used these, I just used the which Windows (in my case wW10) downloaded
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Click to expand...
Click to collapse
I am assuming the device shows it is in fastboot mode, its listed in Device Manager under Android Phone(?) as ADB Interface
After reboot it is listed fro me under USB Devices as ADB Interface. In fastboot boot the driver is from Mediatek, in working mode, the driver is from Microsoft
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Click to expand...
Click to collapse
Used Developer Options to set the Default USB configuration to "File Transfer" works as I set it
Cheers
Tom
Installed mediatek drivers for fastboot, to no avail.
Despite setting the usb preferences to file transfer, the 8505X resets that at every unplugging/rebooting to charging via usb/no data transfer, which also could be the problem, as before entering fastboot mode, usb is disconnected.
In fastboot mode no listing under USB devices in my dev mgr, btw.
Dev mgr shows Alcatel ADB Device>Lenovo Android Interface (as before) and moreover Lenovo Tab M8 under Portable devices. That's in normal working mode.
I presume you are on W10?
Regards, Q.
unlocked bootloader; no root
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Q... said:
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Click to expand...
Click to collapse
1. Go to Lenovo site and download Rescue and smart assistant. Install and run.
2. On the rescue tab you can download the firmware for your tab (it needs to be connected to the PC).
3. Goto where you downloaded the firmware. In the RomFiles folder find the boot.img file. copy it to your device.
4. Install Magisk Manager on your device. Run and select install. select the option to patch a file and select the boot.img file you copied to your device.
5. markdown the location that magisk shows where it saved the patched file. Copy this file back to your PC.
6. Flash the file to your device with fastboot flash boot <patched file location>
7. reboot your device and run again magisk manager this should install the magisk zip file and you are rooted.
Is there any custom recovery and roms available? This tab is quite awsome
Leboboy19 said:
Is there any custom recovery and roms available? This tab is quite awsome
Click to expand...
Click to collapse
I'm looking for a custom recovery as well.
I am having problems with Fastboot. I tried all the drivers etc. and always end up with:
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Any ideas how to connect with Fastboot?
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
lecorbusier said:
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
Click to expand...
Click to collapse
Holding down the down vol while pressing power gets you to Fastboot mode.
That's the common method. Good. On my Acer you need to attach a usb cable even for accessing the stock recovery. But i will dump it anyway, a Tab M8 FHD has been ordered...