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

"locked" internal SD (MMCBL0)

First of all, I'm experienced with android hacking/rooting/whatever but not so much with the galaxy tab.
So, I have this weird problem, whatever changes I make to a partition on the internal SD (including /data and /sdcard) doesnt actually gets applied to the internal SD. This include changes made by installing a app, using a file browser, using mass-storage, a shell command as root, reformat in recovery or even when using ODIN and just re-partitioning the whole thing.
Is this a known issue or does anyone have suggestions?
GSM P1000
edit: running XWJQ8 stock

Mount info:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 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=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preload vfat ro,nodev,noatime,nodiratime,fmask=0133,dmask=0022,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
Tried flashing CF-root and formatting from CWM. /data and /sdcard still have all their data after being formatted.
edit:
Tried fsck, umount, and more linux tools. nothings helps.

Im trying to get to the bottom of what sounds like exactly the same issue.
A few more details noted here:
*edit to note I cant post external links*
My current guess is that at some point it's locked "read only". I'd just be happy with a working 2.3 tab at the moment. Forget any other roms lol.
If you get any further with it, I'd appreciate any answers you come up with. Visa versa if I beat you to it.

The_Double said:
First of all, I'm experienced with android hacking/rooting/whatever but not so much with the galaxy tab.
So, I have this weird problem, whatever changes I make to a partition on the internal SD (including /data and /sdcard) doesnt actually gets applied to the internal SD. This include changes made by installing a app, using a file browser, using mass-storage, a shell command as root, reformat in recovery or even when using ODIN and just re-partitioning the whole thing.
Is this a known issue or does anyone have suggestions?
GSM P1000
edit: running XWJQ8 stock
Click to expand...
Click to collapse
This exactly is my problem. Has someone here know the problem?

Thats three of us then. I'v found another two instances of the isue on "the Galaxy tab fourm" and posted a long log of trying to resolve it.
Those were both some time ago however and havent resurfaced. There is another thread on XDA comlaining of the same issue but no solutions or fix.
I', still trying to get this sorted so if I do encounter a resolution beyond "pay someone to fix it" then I will let you know.
Unfortunately I cant even do that as without knowing the cause I doubt I'd get it back repaired....
Any assitance would be very welcome, Im using just the browser on a p1000 as nothing else works.... Depressing lol.

I have exactly the same issues with a SGT-P1000 GSM. Tried everything but after reboot all data, that i wiped is back on internal memory. i could wipe partition and create ext4 partition with mini tool partition wizard, but just a couple of moments later after creating the partition successfully the partition changes back to fat32 and all data is back on internal memory, neverending story ...

Further research and a new error message suggests that there might be a link to the "system UIDs Inconsistent" error which has been reported across the forums for a variety of devices.
Im looking into it...

Hello! I have the exactly same issue. Has anyone been able to solve this?
I've tried cyanogen rom, the official (stock) ROM and that does not seem to solve my problem.
I've also tried, with a custom kernel, access the ADB shell as root on recovery mode and anything that I do, doesn't "stick". FDisk, file creation, file removal. NOTHING.
I'm a week like this and this post is the only reference I've found that has the exactly same problem that I do.
Please, do tell your findings.
Thanks,
- Sergio Moura

Little dont understand this, but i try to help
Maybe you can try dd command, i never using this for my tab but i often using in my linux..
dd if=/dev/zero of=/dev/path/your/sdcard
dd is unix or linux tools for low level format and can be used to make image file too. Please backup your data first, i dont responsible for your lose..
Sent from my GT-P1000 using Tapatalk 2

Oh and last thing, let me know if the problem still appear
Sent from my GT-P1000 using Tapatalk 2

[Q] Read-Only internal storage?

