[SHARE] Partition Map (S5830i) - Galaxy Ace S5830i General

From being used to a Linux PC with everything on a couple of partitions, trying to suss out how Android works has baffled me a bit what with having so many things hidden away in so many different places. I couldn't find a partition map for our phone so I made one by looking at /proc/partitions, using the mount command, analysing s5830i ODIN pit files and searching the internet. I realise that this isn't new information in that I'm pretty sure this stuff is known by some people but I still thought that this was worth putting out there.
I've listed the information in the following format:
#blocks <device file name> <partition name> (<flash file name> <Odin part>) <information>
Mount points are given where relevant. Partition name and flash file name are from the Odin pit file. To get the 'Odin part' I looked inside my “Full Firmware Backup To Odin Format”, which is a CWM script by Rafael.Baugis.
I've tried to be as accurate as possible and make it clear where I'm not 100% sure but please help me improve it if you can as I done this as a learning exercise in the first place!
Figures from /proc/partitions (also see the mount command):
#blocks name
31166976 mmcblk0 – sdcard (entire device)
29179904 mmcblk0p1 – sdcard partition 1 *
1945600 mmcblk0p2 - sdcard partition 2 *
513024 bml0/c – All bml partitions (figures add up to 513024)
256 bml1 – bcm_boot (BcmBoot.img – BOOT) – Bootloader
2048 bml2 – loke (sbl.bin - PDA) - Secondary bootloader
2048 bml3 – loke_bk (no flash file) - Presumably SBL backup
256 bml4 – systemdata (totoro.pit) – A copy of the Odin pit file by the looks of it
12800 bml5 – modem (BcmCP.img – PHONE) - baseband/modem
5120 bml6 – see stl6 **
5120 bml7 – boot (boot.img - PDA) - The kernel and ramdisk
5120 bml8 – boot_backup (no flash file) – Presumably boot.img backup
235520 bml9 – see stl9 **
40960 bml10 – see stl10 **
201984 bml11 – see stl11 **
256 bml12 – efs (?) (no flash file) – Not sure why this is called 'efs' as efs is well documented as being on bml15 and the number of blocks isn't even the same
256 bml13 – sysparm (sysparm_dep.img – BOOT) – part of the bootloader?
256 bml14 – umts_cal - (HEDGE_NVRAM8_RF_LE.bin – BOOT) – part of the bootloader?
1024 bml15 – cal (no flash file) - Not sure about the name but this is the EFS partition containing IMEI + network/region lock info
1280 stl6 – param_lfs (param.lfs – PDA) - mount point: /mnt/.lfs – SBL data including settings and images such as Samsung S5830i boot logo.
227840 stl9 – system (system.img - PDA) - mount point: /system – Operating System / ROM
36864 stl10 - cache (csc.rfs - CSC) - mount point: /cache – App/system cache storage but apparently CSC (region specific) data is also flashed here which seems odd but true!
194816 stl11 - userdata (userdata.img) - mount point: /data
- (dm-0 to dm-18) - Each app that is stored via SD card has its own virtual partition. I have 19 applications stored via traditional apps2sd, hence dm-0 to dm-18. Mount Point: /mnt/asec/<app's Java package name>
- (loop0 to loop18) – Loop devices. Each numbered loop is directly related to its dm counterpart, filesystem size is practically identical. I don't really understand loop devices that well so I can't say more than that!
* SD card partitions have other block device files, from which they are mounted via, at:
/dev/block/vold/179:1 - sdcard 1st partition – mount points: /mnt/sdcard and /mnt/secure/asec
/dev/block/vold/179:2 - sdcard 2nd partition – mount point: /data/sdext2
** This is from XDA user Darkshado in the following post:
“From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size”
http://forum.xda-developers.com/showpost.php?p=16963172&postcount=1
In actual fact bml and stl counterparts don't differ very much at all in size. From what I've read elsewhere the reason for the availability of stl interfaces on only some partitions may be related to the need for regular read-write access.
*** stl* and bml* interfaces can be accessed through device files such as /dev/stl*, dev/bml*, /dev/block/stl* and dev/block/bml*.
Of course just because they can be doesn't mean it's necessarily a good idea!

Related

[HW][OT] E:V:A's Discussion Thread

