I'm at total idiot for doing this btw, but i'd love some help as to how to get out of this hole!
Due to the file size limitations of FAT32, and me needing to qucikly move some large ISO files, i decided to put them on my flyer. I thought i was formatting the external sd card to ex fat, but only realised when i got home that i actually formatted the internal memory!!! argh!
I comes up as 'your internal memory may be broken, please reformat it' but when i press the option to format nothing happens.
From recovery, i cant mount it, so again cant format it.
I'm guessing this is due to linux/android not being able to recognise these partitions
Any help would be much appreciated! I'm on a 16GB wifi flyer btw.
Thanks in advance
It sounds like you still have hboot and recovery, so you must have formatted the internal storage; have you tried running an RUU for your model? The proper RUU should format your device and restore the stock OS. Is that the US Best Buy 16GB WiFi only Flyer?
Yeah i've got full Hboot and recovery access, and the device works fine, save for the internal storage problem.
I did the format on my PC when i mounted the internal storage for access.
Its a european wifi flyer, and i got the RUU (RUU RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504. 30.089BU_3809.07.04.06_M_release_204727_signed)
Does running the RUU format the internal storage aswell then?
I'm guessing as i've S-OFFed using revolutionary, i'll need to follow this guide?
http://forum.xda-developers.com/showthread.php?t=1346200
Yes, you are are on the right track. If you want to keep the Revolutionary hboot, you could just run the RUU from Windows. It will write the stock system OS, and you'll keep s-off and Revolutionary. You'll just have to push the su files again to get root. You'll also have to flash the cwm recovery again with either the Revolutionary tool or manually.
If you want totally stock with s-on, then follow the instructions in the link you provided.
or.... you could just install busybox and format the partition from the command line using adb or do the same from recovery....you don't need to mount it to format it. If you wait an hour or so until I have my flyer in hand I'll give you the command you want.
Oh that would be fantastic!
Yeah I'm not back at home yet (will be in a few hours), so fixing it without running the ruu again would be the best solution imo!
Sent from my HTC Sensation Z710e using XDA App
globatron said:
or.... you could just install busybox and format the partition from the command line using adb or do the same from recovery....you don't need to mount it to format it. If you wait an hour or so until I have my flyer in hand I'll give you the command you want.
Click to expand...
Click to collapse
Oh, it just dawned on me that the OS is all there and working for the OP, and it is just the internal storage that needs to be formatted. Sorry, didn't read close enough. In CWM recovery, under "Mounts and Storage", choose "format /internal_sdcard". That should be all that is needed. Learning here myself, so I'm curious to see the adb way also.
jscott30 said:
Oh, it just dawned on me that the OS is all there and working for the OP, and it is just the internal storage that needs to be formatted. Sorry, didn't read close enough. In CWM recovery, under "Mounts and Storage", choose "format /internal_sdcard". That should be all that is needed. Learning here myself, so I'm curious to see the adb way also.
Click to expand...
Click to collapse
Yeah I tried that as soon as I realised the problem, but when I went to format the internal memory, it can't complete.
The returned commands seem to imply that it needs to mount it first, before it can be formatted. And it can't be mounted because android can't recognise exFat
Sent from my HTC Sensation Z710e using XDA App
If you have busybox installed and are booted it should be this:
Code:
mkfs.vfat /dev/block/mmcblk0p33
globatron said:
If you have busybox installed and are booted it should be this:
Code:
mkfs.vfat /dev/block/mmcblk0p33
Click to expand...
Click to collapse
I must confess, I've never used busybox before.
When I get back to my flyer, is it a simple case of installing busybox,
then using adb, run adb shell and then the above code line?
Sent from my HTC Sensation Z710e using XDA App
Hereisphilly said:
I must confess, I've never used busybox before.
When I get back to my flyer, is it a simple case of installing busybox,
then using adb, run adb shell and then the above code line?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
yes, as root.
Well i'm having some trouble installing Busybox.
I've downloaded it fro mthe market, and i run through the green install window, check the default path which is system/xbin, and then it says it cannot install as there is not enough space on the SD card or the SD card is mounted!
I'm guessing this is becaue it is looking for the internal memory, and it cannot find it
Any suggestions?
push the apk to /system/app with adb.
Right, i ran this code and this is what i got returned
C:\android-tools>adb push stericson.busybox.apk /system/app
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'stericson.busybox.apk' to '/system/app/stericson.busybox.apk': Read-only file system
seems like it is the same error i got when i tried to install it after downloading and installing the apk fro mthe market
The market download seemed to be a 2 stage process - i could download and install it fine, but once i ran the app from the drawer, it prompted a secondary install, which is where the previosu errors were generated...
ok, download the attached zip file and extract it:
Code:
adb push busybox /data/local/tmp
Code:
adb shell
$ su
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p33
globatron said:
ok, download the attached zip file and extract it:
Code:
adb push busybox /data/local/tmp
Code:
adb shell
$ su
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p33
Click to expand...
Click to collapse
That did it! Thanks so much!
I've just mounted it on my PC again, and the total size is showing an 8.68 GB drvie... i honestly cant remember how big the partiton was last time, but i'm using a 16GB flyer, so i would have thought it would be closer?
Either way, at least its usable again now!
Thanks again
Glad you were able to work this out. 8.68 GB is correct for that partition.
Sent from my SGH-I997 using Tapatalk
Hereisphilly said:
That did it! Thanks so much!
I've just mounted it on my PC again, and the total size is showing an 8.68 GB drvie... i honestly cant remember how big the partiton was last time, but i'm using a 16GB flyer, so i would have thought it would be closer?
Either way, at least its usable again now!
Thanks again
Click to expand...
Click to collapse
yep, as jscott said that would be right for a 16GB flyer.
Fantastic, thanks so much for helping!
I have this problem with my One X, found this topic in search.
But, when trying to mkfs.vfat /dev/block/mmcblk0p33 , im getting this error:
mkfs.vfat /dev/block/mmcblk0p33
mkfs.vfat: can't open '/dev/block/mmcblk0p33': No such file or directory
Pls help?
Phone is wiped, and recovery cannot mount both the external and internal SD card
Recoveries can be written to the 2GB system partition but when launched they cannot mount the SD cards which means no ROMs can be flashed.
Phone is in S-OFF, Relocked state, HBOOT ENG_1.90.2005
What recovery are u using?
Sent from my iced out HTC Ruby
Tried 3 clockworks and 1 TWRP, all have the same problem, any suggestions I can install those no problem!
Ah ha... 4ext is your answer. Dev section, look for my thread containing [RECOVERY] 4EXT by MadMaxx82
Sent from my iced out HTC Ruby
I need the .img file for 4EXT recovery or I cannot command fastboot via adb to install it. There is no .img file available for 4EXT on these forms. He charges about $3 for the program on Google Play so it would not be lying around here for anyone to have.
KillerMafia said:
I need the .img file for 4EXT recovery or I cannot command fastboot via adb to install it. There is no .img file available for 4EXT on these forms. He charges about $3 for the program on Google Play so it would not be lying around here for anyone to have.
Click to expand...
Click to collapse
I'll upload for ya... One sec
I have to do dropbox cuz idk how to direct upload from my phone to tapatalk.
HERE you go
It's in the zip
Sent from my iced out HTC Ruby
Thanks, I managed to juggle my way to getting a ROM to flash to the SD card by trail and error after 8 hours of being away!
Now I realized the Ti back-up folder on my computer is empty so must plunge back into the coma to get the old ROM back again and get Ti to run a batch, save it to my computer and start all over again!
I am running Nils P 5.6 Business ICS ROM with the GB fw (old fw) patch. I S-OFF'd earlier today and flashed the jb_hboot when it asked me if I wanted to flash it during the process. Now my SD card is completely absent from inside the ROM. I was reading in another thread that I need to do the SD card fix, but that is only if S-OFF wipes my SD CARD. However, if I boot into recovery, I can mount my SDcard to windows just fine. I can even flash something else from the sd card if i want to. I tried wiping my the ROM and reflashing it to start fresh to see if my SD card would show up and it's still missing. Any ideas?
Edit: to be clear when I S-OFF'd (not sure if this matters) I used the 3.14.605.5 JuoponutBear's tool running Nils 4.3 Business ICS Sense which had the 3.14.605.5 base and it only took my one try. I know the instructions said to be on a stock ROM...
Did you try to mount your SD card while in the ROM.
Yeah, it only mounts the internal storage.
Format it in the rom
con247 said:
Format it in the rom
Click to expand...
Click to collapse
How? When I go to Settings -> Storage under 'SD card' it says Total Space "Unavailable" and then directly under that it says 'Available' "Unavailable" and then the next 4 options are greyed out.
Put it in an adapter and see what your computer does with it. If you can format it there do so...then if you're phone doesn't recognize it you can rule out the physical sd card from possible issues.
Sent from my ADR6425LVW using xda app-developers app
ericsignals said:
Put it in an adapter and see what your computer does with it. If you can format it there do so...then if you're phone doesn't recognize it you can rule out the physical sd card from possible issues.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have and I've done that. I have a little microSD USB adapter and when I stick my SDcard in that it mounts to windows perfectly. To be clear, I had my spare SDcard in my phone when I ran the S-OFF tool but my normal SDcard was working in the ROM before I attempted S-OFF.
Edit: My spare SD did get picked up in my ROM as "Damaged" after S-OFF. I tried to format it inside the ROM and it said "Erasing SDCARD" but it didn't actually do anything. I couldn't mount it with my microSD usb adapter either. I booted into recovery and partitioned it inside Amon Ra and then was able to mount it using my microSD USB adapter but it doesn't show up in my ROM either.
Which hboot did you install
Sent from my ADR6425LVW using Tapatalk 2
Yeah i fixed it, i had the wrong hboot.
I am using TWRP 2.4 on my jewel, and for awhile it was working flawlessly. Ive only been running cm builds, and have been running decks cm10.1 for a few weeks now. Recently, when updating to the latest build, my TWRP stopped letting me mount the ext sd card, but still recognizes the internal storage. The ext sd is recognized once booted into cm so I can use file mgr to transfer zips to internal for flashing, but its just one extra step.
Any ideas on why TWRP isnt seeing ext sd? Possible fix?
Anything and everything is much appreciated! :good:
Edit:
Reflashing twrp had no effect
If I'm not mistaken you have to go into the advance settings and tell it to mount the external-sd.
#Root-Hack_Mod*Always=LTE
laie1472 said:
If I'm not mistaken you have to go into the advance settings and tell it to mount the external-sd.
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
This is true, it must be done in the 'mount' settings. But this is where twrp was not recognizing ext sd.
However,
By flashing using Goo manager twrp is acting normally again.
Sent using Tapatalk 2 via my HTC Evo LTE
**TAMPERED**
**UNLOCKED**
Zara_UL
S-ON
So i tried to root my desire 601 and accidentally killed my internal SD card and wiped off my rom inside . Now i have no OS and a dead internal SD card inside . I can't mount system/data/sdcard in recovery and almost everything else . I do have am 2gb external memory card though . I tried flashing Insertcoin ROM from my external SD card but whenever its installing halfway in Aroma , the phone will just turn black screen (shutdown or something) and then it will get stuck at HTC bootscreen .
I tried to use adb to mount the internal memory to my PC using some guide on xda forums but it won't work too .
Any help is appreciated . Thanks :thumbup:
Sent from my LG-E980 using XDA Free mobile app
isaacpeh said:
**TAMPERED**
**UNLOCKED**
Zara_UL
S-ON
So i tried to root my desire 601 and accidentally killed my internal SD card and wiped off my rom inside . Now i have no OS and a dead internal SD card inside . I can't mount system/data/sdcard in recovery and almost everything else . I do have am 2gb external memory card though . I tried flashing Insertcoin ROM from my external SD card but whenever its installing halfway in Aroma , the phone will just turn black screen (shutdown or something) and then it will get stuck at HTC bootscreen .
I tried to use adb to mount the internal memory to my PC using some guide on xda forums but it won't work too .
Any help is appreciated . Thanks :thumbup:
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
1. What is your hboot version?
2. What recovery did you flash?
You might have the wrong recovery, which causes the reboots during the flashing process. If you updated to kitkat via OTA, you should install TWRP recovery, which you can find in Desire 601 Original Android Development. Also, if you have an OTG cable, you can use a USB stick or HDD instead of an SD card.
patrik.KT said:
1. What is your hboot version?
2. What recovery did you flash?
You might have the wrong recovery, which causes the reboots during the flashing process. If you updated to kitkat via OTA, you should install TWRP recovery, which you can find in Desire 601 Original Android Development. Also, if you have an OTG cable, you can use a USB stick or HDD instead of an SD card.
Click to expand...
Click to collapse
Thanks for replying , I used this TWRP : http://teamw.in/project/twrp2/217
My HBOOT Version is 2.22.0000 (Shown on hboot screen)
and no , i do not have an OTG cable . >.>
isaacpeh said:
Thanks for replying , I used this TWRP : http://teamw.in/project/twrp2/217
My HBOOT Version is 2.22.0000 (Shown on hboot screen)
and no , i do not have an OTG cable . >.>
Click to expand...
Click to collapse
You have the new hboot with the new partition layout. You HAVE TO use this TWRP. Otherwise it will always do some weird stuff and mess up your phone. If you really can't find a working SD, then use adb to push the ROM zip file in your internal memory by typing this into your cmd/terminal:
Code:
adb push <file>.zip /sdcard/rom.zip
Replace <file> with the name of the ROM zip you downloaded.
Then in TWRP go to Install and select the rom.zip file from the list. It should work fine.
patrik.KT said:
1. What is your hboot version?
2. What recovery did you flash?
You might have the wrong recovery, which causes the reboots during the flashing process. If you updated to kitkat via OTA, you should install TWRP recovery, which you can find in Desire 601 Original Android Development. Also, if you have an OTG cable, you can use a USB stick or HDD instead of an SD card.
Click to expand...
Click to collapse
patrik.KT said:
You have the new hboot with the new partition layout. You HAVE TO use this TWRP. Otherwise it will always do some weird stuff and mess up your phone. If you really can't find a working SD, then use adb to push the ROM zip file in your internal memory by typing this into your cmd/terminal:
Code:
adb push <file>.zip /sdcard/rom.zip
Replace <file> with the name of the ROM zip you downloaded.
Then in TWRP go to Install and select the rom.zip file from the list. It should work fine.
Click to expand...
Click to collapse
Thanks . For once i thought my phone is gone . But it all came to flashing a wrong TWRP . You really saved me . phew. // Thannkks