Database Info

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

[Q] Please Help, Xoom eternal loop

I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?

Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?

No ideas? :crying:
I want to save the tablet if possible.

Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.

alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.

The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is named​Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​If you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​This will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot reboot​and you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.

alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is named​Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​If you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​This will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot reboot​and you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.

Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.

Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:

Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.

alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:

ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse

alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.

recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.

pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.

Is really no one out there that can help? :crying:

There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.

is it dead?

hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

[Q] No Fastboot Mode. Stuck in unfamiliar 'Cyanogen Recovery'

So my OnePlus One started dying when I would still have about 10% left. I thought it might be a bug or something with he CM12 nightlies so I wanted to revert back to stock. I transferred all of my media to my comp, got the 64gb zip from the "Revert back to 100% stock" thread, plugged my OnePlus One in, went into fastboot mode, made sure my comp recognized my phone ("fastboot devices") and clicked the "flash-all.bat" or whatever (not on MY comp right now, don't know the exact name) aaaaand some crazy stuff happened.
My phone started rebooting constantly, back into fastboot mode. This isn't how it worked with my Nexus 5 but the command window looked like it was doing what it was supposed to do. Then it got to sending the "system" and FAILED saying the file was too large. My phone rebooted and now it doesn't get past the first splash screen with the 1+ logo and "powered by android"
When I try to get into the bootloader nothing happens, but sometimes I get into the "Cyanogen Recovery" which I've never seen before. I wish I could take a screenshot and post it. It's options are:
Reboot system now
Apply Update
Wipe data/factory reset
wipe cache partition
wipe media
If I could get into fastboot mode I think I would be fine, but I can't.
When I go to "Apply update" I have the option to "apply from adb" and do the adb sideload thing, which I'm not very familiar with.
I think I might be in trouble, could anybody help me?

Is adb working while in recovery? It should. Try using the adb reboot bootloader command.
Transmitted via Bacon

Try pressing Power + Volume Up until your phone boots into fastboot mode and then run flash-all.bat again. If it is not working again, boot to fastboot mode and do all the steps by hand.

Stupid me, tried Auto Root CF for Pixel and now it is bootlooping badly, No ADB

Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?

boot-to-root is for Android O, you have to follow this guide

I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.

You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/

jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.

falsh factory image inside the bootloader, don't need to go to recovery.

Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.

Lenovo TB-X605F twrp?

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.