This is my own completely Off Topic Discussion thread.
A place where I will bring HW related discussions, that do not fit into
specific threads or discussions.
Please, do not post here with general questions or other junk that I have not initiated myself.
Also do not ask where to find files/programs mentioned in this thread, because if I have not linked to them, I don't know!
They will be removed. (Thanks for understanding.)
See you.
<< Better reserve for more dragons >>
Didn't see that anyone mentioned it and I'm not sure if the S4 modems are as well, but the initial container that the modems are in on the HTC used S3 chips is a fat16 format. I saw that with a simple hex editor showed it and I was able to see the modem file structure as well. I'll snag a few S4 modems later today and take a look. Couldn't unpack and repackaged though, which is probably the EFS formatting with it.
Off topic goes in off topic
Sorry it took so long
I had intended to do this at least a week ago, but had not the chance. Both the S3 HTC Radios and the S4 HTC Radios are fat 16 imgs.
As you see in the Rezound screenshot, in the first few lines of the HEX table in the bottom left mentions no volume label and a fat 16 label on the type. in addition when I use IMG viewers it shows the same with both the MDM9K image and the main IMG. This should theoretically enable us to possibly use amss imgs or other parts of the radios with other devices or even cross the modem over to other Samsung devices with the same modem chips.
In addition as per the Ville screenshot, this is the One S modem for one of the European basebands. Again the HEX shows Fat 16 as the file type, but the file structure and amount of files are much more plentiful. If this can become of any use, great. If not, oh well... but it is good food for thought either way.
On other notes, I did try to copy files from the LTE baseband (MDM9k) from the Vivid and move them to the MDM9k IMG for the rezound, but the IMG bloated. I haven't had enough time to try and mount the images in my Ubuntu environment, but doing it in Winblows caused the IMG to bloat up too much and caused radio issues and IMEI unknown blanks.
Happy perusing and happy hunting!
Very nice, but I doubt you'll be able to mix modem files (between different devices) unless you're absolutely sure that the device modem and AP HW is the same. Apparently from another recent conversation, it seem that HTC and Qualcomm are both moving to unified source code for their devices. So it can still be true that many of those files are the same across devices.
Could you write a few lines on how you go about this extraction and do it for the HTC One X (LTE)?
Also don't forget that US HTC One X (or S, or whatever) is not the same hardware and the European one!
On second thought, I think this is what you got..right?
Pretty much. Seems like another situation where I should have spoke up when I first saw it with Qualcomm S3 modems in May. On moving files though, I was planning to stay in family. S3 w/ S3 ect.
^^ BTW. Could you tell if there are any structural differences (content wise) between files of same prefix, but sequential postfix? What is strange is that they are all very different sizes, which indicate they probably have very different content...
If it was just one solid piece of firmware, it would just have been chopped up into equal sized pieces...
I'll look closer on that. I do remember that most of the sequential pieces were the same size minus either the first or the last, holding with your theory.
Maybe not the right place, but have you looked at the pit files?
COM_TAR2MSM8960
MODEM non-tlos.bin
sbl1.mbm
sbl2.mbm
sbl3.mbm
aboot.mbm
rpm.mbm
BOOT boot.img
TZ
PAD
PARAM
EFS efs.img (ext4)
MODEMST1 nvrebuild1.bin
MODEMST2 nvrebuild2.bin
system.img (ext4)
userdata.img (ext4)
persist.img (ext4)
cache.img (ext4)
recovery.img (ext4)
FOTA
BACKUP
FSG
SSD
GROW
PGPT pgpt.img
PIT MSM8960.pit
MD5 md5.img
SGPT sgpt.img
I know it is not really new, but I hadn't seen the img names.
The ones I took screenshots of were for 3rd and 4th Gen Snapdragon processors, radio.imgs for HTC devices. The Samsung pit files may give good cross references though. I'll re-unbox my Amaze this evening and check the mounts to see any information on the single file broken into pieces theory.
"eMMC Partition tools usage for msm7x30/msm8x60"
(A repost from Anyclub...)
In the eMMC boot, there are some changes in eMMC partitioning.
Code:
[SIZE=2]partition.xml - Everything begins with this file, which describes the number of
partitions desired, and how many sectors each one should be.
PartitioningTool.py - translates partition.xml into binary partitions
msp.exe - writes binary partitions to SD/eMMC cards using card reader
mjsdload.cmm - writes binary partitions to SD/eMMC cards using Trace32
msp.py - writes binary partitions to a single image file
QPST - writes binary partitions to SD/eMMC cards on Target
[/SIZE]
Helper /Debug Tools:
Code:
[SIZE=2]parseBinaryPartitionFile.pl - Decodes MBR partition tables. Run:
"Perl parseBinaryPartitionFile.pl partition.bin"
to generate the partition information
parseGPT.pl - Decodes GPT partition tables
[/SIZE]
partition.xml
These are the property entries that can be added in new partiton.xml to specify the configuration.
Code:
[SIZE=2]<parser_instructions>
WRITE_PROTECT_BOUNDARY_IN_KB = 0
GROW_LAST_PARTITION_TO_FILL_DISK = false
ALIGN_ALL_LOGICAL_PARTITIONS_TO_WP_BOUNDARY = false
</parser_instructions>[/SIZE]
WRITE_PROTECT_BOUNDARY_IN_KB: Typical boundaries are 64MB, i.e. 65536 KB. This
means that a 256MB eMMC card has 4 write protect boundaries. Any or all of
them can be marked as read-only. Different vendors allow for different sized
boundaries.
GROW_LAST_PARTITION_TO_FILL_DISK: In partition.xml the size of each partition
is specified. If this field is TRUE, then the last partition size is ignored
and set to 0. Then during patching this size is updated such that the last
partition extends to use all remaining space.
ALIGN_ALL_LOGICAL_PARTITIONS_TO_WP_BOUNDARY: To allow total flexibility, it
could be that a partition that is currently writeable might need to be marked
as read-only. This can only happen *if* that partition begins on a write
protect boundary (i.e. 64MB). Thus if this field is TRUE, then all logical
partitions are positioned such that they begin on a write protect boundary.
PartitioningTool.py
Is a new tool used to generate the the partition.xml
When run, it will output following 5 files:
1. emmc_lock_regions.xml
This hold the sector ranges that need to be marked as read-only by the
operating system (this is from readonly="true" in partition.xml) i.e. modem
code and boot images are typically on read-only partitions Typical
Write-Protect boundary is 64MB = 131072 sectors = 0x20000 sectors. The file
below is protecting the very first 64MB region of the card,
Boundary #0
Starting at sector 0
Ending at sector 131071 (for a total of 131072 sectors)
Code:
[SIZE=2]<?xml version="1.0" ?>
<protect>
<!-- NOTE: This is an ** Autogenerated file ** -->
<!-- NOTE: Sector size is 512bytes, WRITE_PROTECT_BOUNDARY_IN_KB=0, WRITE_PROTECT_BOUNDARY_IN_SECTORS=0 -->
<!-- NOTE: "num_sectors" in HEX "start_sector" in HEX, i.e. 10 really equals 16 !! -->
<program boundary_num="0" num_boundaries_covered="1"
num_sectors="20000" num_sectors_dec="131072" physical_partition_number="0"
start_sector="0" start_sector_dec="0"/>
<information WRITE_PROTECT_BOUNDARY_IN_KB="0"/>
</protect>
[/SIZE]
2. partition0.bin
This holds the partition tables, i.e. MBR followed by all EBRs. This is the
partition table in binary format. It is copied over to the storage device in a
1 to 1 manner. I.e. how it looks in partition0.bin is exactly how the
partition table will look on the storage device. partition0.bin is a "generic"
file meant to fit on *any* size SD/eMMC card, as a result, there are 0's that
need to be patched,such as EXT partition and last partition size.
3. patch0.xml
Contain the patching instructions to tailor each partition table
"partition0.bin" to a specific SD/eMMC card. I.e. the partition0.bin
partition tables can be applied to any size storage device As a result,
there are empty values (zeros) in the partition tables that must be filled
in with a specific cards sector size
There are two ways to apply this patch:
a) (patch before) When you patch the "zeros" in the partition tables held in the file partition0.bin, and then write it to the card
b) (patch after) When you write partition0.bin to the card (which still has "zeros" in it), and then patch the cards partition tables directly
4. rawprogram0.xml
precise sector details of all partitions and what files (if any) need to
be placed there. In addition to writing partition tables onto a device,
often times it is desired to write one or more files into the partition
area as well, The File has partition name (i.e. label), where it begins
(start_sector) and how big it is (num_partition_sectors). It also
describes what file(s) to write to this partition, as well as any
offsets.
Example:
Code:
[SIZE=2]<program file_sector_offset="0" filename="partition0.bin" label="MBR"
num_partition_sectors="1" physical_partition_number="0"
size_in_KB="0.5" start_sector="0"/>
<program file_sector_offset="1" filename="partition0.bin " label="EXT"
num_partition_sectors="2" physical_partition_number="0"
size_in_KB="1.0" start_sector="779"/>
[/SIZE]
The 1st line describes taking the 1st sector from partition0.bin, and writing it to sector 0 of the card.
The 2nd line describes taking the 2nd and 3rd sector from partition0.bin and writing it to sector 779 of the card.
I.e. file_sector_offset = 2 and num_partition_sectors=2
5. loadpt.cmm
This is used by the mjsdload.cmm to flash the image.
msp.exe
This is used to apply the patches
This program will program a memory card (SD/eMMC) attached to the PC as USB mass storage device
Use -d to detect the path of the memory card if you are unsure what to do first
Commands list:
Code:
[SIZE=2]-h (Print this help message) Ex. msp -h
-d (Detect which storage device ID is active) Ex. msp -d
-p (Print partition information) Ex. msp -p /dev/sdb
-pp (Print partition information - DETAILED) Ex. msp -pp /dev/sdb
-x (Write files as outlined in rawprogram.xml) Ex. msp -x rawprogram.xml /dev/sdb
-xx (Write files as outlined in rawprogram.xml - DETAILED) Ex. msp -xx rawprogram.xml /dev/sdb
-s (Write SINGLE IMAGE "singleimage.bin" as outlined in rawprogram.xml) Ex. msp -s rawprogram.xml 8192
-v (Verify file written correctly as outlined in rawprogram.xml) Ex. msp -v rawprogram.xml boot.img /dev/sdb
-f (Program single file as outlined in rawprogram.xml) Ex. msp -f rawprogram.xml boot.img /dev/sdb
[/SIZE]
To program the SD/eMMC with msp.exe in mass storage mode:
Code:
[SIZE=2]STEPS Complete example (patch after)
-------------------------------------------------------------
parse partition.xml python PartitioningTool.py partition.xml
Detect your device msp -d
Program your device msp -x rawprogram0.xml /dev/sdb
Patch your device msp -xx patch0.xml /dev/sdb
STEPS Complete example (patch before)
-------------------------------------------------------------
parse partition.xml python PartitioningTool.py partition.xml
Detect your device msp -d
Patch your files msp xx patch0.xml 15758336 (patch the 8GB card offline,this will change the partition0.bin)
Program your device msp x rawprogram0.xml /dev/sdb
[/SIZE]
The msp.py program can also used to patch the files.
For example:
python msp.py patch0.xml 15758336
This will patch the 8GB card offline, and change the partition0.bin.
Qualcomm DBL format (source Anyclub)
DBL is combined by three images.
dbl.bin - the raw DBL image
dbl.hd - the dbl header image
dbl_preamble.mbn - the preamble image with following format:
Code:
[SIZE=2]+------------+
|Dbl-preamble|
+------------+
|Dbl-header |
+------------+
|Dbl.bin |
+------------+
[/SIZE]
PBL is using the dbl_preamble to detect the NAND page size. The NAND controller
can detect 512 byte and 2 Kbyte page size automatically, but for NAND page size
more than 2K, PBL needs preamble to determine the page size, so for 512/2K
NAND,eMMC,eSD,oneNAND , the preamble is optional.
For the dbl_preamable, the first two words are same as dbl header, they are
codeword and magic,
ref image_header.c
Code:
data_ptr = autodetectpage;
*data_ptr = sbl_header.codeword;
data_ptr++;
*data_ptr = sbl_header.magic;
data_ptr++;
*data_ptr = AUTODETECT_PAGE_SIZE_MAGIC_NUM;
the third one is auto page size detection magic number.
The usage of the auto detection magic number is as below description To
understand this more clearly, for example ,if the dbl_preamble is 8KB. When we
detect the NAND page size > 2KB, we will set the default page size as 2K, then
try to read the preamble image from NAND flash, in case the page size is 4KB,
when read, can get 2 magic number in 8K size because page size will increase
with 4K byte steps, so page size is detected and that is 8K/2 = 4. For the 8K
page NAND, 1 magic number is read from the 8K size preamble image, so the page
size will be 8K/1 = 8K.
Dbl_preamble layout:
Code:
[SIZE=2]+-------------------------------------------------+
| codeword|magic|autodetection_ magic|............|
2K------------------------------------------------|
| codeword|magic|autodetection_ magic|............|
4K------------------------------------------------|
| codeword|magic|autodetection_ magic|............|
6K------------------------------------------------|
| codeword|magic|autodetection_ magic|............|
8K------------------------------------------------|
| codeword|magic|autodetection_ magic|............|
+-------------------------------------------------+
[/SIZE]
E:V:A said:
parse partition.xml python PartitioningTool.py partition.xml
Detect your device msp -d
Program your device msp -x rawprogram0.xml /dev/sdb
Patch your device msp -xx patch0.xml /dev/sdb
Click to expand...
Click to collapse
Hello, where i can find these files, i have qpst but there are no such files.
So does this explain why the pit references: pgpt.img, md5.img, sgpt.img but they aren't on any partition, (they should be after GROW blk0p23)
dviguha said:
Hello, where i can find these files, i have qpst but there are no such files.
Click to expand...
Click to collapse
I think it could be part of the Qualcomm Development Acceleration Resource Toolkit (QDART), as it supersedes QPST. But I'm not sure...
joederp said:
So does this explain why the pit references: pgpt.img, md5.img, sgpt.img but they aren't on any partition, (they should be after GROW blk0p23)
Click to expand...
Click to collapse
Where do you find these references?
I don't know, so if you find out let us know.
http://forum.xda-developers.com/showthread.php?t=1848267
If you dump the pit file you can see the references if you open in hex editor. Since it defines partition locations it appears they are either after last partition.. I haven't looked into technical pit stuff.
Sent from my SGH-T999 using xda app-developers app
Photo Place Holder Post
All images that I have not yet posted goes here...
Where can i find parseBinaryPartitionFile.pl or parseGPT.pl ?
vache said:
Where can i find parseBinaryPartitionFile.pl or parseGPT.pl ?
Click to expand...
Click to collapse
You tell me!