Hi All,
(I've read tons of Threads here, but not yet found a solution).
My Galaxy Tab 10.1 is useless right now as it cannot write to internal storage.
Lots of apps crashing on use and doing a factory reset from the recovery menu does not help (Tablet is in exact same state aon reboot).
So, I've been using adb
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
Here's the mount information from shell
Code:
[email protected]:/mnt/asec $ mount
mount
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
debugfs /sys/kernel/debug debugfs rw,relatime 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
So, I've tried to mount manually from adb shell:
Code:
[email protected]:/ $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]:/ $
[email protected]:/ $ mount -o remount,rw -t rfs /dev/block/stl9 /system
mount -o remount,rw -t rfs /dev/block/stl9 /system
mount: Operation not permitted
But, I have no SU command:
Code:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I've got the su binary from downloading off this forum, but I cannot copy that up either (even to seemingly writable mount points)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push su /cache
failed to copy 'su' to '/cache/su': Permission denied
Any hints to what I can do now?
Ro

Hey, this forum is for Samsung Galaxy Tab 7.
Here is link for SGT 10.1
http://forum.xda-developers.com/forumdisplay.php?f=1050
But looks like your device is not yet rooted correctly.
The easiest thing is to find pre-rooted kernel and flash them via odin.

Thanks for the reply, yappoe!
I was following a guide I found linked on a forum to get the Tablet Restocked to factory settings.
However, when I try to write via Odin, I get an error message on the tablet in Red
Code:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Obviously a write error, presumably as the File system is in Read-Only mode ?
Ro

Yes, because permission is not set correctly. You need root access to do that.
I really don't know much about G-Tab 10.1, and I don't know what you were trying to do or are trying to do.
But if you are trying to go back to stock firmware, you can follow this steps.. it works on most Samsung. (Note: Unless you are moving from Honeycomb to ICS or vice versa, you do NOT need to re-partition).
you can download any official firmware at http://fus.nanzen.se/
1. Download Fus Check Downloader 2.1 and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
(or find your firmware at sammobile.com, you can skip step 2).
2. Extract the .zip file generated from decoding file to a folder and I got
tar.md 5 file.
3. Start Odin - put the .md5 to PDA and leave everything else as is.
4. Go to download mode on the G-tab
and click start. It takes about 6 to 7 minutes to do the flashing.
Can't guarentee if it would work, but good luck.
Once you get it work with STOCK, go to the Galaxy Tab 10.1 forum
and find the instruction there to ROOT
http://forum.xda-developers.com/forumdisplay.php?f=1050

Thanks yappoe,
That is a nice tool for firmware downloading.
Unfortunately I get the exact same error immediately when trying to write to the tablet via Odin.
Code:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
I think I have a sort of chicken and egg situation where I my problem is my drive is mounted in read-only mode and I cannot change it without rooting/executing su
Ro

same situation
I have the same situation but with my omnia 2.
suddenly, the internal storage became read-only.
I have tried flashing the ROM and unchecking "preserve device contents".
I have tried spyware, malware, antivirus from PC via usb mode.
I have tried low-level format.
I have tried hard reset.
I have tried below cabs.
MoviPatch_Eng_100416
nueStorageManager-v1.1
Til now, i still have the problem.
Im using a micro sd instead.
Im planning on opening my phone and removing the internal memory chip instead lol.

I did open up my tablet.
The internal memory is part of a single mainboard.
(I think its the same in almost every device)
Looking into getting a replacement mainboard now.

It's possible to use an external SD card as the internal storage. This won't fix the internal storage, but your Tab will work again. See this thread.

ableeker said:
It's possible to use an external SD card as the internal storage. This won't fix the internal storage, but your Tab will work again. See this thread.
Click to expand...
Click to collapse
Cheers for the pointer, but the Galaxy Tab 10.1 doesn't have a place for an SD / micro SD card addition.

Ah. But you asked in the wrong forum.
Go to Galaxy tab 10.1 forum
Sent from my GT-P1000 using xda app-developers app

Yeah i asked a technician if he could do it, he said he has no idea where that chip is in the mainboard
Sent from my GT-I8160 using Tapatalk 2

supersaiyanx said:
Yeah i asked a technician if he could do it, he said he has no idea where that chip is in the mainboard
Click to expand...
Click to collapse
The mainboard cannot have components removed/added ... You have to replace the entire mainboard.

[HOWTO] Dual-Boot P31xx

