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...
Related
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
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
Hello XDA,
I just got a v10 and while i'm new to the phone, I'm not new to rooting/ installing custom roms etc. But for the life of me I cant unlock to bootloader of this phone which if im not mistaken, is the only way to get root. I just installed adb on my windows 10 laptop and I'm trying to enter fastboot on my devices by plugging in the power cable and pressing the volume down and I'm greeted with a screen that says"*welcome to fastboot mode for bootloader unlock: *quick Guidance...etc" I cant exit out of this mode so I assume this is fastboot mode? It doesnt look like any fastboot mode Ive ever seen. Anyways when trying to run the fastboot oem unlock command, I am stuck on "waiting for device". I honestly dont know whats wrong with my setup but if someone could help that would be fantastic. I have tried installing the Lg united drivers and samsung drivers but they dont seem to work. Please advise if you could.
http://forum.xda-developers.com/showthread.php?t=3490604
gamin92 said:
http://forum.xda-developers.com/showthread.php?t=3490604
Click to expand...
Click to collapse
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
ayo234 said:
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
Click to expand...
Click to collapse
I looked online at some forums about this issue and I got it fixed Here what the post said
1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list...
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you
Extremely helpful and it solved my problem. Here the original thread, its post number 33
http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
The TL;DR is, I bricked my phone (TMo Nord N200 5G, SIM unlocked, Bootloader unlocked). I'm trying to use the MSM to recover it. I can't boot to EDL (hold down volume up and volume down at the same time, while pressing power or plugging a USB cable into my PC). It just boots to Fastboot when I follow that procedure. I can't get to a place where I can use ADB commands (ADB shows device "unauthorized").
Longer version, my stock phone was upgraded to the June patch level, I think.
I did the SIM unlock, unlocked the bootloader, and installed the drivers.
I successfully flashed the latest PHH squeak FOSS by following this guide but it had some quirks that I wasn't completely satisfied with.
I flashed a SparkOS GSI linked from somewhere else, but it constantly beeped at me after I disabled Google Play Services, so I decided to move on.
I think the next OS I tried was CRdroid from the same place, but I also replaced the boot.img with a stock one that was patched for Magisk. I can't remember why I thought this was a good idea. There was also a thread that said Magisk doesn't like having nothing in system_a so flash this blank partition using these commands. It always errored out, but I tried it before rebooting.
At this point, my phone would either boot to Qualcomm CrashDump on its own, or Fastboot if I held volume down.
Using the latest Fastboot Enhance I was able to get into fastbootd by switching to "A" active, then rebooting to fastbootd. Have to remember to switch back to "B" active to get anything else to work.
I've tried flashing a few different things since I can get to fastbootd now. I'm no longer booting into the Qualcomm CrashDump, it reliably boots to fastboot as long as I'm "B" active. I just can't get anything resembling a working OS.
I've tried flashing the OTA TMo with Fastboot Enhance a few different times, and a few different GSIs through fastboot, and I really want to get back to stock now so I can start all over.
I've also tried a couple different MSM tool versions, but since my phone is never in EDL, it's never recognized.
Thank you for any assistance.
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
scanman0 said:
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
Click to expand...
Click to collapse
Thank you for responding!
The command fastboot oem edl is returning either:
FAILED (remote: 'Command not supported in default implementation')
FAILED (remote: 'unknown command')
I'm running fastboot version 33.0.2-8557947, it's not in my system path.
From a full power off, holding the buttons and plugging in the USB cable, it's about 5 seconds until I see the OnePlus logo, then 2 more seconds before I drop into Fastboot. I'm not sure what I'm looking for, to confirm EDL mode. I'm not seeing my Device Manager update in that time, and the MSM tool isn't displaying anything, either.
try insert cable then volume + and - and power. keep it holding for 10-15 seconds or till you see qualcomm device in device manager
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
try holding both volume buttons (make sure its off!) then plugging your phone in to the computer with msm tool open (you can pre-press the start button) (make sure you have all the drivers installed)
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
yrrebeulB said:
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
Click to expand...
Click to collapse
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Same issue as OP, won't boot into edl
edit: use USB 2.0
You can try enumusb.exe here: http://www.temblast.com/windows.htm
Code:
C:\>enumusb.exe /l /v05c6 /p9008
It will list the first time that a QUSB_BULK was plugged into a port, even if there was no driver found/loaded.
If you want, you can clear past connections by (needs to be admin command line):
This does no harm. I clear everything out occasionally, it just means that next boot will take 5 seconds longer while it discovers "new" devices and installs the same drivers.
Code:
C:\>enumusb.exe /d /v05c6 /p9008
Or, if you don't like that, just plug your device into a different port and see if another port is listed in enumusb.exe /l
On that same page you can find usblog.exe
You just run it and it will show you what pops up and down.
But, this only shows devices that Windows has loaded drivers for.
swee08315 said:
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Click to expand...
Click to collapse
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
I re-installed the Qualcomm driver bundle while my phone was plugged in and in EDL mode, and MSM finally worked! Thank you kind stranger! I'm back to factory now.
Thank you Strangers ,
yrrebeulB , all of you
Ytube21 said:
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
Click to expand...
Click to collapse
thank you
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
this line literally saved me hours
yrrebeulB said:
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
Try my native Windows EDL client. It uses the same Firehose loader as your stock tool does.
At the very least this will give you a second opinion.
http://www.temblast.com/edl.htm