Database Develop

[Q] Galaxy s bricked?! partition error

Total SpaceA few weeks ago I have a problem with memory SD
when I install any version (JPU, JPI, or JPY) but when boot on the
Android Sytem recovery <3e> displayed the following message:
update,media, please wait
E:can't mount /dev/block/mmcblk0p1
(no sucho file or directory)
E: copy_dbdata/media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
After that flash with ODIN and speedmod-kernel-k12k-500hz
Then the phone starts NORMALLY, but it shows me two pop up:
Preparing internal SD, SD CARD IS DAMAGED, after that I go to:
SETTING/SD card and phone storage and shows me:
SD card and phone storage
Total Space
00
Available Space
00
Unmount SD card
Format SD card
Internal SD card
Total Space
Unavaible
Available Space
Unavaible
Format SD card
Format (erase) the SD Card
Internal phone Storage
Available space
00b
So I try to format both SD card, and nothing happens.
Connect the phone to pc, open SuperOneClick v1.91 and click ROOT
Width the phone rooting i go to adb :
c:\Program Files (x86)\Android\android-sdk\platform-tools\
1____I first put the phone in Debbuging mode,
2____Second fixed if the phone is attached:
adb devices >>>
List of devices attached
100012044e6e device
3____Go to adb shell> su > mount, and show me:
# mount
mount
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#
In this case try to find a route to the internal and external sd:
external : /dev/block/vold/179:9
internal: ????????????????
I add to this thread, images with different situations.
I read the following post but to no avail:
http://forum.cyanogenmod.com/topic/6...ernal-storage/
And millions of post that talk of SD brick
PLEASEEE HELLPPP MEEE!!!!!!!!!

What I personally would do first is give it a factory reset and then reflash. Have you tried this already?

bitmaster2000 said:
What I personally would do first is give it a factory reset and then reflash. Have you tried this already?
Click to expand...
Click to collapse
yes, multiple times!

Seens that I have the same problem as you.... can't find an solution yet! Did you find any? can you help me?

nope, nothing...

Try flashing the ezbase rom, follow the walkthrough instructions, it may or may not fix you
Sent from my GT-I9000 using XDA Premium App

Try a flash of a stock rom with a pit file but make sure all the files are there. For example my firmware from samfirmware.com was missing db_data because I think kies uses the existing one. So before I knew this I would flash the stock rom as is but get a mounting error for db_data because it was missing.
See if your stock rom has all the right files. Or try like a Darky rom for odin. That should have all the files.
If that doesn't work then you may be hooped as it is not a good sign when the internal sd reads 0. I got a new motherboard last time that happened to me.
G
Sent from my GT-I9000M using XDA Premium App

mmcblk0p1 is the primary partition that you are having an issue with.....if it says "no such file or directory", then your partition table is gone i believe. you must have an external sdcard in your phone for it to still boot up me thinks? try reflashing it a bunch of times like suggested above, and maybe you'll get lucky.
otherwise, give this a shot:
assuming your phone is rooted, go to recovery, and then create an adb shell with your computer.
type su
then type echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
this will make your phone visible in disk management through MMC. try right clicking on your phone, and initializing, activating and formating a partition.......i can't remember the names, but something along those lines.
also, by doing this, you will lose all your data.

I've tryed EZroom ... nothing... I've flashed to a stock rom... when I'm on stock rom it Appears "System UID Unstable" and it says to wipe data... I did it, my data keeps coming back to life (weird)... I've tryed darky rom, and clockwork mod... what i can do with it is mount the usb storage... then i go on it, delete all files... after reboot the phone... it's all back in there... format the internal sd card... then, files back there again... I really don't know the reason that the files keep coming back to life... It's probably the key to solve my problem...

If it's under warranty then flash with stock rom and pit (if stock rom has all the files some don't) and send it in. There is a method if you flash to 2.1 to get it to boot from the external sd - developed for the I9000M. Then you can wipe everything you can maybe and reflash. If no warranty it gives you a slightly useful phone until repair or replacement.
Sent from my GT-I9000M using XDA Premium App

