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
Related
I messed up my SDcard partition on my phone and it is totally not usable, even from adb shell. Being it uses the GPT scheme, there's no way I have the knowledge of fixing it. I have a clockworkmod recovery image on my PC. Is there a way I can use adb shell to restore the image to my phone?
dman777 said:
I messed up my SDcard partition on my phone and it is totally not usable, even from adb shell. Being it uses the GPT scheme, there's no way I have the knowledge of fixing it. I have a clockworkmod recovery image on my PC. Is there a way I can use adb shell to restore the image to my phone?
Click to expand...
Click to collapse
Hello i am stuck on the google image when phone boots up and can only boot into fastboot mode. did you find a way to return to stock through here? please let me know thank you.
I trashed large parts of my sdcard, but still had ADB/CWM. Downloaded gptfdisk and did recovery option to restore backup gpt from last sector to first GPT sector (LBA1).
With gptfdisk, after backup GPT, make sure print out your new partition table and are happy with the map, before you write it back. Should then be able to recreate recovery, system partitions from backup, even directly through dd.
In the process I noticed MBR in LBA0 got recreated to "a single primary partition"; but recovering partition table pretty much only got partition offsets sorted out - still needed to work on formatting individual partitions and tweaking partition names, types and the like - will depend on circumstances.
Ref: http://forum.xda-developers.com/showthread.php?p=26638440 (for Transformer Prime TF201)
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?
I have a Mi A2 lite (msm8953), and I am trying to boot on two different data mounts. I managed to do it by mounting user data partition as /preData then mounting /preData/second on /data on vendor partition init files, and I booted successfully.
But when going back to the /data as /data, my unlocking pattern doesn't work and I have to delete "/data/system/locksettings.db".
My question is, since the process of booting to a subdirectory (/data/second instead of /data) of the actual data does not touch the actual /data/ files at all, how did the lock process get messed up for the primary data?
My guess is there's a specific partition involved in the lock process that's being modified, if I am correct, which one is it ?