Dual-booting has always intrigued me. I dual-boot between Windows and Linux on one of my computers, dual-boot between stock firmware and RockBox on my Sansa Fuze v2, and I decided to find out how to dual-boot my Galaxy Tab 2 7.0". It took a couple days of work, but I have found one way to do so using the external SD card.
In the future, if I can work it out, I will provide a method for dual-booting using only internal storage. Update: I have successfully tested an internal dualboot setup. I will post details later.
Warning: While I am not aware of any specific way this could brick your device, stuff happens, so don't blame me. I've tested this and found no problems, but you may not be the same.
To use this method, you need a microSD card at least 8GB in size. If you use 8GB, though, you will have pretty limited space for storage, so a card 16GB or greater is advised.
Preparing SD Card
Repartition your microSD card using whatever program suits you. You need to shrink the first storage partition to make room for the new system partitions. The new partitions should take at least 5GB, so be sure to leave at least 5.25GB. You can always resize later if you need to.
After shrinking your storage partition, create four ext4 partitions in this order: system (min 800MB, recommended 1.25GB), cache (min 500MB, recommended 700MB), data (min 3GB, recommended 5GB), and EFS (min 21MB, recommended 32MB).
Verify your partitions on your tablet by inserting the SD card, booting into CWM, and running "parted /dev/mmcblk1" (no quotes) over ADB shell.
Flashing External ROM
Now you just need a ROM to flash. Most ROMs are not packaged to run from external SD card. You MUST either use a provided ROM or edit one yourself. I provide here a repackaged version of the 8/28 CM10 nightly which can flash to and run from your SD card. If you want to edit a ROM yourself, see the bottom of this post.
Boot into CWM and backup. You will need your backed up boot image if anything goes wrong.
Now flash your ROM. It will install to the external SD card on the appropriate partitions if you did everything right. Reboot: you should be in your new ROM.
You'll probably want a Google Apps package. See below for packages for external dualboot.
Using Your Dual-Boot Setup
Your internal and external ROMs do not share internal storage, due to the odd nature of the SD card fuse tool.Your external ROM has an "internal SD card" of its own. You may find a way to mount the internal /data/media to the external ROM's /sdcard. My new ROM conversion script will add attempt to mount the internal ROM's storage to /storage/intSdCard
The ROMs I provide here include a script in /system/bin called "bootinternal." Run this from a terminal emulator or adb to switch from the external ROM back to the internal one. I have attached a script called "bootexternal" to this post. Use it on your internal ROM to switch to the external one (remember to set the executable permission).
In order for the boot switching scripts to work, you must do some preparation. On your external ROM, place the internal ROM's boot.img in /sdcard/Boot/internal.img. For your internal ROM, place your external ROM's boot.img in /sdcard/Boot/external.img.
If you ever need/watch to switch ROMs manually, run the following commands in a terminal emulator or over ADB, replacing "boot.img" with the boot image of the ROM you are switching to:
Code:
cat boot.img > /dev/block/mmcblk0p5
reboot
Alternatively, you could switch boot images using Mobile Odin.
Update: I would skip using my prepackaged ROMs now, because I have uploaded a converter script that will actually do a better job. These will configure the "bootinternal" and "bootexternal" scripts automatically.
If you ever need to wipe your data, cache, or dalvik cache, see the next post for CWM zips.
Downloads
Roms for External SD Card:
CyanogenMod 10 Nightly (8/28/2012)
AOKP P3113 Stable
Note that these are probably unnecessary now, because I provide a script to convert ROMs automatically on Linux.
Google Apps Packages for External SD Card:
Gapps for Jelly Bean - Use for CM10, AOKP, etc
Gapps for Ice Cream Sandwich - Use for stock, RomsWell, etc
If I ever have time, I plan to upload SD card images which you can use to partition your external SD card automatically.
---
Repacking a ROM for Dual-boot from SD Card
Note: You no longer need to do this manually. I have uploaded a script which automates the conversion process. See the next post for download.
First, you need to extract and unpack the boot image. There are tools and scripts available for this, so find one.
Once the boot image is unpacked, you need to edit init.espresso.rc on the ramdisk. Find where the partitions are mounted and change the code to look like this (yours may look slightly different depending on the ROM, but just be sure to replace the default partition mounts with those of your SD card partitions):
Code:
#mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system wait rw
mount ext4 /dev/block/mmcblk1p2 /system wait rw
#mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ro remount
mount ext4 /dev/block/mmcblk1p2 /system ro remount
#mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data wait noatime nosuid nodev crypt discard,noauto_da_alloc
mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data2 wait noatime nosuid nodev crypt discard,noauto_da_alloc
mount ext4 /dev/block/mmcblk1p4 /data wait noatime nosuid nodev crypt discard,noauto_da_alloc
#mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache wait noatime nosuid nodev nomblk_io_submit,errors=panic
mount ext4 /dev/block/mmcblk1p3 /cache wait noatime nosuid nodev nomblk_io_submit,errors=panic
#mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs wait rw
mount ext4 /dev/block/mmcblk1p5 /efs wait rw
Repack the boot image and stick it back into the ROM. Then edit the updater-script, and change all references to the internal system partition (/dev/block/mmcblk0p9) to the external system partition (e.g. /dev/block/mmcblk1p2). If any other partitions are referenced, change them as well.
Optional: insert the "bootinternal" script in /system/bin and the a script to mount the internal storage in /system/etc/init.d.
Your ROM is ready to go. Flash and be happy!
Thanks to Johnsel for helping me edit the boot image and pointing me to sendust7's work on the Atrix, who I also thank for his precedent.

