I was installing a new ROM with TWRP and it got stuck. I can boot back into TWRP, but there is no recovery. I can connect to adb and it sees my device, but i can not get into adb shell to flash. what else can i do? At this point, i just need to flash with a different rom, but cant push or flash
zhzaen said:
I was installing a new ROM with TWRP and it got stuck. I can boot back into TWRP, but there is no recovery. I can connect to adb and it sees my device, but i can not get into adb shell to flash. what else can i do? At this point, i just need to flash with a different rom, but cant push or flash
Click to expand...
Click to collapse
First off. You should have posted in the help-section. You should know this.
Anyways, if you can connect to ADB, you can flash a new boot.img and start over, or a boot.img with CWM\TWRP.
If you want to start at the VERY start though, you can also flash with the official LG Mobile Support Tool to get back to the official non-rooted firmware.
dmbardal said:
First off. You should have posted in the help-section. You should know this.
Anyways, if you can connect to ADB, you can flash a new boot.img and start over, or a boot.img with CWM\TWRP.
If you want to start at the VERY start though, you can also flash with the official LG Mobile Support Tool to get back to the official non-rooted firmware.
Click to expand...
Click to collapse
Yes, i thought of that after i posted. The problem is that although i can see devices in adb, i can not get into adb shell. Can i flash file from outside shell?
Update, even though i can run adb device, it returns a 0123456789abcdef device, which i assuming is not my device.
I can boot into download mode, but its stuck on firmware update.
zhzaen said:
Update, even though i can run adb device, it returns a 0123456789abcdef device, which i assuming is not my device.
I can boot into download mode, but its stuck on firmware update.
Click to expand...
Click to collapse
Shouldnt be 0123456789abcdef, unless you wrote an example.
How long have you tried it to be at firmware update?
I have noticed that mine can also hang for ~5-10mins or so at firmware update now and then (At its worst it was at 21min).
If you cannot get a firmware update \ restore from the LG Support Tool, my limit has been reached.
This is where I allways went when I soft-bricked my phone.
Luckily (I guess), mine allways worked using the LG Support Tool.
dmbardal said:
Shouldnt be 0123456789abcdef, unless you wrote an example.
How long have you tried it to be at firmware update?
I have noticed that mine can also hang for ~5-10mins or so at firmware update now and then (At its worst it was at 21min).
Luckily (I guess), mine allways worked using the LG Support Tool.
Click to expand...
Click to collapse
it sounds like you have recovered your phone a few times. I can get to fastboot and download mode. Not adb. I guess the LG Mobile Support Tool does not use adb, as it see the phone, right?
Thanks....stuck in the 5-21min hang. nerve wracking
Related
i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?
If you could boot into fastmode, then just flash stock rom.
Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.
Hey, guys Im trying to flash my my lg g2 sprint edition back to stock using the lg flash tool. I downloaded the sprint tot and dll and when it says flashing on the lg flash tools it brings up and error that says wrong dll or model, I looked at the model it detected and it says my sprint g2 was a d801.
How do i fix this?
Thanks.
Still need your help guys
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
What rom is your phone currently using right now?
Thank guys I got it to work using the dll. !!
Theboss1242 said:
Thank guys I got it to work using the dll. !!
Click to expand...
Click to collapse
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
afrojoc said:
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
Click to expand...
Click to collapse
i don't know, it worked for my ls980 with a d802 firmware
Alexandercat said:
i don't know, it worked for my ls980 with a d802 firmware
Click to expand...
Click to collapse
where did you get the dll?
OMG ITS WORKING!!!!!!
afrojoc said:
where did you get the dll?
OMG ITS WORKING!!!!!!
Click to expand...
Click to collapse
nice to know :good:
Please Help
I have the same issue. Flashtool thinks my phone is a D801. It boots normally for a few seconds and keep rebooting. Im Reading, dowloading and trying every method around since yesterday afternoon with no luck. I did replace the .dll you provided but i have a different error now, something like mismatch different files and it shows both files names. I just got this phone from a friend. it shows d801 tmo versión in flashtool so i think he was messing around with any tmo based rom (if exits). So flashtool does not let me flash the phone because of this(Think this is a 801 tmo)
I also tried lg suppor tool but it never download the firmware. It get stuck on downloading firmware or checking phone settings (something like that), I found my cell model on the back on the phone so im pretty sure is a SL980. So what comboof files i can use? Do i still can use the.dll provided? Do i have to rename something?(btw...i did and didnt work).
Any other tip? Did i miss something? I have no phone now so im kinda desperate. Thanks in advance for any help.
Sorry for any mistake, english is not my first language.
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Alexandercat said:
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
ToledoG28 said:
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
Click to expand...
Click to collapse
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Alexandercat said:
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Click to expand...
Click to collapse
ok...i will try that...i was able to flash twrp and get to recovery
ToledoG28 said:
ok...i will try that...i was able to flash twrp and get to recovery
Click to expand...
Click to collapse
if you can go to twrp you can flash with adb, i wasn't able to go in recovery, just download with the d801 firmware, that explains why it was complicated
Thanks for all your help. I was able to erase everything via fastboot and my phone fell down and power off before flashing img and now is dead. I have a big blue pitbull inside the house who makes the disaster.,.lol. i just got one white from a friend for $160. Im sure this thread can help any people with a brick device. Thanks again.
Sent from my unknown using xda premium
Pity, dogs like smartphones :/
Inviato dal mio LG-LS980 utilizzando Tapatalk
but i get no adb?
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
try this
boxorandyos said:
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
Click to expand...
Click to collapse
you gotta go do device drivers and your device will show up as some unknown device so you install the adb devices for your phone and then you should get adb to show.
Alexandercat said:
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Click to expand...
Click to collapse
The magic dll, worked for me d802 A very big thanks to you man. I spend hours trying to fix it all it needed was a magic dll from a MagicMan. Thank you again million times.
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
*update*
So now I can't access recovery nor fastboot. Any ideas how to fix that?
*original post*
So, I was dicking around with this zenfone 5 aaaaand I managed to get it stuck in bootloop. Being the epitome of calmness I panicked and screwed up more. Anyway, here's the brass tacks.
The phone is bricked, I can still access droidboot but that's it. I can flash fastboot.img and recovery.img, but can't find device when trying to adb sideload the rom, because I didn't install the adb drivers earlier. The way I see it, I can't flash new roms till I somehow magically able to install adb drivers without being able to boot into the phone and turn on usb debugging.
So, I need help. Is there some way I can still somehow shove adb drivers into this?
Click to expand...
Click to collapse
After a bit of googling, I found out that TWRP has mount feature and I flashed that through fastboot. And then I mounted the phone and managed to install adb driver that way. Then to install the rom I got from asus site, I flashed the fastboot and recovery image that corresponds to the rom, aaaaaaaaaand now I lost droidboot for some reason. Every attempt to boot goes to recovery, so I can't adb sideload anything now. But I got recovery, so yay?
I forgot the question. How do I proceed from this? (My current condition= Nothing is working except recovery)
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
yasin0005 said:
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
Click to expand...
Click to collapse
Yeah I did that. It's just that, now it's stuck at "Asus, in search of incredible". No droidboot, no recovery.
install intel driver !!
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW