Deleted TA partition

So I accidently deleted my TA partition on my Xperia T (I think - I know I deleted partition number 1, while trying to expand storage for apps) and now my phone isn't showing any signals of life. I have some sort of TA backup, but I don't know how to flash it?

Is there any way I can get my phone working again?

Is there a way i can setup a custom partition sizes on xperia z1 nand?

Its not majorly important but i would like to edit the partition sizes of the xperia z1's nand. like shrink system partition and grow the data partition. again its not dire but i would like to experiment and learn more about the NAND setup.

Bootloop and Bad Partition Table? PIT File Please?

Hello!

I got a Galaxy Note 2 second hand and there is something wanky going around.

So the current status of the phone:

The phone will not go into twrp or odin mode without the charger in. However, I check the battery voltage and it was at full charge, 3.4v? ish?

When just pressed power button alone, it goes into a bootloop. So far, it glitches into the galaxy note 2 logo then back to battery with screen. Or other times, it goes into bootloop with only battery screen then on and black screen, which this further repeats.

There are no partitions mounted when observed inside twrp. 0mb so I am assuming that the previous owner tried to flash a custom rom and may have failed at or something.

So my current conclusion of the phone after researching and experimenting with a little knowledge about anything:

The phone has its partition table messed up (ugghghghgh) and there is no platform for the OS or Android to be flashed on to when I was trying to using odin for couple past days.

Any ideas? Anyone have a PIT file that I can test this with? I got some pit file online that I assume that is for Sprint Galaxy Note 2, but re-partitioning with that PIT doesn't seem to do anything.

Any ideas how to approach this?

P.S. it also says that it can't mount /data. Assuming because it doesn't have any partition within the phone itself but could there be any different reason?

Can't mount 2nd partition or enable Init.d

I'm trying to use Link2SD, so I created the 2nd partition with ext3 format.
It did gives me the error "script cannot be created. Invalid argument". I did some research and for what i could understand, I need to enable Init.d, so link2sd scripts can be executed.

So i got Universal Init.d, it says my kernel doesn't support it. Tryed some scripts, but no deal.
The "init.d" folder is there with the script, but it's ignored.
Even if I try to execute the command manually (mount -o rw -t ext3 /dev/block/mmcblk1p2 /data/sdext2) i get the same error using "su" privileges (invalid argument)....

My phone is Xperia Z2 rooted on Lollipop 5.1.1 with SuperSU and XZRecovery (TWRP & CWM).

Thanks for any help

TA partition and the drm keys

Are the drm keys in the ta partition specific to the device?
I have done some flashing my old tablet to a new one and have lost access to my front camera.
I have a backup of the old drm keys from the old tablet that I can restore if it will work.


Sent from my SGP512 using XDA Premium HD app

Rooting using kingo worked but could not partition sd card.

Hi everyone, newbie here . Will.
I have a Samsung galaxy y Gt-S5369.
Android version 2.3.6.
Base band version S5369BULL1 .
Kernel version 2.6.35.7.dpi @ Dell172#1. Mon Dec 3 16:30:31 Ist 2012. Build number GINGERBREAD .BULL1.
Recently I have tried rooting my phone to no avail.
I used kingo app to root and got super user access I installed busy box, link2sd cwm and aparted but could not partition sd card for expansion but it said su binary not updated..

So my question is , is my phone fully rooted ?
And why can't I partition my sd card so I can expand using link2 sd card ?

I am probably leaving out a lot of detail but i hope it's enough to get my problem started to been resolved .
Kind regards.
Will.:):o

Link2sd lost 2nd partition (f2fs)

While working with Link2sd, I moved a ton of apps to the SD's 2nd partition, using f2fs file system. Rebooting the phone (XT926 - 4.4.2 - rooted), the 2nd partition was no longer accessable and, of course, the apps vanished. Worse, I can't re-install some of them. I get the "not enough storage" gripe. Short of doing an FDR, is there any hope of recovering the data or at least making it possible to re-install the lost apps? FWIW, I tried reading the SD under Win7 (nothing found, of course) and SuSE Linux with f2fs.tools installed. Still nothing.

How SOL am I?

Windows 10 Upgrade problem "We couldn't update the system reserved partition"..

I have installed an original copy of Windows 8.1 Pro in my Teclast X98 Air 3G and try to upgrade to Windows 10 using the Windows Update feature, but everytime I try it, it returns the error "We couldn't update the system reserved partition". I increased the System Reserved partition size to 500MB as Windows 10 need, but no luck.

Anyone have a solution to that problem?

Extend system partition

I need to install an apk to /system/app but my system partition has no free space. Using "df" command in terminal emulator, it says 0.0K free in /system.
I have Android 6 DP3 and I've never pushed any file to /system before.
Is there any way to extend system partition?

Trying to flash a dd image I took from the system partition

Long-time UNIX guy here, but relatively new to the world of Android.

I have recently purchased an Asus MemoPAD (ME103K) ; I then became root, and took a `dd` image of the read-only `system` partition to the external SD card:

Code:

---

    $ su
    # dd if=/dev/block/platform/msm_sdcc.1/by-name/system \
            of=/storage/MicroSD/system.img bs=1M
    # ls -l /storage/MicroSD/system.img
    -rw-r--r-- 1 root root 2147483648 Sep 27 13:15 system.img

---

The size (exactly 2GiB) was a bit suspicious - could it be that this was because of the FAT32 partition on the SD card?

No, it was not - `tune2fs -l` revealed that this was indeed, a valid EXT4 image, exactly sized at 2GiB, which passed `fsck -f` with no errors at all.
And `fastboot` (from the linux machine attached to the tablet) concurred, after an `adb reboot bootloader`:

Code:

---

    linuxbox# fastboot getvar all
    (bootloader)  version-bootloader: 3.03
    (bootloader)  version-hardware: rev_c
    (bootloader)  variant: LEOPARDCAT 16G
    (bootloader)  version-baseband: H00_0.16.F_0521
    (bootloader)  serialno: 0a3dXXXX
    ...
    (bootloader)  partition-type:system: ext4
    (bootloader)  partition-size:system: 0x0000000080000000

---

That size, is indeed 2GB:

Code:

---

    linuxbox# python2 -c 'print 0x0000000080000000'
    2147483648

---

So, all is good - I have a backup of the image. Now to test restoring it.

I try to flash the system.img back to the tablet - to make sure I can recover from anything, the sort of bullet-proof backup we do in the Unix world (*e.g. restore contents of a drive via `dd if=backup.image of=/dev/sdXXX`*).

Everything related to `adb` and `fastboot` work flawlessly - so I try...

Code:

---

    linux_box# fastboot devices
    0a3dXXXX    fastboot

    linux_box# mount /dev/sdcard /mnt/sdcard
    linux_box# cp /mnt/sdcard/system.img .
    linux_box# fastboot flash system system.img
    error: cannot load 'system.img'

---

Hmm. I download and build the `android-tools-5.1.1` of my distribution from sources, adding debug information - and step in the debugger, to see this failure:

Code:

---

    # gdb --args fastboot flash system system.img
    ...

---