I Tryied to send it for Samsung, but I bought it outside of my country (brazil). So My phone is i9000T and samsung Brazil just fix the i9000B, they say that they can't fix my phone because they have "incompatible software" ...
So, that is it? I own a rock now?

Well you could get it repaired privately. Or sell it on eBay - even the for parts ones seem to go for better than nothing amounts.
I think in Canada repairs to the main board were running around $125 when the majority of the I9000M units were failing.
Sent from my GT-I9000M using XDA Premium App

Or fedex it to a country it is covered in to samsung. Just say you are working out of country.
Sent from my GT-I9000M using XDA Premium App

And i can view, the partition, but i can,t format or partition.
And so, i think this problem caused because i check the Clear efs in odin, and dont have copy of my nv_data.bin,nv_data.back. And my new imei is:
004999010640000
Do you know how can restore my imei to te original?:
354781/04/656555/9
Thank you!

the nv_data files are going to be hard to fix. i tried changing the imei# between my gf's phone and mine, but didn't get it to work. the nv_data.bin file is signed i believe, so when you edit it, it messes up the signature and the phone won't accept it.
but your main issue is the partition. did you try what i suggested on the first page?

*yes, I tried to do what you told me, but I wasn't lucky. Do you know any programme to edit nv_data? I think this is the reason of my problem.

i thought i remember reading some other forums were working on editing those files, but that was a year ago. i don't know if they ever did. if they did, i guess you could get a donor nv_data file, and paste in your imei. search around, but even if you fix your nv_data file, it won't fix your mmcblk0p1 error.

when the mmcblk0p1 apears in the windows managament like unallocated, y try to re partition, but the windows show me: cyclic redundancy, and i cant continue. any idea to program to repair?

when you right click on it, are there any other options, aside from allocating?
if you can get it going with windows, i was going to suggest something like partition magic, but i usually gave up at this point, and sent my phone in for repair.

no, nothing happen, i try fixed whit low level format. When the program runs, shows me in HEX this line:
"HE OVER WRITING SEQUENCE WILL BE A SINGLE CHARACTER PATTER FOLLOWEB BY ITS COMPLEMENT
AND FINALLY AN OVERWRITING USING RANDOM CHARACTER PATTERN. tHEN VERIFICATION SHOULD TAKE PLACE"
I searched this paragraph in goolge, and the results were: SECURITY POLICES, DOD WIPE 2025, US DoD 5220.22-M.
The questions are: Are my memorys blocked for any reason,
how can revert this situation?!
what is the paragraph telling me?!

[DEV]RECOVERY: CLOCKWORK MOD TOUCH RECOVERY for XL[5.8.0.9}

PLEASE PLEASE READ ALL BEFORE FLASHING
In my attempt to keep things up to date for our Sensation XL I approached Paul O'Brien of Modaco to compile a working unofficial mod of the Clockwork Touch Recovery for our devices. The image which he provided to me IS NOT FULLY FUNCTIONAL!!!!!! I have posted it here as dev to hopefully get someone who knows about recovery to get it working!!!!!!!!!!
COME ON GUYS SOMEONE MUST BE ABLE TO DO THIS.
WHAT WORKS:
- SCrolling and selection works. Can scroll up and down and select options
WHAT DOESNT WORK:
- Cant wipe data, cache or dalvik. error with mounting data or cache partitions
- Cant choose zip from sdcard. error cant mount sdcard
Basically none of the core functions are working and hopefully someone here can get this WORKING!
To flash is simple: From Bootloader screen as with previous recovery type
***** fastboot flash recovery r2xxxxxxx *****
ensure recovery is in fastboot folder. after typing r2 just just hit tab and it will auto fill the filename of the recovery without you having to type it in.
To revert back to normal recovery is basically similar but flash R1 instead from bootlaoder screen.
THANKS FOR READING GUYS!
****AS usual the normal disclaimers apply. If this harms your device in anyway I will not be held responsible! Flash at your own risk**********
All credits for this current recovery to Paul O'Brien. Sahme it is not fully functional as he doesnt actually own the device anymore!