CWM Zips for Wiping External Partitions
If you ever need to wipe /data, /cache, or dalvik on your external dual-boot partitions, you can use these CWM zips to do so.
Update: Here is a script to automate the conversion of a ROM from standard to external dualboot.

interesting... gonna try this later...

Nice guide! Dual boot with stock and cm9/10/AOKP would be ideal.

Confirmed?
Sent from my GT-P3113 using Tapatalk 2

scottx . said:
Nice guide! Dual boot with stock and cm9/10/AOKP would be ideal.
Click to expand...
Click to collapse
Agreed! Is it possible to dual boot stock and AOKP?

IFLATLINEI said:
Agreed! Is it possible to dual boot stock and AOKP?
Click to expand...
Click to collapse
Absolutely. If you're running stock, just follow the instructions to partition your SD card, then flash the provided AOKP package and (I assume you would) the gapps package. You should boot right into to your external AOKP installation. Then just copy your stock boot image to /sdcard/Boot/internal.img and run "bootinternal" from a Terminal Emulator or adb shell to return to stock.

BRILLIANT !!!
A few suggestions:
Possible to have a GUI to switch ROM or even better to have it at boot (through kernel).
Script to Automate the process of converting any(P31xx) ROM to dual-boot. It will take away pressure off you.
Thanks !

thanks for the tutorial.

silentvisitor said:
BRILLIANT !!!
A few suggestions:
Possible to have a GUI to switch ROM or even better to have it at boot (through kernel).
Script to Automate the process of converting any(P31xx) ROM to dual-boot. It will take away pressure off you.
Thanks !
Click to expand...
Click to collapse
The GUI may or may not happen, since I, while familiar with partitions and scripting, don't know much about Java or Android development. I'll look into it, though. Having it run at boot through the kernel is beyond my skills. The closest I could do would be an init.d script.
As for a script to automate the conversion process, that seems doable. It only involves two files (init.espresso.rc in the boot image and the updater-script), so I could see that happening. I'll try to do something with that.

This is very interesting!
But I think it is better if we can install dual-boot like CM10 and some porting of Linux desktop version, chrome OS (love it) and other
I follow this thread!

Update: I've added a script that automatically converts ROMs to external dualboot format. I advise using this script instead of my provided ROMs. Just open a terminal in the script's directory and run:
Code:
./convert.sh rom-to-convert.zip
It will automatically edit the boot image and updater script, as well as configure the dualboot scripts. Go back to the second post to download.

Dual-boot question
Sorry for offtop, but your work is very interesting for me. I have GT-P6800 (Tab 7.7) and will try your method on my device. What can i do for it? May be change numeration of partitions inside a script? And firmware counter will be ticked or not? And my current firmware in internal memory will be untoched? Thanks for your work again!

