Database Develop

[Guide] How to recover Soft-Brick from OTA & custom recovery

I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio

Terminal Command didn't work ...
AtriosM3 said:
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Click to expand...
Click to collapse
I repeated this three times, and no luck... any suggestions?

I did it a tad differently. I am running Windows 7.
First I downloaded these universal drivers so my phone was recognized under Device Manager, went to my adb directory with command prompt and typed the following:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
I just preferred using the keyboard, but your directions will work, too.

secure booting error
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??

eddie 2t said:
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
Click to expand...
Click to collapse
U had a custom recovery flashed correct? To me it sounds like your on stock recovery

bleedingthru said:
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
Click to expand...
Click to collapse
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.

eddie 2t said:
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
Click to expand...
Click to collapse
Ive never used cwm on this device only twrp so i dont know about that recovery

boot
I have philz touch and all my phone will do is boot to philz?

[HELP] Android not booting [URGENT]

It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.

Doppel u r right. follow doppel steps.

doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.

gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.

doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.

Asus MeMO Pad 7 unusable please help!

Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!

Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM

After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????

boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped

Root Lenovo Tab 10 TB-X103F

Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the .img file (if not in the same folder):
fastboot boot TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!

Stock recovery remains
RooterLeopold said:
Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the file:
TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Click to expand...
Click to collapse
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help

That's because the above only boots TWRP to root but does not install it. To install TWRP, when in booted with TWRP, you need to transfer the TWRP img to the tablet storage and then install it while in TWRP.

it is important to show the pathway to the file TWRP-3.0.2_TB-X103F-beta.img in the command line, like:
C:\Users\Public\Documents\My Videos\TWRP-3.0.2_TB-X103F-beta.img

Sorry for this newbie question.
Which part of the above rooting steps is rooting my tablet, what is TWRP doing and why do I need to install the SuperSU app?
During my first try I didn't boot the TWRP image rather I flashed it. But that didn't help at all.
After booting the TWRP image I was able to flash the SuperSU app.
The stock recovery is still in use.
Thanks in advance.

Read the steps carefully and follow the steps, it is a tested successfull strategy. To get deep knowlege about the background processes, please read the threads elsewhere in Web.

Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option

Entering Fastboot on Lenovo TB-X103F tablet
ShottaDopey said:
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Click to expand...
Click to collapse
Hi everyone. I just want to clarify something about this procedure There's a lot of people being confused on how to get into FASTBOOT on some things, and that's stopping them getting anywhere from the beginning.
The Lenovo TB-X103F tablet doesn't have a way of booting directly into FASTBOOT. Turning the tablet On while holding either volume key and the On button doesn't do it directly. . . . . Firstly, there's 3 buttons on the tablet, I call them VOL- VOL+ PWR (again, that's just to clarify things 100%)
here's what must be done (well it's this way on the 3 I have on my desk, so I assume all TB-X103F tablets are the same) . . . . .
1) Turn the tablet off completely.
2) Press & hold the VOL+ button (the middle of the 3 buttons).
3) Press & hold the PWR button, release the PWR button as soon as anything appears on screen - Keep holding VOL+ button.
4) After about 8 seconds the familiar green android lay down will appear. Then, your recovery menu will appear.
5) Release the VOL+ button anytime now.
6) Press either VOL button to select BOOTLOADER on the menu (Bootloader is the same as FASTBOOT on this menu, that's where the confusion lies for many users).
7) Got Bootloader selected? now press PWR and let the tablet reboot itself.
8) it will show the LENOVO logo, and appear to be stuck - it isn't It's in Fastboot mode.
9) Plug in your USB to PC cable, and it'll install appropriate drivers on the PC (hopefully eh?).
10) Once the drivers are installed, test it by getting a Command Prompt in your ADB/FASTBOOT folder on your PC . . . .
11) type the command FASTBOOT DEVICES It should show you that your device is connected, if it shows no devices then either it didn't install the drivers, or something
else is wrong (there's about 30 things that can have gone wrong here, too many to go through in this quick guide).
12) The tablet will stay in FASTBOOT/BOOTLOADER mode until you turn it off (or the battery goes flat lol). So stay calm, there's no rush
I've mentioned about there being no rush, because if you choose ADB connecting from the recovery menu, it disconnects automatically after about 5 minutes -
This is Important to know because it can disconnect while you're pushing/pulling files from the tablet, and cause really nasty problems. Bad design eh?
But we're in Fastboot mode, so nothing to worry about like that

Deleted

Successful root
It was hard, but I had finally had done it. I had figured it out it is easier just to go to the command prompt (I ran it under admin) and "cd C:/adb" (where you installed the adb fastboot software) while having the TWRP image file being placed there. I only wished that I had done it sooner. And for those who are new to the custom recovery it can be overwealming, but with patience and going through the files in the file explorer to find your main storage would lead you to the SuperSU file and successfully root your device.

I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.

So I did the "fastboot oem unlock-go" command and adb said ok but my tablet just went to a black screen and won't turn on now and I'm not sure why. I also heard the Windows USB disconnect sound when i did it.

Would this work with the TB-X104F running 8.1?

Since a few months my tablet is stuck with the 'password changed, wait....' message. I had hoped that I could overcome this with the steps mentioned here. But unfortunately not
I can't start it anymore, so I'm not sure if it is in developers mode or not. Also, plugging the device in my mac didn't let it download the drivers.
Too bad, because when it was working it was a great tablet, now it's just a expensive drawer filler

SynGamer said:
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
Click to expand...
Click to collapse
its the vol+ not - you need to press with the power button

Steridroid said:
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
Click to expand...
Click to collapse
so what exactly do i have to type at the command prompt to run twrp?,ive put the twrp img file in the same folder as the adb stuff.

3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
fastboot shows notting

lenovo seems to have killed these tablets from the old lady next doors experience.. no wifi, no adb, no fastboot, no qualcomm, just unknown device, which loads NOTHING, no drivers work!!!

nexus 6 stuck in booting

Hi I have a nexus 6 in custom ROM which recently get stuck in the booting process. the product is Shamu XT 1103 32GB P3A0. A custom rom was installed some time ago. When pressing power + volume down it goes into start menu which shows the device is unlocked. When pressing recovery mode it goes to TWRP 2.8.6
Is that a way to make the booting work without losing the precious personal data in the phone? I searched and found that there is a way to sideload the OTA images but it could also wipe all the personal data on the phone.
Appreciate your advice here. thanks you so much.
best regards,
Ron

When in twrp, you should be able to transfer files to your computer. I use adb pull for that.
Probably won't help you with "data", but at least you can get everything from "internal storage"

Thanks for your advice. That helps a lot!
Best regards,
Ro

Well, this is how I do it. There are other ways as well.
If you want more details for some of the steps, just ask.
1) boot to twrp
2) connect USB cable to PC
3) make sure you have adb installed on the PC
4) run "adb devices" on a command prompt on the PC and check that the phone shows up. If not, you need to install the driver for the phone.
5) make sure your command prompt is in the directory where you would like your files to be stored.
6) write "adb pull /sdcard/ ." This tells it to pull all files from the so-called sdcard (actually internal storage) to the current directory on the PC (the dot).

thank you so much!