Just had a thought as I flashed this after flashing a custom rom but Chinese boot.img does mess with partitions. Some with stock rom please try and report by that I mean someone who hasn't flashed a custom rom previously. I may actually relock my bootloader to flash a stock ruu and try it.
Sent from my GT-N7000 using xda premium

Will be really beneficial to get this working. Helps everyone in the forum so any help and contribution is welcome
Let's start making forward motions for this handset!

Stickied for the time being

I used Racer_kitchen_v2 to extract the img and make it bit readable and compared the mount points of a working version (r1) with the touch recovery (r2) but unfortunately they seem to be identical.
r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
r2-recovery-clockwork-5.8.0.9-modaco-runnymede.img
they both seem to contain:
Code:
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p30 NULL ext3
/data ext4 /dev/block/mmcblk0p29 NULL ext3
/sdcard vfat /dev/block/mmcblk0p33 NULL
/system ext4 /dev/block/mmcblk0p25 NULL ext3
maybe I'm just looking for the wrong things at the wrong places. Well atleast I tried ^^.
I also used BeyondCompare to look for other differences but they're mostly unreadable.
If the chinese boot.img would mess with partitions etc then R1 wouldnt work either, I think..

hannemaster said:
I used Racer_kitchen_v2 to extract the img and make it bit readable and compared the mount points of a working version (r1) with the touch recovery (r2) but unfortunately they seem to be identical.
r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
r2-recovery-clockwork-5.8.0.9-modaco-runnymede.img
they both seem to contain:
Code:
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p30 NULL ext3
/data ext4 /dev/block/mmcblk0p29 NULL ext3
/sdcard vfat /dev/block/mmcblk0p33 NULL
/system ext4 /dev/block/mmcblk0p25 NULL ext3
maybe I'm just looking for the wrong things at the wrong places. Well atleast I tried ^^.
I also used BeyondCompare to look for other differences but they're mostly unreadable.
If the chinese boot.img would mess with partitions etc then R1 wouldnt work either, I think..
Click to expand...
Click to collapse
thanks for feedback much appreciated mate. Remember the recovery is flashed prior to Chinese boot.img hence when I suggested that. Once we have flashed the Chinese boot.img and flashed a custom rom it changes the partitions. That why I suggested someone with stock rom and not flash any custom rom to try it and report. I am testing Ben's new rom but soon I will relock bootloader flash stock rom and try it
Sent from my GT-N7000 using xda premium

nice hope we get this working...if we can use aroma installer...for roms..
with kind regards

will to donate £20 to get this working. not much i know but its a small incentive towards helping this forum and device forward

shingers5 said:
will to donate £20 to get this working. not much i know but its a small incentive towards helping this forum and device forward
Click to expand...
Click to collapse
I pledge £20 as well please to any Dev that gets this working!
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2 Beta-4

come on there must be someone out there.......................even if a new touch recovery is compiled my pledged amount still stands. WE NEED THIS! we are missing out on things especially AROMA installer. i tried this on Sensation and its definitely worth having!

for your information
I talked to madmaxx(developer of 4EXT touch recovery) asking him to support Sensation XL.
Hi,
Most probably yes.
But at the moment cannot give any eta.
BTW: Please upgrade to version 1.0.0.4 RC3
Have a nice day!
Click to expand...
Click to collapse
Thanks very much!
I'd indeed need someone to test
Will contact you once there's a little time I can spare on that. I think it shouldn't be too difficult to support the XL, since the hardware is not so different to other models already supported.
Click to expand...
Click to collapse

hannemaster said:
I talked to madmaxx(developer of 4EXT touch recovery) asking him to support Sensation XL.
Click to expand...
Click to collapse
ahhhh nice mate. thanks as you can see a few of us would donate to see this happen

Also want this.. also want to pay some euros but before.. want get s-off.. anyway.. @the moment i thibk we are on a good way.. and thx to you.. that you are working hard for this..to write to devs and answer all questions here..
Sent from my HTC Sensation XL with Beats Audio X315e using XDA

