Related
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
jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..
Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================
Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You need to install fastboot in pc and then flash the device to make it work.
You can prefer this thread
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
debdeep98 said:
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
Click to expand...
Click to collapse
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
K.. install adb(https://www.androidfilehost.com/?fid=745425885120698566 ). If you had installed moto assistant then you'll have the drivers. If not then google motorola drivers and install them(http://www.motorola.com/getmdmwin ).
Once it's done. Open the folder where adb is installed.
Hold shift and right click>open command promt here.
At this point boot into the bootloader on your phone (fastboot mode).
On cmd type fastboot devices.
If your device is detected then it will show on screen.
If you get to this part.
Start flashing thru fastboot.
Get the files from google( or https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL)
Instructions to flash are in xda.
If you get failed to flash: security version downgrade then you're probably flashing an older firmware. Download the latest.
If you get failed to flash: preflash validation failed then there's not much you can do. Or atleast i don't know a solution to that.
its not detecting my device
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Anubhav074 said:
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Click to expand...
Click to collapse
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
riyan65 said:
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
Click to expand...
Click to collapse
yeah i tried that but when it is not verifying my phone when i select id (which is xt 1686) it says that phone can not be verified try again.i have tried every given id but it is refusing to accept my device.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
Here's a guide to flash stock firmware.
Try the linked Mini ADB & Fastboot, if your device isn't recognised try to connect it to another usb port or use another usb cable.
Are you sure that you're in fastboot mode when you type the commands?
Read the guide carefully.
You need:
Latest signed stock firmware:
Europe (RETEU):
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
India (RETIN):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flashallO.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
Mini ADB & Fastboot
https://drive.google.com/file/d/1lLYfimKN1U5CJ9cfpTCkhtMiuG8EfXBZ/view?usp=sharing
1) Download the 8.1.0_OPS28.85-17-6-2 Indian firmware (it's the last one for the Moto G5+ (potter).
2) Install Mini ADB & Fastboot (best place is the root directory of C:/ or how the partition/hard drive is named where your OS resists), not in program files or another folder.
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
NOTE: If the command window appears for a brief moment then disappears, device drivers may not be installed. Ask again then.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
Sent from my Moto G5 Plus using XDA Labs
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Anubhav074 said:
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Click to expand...
Click to collapse
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log , you can do that in TWRP->advanced->copy log, if TWRP is installed.
Try to flash the firmware and immediately after that grab a log and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log, you can do that in TWRP->advanced->copy log, it will be stored in your internal storage.
Try to flash the firmware and immediately after that grab the log (with TWRP file manager) and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
debdeep98 said:
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Click to expand...
Click to collapse
That´s what I´ve said. If you would have TWRP you would be able to send a recovery.log but all you want to do is to flash a signed fastboot firmware. That´s possible without TWRP or unlocked bootloader, just by fastboot. Unzip the indian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
into your Mini ADB & Fastboot folder, place the flashallO.bat there too and double-click it, everything in fastboot mode as described before.
What happens when you do that? Are the commands executed in the command window of your Windows PC?
Can you make a screenshot of it? The guide I posted has everything you need in it, you have to tell me what happens when you try to flash the unzipped firmware.
Just to be clear, the firmware and everything has to be on your PC, not your moble device!
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
View attachment batch.txt
Anubhav074 said:
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
Click to expand...
Click to collapse
Ok, that doesn't look to good.
The whole process is failing right at the start when the device is trying to build the partition table.
Have you tried different USB cables and ports?
Imo there are only two possible solutions:
Your device isn't working with fastboot correctly or its a hardware failure, the eMMC (the internal SD) may be corrupted. As your device is locked and hasn't been modded in any way this is the most plausible scenario also because it crashed out of the blue.
The only thing you can try yet is to use a different ADB and Fastboot tool, this one for example:
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
If all that changing of ports, cables and tools doesn't help you have to bring your device to a service center, they will most probably change the motherboard which isn't a cheap repair so if your device isn't under guarantee anymore you have to consider it it's worth the money.
Good luck!
Sent from my Moto G5 Plus using XDA Labs
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Anubhav074 said:
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Click to expand...
Click to collapse
I think you've done everything that's possible.
The device wasn't rooted,modded,unlocked or something.
It showed the failure out of the blue.
You tried different fastboot tools, cables, ports and the correct firmware.
I asked someone with more knowledge about your log and the whole case and he is thinking the same as I do.
So the chance for a software problem is really small. I told you everything I know, maybe a service center has more options for software checks but as far as I know they use the good old Lenovo Motorola Software Assistant.
So I would recommend to go there and ask (before they do anything) what you have to pay if your eMMC is broken. Here in Germany they always change the whole motherboard, the costs are about the half of the price you paid for the device here.
If your still under guarantee it's a different story.
I'm sorry, I told you everything I know and I flashed my Moto G5+ several times.
My opinion is that the device has a hardware failure and visiting the service center is the only thing you could do now.
I really would like to give you better news.
Sent from my Moto G5 Plus using XDA Labs
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
phone crazy said:
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
Click to expand...
Click to collapse
Read this thread. You can flash signed Motorola firmware like discribed. If you don't want to lose your data you can try to omit the "erase user data" command. Just delete it out of the flashallO.bat.
https://forum.xda-developers.com/g5...ked-stuck-fastboot-mode-t3996599/post80792213
Sent from my Moto G5 Plus using XDA Labs
Hi!
I borrowed this tablet from a friend who said I could use it for awhile. I was installing OTA OS updates to the device and I think I inadvertently hit the power button at a bad time while futzing with putting it in a case. Now it won't boot and just hangs on the LENOVO logo screen.
I can hold volume up + power and get to the Android 8.1 Recovery menu. I've cleared all the data and cache, but that didn't fix it. I think I will have to restore the firmware on it, but am open to other suggestions.
Now, finding that firmware has been a real challenge. It looks like a russian "lenovo forums" website hosted the file at one point, and literally everything links to that russian website and file, but all I get is a 404 when trying to download the firmware file. I was able to find the Tab4 8 Plus file, but that doesn't match this tablet.
I already told my friend who said not to worry about it, but I feel bad and want to fix it. I can't find anything useful on the Lenovo support pages, except other people mentioning the russian website and getting the firmware file from there. Thanks for any help you can provide.
This is the site that I keep getting links to: -x--snip--x- I guess I can't post URLs yet since this is a new account.
Some of the OTA incremental updates I can download, but I need to find the full firmware file. Judging by the linking to this file I see in other threads and forums, this file link stopped working sometime between July 2019 and today. Thank you.
I was just in a similar situation yesterday.
https://forum.xda-developers.com/showpost.php?p=81833275&postcount=2055
Lenovo MOTO Smart Assistant downloads the QFIL file and rewrites the internal flash via EDL mode to restore the stock ROM.
https://pcsupport.lenovo.com/jp/en/...er-list/component?name=Software and Utilities
I have the same problem I downloaded the program but it can not install stock rom.When I open the device it enters fastboot and I can not configure anything. I can access fastboot twrp but when. Any help?
giorgakis1966 said:
I have the same problem I downloaded the program but it can not install stock rom.When I open the device it enters fastboot and I can not configure anything. I can access fastboot twrp but when. Any help?
Click to expand...
Click to collapse
I'm just a noob, but i recovered from a similar scenario this morning... I found that pushing volume+ and powering on doesn't enter EDL like it needs to, but rather boots to TWRP, if you can boot into the ROM you can run the command "adb reboot edl" which gets it into the Emergency Download Mode. I would imagine that you could boot into TWRP then run a similar command in the terminal
ROM Unbrick LenovoTAB 4 8 Plus Stock Rom_Rooting File1- BOOT.img RECOVERY.img for Fastboot flashing— File2- For QFIL resulting in Android 7.1.1. which will find the OTA update to Oreo after completing the installation. File3- For TWRP Restore. (use
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