Database Info

[Q] Pushing recovery to device using ADB... please help!

I have installed the 5.5.0.4 recovery from Koush via Rom Manager. That recovery is broken and it will not let me flash another recovery. I am asking someone who knows how to push a different custom recovery ( like rogue recovery http://bit.ly/ADptUO ) to the device using ADB, to write a step by step guide with all the commands and necessary files to do so. This will help many people who are stuck in the same situation that I have found myself in. Any help will be appreciated, thank you.

This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337

gee one said:
This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
It says to type the command though ADB while in CWR... my device does not show up in ADB while in recovery.

If you have access to the rom, you can copy your new recovery to the internal sdcard. You can also type the command in the rom with adb or terminal, but be careful since anything that you have in the staging partition will flash after you type the commands and then reboot. So, 1) copy rom to the internal sdcard, 2) reboot to recovery, 3) flash new recovery (nothing will happen yet) 4) reboot to the rom) 5) type commands in adb 6) reboot 7) then make a step by step guide for the next person.
sent from my cyanogen(mod) vision

No fastboot, TWRP flickering screen

Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...

djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??

Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.

I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.

As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?

You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.

_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found

djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot

Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.

djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.

where can i wirte this codes i dont know , can anyone help me??? i have same problem

i can not connect device also in adb mode pc didnt accept the drivers

y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices

berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag

y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240

now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work

y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window

sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file

berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??

y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.

[Q]Help! Soft-bricked NEXUS 5. Needs access to internal storage

Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
OR a method to solve the soft-brick situation without wipe the files on /sdcard would work as well.
Thank you.

lgm said:
Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
Click to expand...
Click to collapse
You have lost your internal data after using the factory images...

Primokorn said:
You have lost your internal data after using the factory images...
Click to expand...
Click to collapse
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?

lgm said:
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?
Click to expand...
Click to collapse
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..

fxdil said:
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..
Click to expand...
Click to collapse
I see. That solves the problem too, I guess. Thank you for clarifying.
:crying::crying:

[Q] Accidentally wiped the system and now my Nexus 5 says No OS installed!

I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:

Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk

First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app

Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.

raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk

All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache

raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/

thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk

raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.

1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk

rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?

Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy

thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.

rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option

Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.

thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk

rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were

thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect

Someone else posted twrp default path as /sdcard/downloads - try that.

teamwin flashing, device can't connect to fastboot

So I screwed up. I was trying to flash Zombi-Pop and I wasn't careful to say the least. I was trying to format /data to f2fs so I could do ROM2SD. When I did this I wasn't thinking straight and all my data got deleted (duh). I had already formatted my sdcard properly so all of my data on there got deleted as well (idiot!).
After booting the device it got stuck at crombi-kk as if it was trying to boot. It never did. I was then able to get into recovery by entering fastboot. I tried flashing Zombi-pop from my sdcard but it failed even though it said it was a success. I think the problem was after thinking about it was the fact that I also forgot to flash Kang's TWRP and was still using the one I flashed Crombi-kk. I have the log for successful installation of Zombi-pop, if anyone wants to take a look, which was suspiciously fast which made me think it wasn't successful at all.
Now when I boot, it flashes teamwin and nothing happens. I can still enter fastboot on the tablet, but I can't get a connection. It says key driver not found.. booting os. Android cardhu_user bootloader <1.00 e> released by "US_epad-10.6.14.10-20130801" A03. Starting Fastboot USB download protocol. RCK flashes and when I enter recovery this way teamwin continues to flash.
The idea is to get zombi-pop up and running. If that means I need to reflash crombi-kk and do it all over again I am willing. If anyone could help out, it would be greatly appreciated.
Thanks in advance.

What do you mean: You cannot get a fastboot connection? What is the return for 'fastboot devices'?
Reboot your PC, try a different USB port. You need to establish fastboot or your tablet is a brick.
And then slow down. From your description up there ^^ I cannot tell what you are doing wrong, but you are doing something screwy....
Flash the latest Kang TWRP then read the script when booting. It should tell you in which file format you have on data and cache.
Do not use the rom2sd partitioned microSD! That is a level of complexity you don't need right now.... Use a plain vanilla micoSD to flash ZOMBi-POP from.
Zombi is better flashed internally with data on f2fs anyway....
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
What do you mean: You cannot get a fastboot connection? What is the return for 'fastboot devices'?
Reboot your PC, try a different USB port. You need to establish fastboot or your tablet is a brick.
And then slow down. From your description up there ^^ I cannot tell what you are doing wrong, but you are doing something screwy....
Flash the latest Kang TWRP then read the script when booting. It should tell you in which file format you have on data and cache.
Do not use the rom2sd partitioned microSD! That is a level of complexity you don't need right now.... Use a plain vanilla micoSD to flash ZOMBi-POP from.
Zombi is better flashed internally with data on f2fs anyway....
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Hi! Thanks for the reply. When I type in 'fastboot devices' it returns 'no permissions fastboot'. Just to make sure, I type this in while my tablet has the three options for RCK, Android, and Wipe Data, correct? Otherwise there isn't another place I could do it unless I do it while teamwin is flashling. Also, I'm not sure if this matters but I'm running Ubuntu.

10 seconds on Google gave me this: http://ubuntuforums.org/showthread.php?t=1890861
You gotta learn how to do research before you do stuff...