(sorry, can't paste links yet - see this image: http i stack imgur com 9bIEM.png

Interesting - even though I am in a 64bit machine, apparently there are issues that turn the file size "negative" (in a 32bit world, the file size of my image, 2^31, is indeed considered negative - to be exact, `-2147483648`.

OK, fine - how do they flash large image files in Android?

Googling, searching - turns out they use this `make_ext4fs` tool, that creates flashable images. In fact it is part of what I just compiled, so I might as well use it:

Code:

---

    # mkdir /system
    # mount -o loop,ro system.img /system
    # ls -l /system
    total 208
    drwxr-xr-x 106 root root  8192 Sep 17 22:24 app
    drwxr-xr-x  3 root 2000  8192 Sep 26 21:08 bin
    -rw-r--r--  1 root root  6847 Sep 12 16:59 build.prop
    drwxr-xr-x  19 root root  4096 Sep 26 21:08 etc
    drwxr-xr-x  2 root root  4096 Aug 11 22:27 fonts
    drwxr-xr-x  4 root root  4096 Sep 12 16:56 framework
    drwxr-xr-x  10 root root  16384 Sep 12 16:59 lib
    drwxr-xr-x  2 root root  4096 Jan  1  1970 lost+found
    drwxr-xr-x  3 root root  4096 Aug 11 22:18 media
    drwxr-xr-x  59 root root  4096 Aug 11 22:29 priv-app
    -rw-r--r--  1 root root 126951 Aug  1  2008 recovery-from-boot.p
    drwxr-xr-x  3 root root  4096 Aug 11 21:02 scripts
    drwxr-xr-x  3 root root  4096 Aug 11 21:02 tts
    drwxr-xr-x  11 root root  4096 Sep 26 21:08 usr
    drwxr-xr-x  8 root 2000  4096 Aug 11 22:29 vendor
    drwxr-xr-x  2 root 2000  4096 Sep 26 21:09 xbin
       
    # ../extras/source/extras/ext4_utils/make_ext4fs \
          -l 2048M new_system.img /system
    Creating filesystem with parameters:
        Size: 2147483648
        Block size: 4096
        Blocks per group: 32768
        Inodes per group: 8192
        Inode size: 256
        Journal blocks: 8192
        Label:
        Blocks: 524288
        Block groups: 16
        Reserved block group size: 127
    Created filesystem with 2666/131072 inodes and 375014/524288 blocks

---

Cool - so I can apparently build system images from plain old folders. The sky will be my limit - I'll be able to add anything I want to this image.

Let's burn it...

Code:

---

    # fastboot flash system new_system.img
    erasing 'system'...
    OKAY [  0.064s]
    sending 'system' (2088960 KB)...
    ^C

---

I waited for 1h before hitting that Ctrl-C. And had to power-cycle the tablet, which booted back in fastboot mode.

This is not looking good.

What if I build a smaller image? Maybe the 2GB are somehow an issue, and this partition is not used to full capacity - it has free space:

Code:

---

    # ../extras/source/extras/ext4_utils/make_ext4fs \
          -l 1536M new_system.img /system
   
    #  ./fastboot flash system system.img
    erasing 'system'...
    OKAY [  0.065s]
    sending 'system' (1572864 KB)...
    OKAY [ 51.039s]
    writing 'system'...
    OKAY [235.080s]
    finished. total time: 286.183s

---

OK, this looks very promising (and only took 5 min). I guess I can now reboot back and everything should be normal, yes?

No :)

(sorry, can't paste links yet - see this image: http i stack imgur com U7wiX.png

I don't mind a temporarily bricked device, as long as I **do** get to control it in the end (machines that I am not a master of, are machines I don't care to operate ;)

Any ideas on what I did wrong and what I can do to fix this?

Thanks in advance.

P.S. I checked the Asus support page for my tablet - they only provide the sources for the kernel, and the Over-the-air .zip file. That in turn contains a file-system level backup from the root - i.e. the `system` folder exists in there as just a folder, not an image, not a `system.img` that I can flash - so that doesn't really help me.

[Q] How do I resize the partition that stores my data?

I own the 64gb version of the Oneplus One but after flashing cm-12.1-YOG4PAS1N0 only ~12gb are available. Flashing a different rom and reflashing cm-12.1-YOG4PAS1N0 didn't help.
Also, someone told me to use this make_ext4fs /dev/block/mmcblk0p15 command in the twrp command prompt. Does that have something to do with it?

Thanks for your help!

is it possible to fix lg gflex 2 damaged efs partition?

hi guys,
i have a very big trouble with my lg gflex 2. here is my problem: i installed europe rom to my at&t lg gflex 2. but sim not worked. and when i searched forums, i've seen h950pr rom, and installed too. but this time imei gone. when i install the europe rom back imei is showin' up again. but sim card not working anymore. i need to back up my efs partition from europe rom and modify h950pr rom, is it possible? and need serious help?
thanks in advance...

[Help]16GB partition on 32gb...

Well afaik I own a 32gb N5 :D
I only noticed this recently because it kept complaining about lack of space, at first I was kind of surprised. But after I looked in the settings I found that I had the wrong partition.
I went on to flash back to stock image. However, that didn't do it.

^The image I just finished flashing.
Am I flashing the wrong one? If so, where can I find the 32gb version?