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
Hello,
I just got the OTA message for 4.4 and tried to install it but I got a bootloop. After clearing the cache and performing a factory reset in TWRP (which got installed through Nexus Toolkit) it still didn't work. Someone told me to perform a complete format through TWRP which I did (hindsight, I know) and now TWRP says I have no OS installed, adb won't see my device (I have the drivers installed) and when I go into the bootloader (which says FASTBOOT MODE) fastboot still won't recognize the device (nothing shows up on my PC either but that can be normal).
I'm at my wit's end here, is there anyone who can help me?
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature). After that if it still don't boot due to existing data, boot into a custom recovery and do a factory reset without wiping the internal storage.
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
eksasol said:
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature).
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
Click to expand...
Click to collapse
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen), not in recoveries. If you have the UND installed then they both should work, if not it wasn't installed correctly. If you are using Windows 8 you need to disable driver signature before you can install UND (search google for that).
You could also make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen)
Click to expand...
Click to collapse
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
You might have to point the drivers to your phone. If you go into device manager, see if your Nexus 4 has an error. If it does, right click it, and then update the driver. Do a manual install, and point it to the .ini file for the driver
fverswijver said:
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
Click to expand...
Click to collapse
Fix your drivers, uninstall them and select the checkbox to delete the driver files, search Google on how to disable driver signature and try reinstalling the driver again.
or
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
Click to expand...
Click to collapse
I did this and still the same, adb gives an empty list and fastboot gives nothing.
fverswijver said:
I did this and still the same, adb gives an empty list and fastboot gives nothing.
Click to expand...
Click to collapse
Try using a different cable and on different computers.
eksasol said:
Try using a different cable and on different computers.
Click to expand...
Click to collapse
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
fverswijver said:
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
Click to expand...
Click to collapse
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
If you tried it with Ubuntu, make sure you do the 1st step from here also:
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Same here
i installed the ota update normally with twrp installed everything went fine but im kind of disappointed in this update:/
eksasol said:
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
Click to expand...
Click to collapse
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
fverswijver said:
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
Click to expand...
Click to collapse
Is file transfering working atleast? If it is, then it's a software problem. If it isn't, then it could be a hardware problem, you can try replacing the USB charging board for the phone. Also some roms with corrupt files can cause this issues, so try a different roms if you haven't.
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
fverswijver said:
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
Click to expand...
Click to collapse
Get one of these: http://www.ebay.com/sch/i.html?_nkw=nexus+4+usb+charging+port+replacement&_sacat=0
If it don't work, then use the phone as a door stopper.
hey guys, I'm having the same problem here but with a Nexus 5 now.
Its been over a month and I've kind of gave up over the situation.
I couldn't resist to write a comment on the thread, since it appears to be the same problem as mine.
long story short, I decided to order an USB charging port to replace the one on the phone (as my last attempt).
Otherwise I will consider using the device as a door stopper.
Do not despair! Check this out: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
http://highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/
i installed nokia xl rom into my device un fortunately i wipe the os and later i copy a rom file into my sd card and tried to flash tjat but it showing unable to open the zip. iam stuck with my company logo on the screen. twrp cannot open the zip and flash the rom. please help me in this issue.
thanks in advance
Hi,
Sony released new firmware update for Z4T: 32.2.A.5.11
See on Xpericheck and FlashTool.
November security patch update:
http://www.xperiblog.com/2016/12/322a511-hits-xperia-z5-series.html
For those who have installed Xposed upgrade to version 87 (due to a bug with november security patch that causes a bootloop)
Nice. Though I think I'll skip this update. I have the best stability and battery life I've ever had on any Android device right now, so I'm sticking with that.
For example, with my Samsung Galaxy S6 I regularly updated, but in the end I was stuck with different ROMs that all suffered from battery drain or stability issues. I eventually rolled back to a very old ROM that performed well again.
Not saying it's the same with Sony, but.. it ain't broken so I'm not fixing it And I couldn't care less about the November security update.
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v42.zip
SuperSU-v2.79-201612051815.zip
TWRP-3.0.2-0-20160604.img
xposed-v87-sdk23-arm64.zip
drmrestore.zip
killdozer56 said:
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v40.zip
TWRP-3.0.2-0-20160604.img
SuperSU-v2.78-SR4-20161115184928.zip
xposed-v87-sdk23-arm64.zip
drmrestore.zip
Click to expand...
Click to collapse
M8, is this combination really working with DRMrestore? It is said that you need the same version of firmware and kernel...
GhostLeader said:
M8, is this combination really working with DRMrestore? It is said that you need the same version of firmware and kernel...
Click to expand...
Click to collapse
Hi,
Yes it works with the features I tested (X-Reality, camera enhancement). And after flashing drmrestore.zip you got new tabs for update sony applications in
Parameters-> about the tablet->Software update
Here is the Sony service menu after flashing drmrestore.zip:
After trying the CM 13 Alfa version, I can confirm the configuration of Killdozer56 (Andro+ kernel v42) is working like a charm, including keys.
After uninstalling most of the Sony bloatware I have never seen such a responsive piece of hardware.
aykito said:
After trying the CM 13 Alfa version, I can confirm the configuration of Killdozer56 (Andro+ kernel v42) is working like a charm, including keys.
After uninstalling most of the Sony bloatware I have never seen such a responsive piece of hardware.
Click to expand...
Click to collapse
It really is something, right? Yesterday I was reading some manga for several hours (Berserk on PerfectViewer) and the battery drained very, very slowly. And this is while constantly upscaling images with Lanczos 3 to 2560x1600, which is quite intensive. Super impressive.
killdozer56 said:
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v42.zip
SuperSU-v2.79-201612051815.zip
TWRP-3.0.2-0-20160604.img
Click to expand...
Click to collapse
did this, but twrp touch is not responding, i can't do anything in twrp. device boots only into twrp...
whta did I wrong?
thanks in advance!
theeyeofspike said:
did this, but twrp touch is not responding, i can't do anything in twrp. device boots only into twrp...
whta did I wrong?
thanks in advance!
Click to expand...
Click to collapse
Hi,
You are sure you have flashed the right versions for the right models (kernel v42 and TWRP-3.0.2-0-20160604-1.img). Try to reflash via ADB.
killdozer56 said:
Hi,
You are sure you have flashed the right versions for the right models (kernel v42 and TWRP-3.0.2-0-20160604-1.img). Try to reflash via ADB.
Click to expand...
Click to collapse
I used this ones:
Xperia Z4 Tablet LTE,
Central Europe 1 , Customized CE 1, 32.2.A.5.11 / R4C
TWRP-3.0.2-0-20160604.img
Z4T_SGP771_AndroPlusKernel_v42
flashed via flashtool-0.9.23.0-windows. right after flashing the kernel, there is the red light blinking...and the device soesn't do anything.
I flashed Z4T_SGP771_AndroPlusKernel_v42 - only the img.
Should I flash the whole Z4T_SGP771_AndroPlusKernel_v42.zip??? how would I do that?
You might be up for a factory reset (full wipe) since you are the only one with this combination and touch not working.
theeyeofspike said:
I used this ones:
Xperia Z4 Tablet LTE,
Central Europe 1 , Customized CE 1, 32.2.A.5.11 / R4C
TWRP-3.0.2-0-20160604.img
Z4T_SGP771_AndroPlusKernel_v42
flashed via flashtool-0.9.23.0-windows.
I flashed Z4T_SGP771_AndroPlusKernel_v42 - only the img.
Should I flash the whole Z4T_SGP771_AndroPlusKernel_v42.zip??? how would I do that?
Click to expand...
Click to collapse
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
killdozer56 said:
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
Click to expand...
Click to collapse
i tried to flash the kernel via fastboot command line, BUT, i writes "waiting for devide" and nothing happens.. I connected the device in fastboot mode. thats why later I tried to flash with flashtool...
theeyeofspike said:
i tried to flash the kernel via fastboot command line, BUT, i writes "waiting for devide" and nothing happens.. I connected the device in fastboot mode. thats why later I tried to flash with flashtool...
Click to expand...
Click to collapse
"Waiting for device" This indicates that the drivers are incorrectly or not installed
when you type fastboot devices a serial number like CB5A27N6F must appear.
Check into windows devices manager to see if there's no problems when the tablet is connected in fastboot mode (for me i have it under Android devices -> Android composite ADB interface)
What windows version ?
killdozer56 said:
"Waiting for device" This indicates that the drivers are incorrectly or not installed
when you type fastboot devices a serial number like CB5A27N6F must appear.
Check into windows devices manager to see if there's no problems when the tablet is connected in fastboot mode (for me i have it under Android devices -> Android composite ADB interface)
What windows version ?
Click to expand...
Click to collapse
thanks!
in the device manager, everything seems to be alright.
i installed:
"C:\Flashtool\drivers\Flashtool-drivers.exe"
Xperia_Z4_Tablet_driver
and ran the cmd in admin mode...
killdozer56 said:
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
Click to expand...
Click to collapse
I was also having issues with touch not working, but I found it it was because I was trying to use the rootkernel tool to generate the boot.img with DRM fix... so either the rootkernel tool doesn't work anymore, or the DRM fix is causing an issue.
Anyone know how to restore the backed up TA drm keys without using the rootkernel tool?
theeyeofspike said:
thanks!
in the device manager, everything seems to be alright.
i installed:
"C:\Flashtool\drivers\Flashtool-drivers.exe"
Xperia_Z4_Tablet_driver
and ran the cmd in admin mode...
Click to expand...
Click to collapse
And Fastboot devices ?
killdozer56 said:
And Fastboot devices ?
Click to expand...
Click to collapse
as well... i must say, that i had connected a sony xperia z5 premium to this computer... is this a problem?
when I do : cmd "fastboot devices", there apperrs a serial number...
now i finally got the boot.img flashed via "C:\Flashtool\x10flasher_lib", BUT red lights blinkung on the device.
i just don't know what to do right now...
theeyeofspike said:
as well... i must say, that i had connected a sony xperia z5 premium to this computer... is this a problem?
when I do : cmd "fastboot devices", there apperrs a serial number...
now i finally got the boot.img flashed via "C:\Flashtool\x10flasher_lib", BUT red lights blinkung on the device.
i just don't know what to do right now...
Click to expand...
Click to collapse
Are you sure the USB device debug mode was activated in andoid developper options before you flash the kernel first time after flashing the new firmware.
killdozer56 said:
Are you sure the USB device debug mode was activated in andoid developper options before you flash the kernel first time after flashing the new firmware.
Click to expand...
Click to collapse
yes. did that...
just tried with itala firmware, no success... still just blinking re light...
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.
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