Database Info

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

Need help restoring device, big problem, read inside

Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!

Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.

format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.

Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.

BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.

frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.

Did you issue the su command and get a popup for root access?

frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.

Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.

frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg

Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.

frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.

BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.

possible bricked Tf300t

Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !

_shakabra_ said:
Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !
Click to expand...
Click to collapse
Does it connect to fastboot using the universal naked drivers? If so, try this: http://forum.xda-developers.com/showthread.php?t=2425581

Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!

i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.

Help
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883

_shakabra_ said:
Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!
Click to expand...
Click to collapse
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
norm883 said:
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883
Click to expand...
Click to collapse
Have you seen this:
http://forum.xda-developers.com/showthread.php?t=2403674
---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------
olster said:
i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.
Click to expand...
Click to collapse
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?

Follow-up
cmendonc2 said:
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Have you seen this:
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?
Click to expand...
Click to collapse
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
That is very doable, just google it.

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.

Have done that, "partial brick"
Graiden05 said:
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.
Click to expand...
Click to collapse
That does work, but the problem is it does not stay. You need to do each time you want to use the table (shut down / reboot etc.). But it does allow me to boot into Android 4.3 but it is only a partial load since GAPPS was never loaded. I can push via ADB but nothing seems to stick! I believe all except /system has a no write or no permission granted. In the Android part (4.3) with Root Explorer I have granted the permissions? It appears that TWRP is both the bootloader (fastboot) and recovery. So any fastboot commands are futile, (waiting for device. I did see somewhere there is an administrative function for fastboot but have not been able to locate in all my readings. Except one persons mention of it to eliminate the waiting for device.
norm883

Partial Brick
If this helps anyone I found in a post:
I used it in Terminal Emulator while in Android 4.3 from (adb reload bootloader)
• # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
• # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
• # reboot
This now stops when I reboot or turn off the tablet from going directly to TWRP which basically allows me to do nothing, except pretend to do ADB then on a reboot nothing happened.
norm883

Terminal Emulator in Android 4.3
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883

norm883 said:
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883
Click to expand...
Click to collapse
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.

BAHHH Hummbug
Graiden05 said:
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.
Click to expand...
Click to collapse
All seem to be different say directory does not exists etc Crazy program.
Is it possible that from a corrupt there could be 2 layers here? Because in the recovery mode it tells me that there is not OS installed?
Yet I know I can boot to CM Android 4.3.
Wish I could think of a way to clear and start fresh, but without fastboot I am up the creek.
Thanks,
norm883

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.

How to create a TWRP flashable zip to wipe system partition and reboot to bootloader?

I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.

SnoopDoggyStyleDogg said:
I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.
Click to expand...
Click to collapse
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript

SnoopDoggyStyleDogg said:
I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.
Click to expand...
Click to collapse
You can wipe system using TWRP alone, no script needed. Just choose the "Wipe" option in TWRP, then choose "advanced wipes" then you will see a list of partitions, select the system partition then swipe the slider to perform the wipe and you're done.
The, go back to home screen in TWRP and choose the "Reboot" option, then choose to reboot bootloader, done.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You can wipe system using TWRP alone, no script needed. Just choose the "Wipe" option in TWRP, then choose "advanced wipes" then you will see a list of partitions, select the system partition then swipe the slider to perform the wipe and you're done.
The, go back to home screen in TWRP and choose the "Reboot" option, then choose to reboot bootloader, done.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I know all of this but the idea was to actually do this automatically which I've found the solution by using adb shell and mkfs.f2fs to format the system partition which works just great.

oneboiwithRosy said:
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript
Click to expand...
Click to collapse
Yep, I've found my solution by using adb shell and mkfs.f2fs to format the system then simply adb reboot to reboot to bootloader. So now my tool does 95% of the job automatically.

SnoopDoggyStyleDogg said:
I know all of this but the idea was to actually do this automatically which I've found the solution by using adb shell and mkfs.f2fs to format the system partition which works just great.
Click to expand...
Click to collapse
Why use adb when TWRP can do it directly from the device? The point of giving TWRP the ability to do this was so that adb is not necessary. Besides, you better get used to using TWRP instead of adb, the word is that Google will be dropping support for adb at some point, adb will be a thing of the past at that point.
You can run scripts using the terminal emulator that is built into TWRP also, instead of using adb to run it.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Why use adb when TWRP can do it directly from the device? The point of giving TWRP the ability to do this was so that adb is not necessary. Besides, you better get used to using TWRP instead of adb, the word is that Google will be dropping support for adb at some point, adb will be a thing of the past at that point.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Looks like I have to explain myself better.
I'm working on a tool for my specific device and the idea is for the user that uses the app to not warp around his head doing all of this that's where the automation comes in and this is the main reason I was looking for an way to do it.

SnoopDoggyStyleDogg said:
Looks like I have to explain myself better.
I'm working on a tool for my specific device and the idea is for the user that uses the app to not warp around his head doing all of this that's where the automation comes in and this is the main reason I was looking for an way to do it.
Click to expand...
Click to collapse
Again, using the terminal emulator that is built into TWRP or even a terminal emulator app while booted into system to run a script would achieve the same automation without the need for an external PC.
The point is, there is a more efficient way to do this from the device itself without an external device. Would that not be more simplified and more automated than having to include booting a PC, opening adb and connecting your device in order to run the script?
Besides, the title of your thread was for a using a TWRP flashable zip to do this, if that is the case, why use adb instead of TWRP as your title suggests?
Sent from my SM-S767VL using Tapatalk

oneboiwithRosy said:
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript
Click to expand...
Click to collapse
This method isn't working in my case! I tried to wipe system, also to change its file format it didn't change instead gave me an error that unable to mount system. Also, when I check partition in Orange fox it is nowhere! Anyone help me...I accidentally corrupted my system partition. I want to erase it but even adb failed to erase it.