partola1 said:
Sorry for offtop, but your work is very interesting for me. I have GT-P6800 (Tab 7.7) and will try your method on my device. What can i do for it? May be change numeration of partitions inside a script? And firmware counter will be ticked or not? And my current firmware in internal memory will be untoched? Thanks for your work again!
Click to expand...
Click to collapse
I would assume our tablets are very similar, so my method probably would work as is. To be sure, extract the updater-script from your rom and send it to me, along with the boot image, and I'll check it out. Your firmware counter will not be increased, and your current firmware should not be affected.

marry me. I just asked the dual boot question like a week ago lol

Macadamia Daze said:
I would assume our tablets are very similar, so my method probably would work as is. To be sure, extract the updater-script from your rom and send it to me, along with the boot image, and I'll check it out. Your firmware counter will not be increased, and your current firmware should not be affected.
Click to expand...
Click to collapse
Hi, this is my p680 kernel & updater-script:
http://hotfile.com/dl/170647189/80fec16/P6800.ZIP.html
Please, check it!
Also, i have some questions:
as you know, only 4 primary partition allowing on sdcard. I create 1 partition primary fat32 and 4 partitions logical ext4. Is this ok?
And how can i check partitions directly on tab? Terminal emulator not understand parted command, and from recovery TWRP 2.2.0.0 terminal asking me about from which directory execute commands. I try few directories, but parted/dev/mmcblk1 command show nothing to me.
Thank you for your adwise.

partola1 said:
Hi, this is my p680 kernel & updater-script:
http://hotfile.com/dl/170647189/80fec16/P6800.ZIP.html
Please, check it!
Click to expand...
Click to collapse
I'm having problems unpacking your boot image. Run the command "mount" on your tab and give me the output. I looked in your updater-script, though, and that seems compatible.
as you know, only 4 primary partition allowing on sdcard. I create 1 partition primary fat32 and 4 partitions logical ext4. Is this ok?
Click to expand...
Click to collapse
I was able to put 5 primary partitions on my SD card. Are you using an MBR partition table or GUID partition table? You need to use GUID to have 5 primary partitions. Anyway, I don't know if it will make a difference for logical partitions. Once you can check the partitions from your tab, I'll be able to tell you if it will work.
And how can i check partitions directly on tab? Terminal emulator not understand parted command, and from recovery TWRP 2.2.0.0 terminal asking me about from which directory execute commands. I try few directories, but parted/dev/mmcblk1 command show nothing to me.
Click to expand...
Click to collapse
Use CWM instead of TWRP.

Macadamia Daze said:
I'm having problems unpacking your boot image. Run the command "mount" on your tab and give me the output. I looked in your updater-script, though, and that seems compatible.
Click to expand...
Click to collapse
Hi, this is result of mount command:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:9 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
Also, i get CWM instead TWRP. But CWM have not possibility entering commands at all.
If you had troubles with unpacking CM10 kernel, any way for update it to booting from sd?
Thank you.

Why duplicate the efs partition?
And what makes it need such a big cache partition?
Sent from my GT-P1000

partola1 said:
Hi, this is result of mount command:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:9 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
Click to expand...
Click to collapse
Your essential partitions are the same, but are referenced differently. I will need to make a slight alteration to the conversion script.
Also, i get CWM instead TWRP. But CWM have not possibility entering commands at all.
Click to expand...
Click to collapse
You do it through ADB.
If you had troubles with unpacking CM10 kernel, any way for update it to booting from sd?
Click to expand...
Click to collapse
I'm looking into the boot image, but let's try something out. In the terminal emulator, run "cat /dev/block/mmcblk0p5 > /sdcard/full-boot.img" (without quotes). Then upload that file.
cdesai said:
Why duplicate the efs partition?
Click to expand...
Click to collapse
When I first ran across it, I wasn't sure what it was, so I added it for safety.
And what makes it need such a big cache partition?
Click to expand...
Click to collapse
I'm not sure. I decided to keep it close to the original cache partition size, which was 700+ MB. However, I've found in another setup that I can get by with half that. In my internal dual-boot setup, I have a 384MB cache partition.