[REPARTITION] Nexus 4 Repartition [MAKO] [8GB/16GB] [UA TWRP]

[finaluser]

Thank you very much to all the work for this incredible ROM, it is installed and working much better than expected on my Nexus 4 8GB, now it is even faster than other firmwares. I'm so excited. Thank you!!

 

[ze7zez]

custom theme

@Clamor
Due to the damaged area of the touch screen, I would like to change the appearance and position of the twrp keys.
However, after making changes, for example in /twres/ui.xml and restarting, the file is still original, i.e. without my changes.

How could I modify the TWRP appearance?

 

[Clamor]

@ze7zez I need few days to investigate this and then I'll provide answer in this post.

Theme is loaded from ui.zip that lies in TWRP/theme folder

 

[PsK2010]

Thank you very much Clamor! I just repartitionned my old Nexus 4 (on official Lollipop Stock Rom) to try LineageOS 16 GO Rom and everything works super smooth!

 

[ALEXIS_0071]

it would be great if someone made a video explaining how to do it, so that new ones like me, be guided

 

[Vegeta IV]

Hi guys and thank u for this work all working good but for now i need to install official google rom so is it safe? Or i need repack it somehow?

 

[sellless]

Hi there,

I have an old Nexus 4 where the screen doesn't work along the right side of it so I can't press enter after I type modify.

I am trying to install a battery friendly rom before handing this off to an friend of mine but I can't becuase of the system partition size.

I tried "adb shell" but it wasn't working, though I can see my device.

I realize that this thread is quite old but I would really appreciate some help as the last offical stock build of Android for mako is the only one I can seem to get to work and we all know that isn't good enough.

Thanks to anyone that can help.

 

[ze7zez]

Hi there,

I have an old Nexus 4 where the screen doesn't work along the right side of it so I can't press enter after I type modify.

I am trying to install a battery friendly rom before handing this off to an friend of mine but I can't becuase of the system partition size.

I tried "adb shell" but it wasn't working, though I can see my device.

I realize that this thread is quite old but I would really appreciate some help as the last offical stock build of Android for mako is the only one I can seem to get to work and we all know that isn't good enough.

Thanks to anyone that can help.

Here we write about the repartition.
Just a hint, because I see that you do not have much interest in reading the forum
and you would like to have work done without any effort.

Trick with changing the TWRP graphical interface

 

[Luis_Viera]

Modify the system partition Nexus 4 Mako 16 GB with Mako_clamor_repartition_zip

I want to thank you for the publication of this tutorial, I applied your instructions and followed them to the letter and finally, after several attempts, I managed to modify the system partition and updated my old but useful LG Google Nexus 4 E960 Mako 16 GB with OS Android 10 Lineage 17, the only problem I had was that the Terminal did not work for me and I could not execute the "modify" instruction but I connected the phone to my PC and using ADB and Fastboot I introduced the command "adb shell modify" and it automatically modified the system partition and I was able to flash the ROM and its GAPPS, thanks.

 

[dj_s_021]

please help please help me
I was the installation when I unfortunately encountered the following error:
Failed to mount '/vendor; ( invalid argument )
What should I do ??
Of course Despite this error I'm ROM and installed! Is it okay for the phone to crash over time?
How do I know if the REPARTITION is working properly?

 

[coffee-coffee]

Decryption on Android 10 (CarbonRom)

Hey there,

thank you for the guide, all worked well. However, after encrypting my mako on Android 10 (CarbonRom), TWRP is not able to decrypt the data any more. Any thoughts on this?

Kind regards
coffee

 

[llazcanoster]

Hello!!
I Have the same problem, I wanted to check if anyone has trouble decrypting the storage in TWRP, and if so, is it caused by the rom or by the recovery?

Thanks for the great work!

 

[ze7zez]

Hello!!
I Have the same problem, I wanted to check if anyone has trouble decrypting the storage in TWRP, and if so, is it caused by the rom or by the recovery?

Thanks for the great work!

Did you use twrp 3.4 for this?
Note! This version has an annoying restart error so you have to do it manually in the terminal, e.g.
twrp reboot recovery

 

[llazcanoster]

Did you use twrp 3.4 for this?
Note! This version has an annoying restart error so you have to do it manually in the terminal, e.g.
twrp reboot recovery

Yes, I have tried 3.4.0.0, 3.3.1.0 and 3.3.1-1_UA, with the same result

 

[basturd22]

Oh my gosh! oh my gosh! you fixed my freaking fone!

 

[thangcuoi]

My Nexus 4 was running ASOP 6.0.1. In order to flash a more current rom, I needed to resize its partitions.

After flashing mako_clamor_repartition.zip in official TWRP 3.4, my Nexus 4 seems to have lost all partitions.

I managed to flash twrp-3.3.1-1_UA-mako.img after, but it's unable to mount any partition apart from Cache which it reports as zero byte. Trying to wipe/erase partitions does not work as it could not mount them.

