Database Info

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!
Click to expand...
Click to collapse
wheres the openrecoveryscript.txt??

Sorry. It's attached here
http://forum.xda-developers.com/showthread.php?t=2353828
I'll attach it to this post when I get home, I keep forgetting.
Sent from my buttered S3

[Q] Stuck in TWRP 2.1.1 with no Sideloader

Hi All,
I wanted to change the stock ROM on my tf700t so I downgraded to V10.6.1.14.8 from V10.6.1.14.10 installed unlocker and installed GooManager. Now when GooManager went to InstallOpenRecovery Script it got stuck on the 'download has started' screen. I looked for alternative options and found out that you could install via the ADT/SDK options using latest twrp.blob file. So I went to the twrp site and got latest blob file but rather stupidly they list the oldest at the top and the newest at the bottom?. So I ended up installing the 2.1.1 version using adb terminal via these instructions:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
Now I did this but I didn't put the Roms that I wanted into the default SD Card first and this version of TWRP doesn't support microSD or ADB Sideload. It now just keeps rebooting into TWRP and when I connect to PC in TWRP the PC just recognizes the driver as Transformer but none of the ASUS drivers work. I have no idea where to go from here, backup doesn't seem to work....?
I've been looking around but seems perhaps I've hit a unique issue.
Any help on how I can progress from here to get the latest version of TWRP or indeed any decent ROM - I was originally going for cm-10.2-20131112-NIGHTLY-tf700t.zip and googleapps.
Help would be most appreciated.
Thanks,
Kavster

also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide - cannot get boot recovery now just boots into TWRP...
android.sc/update-asus-transformer-pad-tf700t-to-cm-10-2-android-4-3-jelly-bean-rom
am I screwed..???

Kavster76 said:
also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide
Click to expand...
Click to collapse
This option causes the bootloader to force starting the recovery until the wipe is done. The problem: The ancient recovery that you flashed cannot access the eMMC due to bootloader incompatibilities.
So your only chance to unbrick now is to get adb shell access working, then try "adb reboot bootloader" and see if you can get back to the bootloader menu. Then choose Android and run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1

The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.

Kavster76 said:
The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.
Click to expand...
Click to collapse
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502

flumpster said:
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.? Can I also install new version of TWRP..??
Cheers...

Kavster76 said:
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.?
Click to expand...
Click to collapse
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974

_that said:
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?

Kavster76 said:
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?
Click to expand...
Click to collapse
I'd use fastboot to flash a proper version of TWRP now.

OK So clicking Android has taken me back to 4.2.1. Think I'll do some more reading before messing about with it again - Thanks for all your help - Much Appreciated !!!!!

Trying to get back to the latest TWRP I have renamed openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob I then put it in /sdcard root copied it over and ran the following:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12212+1 records in
12212+1 records out
6252648 bytes transferred in 3.658 secs (1709307 bytes/sec)
[email protected]:/ #
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.

Kavster76 said:
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.
Click to expand...
Click to collapse
Meaning he has to flash TWRP in fastboot not in adb shell - correct?
If yes - how is it different?

So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.605s]
writing 'recovery'...
OKAY [ 1.482s]
finished. total time: 4.087s
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Surely that should of worked..?