if that leads us to having our sxl aroma or miui....i m in with 25$ as well

Alex-V said:
Also want this.. also want to pay some euros but before.. want get s-off.. anyway.. @the moment i thibk we are on a good way.. and thx to you.. that you are working hard for this..to write to devs and answer all questions here..
Sent from my HTC Sensation XL with Beats Audio X315e using XDA
Click to expand...
Click to collapse
Its not a bother as things here was so dead it was only me and cappy lol and another guy nintendino. Its nice to see things picking up now and new devs trying to help our device
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

Here are some of the errors which stop it from working correctly. For people who know a bit more about this stuff than we do.
What we do know is that it has something to do with Partitions/Filesystems/mmcblocks.
failed to open /sys/class/android_usb/android0/state: No such file or directoryThat's right according to the list below it doesnt exist - also the recovery that is working doesn't call to this path...
Code:
/sys/class # ls
ls
adsp htc_portlist msm_vidc_enc scsi_generic
audlpa i2c-adapter msm_vidc_reg scsi_host
backlight input mtd sound
bdi lcd net spi_master
block leds oncrpc switch
bluetooth mem optical_sensors timed_output
diag misc power_supply tty
firmware mmc_host ppp usb_composite
gemini msm_camera rfkill usb_device
graphics msm_kgsl rtc video_output
gyro_sensors msm_mdp scsi_changer
htc_accessory msm_rotator scsi_device
htc_acoustic msm_vidc_dec scsi_disk
E: Unknown volume for path [/system]
E: Unknown volume for path [/cache]
E: Unknown volume for path [/data]
E: Unknown volume for path [/cache/recovery/log]
E: Unknown volume for path [/cache/recovery/last_log]
E: Unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/log
E:Can't mount /sdcard/
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
When android is loaded this is the partition information:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p30 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p31 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
this is the recovery.fstab of the touch recovery:
Code:
# mount point fstype device [device2] fstype2
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p30 NULL ext3
/data ext4 /dev/block/mmcblk0p29 NULL ext3
/sdcard vfat /dev/block/mmcblk0p33 NULL
/system cd senext4 /dev/block/mmcblk0p25 NULL ext3
unfortunately I can't run logcat when android is not booted. We need to know what commands are executed that return these errors.
for troubleshooting I first flashed "r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img" and booted in recovery. than I opened an adb shell and executed the mount command that lists the currently mounted partitions. after that I did the same for "r2-recovery-clockwork-5.8.0.9-modaco-runnymede.img" and notice there is a difference. as you can see the R1 mounts the cache partition for some reason and R2 doesnt. see below.
Code:
[B]R1 (non touch - working)[/B]
E:\SensationXL\files>adb shell
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
[COLOR="Red"]/dev/block/mmcblk0p30 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)[/COLOR]
[B]R1 (touch - not working)[/B]
E:\SensationXL\files>adb shell
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
@shingers5 - Have you tried relocking your device and going stock yet?
additional info gathered:
It seems while in recovery and using adb shell I can mount any partition except for the sdcard. It's seems kinda logic, to make a backup or restore you need the sdcard.
according to the partition table inside the recovery sdcard should be on address:
/dev/block/mmcblk0p33 /sdcard
when android is booted and I list mounted partitions it says:
/dev/block/vold/179:33 /mnt/sdcard
both addresses won't mount.
>> New info
using the following command I can mount the sdcard and access it(from adb shell, while phone is in touch recovery), allthough recovery keeps telling me it cant mount sdcard..
mount -t vfat /dev/block/mmcblk0p33 /sdcard -o rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022
So without the extra options (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022) sdcard won't mount.
I'm feeling i'm getting closer to the point to where I'll give up and just sit and wait for a pro. ah well atleast I gained some knowledge about all this ^^

Guess we can't get this going..maybe someone else can compile one from source and see if it works
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

