I installed postmaketos on my tf-300t and it was fine.
the next day the system did not have access to it's root partition.
and I made a silly act repatriationing all memory and copying root partition to new partition hoping that boot partition will find it and works.
and then
nothing. only a black screen.
can anyone help me repair partition table?
Related
Sick of the separate userdata and fakesd partitions and familiar with Nexus 4's way of doing things (only userdata), I've tried to repartition my device.
The way I went about it was by booting a recovery (twrp), and, via adb shell, sharing the whole mmcblk0 via usb_mass_storage. It is a GPT partition table, so I used gparted, got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'd appreciate some intel if any of you know what's actually going on.
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
li_suna said:
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
Click to expand...
Click to collapse
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
skorzo said:
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
Click to expand...
Click to collapse
Why don't you try this guide:
http://forum.xda-developers.com/nexus-s/general/howto-combined-emulated-storage-nexus-s-t2848752
Accidentally I deleted boot and boot1 partitions on my Mi4 while extending system partition. Could create system partitions as ext2 but I do not understand what type of filesystem boot and boot1 belong to. Could someone help in creating back the lost partitions? Thanks in advance
[update]
I think I messed up boot partition...so tried to flash rom via fastboot(since I created the system partition already). Now I can't flash recovery also. Can enter only fastboot mode.Is my mobile permanently bricked?
Hi,
before I brick my smartphone: is the internal storage a real GPT partitioned thing which can be changed by gdisk, parted and friends? I'll change only the things starting with cache - and only sizes & partitions, not the overall layout. I would like to squeeze the unused cache-partition to a few MBs and reduce the cdrom-partition, move the system-partition at top and increase the userdata partition.
Best regards,
mifritscher
Any infos on this one? Could I recover from a completely broken flash via fastboot, qdload or sdboot?
Ok, I tried - and failed *g*
I partitioned with parted - and the kernel accepted the new partition table as well. But it seems that the phone either blocks write access to the GPT, or has its own internal version. Because after a reboot, I got the old partition table again.
Luckily I had a backup (with I needed for repartitioning anyway), and both fastboot and recovery worked. TWRP was only a bit refused regarding the broken partitions, but it could both reformat the partition and fire the backup (with I did with dd and gzip) before).
So the big question is: How can I unlock the emmc to write to the GPT?
Hi everyone. My phone (redmi 6 cereus) has realtively small system partition, so I decided to try to manually alter the partition table. I did that one time without any problems so I thought it would go smoothly this time. Boy was I wrong Like the last time, I resized my data partition, deleted system partition and created a new one to use all the space left available after shrinking data partition. After that I rebooted my device to twrp but this time I forgot to name that new partition as system (now its label is something like "Microsoft basic data partition") and now my device bootloops. I cannot even boot to recovery, fastboot is the only thing that boots.
I've tried booting twrp using fastboot boot twrp.img but that also resulted in bootloop. My theory is that my device is trying to mount system partition during early stages of booting, but it cannot find one so it crashes and reboots. So I thought that maybe I could extract boot.img and modify it so fstab would not have any references to system partition, but my boot.img has empty ramdisk. I've tried to to the same thing with twrp image, but there I could not find fstab file.
Maybe my thinking is wrong and there is another solution to this problem. Maybe it is possible to name partition from fastboot? I don't know, I'm pretty familiar with linux, but not so much with android. Any help would be appreciated