[GUIDE] External2Internal Ultimate for Galaxy Tab P1000

I thought about this idea while comparing my Android phone to my iPhone.
Both systems use variants of Unix, but the implementation is very different: there is one partition available to iPhone users, where all apps/music/everything gets installed. If you have a 64GB iPhone, this means you never run out of space for apps.
On the other hand, having a 16GB Android phone and a 64GB Micro SD puts you in a bit of a predicament, rather than a better place compared to the iPhone owner. Some genius has decided that there should be a 1-2GB /data partition where your apps go, and their data goes into the internal SD card; about 100-200 apps down the line (clearly, more than you need, but who are the android designers to judge), you run out of /data space and you end up doing ridiculous things like moving apps to SD, using some form of link2sd/data2sd script etc… Meanwhile you realise that your 64GB microSD is dead space and all you can do is store photos, music, video etc in it - rather than Asphalt data or Navigon maps.
This can change if you have a rooted phone! It took me a while to figure it out, but I first did it on my Galaxy Note N7000 following this guide: http://forum.xda-developers.com/showthread.php?t=1887864 and then decided to create a new guide for my Galaxy Tab 7 (P1000). Credits to badge2033 for the first guide.
After following this guide you will have:
* supersized data partition (12 gigs): no more move to sd needed and then again the stock move to sd feature will work as expected (it will move data to the actual external sd card)
* external sd card mounted as internal sd card: nothing to say here, just does what is expected
* real internal sd (ums partition) shrunk to minimum (half gig) because it needs to stay present: used to mount a swap file (optional)
What you will need:
* Rooted Galaxy Tab P1000 - hopefully running Android 4.3 HumberOS CyanogenMod, but not necessarily (this guide is made with CM10.2 in mind)
* Working knowledge of ADB / Google to get you through bits if you get stuck
Code:
/* Standard disclaimer: Your warranty is now void. Use at your own risk.
Modifying or replacing your device's software may void your device's warranty,
lead to data loss, hair loss, financial loss, privacy loss, security breaches, or
other damage, and therefore must be done entirely at your own risk.
Every time you do not backup and complain a puppy dies.
No one is responsible for your actions but yourself. Good luck. */
Procedure:
1. reboot to recovery, and connect your phone to your pc
2. run a command prompt and type the following (wait a little bit until the adb server starts on the phone, you can verify it by typing "adb devices" if you get a serie of digits then you're good to go.
Code:
adb shellcat /proc/partitions
You should see something like:
Code:
31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 443904 mtdblock2
31 3 22528 mtdblock3
31 4 12800 mtdblock4
31 5 11264 mtdblock5
179 0 15552512 mmcblk0
179 1 13455328 mmcblk0p1
179 2 1994752 mmcblk0p2
179 3 102400 mmcblk0p3
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 31166976 mmcblk1
179 25 31162880 mmcblk1p1
Backup your /data to External SD. REMEMBER YOU HAVE ALREADY COPIED YOUR INTERNAL SD TO THE EXTERNAL ONE!!! I did a dd backup and a nandroid in CWM. You only need the nandroid to restore later.
Code:
dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/databack.img bs=4096
Code:
/*** WARNING!!! Do your own backups / nandroids /
write important things down on a napkin, if this does not work for you
and you lose data I'm not responsible!!! ***/
You should see something like:
Code:
498688+0 records in
498688+0 records out
2042626048 bytes (1.9GB) copied, 277.149450 seconds, 7.0MB/s
Then use parted, the partition editor:
Code:
parted /dev/block/mmcblk0
you'll get into the parted interactive shell, this is where serious work done
Code:
unit b
print
You should see something like:
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15925772288B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32768B 13778288639B 13778255872B primary fat32
2 13778288640B 15820914687B 2042626048B primary ext4
3 15820914688B 15925772287B 104857600B primary ext4
Code:
did i remind you to backup your system,this is your last stop before the no back pointso you just might wanna "move" all your internal sd stuff to the external sd,and backup your system to the external sd also (you just need to restore the data partition afterwards the rest of the system is safe but who knows :p)ps: you can do your backup on cwm without leaving adb shell on the pc just like you will do the format later thanks to cwm
remove the partitions
Code:
rm 1
rm 2
make the new changed size partitions
Code:
mkpart primary 32768 536903167
mkpart primary 536903168 15820914687
print
you should see this output
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15925772288B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32768B 536903167B 536870400B primary fat32
2 536903168B 15820914687B 15284011520B primary
3 15820914688B 15925772287B 104857600B primary ext4
Format the data partition as ext2 (so that CWM can see it)
Code:
mkfs
Then choose 2, ext2
now in cwm go to mounts and storage and select "format /storage/sdcard0" and "format /data"
now restore your data partition in CWM.
and you will be able to boot you system normally. and you go to your storage information you will find that your app storage is now 13gigs and the usb storage is just 500 megs yay
For Android 4.3 modifying vold.fstab file (but for other versions do so with ciphray's guide on how to do so)
you can use the modified file from ciphray thread here which i didn't beacuse his file was smaller
What DOES work is the free External 2 Internal app in Google Play: https://play.google.com/store/apps/details?id=eu.codlab.int2ext&hl=el
Settings are (for CM 10.2 ROM):
Original Internal mounting point: /storage/sdcard0
Original External mounting point: /storage/sdcard1
Ext.sdcard device access: /dev/block/vold/179:25
[Have not done this - badge2033 suggests it]
as a final step you can use the now pretty useless internal space (500megs remember) as a swap sapce
download swapper2 from the play store here https://play.google.com/store/apps/d...v.n3o.swapper2
run it and go to settings
set swap place as /sdcard/external_sd/swapfile.swp
set swap size to the max
set the swappiness to 20 ( you can rise the value a little but don't put a high value or the system will do much swapping all the time -value of 100 means any memory not used actively will be swapped- )
wait until the process finishes then reboot your phone
you can verify that swap is working by typing "free" in the shell if the line beginning with swap is not all zeros then you're swap is working.
Phew! That was a long guide. Questions / comments below.
Good idea!
im waiting for better CM 10.2 and will try (my p1000 is on alroger's cm 10.1 now)
Sent from GT-P1000 using Tapatalk4
Just to be sure to have understood everything.
You have convert the internal storage in data partition but It can't be use anymore as a storage?
Thanks
Yes. The original partitioning of internal storage is about 2gb data / 12gb storage, now it's just 500mb storage. Then with the sd card swap this 500mb becomes obsolete as a 32 or 64 gb microSD takes the place of storage.
help me.
I really like the way you propose, I like to do this but,
after going to recovery and plug in,i open a cmd(admin) and type adb devices and this massage appear:
##################################
C:\Users\farzad>adb devices
List of devices attached
32348202BA2300EC device
C:\Users\farzad>
##################################
after that when I type this code:
>adb shellcat /proc/partitions
the help of adb appear:
##################################
Android Debug Bridge version 1.0.25
-d - directs c
e
returns a
present.
-e - directs c
returns a
unning.
-s <serial number> - directs c
ith
the given
##################################
what should I do? where is my mistake?
tnx
farza(db)astany said:
help me.
after going to recovery and plug in,i open a cmd(admin) and type adb devices and this massage appear:
after that when I type this code:
>adb shellcat /proc/partitions
the help of adb appear:
what should I do? where is my mistake?
tnx
Click to expand...
Click to collapse
Try entering separate commands in the command line
adb shell
cat /proc/partitions
You are welcome.
---------- Post added at 02:32 AM ---------- Previous post was at 01:58 AM ----------
Thanks for this post. In my case, this method somehow unlocked hidden 16GB storage. Without microSD inserted, it has 14GB of internal storage (where you can have your apps)... and 15GB of SD internal storage. (can be used as usb drive and storage for movies and music and books)
Moving EVERYTHING to external SD card
Hello,
Sorry for necroposting, but I'm looking for a way to revive a Samsung Galaxy Tab GT-P1000 that had a damaged internal storage chip physically removed.
I managed to intall CyanogenMod 13 on the external SD card partitionned as follow :
Code:
cat /fstab.p1
# Android fstab file.
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
recovery /recovery mtd defaults recoveryonly
boot /boot mtd defaults recoveryonly
radio /radio mtd defaults recoveryonly
/dev/block/mtd/by-name/cache /cache yaffs2 defaults recoveryonly
# LVM Volumes
/dev/lvpool/system /system ext4 ro,discard wait
/dev/lvpool/userdata /data ext4 noatime,discard,nodev,nosuid,nomblk_io_submit,errors=panic wait,encryptable=footer,length=-16384
/dev/lvpool/userdata /data f2fs rw,noatime,discard,nosuid,nodev,nodiratime,inline_xattr wait,encryptable=footer,length=-16384
/dev/block/mtd/by-name/datadata /datadata yaffs2 defaults recoveryonly
/devices/platform/s3c-sdhci.0/mmc_host/mmc0/*/mmcblk0 auto auto defaults voldmanaged=sdcard0:1,noemulatedsd,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc1/*/mmcblk1 auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
# zRAM
/dev/block/zram0 none swap defaults zramsize=134217728
However, most apps crash when started, as they expect a writable internal storage, and there is none.
Additionnal data :
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
254 0 131072 zram0
31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 432128 mtdblock2
31 3 17920 mtdblock3
31 4 12800 mtdblock4
31 5 16384 mtdblock5
31 6 11264 mtdblock6
179 0 15558144 mmcblk0
179 1 10844160 mmcblk0p1
179 2 4193280 mmcblk0p2
179 3 510976 mmcblk0p3
253 0 921600 dm-0
253 1 3768320 dm-1
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00780000 00040000 "boot"
mtd1: 00780000 00040000 "recovery"
mtd2: 1a600000 00040000 "datadata"
mtd3: 01180000 00040000 "cache"
mtd4: 00c80000 00040000 "efs"
mtd5: 01000000 00040000 "radio"
mtd6: 00b00000 00040000 "reservoir"
What I'm looking for is a way to use the external SD card as /system, /data, AND internal storage. Can anyone help me achieve this ?

Device Essential Material *** Firmware, Source Code, Root etc.***

This thread will list and link to all core device essential stuff.
PM me if there is new stuff please​
STOCK ASUS FIRMWARE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
Seperate Sd update for WW versions to recover from wrong released OTA, when unzipped place it on MicroSdcard and reboot:
WW_10_26_1_18_SDupdate.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
TW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
US_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_42_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
Altered CWM Recovery V6.0.3.7. for 4.2.2.*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery CWMrecovery4.2.2.img [where CWMrecovery4.2.2.img is the name of the file image you downloaded]
There is at the moment no CWM-Recovery or TWRP-Recovery for 4.3. version yet!!!
* With thanks to Drgravy for his work on that.
CUSTOM ROM'S
None available yet.
Will be released by Sbdags when there is a custom recovery for 4.3. available.
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION​
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!​
Odd that you just started this thread and it's outdated ;P
Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/showthread.php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/showthread.php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/showthread.php?t=2621028
Sorry folks. Thread closed as it already exists in the General Forum.
MD

No LTE with Sprint

I have an HTC One M8, and I installed Cyanogenmod 12.1 (I followed their guide and did HTCdev Unlock). For a little while, LTE was working fine with my phone, but then about a couple of weeks ago, my LTE connection stopped working, and it hasn't worked since. So ultimately that's the problem I'm looking to solve.
I had backed up my HTC factory ROM and restored that to see if LTE would work there. That's when I found that it wants me to do an update, but the update reboots me into TWRP and doesn't work. My thought is that to solve this, I will need to apply the update somehow, and if that's the case, then I could use some help figuring out how to do that. (I'm trying to run "Update Profile".)
If you have other ideas of what I can do to fix LTE, then I'm open to hearing them as well.
Thanks!
You need to install stock recovery to enable the update to install.
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
komi_9 said:
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
Click to expand...
Click to collapse
Yup sounds correct except being you are on 2.16 there will be a few updates you will need to do to get current.
I went through the process, and each step went fine (you were right about having to update a few times), but LTE is still not working in CM when I switched back over. It is working on the Stock ROM side of things; that's how I did my OTA update. (At least it says LTE in the status bar, so I assume that's what it's using, as opposed to just defaulting to LTE but switching to 3G when LTE is not present.)
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Thanks for the help again!
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
Click to expand...
Click to collapse
I don't use CM so can't answer but yeah your best bet would be to ask in their forum.
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Click to expand...
Click to collapse
If you took all the update to make you current you should have the latest stock recovery. You can always pull the stock recovery from the latest Full Firmware zip.
HK = Harmon Kardon Edition
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
komi_9 said:
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
Click to expand...
Click to collapse
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Sloth said:
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
komi_9 said:
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
Click to expand...
Click to collapse
Have you updated your twrp recently?
I have 2.8.7.0 downloaded from here: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
komi_9 said:
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
Click to expand...
Click to collapse
Yes that might be the problem. A full wipe shouldn't wipe anything important.
If you have a backup and you need to use it you will be back to the ROM you made the backup of.
Sent from a Glade Plugin.
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
komi_9 said:
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
Click to expand...
Click to collapse
V7.4.2 is not the latest version...try the latest and see if it makes a difference. Usually status 7 error means the updater script is out of date (if I remember correctly).
When I do a full wipe I choose Advance Wipe then check the boxes next to cache/dal cache/data/system. From my experience wiping in twrp and then wiping again in Aroma usually causes problems. I prefer the twrp method myself.
I also put anything I'm going to flash on the EXT sdcard.
The 7.4.3 version is only available as a patch to 7.4.2 as far as I can tell. The full download is only available in 7.4.2. Or at least that's all I see.
Anyway, the point is moot now since I seem to have gotten LTE working. I went into APN settings and the option CDMA 0 was selected. Any of the other options pop me over to the Sprint LTE Internet option, but that one will just sit there and not work. I'm not quite sure how I got stuck on that APN. But oh well, since it's working now.
I really appreciate all the help! One day I might embark on trying out different ROMs again, but for now I'm happy that CM is working out OK.
Cool glad you got it sorted.

[DEV][ Expand System Partition To 5GB - MediaPad M3 ]

Hello !
Here you will find the information needed to change the system partition from 2GB to 5GB - this operation is somewhat useful for installing any version of GApps on your device : Huawei MediaPad M3 8.4 Kirin version ( BTV-DL09; BTV-L0J; BTV-W09 )
Thanks to @accerian for his help, and you can also check out this tutorial for more information !
Download mkfs.ext4 and parted from here : https://forum.xda-developers.com/attachments/parted_gdisk_fdisk_mkfs-ext4-arm-zip.4494671/
Warning : the entire data partition will be deleted following this procedure, make sure you have backed up and saved it to a microsd card
Step I : extended system partition from about 2GB to 5GB ( example for a 32GB device, for 64GB devices the procedure is 99% similar, only one operation differs which will be specified at the appropriate time ) - also this example is for BTV-DL09 which is with LTE capabilities.
- extract "mkfs.ext4" and "parted" from previously download archive and put them into a new created tmp directory
- connect the device to the computer via the USB cable and bring the device into TWRP revovery with this command :
> adb reboot recovery
- copy the two executable files from the computer to the device :
> adb push tmp data/local
> adb shell
# cp -r data/local/tmp/mkfs.ext4 sbin/mkfs.ext4
# chmod 0777 sbin/mkfs.ext4
# cp -r data/local/tmp/parted sbin/parted
# chmod 0777 sbin/parted
- launch the "parted" function as follows :
# parted /dev/block/mmcblk0
- display all properties of all partitions : (I wrote what needs to be displayed as a command before pressing enter, so you just have to type "print" and press enter because (parted) is already displayed as promter ... be careful not to type (parted) twice in the following commands)
(parted) print
- go to line 43, which should be the same for all devices :
43 1174MB 3255MB 2080MB ext2 system msftdata
44 3255MB 3456MB 201MB ext4 cust msftdata
45 3456MB 3490MB 33.6MB ext4 version msftdata
46 3490MB 4127MB 638MB ext2 vendor msftdata
47 4127MB 4329MB 201MB ext4 product msftdata
48 4329MB 4333MB 4194kB hisitest2 msftdata
49 4333MB 31.3GB 26.9GB userdata msftdata
Click to expand...
Click to collapse
- if line 43 is not identical to this one here, please stop the process by writing quit and enter, I'm waiting for a private message with what is written on line 43 in the case of your device so that I can guide you correctly .
- assuming that all devices have the same system partition ( the same 43 line ) - approximately 2GB, we go to the next steps:
- access the Mount menu in TWRP and uncheck Data, and follow the steps below step by step :
(parted) rm 49
(parted) rm 48
(parted) rm 47
(parted) rm 46
(parted) rm 45
(parted) rm 44
(parted) rm 43
(parted) mkpart system ext2 1174 6501
(parted) name 43 system
(parted) set 43 msftdata on
(parted) mkpart cust ext4 6501 6702
(parted) name 44 cust
(parted) set 44 msftdata on
(parted) mkpart version ext4 6702 6736
(parted) name 45 version
(parted) set 45 msftdata on
(parted) mkpart vendor ext2 6736 7374
(parted) name 46 vendor
(parted) set 46 msftdata on
(parted) mkpart product ext4 7374 7575
(parted) name 47 product
(parted) set 47 msftdata on
(parted) mkpart hisitest 7575 7579
(parted) name 48 hisitest2
(parted) set 48 msftdata on
- for devices with 32GB :
(parted) mkpart userdata 7579 31.3GB
- for devices with 64GB :
(parted) mkpart userdata 7579 62.5GB
(parted) name 49 userdata
(parted) set 49 msftdata on
(parted) quit
Step II : activating partitions for reuse :
# mkfs.ext4 /dev/block/mmcblk0p43
# mkfs.ext4 /dev/block/mmcblk0p44
# mkfs.ext4 /dev/block/mmcblk0p45
# mkfs.ext4 /dev/block/mmcblk0p46
# mkfs.ext4 /dev/block/mmcblk0p47
# mkfs.ext4 /dev/block/mmcblk0p49
- go to TWRP -> Wipe -> Advanced Wipe -> select System -> Repair or Change File System -> Change File System -> EXT4 -> Swipe to Change
- go to TWRP -> Wipe -> Advanced Wipe -> select Vendor -> Repair or Change File System -> Change File System -> EXT4 -> Swipe to Change
- go to TWRP -> Wipe -> Format Data -> yes
- reboot device from TWRP to TWRP in order to use data again after formated !
- go to TWRP -> Wipe -> Advanced Wipe -> select Dalvik/ART Cache, Cache, Data, Internal Storage, System, Vendor -> Swipe to wipe
- copy the new updated of LOS 17.1 with system partition of 5GB into your device
- copy any GApps arm64 Android 10 to your device
- Install them like always, enjoy !
Mention :
- if your device is WiFi only, you may have fewer partitions .... the above instructions can be easily adapted from case to case !
The main idea is that we must first find out what position the system partition is in, in this case it was at position 43 which corresponds to /dev/block/mmcblk0p43 - then we need to delete all partitions from userdata to system, and recreate them in the same order !
To calculate the start and end position, it is again very easy : for example the system partition starts from the initial position 1174, which is the same as the end position of the previous partition 42 (42 1160MB 1174MB 14.7MB reserved3 msftdata), and the end position was incremented by 5327 in this case (almost 5GB), resulting in 6501. .. the next partition 44 (cust) will have the starting position 6501, and the end position will be incremented by 201 (i.e. 201MB) as shown on line 44 (44 3255MB 3456MB 201MB ext4 cust msftdata)
If really needed, a concrete example will be added here for WiFi only devices !
Thanks for this guide.
Thank you surdu_petru.
The internal storage size of BTV-L0J is 16GB, is the above procedure effective?
Is it possible to restore a partition size back to its original size? I sometimes use a dd command as a way to restore from LineageOS to stock ROM. So I need to restore it to its original size before using a dd command.
According to z3DD3r, who created a tool to resize the Nexus 5 system partition, it is recommended that after changing the partition size, TWRP should also be changed.
z3DD3r said:
Because TWRP includes size of system partition. This size should match the size of system partition on device. Otherwise bad things can happen...
Click to expand...
Click to collapse
Is there any problem without changing TWRP?
I am sorry for asking so many questions. I am cautious about changing the partition size because it is perilous.
Me said:
Thank you surdu_petru.
The internal storage size of BTV-L0J is 16GB, is the above procedure effective?
Is it possible to restore a partition size back to its original size? I sometimes use a dd command as a way to restore from LineageOS to stock ROM. So I need to restore it to its original size before using a dd command.
According to z3DD3r, who created a tool to resize the Nexus 5 system partition, it is recommended that after changing the partition size, TWRP should also be changed.
Is there any problem without changing TWRP?
I am sorry for asking so many questions. I am cautious about changing the partition size because it is perilous.
Click to expand...
Click to collapse
If you still have 49 partitions, and partition 43 (system) shows that in the above tutorial then the procedure is identical, you just have to put a lower value of the user data partition in the last corresponding line of 16GB!
- for devices with 16GB:
(parted) mkpart userdata 7579 ?? GB
Click to expand...
Click to collapse
There is no need to change anything, neither TWRP nor the partition to the initial value ... the most important thing is to pay attention to the Start and End position of system partition to make the calculations as accurate as possible !
I can help you if you can send me a screenshot of what the command below displays on your device (from the system down to the last partition):
> adb shell
# parted /dev/block/mmcblk0 print
surdu_petru said:
If you still have 49 partitions, and partition 43 (system) shows that in the above tutorial then the procedure is identical, you just have to put a lower value of the user data partition in the last corresponding line of 16GB!
There is no need to change anything, neither TWRP nor the partition to the initial value ... the most important thing is to pay attention to the Start and End position of system partition to make the calculations as accurate as possible !
I can help you if you can send me a screenshot of what the command below displays on your device (from the system down to the last partition):
> adb shell
# parted /dev/block/mmcblk0 print
Click to expand...
Click to collapse
Thank you for your reply.
It is good news that if each partition has the same number it is effective.
I am currently not having trouble with the size of system partitions, so I will give it some more thought.
@surdu_petru - many thanks for this guide, I found it very clear and straightforward. I wasn't sure if you were wanting confirmation that these instructions work with other models of the tablet - if so, I can confirm it works perfectly with my (wifi only, 32GB) BTV-W09.
Herby007 said:
@surdu_petru - many thanks for this guide, I found it very clear and straightforward. I wasn't sure if you were wanting confirmation that these instructions work with other models of the tablet - if so, I can confirm it works perfectly with my (wifi only, 32GB) BTV-W09.
Click to expand...
Click to collapse
Thanks for confirmation. I'm not waiting especially confirmation, but it's always better if you can confirm. I'm here to help in case that something goes wrong.
I'm going for the 3rd time as the first I messed up. Second I did it right but I think I have to switch it up a little as I have the WIFI, and I can't do mkfs.ext4 after doing the parted commands. But I'll keep on it to see if all the partitions are exactly correct. I know 43 is the same as the directions said to make sure. 3rd times the charm. Good luck out there
Hey man, things are kinda messed up for me at the moment.
I've followed your steps however my cmd crashed for some reason during the process. Now I can't mount data to start the process again. Using the genuine EMUI Recovery offerd at startup doesn't work because the partitions are messed up and my own recovery points are inaccessible probably due to a currupted ext sd card (you can't make this up )
Do you have any tips on how to regain control? Or are all hopes lost?
I've tried using pro-team multi tool, however their database/website seems to be unavailable at the moment...
Edit: I have it fixed now, using a sd-card I did a force update to stock firmware, that fixed the storage. Had to restart the entire process starting with TWRP installation, device was still unlocked though. Don't be stupid like me and always check your recovery data before and not after you already messed things up
hey guys,
I somehow messed it up and I'm getting this error message
/data is not present!
Failed to mount '/data'
Partitions are formatted:
43 1174MB 6501MB 5327MB ext4 system msftdata
44 6501MB 6702MB 201MB ext4 cust msftdata
45 6702MB 6736MB 33.6MB ext4 version msftdata
46 6736MB 7374MB 638MB ext4 vendor msftdata
47 7374MB 7575MB 201MB ext4 product msftdata
48 7575MB 7579MB 4194kB hisitest2 msftdata
49 7579MB 31.3GB 23.7GB userdata msftdata
Here is an output of "df" command:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 1.8G 184.0K 1.8G 0% /dev
tmpfs 1.8G 2.0M 1.8G 0% /tmp
/dev/block/mmcblk0p36 232.0M 756.0K 223.6M 0% /cache
/dev/block/mmcblk0p46 582.4M 468.0K 563.7M 0% /vendor
/dev/block/mmcblk1p1 59.5G 5.0G 54.5G 8% /external_sd
I can't continue with "TWRP -> Wipe"
Any ideas what went wrong?
BlueLife98 said:
Hey man, things are kinda messed up for me at the moment.
I've followed your steps however my cmd crashed for some reason during the process. Now I can't mount data to start the process again. Using the genuine EMUI Recovery offerd at startup doesn't work because the partitions are messed up and my own recovery points are inaccessible probably due to a currupted ext sd card (you can't make this up )
Do you have any tips on how to regain control? Or are all hopes lost?
I've tried using pro-team multi tool, however their database/website seems to be unavailable at the moment...
Edit: I have it fixed now, using a sd-card I did a force update to stock firmware, that fixed the storage. Had to restart the entire process starting with TWRP installation, device was still unlocked though. Don't be stupid like me and always check your recovery data before and not after you already messed things up
Click to expand...
Click to collapse
hey man, how did you install the stock firmware? tried to install these firmware's but didn't work at all https://firmwarefile.com/huawei-mediapad-m3-btv-dl09

Categories

Resources