Kavster76 said:
So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.
Click to expand...
Click to collapse
OK Cheers (sorry wasn't sure what post you were on about), all sorted now phew...
Backing up system now and I'm ready to install latest CyanogenMod...

_that said:
run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1
Click to expand...
Click to collapse
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Thanks!

berndblb said:
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Click to expand...
Click to collapse
In theory, yes. However, when asking the bootloader for supported partitions (fastboot getvar all), "misc" is not among them, so I don't know if it really works.

Latest CyanogenMod all installed and looking good....
Thanks for all the help (I have added thanks) !!!
Kavster.

about qoute #8
hi friend.I have this problem too but my phone is samsung i9001.as you said,I downloaded the file and extracted it and then conected my phone to the pc and went to this path {start*accessories*command prompt} and entered the command "adb push bootit.ko" ,but responsed " adb is not recognised as an internal or external command, operable program or batch file" . I m too unhappy now,because my phone just boot to TWRP and like Kavster I have used TWRP 2.2.1 without adb sideload option.please help to rescue my phone.tanks dear friend

Is there a way to delete/uninstall an APK and its data from fastboot?

so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!

nextelbuddy said:
so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!
Click to expand...
Click to collapse
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.

Lethargy said:
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.
Click to expand...
Click to collapse
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.

nextelbuddy said:
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.
Click to expand...
Click to collapse
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk

rootSU said:
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
It could say "device busy" if data is already mounted. Does twrp have a "mounts and storage" menu like CWM? Where you can mount data? If so, check if it is mounted there (would typicall say "unmount data" if it was mounted, otherwise it would say "mount data" if it is unbmounted)

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID

nextelbuddy said:
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID
Click to expand...
Click to collapse
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.

rootSU said:
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.
Click to expand...
Click to collapse
Thanks so much for your help
I ended up taking the leap and performing a Factory reset from TWRP and when I logged back into the phone I saw all my media was still present Whew.
just for posterity I went ahead and tried your code in ADB to make sure the quotes worked and it did so thank you very much and i will keep those notes handy for next time.

[Q] Can my TF700T be fixed? SOLVED

Hello All,
This is my first post to the Forum. With that said I have been a long time follower of many of you. You have helped me learn a great deal and I have since unlocked, and flashed several ROMS to my TF700T. With that said I couldn’t find an answer to my dilemma and to be honest I don’t know how I got to where the current state of my tablet is.
As not to bore you all here is the short version. I was in the process of flashing the ZOMBi-POP-5.1.1_B2_omni_tf700t-KANG_signed ROM through TWRP v2.8.6.0. I made the mistake of picking up my sick toddler and putting here in my lap. While the tablet was running I was reading an article on the forum. My little princess hit something on the tablet and poof my tablet seems FUBAR!
I can get into TWRP if I flash it to my device via a command line on pc. If I try to reboot device it goes into a boot loop TWRP flashing every 5-10 seconds. I reflashed it and was able to get TWRP to load correctly. I am on bootloader version “US_epad-10.6.1.14.10-20130801”. I tried flashing a different Kernel (10.6.1.14.4-that2) in my forum reading to fix my issue. I can use some fastboot command to send files to my TF700T.
I get the following errors looking at the terminal window in TWRP
E:Unable to find partition size for ‘/misc’
E:Unable to find partition size for ‘/staging’
Erimary block device ‘/dev/block/mmcblk0p8’ for mount point ‘/data’ is not present!
E:Unable to mount ‘/data’
E:Unable to recreate /data/media folder.
E:Unable to find partition sixe for ‘/recovery’
E:Unable to find partition size for ‘/boot’
Updating partition details
E:Unable to mount ‘/system’
E:Unable to mount ‘/cache’
E:Unable to mount ‘/data’
… done
E:Unable to mount storage
E:Unable to mount /data/media during GUI startup.
E:Unable to mount ‘/cache’
Kernel does not have support for reading SELinux contexts.
E:Unable to mount ‘/cache’
E:Unable to set emmc bootloader message.
E:Unable to mount ‘cache’
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount ‘/data’
MTP enabled
Is my tablet now a paperweight or is there something I can do to resurrect it and try Zombi-POP? I hope I gave you enough information. If you need anything else let me know and I will see if I can get it.
Thank you in advance for your help.

You should have adb access in recovery. Run this command:
Code:
adb shell ls -l /dev/block/mmc*
and post the output.
I suspect you have to rebuild the partition table. Fortunately @_that provided a fastboot flashable blob here: http://forum.xda-developers.com/showpost.php?p=55166540&postcount=33
Read the whole thread though
Edit: And TWRP 2.8.6.0 may have a reboot bug. Use the official 2.8.4 or lj's Kang: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395

berndblb said:
You should have adb access in recovery. Run this command:
Code:
adb shell ls -l /dev/block/mmc*
and post the output.
I suspect you have to rebuild the partition table. Fortunately @_that provided a fastboot flashable blob here: http://forum.xda-developers.com/showpost.php?p=55166540&postcount=33
Read the whole thread though
Edit: And TWRP 2.8.6.0 may have a reboot bug. Use the official 2.8.4 or lj's Kang: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Click to expand...
Click to collapse
berndblb,
Thank you for the quick response. I ran the command as you said and here are my results:
C:\adb>adb shell ls -l /dev/block/mmc*
error: device not found
So I ran the fastboot command and found device
C:\adb>fastboot devices
015d2a50885c220f fastboot
I tried it as well in the terminal command through TWRP after getting the version you suggested and it said sh: adb: not found
any other suggestions?
I also ran the PT.blob file you linked to and it showed the status bar on the screen it loaded but no dice either. After I rebooted device and I get the same thing with TWRP v2.8.4. It just reboots screen every 5-10 seconds.

Ok, we need to backtrack a little. That command is supposed to be run from your computer through adb with the tablet booted to recovery.
You say that TWRP reboots every few seconds, but you also say that you used terminal in TWRP. Can you boot into TWRP??
If you can boot into it: What do you get with
Code:
adb devices
?
To check if the tablet can see your partitions, in terminal try
Code:
cat /proc/partitions

berndblb said:
Ok, we need to backtrack a little. That command is supposed to be run from your computer through adb with the tablet booted to recovery.
You say that TWRP reboots every few seconds, but you also say that you used terminal in TWRP. Can you boot into TWRP??
If you can boot into it: What do you get with
Code:
adb devices
?
To check if the tablet can see your partitions, in terminal try
Code:
cat /proc/partitions
Click to expand...
Click to collapse
I believe I may not be explaining it correctly. I booted my tablet up power + volume down key. Once I get to screen with 3 options in center and shows bootloader version. From here I plugged in my tablet to my pc and opened a command line, went to my adb folder and ran the code you suggested. Is this the correct steps or do I need to be in TWRP to run these commands?
I need to flash TWRP every time I reboot my tablet. If I do not it will cycle not find my OS and reboot into TWRP logo screen. This screen will just flash every 5-10 seconds. From here I can reboot with power + volume down get to the bootloader screen and then flash TWRP and reboot into it and it will work for that 1 time.
In TWRP terminal I get:
CODE
Adb devices
Sh: adb: not found
Code
Cat /proc/partitions
Cat can’t open /proc/partitions: No such file or directory
With TWRP on tablet screen I ran the codes you suggested via command line on PC with these results
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adb>cat /proc/partitions
'cat' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>

Ok we got to back up even more. You are confusing adb and terminal commands which are two different shoes.
You use adb to connect to your tablet from your PC when
a) the tablet is booted into Android or
b) the tablet is booted into recovery
You check the connection with 'adb devices'
Booted into recovery the return under "List of devices attached" should be something like: 1234567abcdsefg recovery
If you have an adb connection (and you need to have the correct drivers installed on your PC) you can run adb commands or connect to the tablet in an adb shell.
The command I posted earlier is a shell command. So the tablet needs to be in recovery to run that command.
Another way to manipulate your tablet is in Terminal, which is build into TWRP. The 'cat /proc/.." command is a terminal command.
And then there's fastboot which you use when the tablet is in the bootloader and fastboot mode.
Each tool is used for different things, so you cannot run fastboot commands in adb or terminal commands in adb and vice versa.
So before you do anything else let's try to get a clearer picture:
To flash the recovery you are using this command??
Code:
fastboot flash recovery <name_of_file>
Get into recovery.
Then EITHER connect to it in adb and run the adb shell command OR use the terminal in TWRP to run the cat / proc command.
Post the output.
Since it's easier to cut/paste from the cmd window on your PC or take a PrintScreen I think it's best if you use adb shell.

