Originally Posted by Justin Buser

So, let me just try to get my head around this. You see a user complaining about CWM erroneously formatting his sd card with no confirmation during a factory reset. This is then followed by another somewhat ambiguous complaint that CWM is unable to properly format the sd-ext partition and despite the fact that you don't know what the actual error is, or have the slightest clue what is causing it, you still have the gall to repeatedly claim there is nothing to worry about and that it is "expected" behavior.

It may not be a big deal do you but not everyone can afford to blow $600 on another phone. Saying "Don't worry about it" is an irresponsible and frankly despicable response to give people, you didn't even BOTHER to ask what the f'ing error was.

PART of the problem has to do with the following fdisk output and fstab entries. You're just lucky the filesystem type was unknown in the recovery environment because if formatting the sd-ext partition DIDN'T fail during the wipe routine and actually deleted the boot sector it's pointing at you'd have a lot of PISSED off people wanting answers.

Disk /dev/block/mmcblk0: 15.7 GB, 15756951552 bytes
1 heads, 16 sectors/track, 1923456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device 
 Boot      Start         End      Blocks  Id 
System
/dev/block/mmcblk0p1           1           12801      102400  92 Unknown
/dev/block/mmcblk0p2   *     12801   12863         500  4d Unknown
/dev/block/mmcblk0p3           12863  13051        1500  51 Unknown
/dev/block/mmcblk0p4           13051  1923584    15284271+  5 Extended

~ # cat /etc/recovery.fstab
cat /etc/recovery.fstab
# mount point   fstype    device        [device2]
/boot           emmc      /dev/block/mmcblk0p8
/recovery       emmc      /dev/block/mmcblk0p22
/efs            ext4      /dev/block/mmcblk0p21
/data           ext4      /dev/block/mmcblk0p25
/system         ext4      /dev/block/mmcblk0p24
/cache          ext4      /dev/block/mmcblk0p26
/emmc           vfat      /dev/block/mmcblk0p28
/sdcard         vfat      /dev/block/mmcblk1p1 /dev/block/mmcblk0p28
/sd-ext         ext4      /dev/block/mmcblk0p2

Finally a word of advice to everyone else, never accept any answer from anyone that doesn't _actually_ answer you. Responses like:
'The "external sd card not found error" is not an actual error' and gibberish like: "that error is expected because you arent backing up the external sd-card, you would have to manually mount the external sd-card" are as useless as they sound, if your question isn't answered to your satisfaction don't just take someones word for it as you could easily end up with a bricked device.

LOL what a joke. I'm not even gona comment on that.

Sent from my SAMSUNG-SGH-I727 using XDA

Originally Posted by shaggyskunk

Check this out, it should answer your question.


http://android.stackexchange.com/que...ckup-of-sd-ext

Sent from Down The Rabbit Hole, using Tapatalk 2.

If you have any worries about this issue please read this. Justin Buser.... I'm looking at you.... Do some research before you make these ignorant accusations. That is all.

Sent from my SAMSUNG-SGH-I727 using XDA

Originally Posted by bluntman420

I agree about calming down but i have already hard bricked once using TWRP. Warranty covered it and i got a refurb(Which was actually brand new). But still OP could you please take a closer look at it and better explain what is going on? THANKS!

Twrp was because of something totally different

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Originally Posted by nrm5110

Twrp was because of something totally different

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Clearly i know it was a totally different issue.I was only trying to say that i have hard bricked once and don't want that too ever happen again.

Tell me you didn't just call me an idiot. I been on sk8's side this whole time his recovery has been incredible for us skyrocket users and any bugs that we report as long as they are legit and we do it in a proper fashion he has always looked into it I have nothing but respect for the dude plus every time people mentioned issues with team wafflehouse roms on his recovery he was always there making sure it wasn't on his end and was always willing to help us out sk8 sorry for the rant on your thread bro much love no homo lol

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

sk8er

Thanks for this. I'd much rather have control of my own recovery as opposed to letting ROM mangler handle it. I've had the phone four days and have used this recovery the whole time. Backup and restore are working fine. Getting access to mounting the external SD would be huge so thanks for looking into that.

As far as people having their SD card wiped I would have to guess their are hundreds of people using this and to have only one report it leads to user error. The SD-ext was also not backed up by recoveries on my last phone as well(SGS4G). Never an issue at all.

Originally Posted by nrm5110

Tell me you didn't just call me an idiot. I been on sk8's side this whole time his recovery has been incredible for us skyrocket users and any bugs that we report as long as they are legit and we do it in a proper fashion he has always looked into it I have nothing but respect for the dude plus every time people mentioned issues with team wafflehouse roms on his recovery he was always there making sure it wasn't on his end and was always willing to help us out sk8 sorry for the rant on your thread bro much love no homo lol

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Hey listen, the only reason i said what i said was because of the way you've been posting. If you are on Sk8's side than why the uncalled for RANT? Let's just drop it now cuz it aint getting us nowhere.

theres no reason to choose "sides". we are all on the same side......... making our phone better than samsung intended it to be :D

in terms of getting a way to choose whether you want to mount internal/external usb storage from recovery: my boss is on the Team DRH (viewsonic gtab dev team) and he is the creator of the touch recovery for the gtab and he said his team has been trying to find a way to be able to mount both and they are having trouble as well. just because the way recovery looks at the different storage locations its a bit tricky. its definitely on the to-do list though and hopefully will be able to be done someday *crosses fingers*

and again, if someone out there with a little more coding knowledge wants to give it a go the code is at https://github.com/sk8erwitskil

I had the backup working... Had the .hidenandroidprogress file in the correct location, mounted the sdcard prior to backing up, & made a successful backup... Now a few weeks later i try to backup again and hang at backing up data.
I've double & triple checked everything, but end up having to do a battery pull a half hour into the process to reboot the phone. After rebooting, i can locate the backup in the backup folder, but not sure if it's a complete, usable backup.
Any ideas?

Sent from my SAMSUNG-SGH-I727 using xda premium

Originally Posted by eachitandi

I had the backup working... Had the .hidenandroidprogress file in the correct location, mounted the sdcard prior to backing up, & made a successful backup... Now a few weeks later i try to backup again and hang at backing up data.
I've double & triple checked everything, but end up having to do a battery pull a half hour into the process to reboot the phone. After rebooting, i can locate the backup in the backup folder, but not sure if it's a complete, usable backup.
Any ideas?

Sent from my SAMSUNG-SGH-I727 using xda premium

if it doesnt complete then dont try to restore it as its not complete and will not work correctly. are you backing up to internal or external sdcard? do you have an external sdcard in your phone? if you do can you take it out and go into recovery, mount /sdcard and tell me if backing up to internal works for you?

also once you boot into recovery you can connect your phone to your computer through usb and run this command (if you have adb installed)

adb shell tail -f /tmp/recovery.log

then run a backup while that command is running and if it fails then copy everything that is thrown out of that command prompt and paste it somewhere and send it to me.