here‘s a touch recovery for HBOOT ver 1.28 or higher
wipe data/cache,install from sdcard,backup and restore all work
orginal posted on: http://bbs.anzhi.com/forum.php?mod=redirect&goto=findpost&ptid=5117313&pid=21055370
View attachment recovery_for_1.28.img

alfchin said:
here‘s a touch recovery for HBOOT ver 1.28 or higher
wipe data/cache,install from sdcard,backup and restore all work
orginal posted on: http://bbs.anzhi.com/forum.php?mod=redirect&goto=findpost&ptid=5117313&pid=21055370
View attachment 1041596
Click to expand...
Click to collapse
I get an Error: Can't mount /sdcard/
whenever I try to do something that requires the sdcard.

hannemaster said:
I get an Error: Can't mount /sdcard/
whenever I try to do something that requires the sdcard.
Click to expand...
Click to collapse
What hboot version you using?
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2

[Q] Problem with disabling lagfix

So I tried to disable Voodoo lagfix (from Voodoo app) and now I'm stuck in the boot screen. Somehow disabling lagfix in CWM isn't working either. I accidentally had my phone corded up to my PC and had internal memory propably mounted while I booted the phone and it tried to convert the filesystem. Not sure if mounting caused the problem.
Being in this situation, is it safe to flash stock rom with .PIT file in Odin while having lagfix enabled? What (I think) I'm trying to ask is does re-partition convert my filesystem back to RFS? If it doesn't work that way, what should I try next? Already backed up all necessary data and ready to wipe. I'm currently on Darky's 10.1 RE and thought about moving on to newer roms, first through stock rom.
I have limited experience in flashing roms. I've read numerous threads and seen one case in which flashing with .PIT file in Odin helped but I wish not to hesitate with this.
Thanks for reading.
EDIT: Here's my /proc/mounts:
Code:
adb shell cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /datadata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
Everytime I plug it to charger, missus Voodoo robot says "convert /data partition".
EDIT 2: Flashed with .PIT + repartition in Odin and the system boots great! It all worked out!

[WANTED] File Recovery after Deletion

Good morning, lovely HTC ONE owners!
Yesterday, I manually deleted a folder from my HTC ONE containing an important file. I have tried finding a software or app to restore that folder, but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Is there any chance to get back my data? In the future, I will use the app 'Dumpster', which only throws files into a special trash bin where files can be restored if necessary...

SecUpwN said:
but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Click to expand...
Click to collapse
which filesystem?

We need to know which file you deleted

tryin said:
which filesystem?
Click to expand...
Click to collapse
Thanks for helping, guys. The HTC ONE doesn't have an SD card, thus only offering 32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.

matt95 said:
We need to know which file you deleted
Click to expand...
Click to collapse
A file inside a folder with the extension *.bck - it was a settings file created by another app. It is important to me because it contains phone numbers I have not written down. What to do?

I don't think you'll get it back man....

matt95 said:
I don't think you'll get it back man....
Click to expand...
Click to collapse
Darn. Maybe it's gods will. For other peeps reading this: Install DUMPSTER to avoid deletion without being able to recover files. This recycle bin will keep your deleted files for a set amount of time and delete them for good afterwards. If I had only known this app before, this wouldn't have happened.

SecUpwN said:
...32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
Click to expand...
Click to collapse
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...

tryin said:
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
Click to expand...
Click to collapse
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?

SecUpwN said:
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
Click to expand...
Click to collapse
:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/stericson.busybox.donate-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.gameloft.android.ANMP.GloftA8HM-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.eclipsim.gpstoolbox.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.eightyeightgames.tenmillion-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p35 /system ext4 ro,seclabel,noatime,nobarrier 0 0
/dev/block/mmcblk0p37 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc 0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier 0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p31 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

@BenPope, what's that supposed to be?

SecUpwN said:
@BenPope, what's that supposed to be?
Click to expand...
Click to collapse
That would be the list of filesystems, their mount points and parameters on my phone.
As you can see, it's not as simple as "a filesystem".

It is possible, try this guide: htc phone photo file recovery
hope this helps.

jackthomas251 said:
From phone it's much more complicated.
Click to expand...
Click to collapse
But not impossible?