berndblb said:
Ok we got to back up even more. You are confusing adb and terminal commands which are two different shoes.
You use adb to connect to your tablet from your PC when
a) the tablet is booted into Android or
b) the tablet is booted into recovery
You check the connection with 'adb devices'
Booted into recovery the return under "List of devices attached" should be something like: 1234567abcdsefg recovery
If you have an adb connection (and you need to have the correct drivers installed on your PC) you can run adb commands or connect to the tablet in an adb shell.
The command I posted earlier is a shell command. So the tablet needs to be in recovery to run that command.
Another way to manipulate your tablet is in Terminal, which is build into TWRP. The 'cat /proc/.." command is a terminal command.
And then there's fastboot which you use when the tablet is in the bootloader and fastboot mode.
Each tool is used for different things, so you cannot run fastboot commands in adb or terminal commands in adb and vice versa.
So before you do anything else let's try to get a clearer picture:
To flash the recovery you are using this command??
Code:
fastboot flash recovery <name_of_file>
Get into recovery.
Then EITHER connect to it in adb and run the adb shell command OR use the terminal in TWRP to run the cat / proc command.
Post the output.
Since it's easier to cut/paste from the cmd window on your PC or take a PrintScreen I think it's best if you use adb shell.
Click to expand...
Click to collapse
Here is the results from using a command line on pc in recovery/adb.
C:\adb>adb devices
List of devices attached
0123456789ABCDEF recovery
C:\adb>cat /proc/partitions
'cat' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>
Yes that is the code I used to flash recovery to my tablet. I used the program by Snoop05 from here http://forum.xda-developers.com/showthread.php?t=2588979 to load ADB and Fastboot onto my pc.

