Related
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
Hello Everyone. Normally I´m the quiet Reader and not the Active Poster but I need your help guys.
I have a problem since yesterday and I tried to fix it by myself with searching everywhere but couldn´t do it by myself.
What I had before:
Optipop 5.0.2 with Racer Kernel (both had Builds from January) + TWRP 2.8.1
What I wanted to do:
Flash Grogg's AOSP 5.1 and newest Code Blue Kernel
What happenend:
I factory resetted and successfully flashed Grogg's AOSP 5.1 and Code Blue Kernel but had Problems with FCing Clock and Dialer so I tried to reflash both after wiping completely (even internal storage), mounted it and put the needed new files on the internal storage.
I reflashed the Custom Rom + Custom Kernel and the newest Radio, wiped Cache/Dalvik and rebooted. It booted and the notification screen with 'optimizing apps' appeared. After that that screen went black and nothing else.
It was lit so I´knew that the device wasn´t shut down and tried to rebbot sincee nothing happened. I noticed that it was possible to reboot or shut down the device normally so there might have been a Problem with the Rom.
I retried the whole procedure and this time the notification screen didn´t show up after the boot logo and went directly to the black blank screen but i still had the possibility to rebbot/shut down the device normally. This time I didn´t wipe the whole storage and this time it got stuck at the boot logo and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
My Problem is that I can´t connect my device to the computer, find it with 'adb devices' and reflash the Recovery with fastboot. The device is shown as 'android' in device manager in Windows 7 and nothing else. I already tried to un- and reinstall the Google drivers and that whole stuff but it doesn´t work for God's sake. adb doesn´t list my device and the 'list of devices attached' is blank although my device is connected.
I know my phone is soft bricked and that it is possible to fix that although I don´t know why it even broke the OS and Custom Recovery.
Can anyone help me out with a step-for-step-guide to fix the adb Problem and explain me why that blank screen even happenend?
Edit: If I´m in fastboot mode the device is shown as >Android Bootloader Interface< and isn´t listed with 'adb devices'. If it is powered off it is shown as >Android Composite ADB Interface< but is listed with 'adb devices' but I can´t flash the Custom Recovery.
Beyazid said:
My Problem is that I can´t connect my device to the adb to reflash the Recovery.
Click to expand...
Click to collapse
You don't use adb to flash a custom recovery. You use fastboot. That's your first problem.
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Beyazid said:
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Click to expand...
Click to collapse
I see a couple problems here.
First one is use the newest version of TWRP. You can get that from my signature.
Second is Code_Blue may not be compatible with the ROM you are testing.
You don't need ADB at all for this, you need fastboot.
As I said. I just use adb to make sure that my device is found by and connected to the pc. I know that fastboot is used to flash everything but my Nexus 5 isn´t even shown. So how can I get my phone connected to flash the custom recovery?
And it seems like it is compatible since it worked the after the first installation and boot
FFS, XDA. I had just written a huge ass post on how to use fastboot properly, with the proper commands and ****, and you logged me out, making me lose all that. F U.
Beyazid said:
and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
Click to expand...
Click to collapse
This is the stock recovery.
You need to put your device in fastboot mode, REFLASH TWRP again with fastboot, then STRAIGHT FROM FASTBOOT select (with vol keys and Power) "Restart recovery". When you're in TWRP, wipe data/factory reset, reflash rom, gapps, REBOOT, PROFIT.
`fastboot devices` and `adb devices` are two commands to check if an active connection exists, between the host interface (on the PC, look at it as servers) and the device interface (look at it as clients). both commands will only return your device's SN IF drivers are correctly installed (speaking on a basic level, and about Windows). If you execute those commands, no SN comes up, then you need to fix drivers FIRST. Not even worth trying to do other commands.
`fastboot devices` only works here -> http://bazalabs.com/wp-content/uploads/2014/07/20140705_215603.jpg
`adb devices` works in TWRP/CWM (NOT in stock recovery) and in Android itself (needs USB Debugging active).
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Beyazid said:
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Click to expand...
Click to collapse
Try another ROM.
System.img .. boot.img.. comes with the ROM you flashed (well, not exactly, but both partitions do get written to), so no, they're not missing.
I gave it another try and fixed it.
I'll write it down so anybody who ever faces that problem can solve that, too.
Follow that guide (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) step by step and after a few minutes of flashing and a few minutes of booting you should get a clean and fresh Android Version on your device. It removes all the old files and installs the newest files.
And thanks guys for helping me out with that adb/fastboot mistake. Kudos to you
Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this >?
ilko83 said:
Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this >?
Click to expand...
Click to collapse
I answered this in the other place you posted but adding here as well:
ilko83 said:
Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this ****>?
Click to expand...
Click to collapse
TWRP 3.0.0-1 is for A 5.x and Earlier (Lollipop and earlier)
zarish said:
These are the versions I recommend (in order of current and prior versions that I have tested on an Original 2014 Shield Tablet):
NVIDIA 1.x to 3.x - Android 4.x to 5.x (KitKat to Lollipop) -- Untested by me but should match for K1 NVIDIA 0.0.0 - Android 5.1.1:
TWRP 3.0.0-1 lj50036 - http://forum.xda-developers.com/showpost.php?p=65249195&postcount=94
TWRP 2.8.7.1 romracer - http://forum.xda-developers.com/showpost.php?p=55446061&postcount=2
NVIDIA 4.0 - Android 6.0 (Marshmallow) -- Untested by me but should match for K1 NVIDIA 1.0 to 1.1 - Android 6.0:
TWRP 3.0.0-0 romracer - http://forum.xda-developers.com/showpost.php?p=55446061&postcount=2
TWRP Experimental Steel01 - http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
Click to expand...
Click to collapse
As for how to fix.
Hold power button until device turns off completely
release power button
Hold volume down button, while continuing to hold volume down, press power until device turns on and menu appears.
Once the fastboot menu appears, connect to the PC.
use fastboot to flash a recovery compatible with marshmallow (e.g. - fastboot flash recovery twrp-3.0.0-0-shieldtablet.img ) (NOTE: Use romracer's Marshmallow 3.0.0-0 here if on A6.0 or above)
select Reboot Recovery on the device just to prime it and go in once (this is what I do, you could just reboot if you like).
zarish said:
I answered this in the other place you posted but adding here as well:
TWRP 3.0.0-1 is for A 5.x and Earlier (Lollipop and earlier)
As for how to fix.
Hold power button until device turns off completely
release power button
Hold volume down button, while continuing to hold volume down, press power until device turns on and menu appears.
Once the fastboot menu appears, connect to the PC.
use fastboot to flash a recovery compatible with marshmallow (e.g. - fastboot flash recovery twrp-3.0.0-0-shieldtablet.img ) (NOTE: Use romracer's Marshmallow 3.0.0-0 here if on A6.0 or above)
select Reboot Recovery on the device just to prime it and go in once (this is what I do, you could just reboot if you like).
Click to expand...
Click to collapse
I tried that- it shows 'waiting for device' , im in fastboot menu on the device, and i gt the usb drivers instaled, and yes i tried different usb port. Is the usb drive different for W10>?
Have you tried selecting fastboot on the device (should pretty much reboot the bootloader screen and end up right back at the same menu?
It sounds like your drivers are installed wrong and/or you selected the wrong driver if the device is not showing in Windows.
If the above doesn't work, I would disconnect the device from the PC.
Open device manager.
Connect the device to the PC, and watch what the device gets recognized as.
Then forcibly update the driver and point it to the one from this package and select the fastboot one: http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201506.zip
zarish said:
Have you tried selecting fastboot on the device (should pretty much reboot the bootloader screen and end up right back at the same menu?
I tried that. It still shows 'waiting for device'
It sounds like your drivers are installed wrong and/or you selected the wrong driver if the device is not showing in Windows.
If the above doesn't work, I would disconnect the device from the PC.
Open device manager.
Connect the device to the PC, and watch what the device gets recognized as.
Then forcibly update the driver and point it to the one from this package and select the fastboot one: http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201506.zip
Click to expand...
Click to collapse
When I forcibly update the driver and point it to the one from this package it shows 'the folder you specified doesn't contain a compatible software driver for you device'.... The tablet boots to the rom and then goes to a bootloop , and i didn't have developer mode turnd on. Maybe that's y i cant connect to ADB -fastboot.
Any suggestions>?
I can't speak to Windows 10 as I refuse to use that OS.
I can say the driver package is right and should most certainly contain the fastboot driver for all version of the Shield Tablet.
You should not be seeing the NVIDIA logo if doing things right. It should turn on to the bootloader menu. If you see the NVIDIA logo, then start over as it didn't register you turning it on and holding the volume down at the same time. Generally I keep holding volume down until I see the bootloader menu.
The bootloader and fastboot mode have nothing to do with if you have enabled USB debugging or not as it is well before that level of OS.
Where is the link twrp 3.0.0.1 cheers
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?
turboperson123 said:
I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?
Click to expand...
Click to collapse
Could you link me to the method you used for root please?
Sent from my God Mode 8
Hi
I'm highly interested too. Could you share the method please?
Do you manage to install twrp?
Thanks!
Hello,
How do you do to unlock bootloader.I was able to download and patch with magisk the last ROM but I can't flash it !
Please would you tell us how you do that ?
Thanks
here is the link https://forum.xda-developers.com/ge...agisk-root-t3992477/post80692227#post80692227
Thank you !
go to settings and enable developer options, then go to developer options / enable usb debugging and enable oem unlock
then on pc if you have adb and fastboot installed then type adb reboot bootloader
then once the tablet is in fastboot type fastboot oem unlock-go to unlock the bootloader
TWRP 3.3.1-0 TB-X605F Lenovo Smart Tab M10
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Working fine from my side
Turbo, many Thanks!
It works perfectly ! ?
turboperson123 said:
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
Good job, @turboperson123 ! @Monpseud0 pointed me over here.
I've got some time this week & I'm going to start on a version that will handle encryption. You can find the device tree and code here. I've included a link to this thread.
I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.
stefankkl said:
I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.
Click to expand...
Click to collapse
Easiest thing to do is use LMSA. It's available on Lenovo's support page: https://pcsupport.lenovo.com/au/en/...r-list/component?name=Software and Utilities.
Still unable to re-flash stock ROM
Yahoo Mike said:
Easiest thing to do is use LMSA. It's available on Lenovo's support page:
Click to expand...
Click to collapse
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.
stefankkl said:
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.
Click to expand...
Click to collapse
Tough one! Try this. It will wipe your data partition, though.
If it will let you, power down the tablet for about 10mins. Then boot into TWRP. Go to "Wipe" and swipe for Data/Factory Reset. Reboot.
If the M10 still won't boot, in TWRP re-format Data (by typing 'yes' under Wipe->Format Data), and wipe cache and Dalvik Cache. I think dalvik is under Wipe->Advanced. Factory reset again. Reboot.
As an absolute last resort, you might try fixing permissions in TWRP under "Advanced". But I don't think that's going to do much, because you haven't booted the ROM successfully yet.
Hope one of these works for you. Let us know what worked for you. If nothing works, PM me and we'll try some other things.
Lenovo Logo THEN black screen -- DEAD
turboperson123 said:
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
For the record the device was already rooted with Magisk. I was just trying to do a TWRP backup but found /data mounting errors so tried following steps 6 & 7. At the moment the device refuses to boot up. I am unable to get back into Recovery Mode. The ONLY thing i can do is get into FASTBOOT mode and issue commands from CLI.
The following hardware key combos produce the same results -- tablet turns on to show the Lenovo logo, after a few seconds the screen goes black (the device appears to have turned off):
x Power key
x Power Key + Volume Down
x Power Key + Volume Up
x Power Key + Volume Up + Volume Down
** Release of keys is done once Lenovo logo appears
Any ideas?
UPDATE
I went ahead and performed: fastboot flash boot boot.img << the boot.img was the earlier patched magisk image i used to get the rooted working tablet.
After performing the above the tablet turned on and is now showing the Lenovo logo however it does nothing else --- it remains on the logo forever. I am able to get into TWRP recovery. I went ahead and wiped Dalvik, Cache, and Data. Rebooted to System but still it is stuck on the Lenovo Logo.
The device if fully charged.
crosis99 said:
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
Any ideas?
Click to expand...
Click to collapse
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
Yahoo Mike said:
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
Click to expand...
Click to collapse
Thanks for the response. Yes mine has the Snapdragon 450. I will investigate the LMSA. Been messing around all day but made no progress -- not even QPST is working out.