When I try reflashing the stock rom, it reported that it can write to Boot and Recovery but not System partition.

I have also tried plugging in a micro usb drive, but TWRP won't mount it either.

Does anyone have any advice on how to rescue my Nexus 4?

Also, I managed to get back into TWRP one time. The rest of the time, it get stuck on the Google logo screen. Holding down Volumes + Power just restart the phone instead of going to the bootloader screen. Alternatively, it would shows the battery charging logo and my Windows computer would play the sound that it has detected a device.

https://photos.app.goo.gl/uaesEAVVwQ6RApaL9

 

[ze7zez]

My Nexus 4 was running ASOP 6.0.1. In order to flash a more current rom, I needed to resize its partitions.

After flashing mako_clamor_repartition.zip in official TWRP 3.4, my Nexus 4 seems to have lost all partitions.

I managed to flash twrp-3.3.1-1_UA-mako.img after, but it's unable to mount any partition apart from Cache which it reports as zero byte. Trying to wipe/erase partitions does not work as it could not mount them.

When I try reflashing the stock rom, it reported that it can write to Boot and Recovery but not System partition.

I have also tried plugging in a micro usb drive, but TWRP won't mount it either.

Does anyone have any advice on how to rescue my Nexus 4?

Also, I managed to get back into TWRP one time. The rest of the time, it get stuck on the Google logo screen. Holding down Volumes + Power just restart the phone instead of going to the bootloader screen. Alternatively, it would shows the battery charging logo and my Windows computer would play the sound that it has detected a device.

Links to your pictures can only be seen after trying to answer the post. What TWRP did you use to make the pictures?

What happens after using mako_clamor_repartition.zip in twrp-3.3.1-1_UA-mako?

 

[thangcuoi]

Links to your pictures can only be seen after trying to answer the post. What TWRP did you use to make the pictures?



What happens after using mako_clamor_repartition.zip in twrp-3.3.1-1_UA-mako?

https://photos.app.goo.gl/uaesEAVVwQ6RApaL9

I flashed the clamor repartition zip file with the official TWRP 3.4. At this point all partitions (except Cache) could not be mount or wipe. I managed to flash twrp-3.3.1-1_UA-mako to replace the 3.4 version from the computer but that did not help with being able to mount or wipe the partition.

Sent from my PH-1 using Tapatalk

 

[LunkHead]

EDIT: And I'm an idiot and missed the format all partitions step. Leaving the rest of this post as a testament to my shame =)

I'm in the same boat with my 16GB Nexus. Ran the mako_clamor_partition, then went to the terminal and specified 'modify', and now the partitions on the device are in a wonky state.

When inspecting the partitions in twrp in the 'Advanced Wipe' menu, checking a partition, and hitting 'Repair or Change File System' these are the results:

/system is 1476MB
/vendor is 0MB
/data is 0MB
"internal storage" says "Invalid partition selected"
/cache is 98MB
"Dalvik/ART Cache" says "Invalid partition selected"

Because internal storage and data are 0/invalid copying files to the device isn't possible. There is no storage available/detected when connecting via USB to a PC.

I tried the method of unbricking the N4 from this thread:
https://xdaforums.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
However the LGNPST program does not detect the phone when connected in download mode.

Is there any way to restore the partition table from inside TWRP with no access to the internal device storage? It looks like fdisk is installed in /sbin (though running 'sbin/fdisk -ul' reutrns nothing?), does anyone have the proper commands to issue to get the partition table back to stock?

Also, if I attempt to copy the logs, this error is in the output:
'Failed to mount '/data' (Invalid argument)'

Any ideas how to get out of this state?

Thanks!

 

[ze7zez]

EDIT: And I'm an idiot and missed the format all partitions step. Leaving the rest of this post as a testament to my shame =)

I'm in the same boat with my 16GB Nexus. Ran the mako_clamor_partition, then went to the terminal and specified 'modify', and now the partitions on the device are in a wonky state.

When inspecting the partitions in twrp in the 'Advanced Wipe' menu, checking a partition, and hitting 'Repair or Change File System' these are the results:

/system is 1476MB
/vendor is 0MB
/data is 0MB
"internal storage" says "Invalid partition selected"
/cache is 98MB
"Dalvik/ART Cache" says "Invalid partition selected"

Because internal storage and data are 0/invalid copying files to the device isn't possible. There is no storage available/detected when connecting via USB to a PC.

I tried the method of unbricking the N4 from this thread:
https://xdaforums.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
However the LGNPST program does not detect the phone when connected in download mode.

Is there any way to restore the partition table from inside TWRP with no access to the internal device storage? It looks like fdisk is installed in /sbin (though running 'sbin/fdisk -ul' reutrns nothing?), does anyone have the proper commands to issue to get the partition table back to stock?

Also, if I attempt to copy the logs, this error is in the output:
'Failed to mount '/data' (Invalid argument)'

Any ideas how to get out of this state?

Thanks!

The easiest thing to do is to go back to stock rom and start all over again, but this time in the right way.

.