Re: File Recovery after Deletion
I have also done this kind of mistake previously then my friend told me about Remo Android Recovery software and seriously it worked for me as a miracle. I got back all my accidentally deleted photos. You can give a try to this to recover your deleted folder. Hope you will get success.

This topic is like more than a month old, I guess there's nothing to rescue anymore. But thanks for the hints, everyone should install DUMPSTER beforehand.

Even worse.... I deleted storage/emulated/0 folder on my htc one
Ok. So check this ish..... I was tryna free up room on my htc one, so i went into file manager, was lookin for unnecessary stuff to delete, and thats when i notice.. Inside the emulated folder are 2 folders, one named "0" and one named "legacy" so after going back and forth one to the other... I realized that the same exact files and folders as the other, so my retarded asss deleted one thinking it was a whole duplicated folder. Ok, yeah, i messed that one up bad. How could i be so stupid? So i looked up some claims of some solutions, downloaded the pc software they swore would recover everything. Nada... Zip. Zero... What can i do? The htc one is no removable sd card or battery and my phone is not rooted.... Please get back at me on this... Im beginning to think,an htc csr or one of the smartest phone dudes on this forum will know how or what to do... :crying::crying::angel:

Oh yeah i forgot....
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something

datbitch said:
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
Click to expand...
Click to collapse
Sorry pal, no chance to recover anything. If you continued to use your phone after erasing all of that, it has been overwritten multiple times already. To make sure such thing does not happen again, install ES File Explorer and enable the RECYCLE BIN in the options - thus, you can recover deleted files easily. And for cleaning your device, always use SD Maid.

[Q] erased cache, need help with ....

Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.

godzilla61 said:
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
Click to expand...
Click to collapse
Reinstall twrp?
Sent from my lunar powered Inverted ViperONE using Tapatalk 2

That was the first thing I tried, no-joy!

godzilla61 said:
That was the first thing I tried, no-joy!
Click to expand...
Click to collapse
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP

Kraizk said:
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Click to expand...
Click to collapse
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').
Click to expand...
Click to collapse
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....

godzilla61 said:
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
Click to expand...
Click to collapse
rebuild your cache partition? or your cache filesystem? two totally different things.
if your disk is wrecked (partitions no longer valid) you're likely into RUU.
If your disk is fine (partitions are there, just no file system), TWRP should boot fine, it'll just piss and moan about /cache not being there. If it keeps restarting to the curtain (the TWRP graphic while booting) no big deal -- adb should still be up. If it does come up, you can 'wipe cache' and it'll rebuild the file system for you. Either that or use fastboot to format it.
Either way -- if you actually placed interesting stuff on /cache (why would you do that?), it's gone. The cache partition is 99% useless to users, so it would surprise me if you put stuff there.
Here's what I'd do:
1) Boot TWRP (get my 2.7.1.1 version, fastboot flash it, start it up);
2) plug the phone into usb:
3) adb shell
4) mount
copy/paste what that last command says and let's see what's really up. If TWRP won't boot, you have bigger problems than you lead us to believe.

Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p37 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p39 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto
_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered
0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime 0 0
/dev/block/mmcblk0p30 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=
ordered 0 0
/dev/block/mmcblk0p33 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow
_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse

godzilla61 said:
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
Click to expand...
Click to collapse
I have no idea why you think /cache is your problem:
"/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0"
It mounted fine.
As for flashing TWRP, you have to give fastboot an actual file:
"error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014"
The file is (assuming you didn't rename it) "openrecovery-m7wls-2.7.1.1-06-05-2014.img" -- there's an extension on the end.
If you did rename it, then you didn't place the file where you have fastboot. Either give the *full path* to the .img file, or move (or copy) it to the directory in which fastboot exists.

Thanks for taking the time to help! This gave me a reason to update my tool box for android. It's funny I never had to use a file ext. before when installing. It was that simple! So twrp is up and running again, I wonder why it was looping.....for another time perhaps. Thanks once again tdhite!!!