berndblb said:
10 seconds on Google gave me this: http://ubuntuforums.org/showthread.php?t=1890861
You gotta learn how to do research before you do stuff...
Click to expand...
Click to collapse
Yea, you're right. I got caught up in browsing the xda forums that I forgot about Google! Well anyway your post reminded me about permissions and everything I did and I was able to figure out how to get my computer to recognize my device. Now when I type in fastboot devices it returns a serial number which is my device. Now when I try to flash TWRP it says "error: cannot load 'twrp_tf700t_kang_2.8.7.2.img': No such file or directory"
I've been searching forums (not just xda this time) and I can't seem to figure out where to put TWRP. I've followed these directions where they say put it with the fastboot.exe and binaries but, and I'm embarrassed to say, I don't know where that is. I've tried putting it with the SDK and that doesn't work. I've tried putting it my sdcard and putting it into my tablet and that doesn't work either. I'm not sure what to do next here. Should I try to find a way to move where fastboot is located on my computer and place twrp with it? Or is there something else going on here?
Thanks in advance.

Okum4 said:
Yea, you're right. I got caught up in browsing the xda forums that I forgot about Google! Well anyway your post reminded me about permissions and everything I did and I was able to figure out how to get my computer to recognize my device. Now when I type in fastboot devices it returns a serial number which is my device. Now when I try to flash TWRP it says "error: cannot load 'twrp_tf700t_kang_2.8.7.2.img': No such file or directory"
I've been searching forums (not just xda this time) and I can't seem to figure out where to put TWRP. I've followed these directions where they say put it with the fastboot.exe and binaries but, and I'm embarrassed to say, I don't know where that is. I've tried putting it with the SDK and that doesn't work. I've tried putting it my sdcard and putting it into my tablet and that doesn't work either. I'm not sure what to do next here. Should I try to find a way to move where fastboot is located on my computer and place twrp with it? Or is there something else going on here?
Thanks in advance.
Click to expand...
Click to collapse
If I remember correctly you should have the file in your Home directory.
The command is
Code:
fastboot flash recovery twrp_tf700t_kang_2.8.7.2.img

berndblb said:
If I remember correctly you should have the file in your Home directory.
The command is
Code:
fastboot flash recovery twrp_tf700t_kang_2.8.7.2.img
Click to expand...
Click to collapse
Awesome! It works! Thanks a bunch!
Now. I feel that the last thing I need to do is format /data since it cannot be mounted. I check my internal storage and it is at 0. I found this and I wanted to hear your thoughts on it.
I want to format the /data since it can't be mounted. First of all I want to make sure this is the step I need to take. Secondly, I am confused to whether I need to follow this command,
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Or this command.
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
I am assuming I should follow the first one first to see if that works, then try the second one, but I thought I might as well make sure from someone who is knowledgeable. I also realize this TWRP is probably newer than the one that was used in this thread, therefore there may be a different way in doing things.
Thanks again!

Or should I just go to Wipe, advanced wipe, check data, then press repair or change file system, then resize file system? It says there is 0MB for size. It says it is present, and that it is ext4.

Okum4 said:
Awesome! It works! Thanks a bunch!
Now. I feel that the last thing I need to do is format /data since it cannot be mounted. I check my internal storage and it is at 0. I found this and I wanted to here your thoughts on it.
I want to format the /data since it can't be mounted. First of all I want to make sure this is the step I need to take. Secondly, I am confused to whether I need to follow this command,
Or this command.
I am assuming I should follow the first one first to see if that works, then try the second one, but I thought I might as well make sure from someone who is knowledgeable. I also realize this TWRP is probably newer than the one that was used in this thread, therefore there may be a different way in doing things.
Thanks again!
Click to expand...
Click to collapse
Okum4 said:
Or should I just go to Wipe, advanced wipe, check data, then press repair or change file system, then resize file system? It says there is 0MB for size. It says it is present, and that it is ext4.
Click to expand...
Click to collapse
You need to format data and there are several ways to go about it.
Have you tried doing it in TWRP? Wipe > Format data > type yes
This will take upwards of an hour. Do NOT interrupt it. Make sure the battery has sufficient charge!
The mke2fs command is the same thing just issued from TWRP's build in terminal.
If both don't work try the last one from your computer, while in recovery, in an adb shell.
The killall -19 recovery just suspends the recovery so that it does not interfere with the formatting. I don't think that's your problem, but it won't hurt either.
Oh, and once you got it going your data partition will be ext4 again. If you want to run ZOMBi-POP use TWRP to convert data (and only data) to f2fs before you flash.
Good luck!

berndblb said:
You need to format data and there are several ways to go about it.
Have you tried doing it in TWRP? Wipe > Format data > type yes
This will take upwards of an hour. Do NOT interrupt it. Make sure the battery has sufficient charge!
The mke2fs command is the same thing just issued from TWRP's build in terminal.
If both don't work try the last one from your computer, while in recovery, in an adb shell.
The killall -19 recovery just suspends the recovery so that it does not interfere with the formatting. I don't think that's your problem, but it won't hurt either.
Oh, and once you got it going your data partition will be ext4 again. If you want to run ZOMBi-POP use TWRP to convert data (and only data) to f2fs before you flash.
Good luck!
Click to expand...
Click to collapse
Alright! It seemed to have worked! It's up and running and it's so snappy that it seems as if it's running in turbo mode! Many many thanks.
Also I don't close the thread right? That's a moderator?

Okum4 said:
Alright! It seemed to have worked! It's up and running and it's so snappy that it seems as if it's running in turbo mode! Many many thanks.
Also I don't close the thread right? That's a moderator?
Click to expand...
Click to collapse
Yep, you're all good. Glad to see you back in business!