You are still running a terminal command in adb. That won't work... Read my last post again.
Run the adb shell command instead.

berndblb said:
You are still running a terminal command in adb. That won't work... Read my last post again.
Run the adb shell command instead.
Click to expand...
Click to collapse
My fault I failed to read your post correctly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure if you can read the jpeg but the result is
adb shell ls -1 /dev/block/mmc*
ls: Unknown option '-1'. Aborting.

DELS71 said:
My fault I failed to read your post correctly
Click to expand...
Click to collapse
Indeed. The character after "-" should be the same as the one before "s". Not "1".

_that said:
Indeed. The character after "-" should be the same as the one before "s". Not "1".
Click to expand...
Click to collapse

DELS71 said:
View attachment 3351047
Click to expand...
Click to collapse
Reboot TWRP, then run this:
Code:
adb shell dmesg > dmesg.txt
Post the created file.

_that said:
Reboot TWRP, then run this:
Code:
adb shell dmesg > dmesg.txt
Post the created file.
Click to expand...
Click to collapse
View attachment dmesg.txt
I wasn't sure if this was proper way. I can post actual file in field if necessary.

DELS71 said:
View attachment 3351150
I wasn't sure if this was proper way. I can post actual file in field if necessary.
Click to expand...
Click to collapse
Code:
<6>[ 5.046834] mmcblk0: mmc0:0001 HYNIX 29.6 GiB
...
<6>[ 5.050342] mmcblk0: unknown partition table
Looks like your partition table got lost. Are you sure you flashed the partition table correctly using fastboot? http://forum.xda-developers.com/showpost.php?p=55166540&postcount=33

_that said:
Indeed. The character after "-" should be the same as the one before "s". Not "1".
Click to expand...
Click to collapse
Berndblb
THANK YOU THANK YOU THANK YOU!!! You save me with your skills. I was able to follow the steps and get back into TWRP after loading the PT.blob file without issue. I believe you were correct in going to 2.8.4. It did not refresh every few seconds. I loaded the files from my sd card and now have a working Zombi-POP tablet again. I really appreciate the help. If I can comment on your efficiency and help show me the link and I will.
Again I really appreciate the time and effort.

DELS71 said:
Berndblb
THANK YOU THANK YOU THANK YOU!!! You save me with your skills. I was able to follow the steps and get back into TWRP after loading the PT.blob file without issue. I believe you were correct in going to 2.8.4. It did not refresh every few seconds. I loaded the files from my sd card and now have a working Zombi-POP tablet again. I really appreciate the help. If I can comment on your efficiency and help show me the link and I will.
Again I really appreciate the time and effort.
Click to expand...
Click to collapse
Great to see you are up and running .... :good:
Can you add 'SOLVED' to the tread title ....
Thx Josh

For the record: the problem was that DELS71 flashed TWRP right after plashing the pt.blob - without rebooting in between. The rest of the conversation is here: http://forum.xda-developers.com/showpost.php?p=61217933&postcount=36

"write error: No space left on device" error fix

when im about to remove the modem files like this from adb menu
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs2
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs3
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefsc
im getting "write error: No space left on device" error.
how to fix this. or is there any other way to delete those files.

Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.

jwoegerbauer said:
Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.
Click to expand...
Click to collapse
ok, so is there a way to overwrite them? cos atm i cant with those commands

To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted

jwoegerbauer said:
Look inside here:
dd: No Space Left on Device | Beamtic
After running dd for a long time, it stops with an error saying no space is left on the device.
beamtic.com
Click to expand...
Click to collapse
would it also be fixed when i format the device and wipe all data?

Raw34 said:
would it also be fixed when i format the device and wipe all data?
Click to expand...
Click to collapse
Re-read my altered post above yours.

jwoegerbauer said:
To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted
Click to expand...
Click to collapse
can u give me an example for the command for adb menu?
i want to get rid of this file mi10orj.bin in the modem

What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK

jwoegerbauer said:
What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK
Click to expand...
Click to collapse
its called "minimal adb and fastboot tool".
yes the device is rooted. im gonna try this commands when im done with my working.
thx so much for your help and insight, so far.