Related
Similar to Adrynalyne's post, I would greatly appreciate anyone that could do this. What I am looking for is a dump from a completely stock system, the only requirement is that you be rooted. So, if ANYONE has a completely stock Continuum and would be willing to do this, that would be great. It would also be good to get this from both DJ20 and DL17 if possible, but even getting it from just one of the two would be great. Here are the steps to produce the files.
This is easiest to do via adb.
As root (#)
To backup the .lfs partition
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
To backup the kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
To backup the recovery partition:
Code:
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096
To backup the system partition:
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
To backup the dbdata partition:
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
To backup the cache partition:
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
Once you have the files, zip them together and upload them to a sharing site (Dropbox, MediaFire, Megaupload, personal webhost, etc.) and post a link to them. If you don't want the link in the public, feel free to PM me a link to download the file. Once we have these, it will be much easier to do development work, especially with the voodoo kernel. Thank you to anyone that follows this and sends files.
EDIT: Received stock DJ20, which is a definite plus. Now for DL17
is it possible to grab these from a non-activated continuum?
I still have that phone that won't boot if you end up with something you'd like to try... for now..buddy's leg is broken and he's not moving around too much right now.. plus he's been playing on a droid X...
dottat said:
is it possible to grab these from a non-activated continuum?
I still have that phone that won't boot if you end up with something you'd like to try... for now..buddy's leg is broken and he's not moving around too much right now.. plus he's been playing on a droid X...
Click to expand...
Click to collapse
It is possible as far as I know. The only thing this really requires is root access, the phone being activated shouldn't really do anything to the file dump. If you'd like to try to resurrect the dead phone, I'll be posting up a DJ20 Odin file later tonight or tomorrow morning that should hopefully work to fix it if all that is dead is the file system structure.
Yah,
it if nearly impossible to brick the galaxy s phones (as long as you see the samsung logo even for a second), because we can use odin.. The only problem is getting the files to flash to fix it xP
Dottat: since you are not using this phone, may you please allow us to use this device for our sake? We need a device to send to the devs
Please man, it would be much appreciated and, you would eventually get it back, so no worries <3
Well... this phone is due back to the carrier (surprised they haven't called for it yet).... so at this point i would just like to prove proof of concept on the recovery piece. Download mode is all this phone will do so i'll be curious to see where we get with the odin imnuts is posting tonight..
imnuts said:
Similar to Adrynalyne's post, I would greatly appreciate anyone that could do this. What I am looking for is a dump from a completely stock system, the only requirement is that you be rooted. So, if ANYONE has a completely stock Continuum and would be willing to do this, that would be great. It would also be good to get this from both DJ20 and DL17 if possible, but even getting it from just one of the two would be great. Here are the steps to produce the files.
This is easiest to do via adb.
As root (#)
To backup the .lfs partition
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
To backup the kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
To backup the recovery partition:
Code:
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096
To backup the system partition:
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
To backup the dbdata partition:
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
To backup the cache partition:
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
Once you have the files, zip them together and upload them to a sharing site (Dropbox, MediaFire, Megaupload, personal webhost, etc.) and post a link to them. If you don't want the link in the public, feel free to PM me a link to download the file. Once we have these, it will be much easier to do development work, especially with the voodoo kernel. Thank you to anyone that follows this and sends files.
EDIT: Received stock DJ20, which is a definite plus. Now for DL17
Click to expand...
Click to collapse
Unable to dump . Keep getting this error with each block.
sdcard
sdcard not sdram
PZ PZ
I have a DL17 I want to root the phone but i dont want to make my phone un-returnable if something were to happen to it. so My question is what does Verizon consider illegal software. Does this mean root and all Available after market roms. is it the same as buying a new car on loan and putting after market parts Rather.?
remotehunger said:
I have a DL17 I want to root the phone but i dont want to make my phone un-returnable if something were to happen to it. so My question is what does Verizon consider illegal software. Does this mean root and all Available after market roms. is it the same as buying a new car on loan and putting after market parts Rather.?
Click to expand...
Click to collapse
rooting does void your carrier warranty...but not your samsung warranty...
however if you unroot/return to stock before returning your phone for whatever reason thats fine, they wouldnt know
*if* you brick your phone (nearly impossible to do with odin files) and try and return after a mod/rom gone bad....thats a big no-no...and the reason carriers/oems are locking down devices.
read up on rooting and the pros/cons before diving in...but for the most part if you are careful...its safe
I know how I know how I'm pretty experienced I have rooted 5 phones including hero cdma a droid erris to touch pro 2 2 different carriers also some minor a developing a bit but the only thing is I don't wanna have to send it samsung is something
Sent from my SCH-I400 using XDA App
if something does go wrong because accidents do happen I just wanna make sure that the phone is
unrootable and that there are available stock odin files but other then that I would be more than happy to dump for you guys and I could possibly help with the dip in developing as well give me your instant messenger or phone number so we can get together
Sent from my SCH-I400 using XDA App
EDIT: i must've been high LOL!
i was wondering if anyone knows where i can get all of these as i sorta repartitioned the phone and lost everything on it. i can get it into download mode just fine just im missing alot of peices. it loads the factory.rfs fine but i think the bootloader is gone. i even managed to get it into clockwork but since the boot partition is kinda messed up it wont boot into anything else. since theres not a factory firmware that i can find im sorta stuck
I would like create a backup (of my entire system including boot image, data and system partitions. Is there any way I can do this without the CWM. The main reason is that I could return the phone to the original state in case if I have to return for service.
For my knowledge (and i have no knoledge! ) samsung accept rooted device on service (otherwise if the phone has broken screen it is not accepted)...but, if i were you, i would install cwm and make a nandroid backup of the whole system. If you want to have all of google system images(to restore original stock) you could set your sdk environment http://developer.android.com/sdk/index.html and download google images (bootloader, rom, radio) and put in a safe place (the SDK supply adb/fasboot which are tools that you would use to restore the google's files). that's the thread with these contents: http://forum.xda-developers.com/showthread.php?t=1366806 That's the standard (so yours) original stock files from google actually on your phone!
and also i advise you to follow these steps to save your /EFS partition (you never know) before flashing custom things, BUT IT REQUIRES ROOT: http://forum.xda-developers.com/showthread.php?t=1352371
BUT, if you don't want to install cwm, you could also see here: http://forum.xda-developers.com/showthread.php?t=1392310
Thank you. If I am right, msskip's tools will install the CWM onto my phone as well. I have just come across a guide for back-up without CWM <http://forum.xda-developers.com/showthread.php?t=1420351>. I am just not quite sure if it is the same full back-up as I get for the Nandriod or CWM. Does anyone have any experience with this?
The post you linked doens' backup /boot partition and recovery. So you can backup only /system and /data; you can obtain these EXACTLY files just downloading the google system (4.0.1 - 4.0.2 - 4.0.3) files (*.img estension) and you have the same result, plus you can get bootloader.img and recovery (evrything stock, meaning samsung galaxy nexus stock files)...these are in the post i linked and are the stock google images and these are the files that our phones has inside (also including system.img).
that' the explanation why i think that is basically useless to make a backup of /system and /data for warranty purpose, because google (or first phone users in november when the phone came out on the market) provied all .img that you need to revert (using fastboot) anytime your phone to a stock 'new'phone (which is your now, so in warranty!). Make, instead, a backup for the files and apps (apk) (usually /data) that you need if you want to try custom roms and then if you are not satisfied get back to stock...
To answer to your question, no is not the same kind of backup, you will lack /boot and recovery.
adding that you can use adb to generate .img by
Code:
cat /proc/mtd
and you will have a fs table with adresses (i have no phone now so cannot provide), then using dd (assuming boot is on mtd2):
Code:
dd if=/dev/mtd/mtd2 of=/sdcard/boot-stock.img bs=2048
and also use this for recovery partition...never tried for system and data partition (but could work, i'm not sure so not do that in this way, wait more knowing-knoledge people and also never tried on ics but, just ginger remembering...dont' know if it's the same in this new system)
but this process make use of
Code:
adb shell
su
the second one requires root....
as of now, i dont' now any method not involving root to make these things but as i stated at first post, i don't know anything
Thank you. I am wondering if the image file you have provided is for yakjuux. I have come across many posts that if I get the wrong baseband, the phone will not work correctly.
post, please, your baseband version which you can find on settings->phone info->basedand version in your phone; mine is 19250xxkl1 that i have recently updated from xxkk1 (the stock one)
My Build # is ITL41F I9250 UGKL1 and the kernel is 3.0.1-ga052f63 [email protected] #1.
Do you think you have a image of this? Thanks.
As far is i know, you have a GSM version of Galaxy Nexus. So it's safe to grab google image of /system, /boot and for the radio grab UGKL1 radio/baseband version. To better answear it's better to know also you bootloader version (which probably is primekk15): you can view this by going on bootloader on you phone doing this:
1 setup android sdk environment (include fastboot) for your pc system (windows-linux-osx)
2 enter in the settings menu of the phone and tic the 'debug usb'
3 attach the phone to the pc and let it recognize your phone (windows-osx), for linux install udev that already are in your distrib/repo
4 (assuming you are on windows) on pc... start/run/ cmd: the the terminal open up and go in your android-sdk directory, enter and then go to platform-tools; there is adb command, run: adb reboot bootloader
this will restart your phone in the bootloader menu. There, you have all of information you need...just write here your bootloader version (to have a confirmation) to understand which versione you need to download and put in a safe place in case of warranty-need...
Then wait someone better than me that knows how to make backup of all partitions without root (without exploit i think it's difficult to grant su access on the standard ics system); if there is no such possibility, just root, install cwm and do a nandroid backup and then trasnferr on a safe place on your place and you are good to go to try modding.....
now i need sleep as here is 8 in the morning and finishing compilemy l701x kernel which weight 3,4 mb lzo compressed, fine tuning.....good nite,ehm,good mornig..mmm... good is enough
Thank you. It takes some time to download the packages.
The Bootloader shows the following
Product Name: Tuna
Variant: Maguro
HW Version: 9
Bootloader Verson: Primekk14
Baseband Version: I9250UGKL1
Carrier Info: None
Signing: Production
What would be the appropriate to donload. Do you have their respective link? Thank you for your ongoing support.
Would anyone with experience please provide me with inputs if:
1. there is any way to back-up without root
OR
2. the phone has to be rooted, is there any way to have a program residing in my computer iso the phone (CWM in this case).
OR
3. there is any way to remove CWM and other rooted apps before I use GNex Toolkit to relock the phone.
Thanks.
Here you go:
http://forum.xda-developers.com/showthread.php?t=1420351
Would anyone with experience please help?
I am struggling with the same issue. Restoring the nandroid, removing su and superuser.apk and then relocking the bootloader actually brings the phone to quite factory looking mode (except for timestamps in system)
I wonder if it is possible to pull dump of system the same way it is done for boot and recovery.
Guys - it is pretty trivial to restore all partitions you would be modifying to factory conditions because Google provides the factory images for which you can use fastboot to restore. You don't even need to be unlocked much less rooted or have CWM installed because the Google images are official and have the correct signatures.
As for making image copies of your phones partitions this cannot be done w/o root access because these partitions are only available to root. If you are rooted you can use a utility such as dd on the phone to copy the partitions.
Sent from my Galaxy Nexus using XDA App
silow said:
Guys - it is pretty trivial to restore all partitions you would be modifying to factory conditions because Google provides the factory images for which you can use fastboot to restore. You don't even need to be unlocked much less rooted or have CWM installed because the Google images are official and have the correct signatures.
As for making image copies of your phones partitions this cannot be done w/o root access because these partitions are only available to root. If you are rooted you can use a utility such as dd on the phone to copy the partitions.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Google provides yakju images only. Phones here in Canada come with yakjuux which is even 4.0.1. It will be pretty obvious you have thinkered with your phone if you return it with yakju image instead the original one.
As for root - I think it might not be necesary - I was able to do nandroid backup without flashing neither recovery or root to my system by simply unlocking the boot loader and booting CWM off fastboot. I am thinking can we dd while in CWM (flash of phone still intact - except of bootloader which is not an issue since it can be relocked)
Anyone have the dd syntax handy and the partition that needs to be dumped?
system partition seems to be /dev/block/platform/omap/omap_hsmmc.0/by-name/system (this is the df output after I mounted it in CWM)
Would the dd command be something like
Code:
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/yakjuux.img
CWM provides you "root" because it has the su binaries in the ramdisk.
You can run the following when booted into CWM since CWM will mount /data:
Code:
dd if=/dev/block/mmcblk0p10 of=/data/media/system.img
leobg said:
[snip]
Anyone have the dd syntax handy and the partition that needs to be dumped?
system partition seems to be /dev/block/platform/omap/omap_hsmmc.0/by-name/system (this is the df output after I mounted it in CWM)
Would the dd command be something like
Code:
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/yakjuux.img
Click to expand...
Click to collapse
I think that may work. The output file may be padded with extra zeros, so you may need to trim them before flashing (this is certainly the case when you dump the radio).
EDIT: I would probably use this instead (although I am not sure it will make a difference:
Code:
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/data/media/yakjuux.img
efrant said:
I think that may work. The output file may be padded with extra zeros, so you may need to trim them before flashing (this is certainly the case when you dump the radio).
EDIT: I would probably use this instead (although I am not sure it will make a difference:
Code:
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/data/media/yakjuux.img
Click to expand...
Click to collapse
Yes, that was what I actually ended up doing since /sdcard was a sym link to /data/media. Resulting file is 654MB uncompressed. I wonder how can I easily check if content is right on a win machine.
---------- Post added at 09:44 PM ---------- Previous post was at 09:37 PM ----------
silow said:
CWM provides you "root" because it has the su binaries in the ramdisk.
You can run the following when booted into CWM since CWM will mount /data:
Code:
dd if=/dev/block/mmcblk0p10 of=/data/media/system.img
Click to expand...
Click to collapse
Yes, I meant it's not necessary to make any changes on the filesystem to achieve it once bootloader lock is off. And by simply relocking the device after, there are zero traces of any 'hackery' being done on the phone.
leobg said:
Yes, that was what I actually ended up doing since /sdcard was a sym link to /data/media. Resulting file is 654MB uncompressed. I wonder how can I easily check if content is right on a win machine.
Click to expand...
Click to collapse
There is obviously some extra padding in there, as the file size should be closer to half that size uncompressed.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
leobg said:
[snip]
And by simply relocking the device after, there are zero traces of any 'hackery' being done on the phone.
Click to expand...
Click to collapse
Not sure why so many people are worried about "traces of hackery". I can't speak from personal experience, but many Nexus One owners (if not all of who have attempted), had NO issues returning devices to HTC that were unlocked... Remember, the N1 did not have a relockable bootloader, so they obviously knew you were messing around.
You don't have to FLASH CWM to USE CWM.
Just BOOT CWM. Simple.
I'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
neph81 said:
I'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
Click to expand...
Click to collapse
Doing it now
Sent from my LG-P930 using XDA
https://www.box.com/shared/5ae03c2053bb25c0a840
there you go!
Sent from my LG-P930 using XDA
is the misc.img identical across all the ROMs?
Before I saw this thread, I had already uploaded my misc partition here: http://forum.xda-developers.com/showpost.php?p=28617084&postcount=16
The imgs aren't bytewise identical for whatever reason, so try both I guess.
scott0 said:
is the misc.img identical across all the ROMs?
Click to expand...
Click to collapse
got the answer elsewhere, thx anyhoo!
neph81 said:
I'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
Click to expand...
Click to collapse
what is the misc.img for?
I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?
Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.
kgalv419 said:
Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.
Click to expand...
Click to collapse
You need to update your recovery to its latest version. I recomend philz touch!
That's what I'm using bro
i have installed philz touch, so how do we downgrade bootloader?
That's all i want to know too? I know someone can figure it out
from my post in note 10 forum
kgalv419 said:
I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?
Click to expand...
Click to collapse
stewart30 said:
i have installed philz touch, so how do we downgrade bootloader?
Click to expand...
Click to collapse
this has worked on gt-p5210, gt-n8013 so it stands to reason it should work on the t210
keep in mind these instructions are in the specifics for the gt-n8013, adjust accordingly.
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb in recovery mode
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
edit-or pack it for recovery flashable
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
Click to expand...
Click to collapse
m
kgalv419; you can pull the original from your sister's tab if it's t210r , just don't screw it up.
Thanks a lot bro will get to work on it now and let u know how it went thanks again
i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?
kgalv419 said:
i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?
Click to expand...
Click to collapse
for my note 10 and for the tab 3 10
flash the fix first - provided you're absolutely certain you got it right.
then flash the rom though, i don't think you should any of the above for a tab
that doesn't really need a rescue. Just triple check every step before you perform it
and be deliberate and not impulsive. Good luck.
m
Thanks a lot moon
What exactly does the fix.img do moon?
kgalv419 said:
What exactly does the fix.img do moon?
Click to expand...
Click to collapse
k,
hey,
sorry to take so long in getting back to you,
please re-read my post in this thread about the procedure carefully, just to get your head in the game.
now, the reason for this approach to restoring original bootloader is because if you try to write the bootloader
via the dd command directly in normal operation and recovery the tab kicks back and reboots and in that
scenario you stand a VERY good chance of hard-brick, dead, done.
pulling/dumping from /dev/mmcblk0 for X=amount in MB has the same effect as a cloning procedure and seems to work
well, i have done this on my gt-n8013 and coached another user through the process for the gt-p5210 using the data i pulled
from my own tab and packeged for recovery flash. I am saying you should consider not doing this for a tab that isn't
soft-bricked to a degree that would make this exercise necessary. You may just need to use a different rom instead.
m
keep in mind you will need to re-flash a rom afterward. NOT and odin firmware but an appropriate xda recovery flashable
rom for your device.
Nexus 5 Repartition​
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you backup persist using terminal and dd comand and EFS
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~1G system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 5 Repartition, Tool/Utility for the Google Nexus 5
Contributors
Clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
HAMMERHEAD STOCK
Code:
25 192937984B 1266679807B 1073741824B system
26 1266679808B 1298137087B 31457280B crypto
27 1298137088B 2032140287B 734003200B cache
HAMMERHEAD MODIFIED
Code:
25 192937984B 1803551231B 1610613248B system
26 1803551232B 2065695231B 262144000B vendor
27 2065695232B 2097152511B 31457280B crypto
28 2097152512B 2306867711B 209715200B cache
4. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
5. To backup persist partition you need PC with installed adb. Boot your hammerhead in TWRP and plug to PC. Than use next commands.
Code:
adb root
adb shell
dd if=/dev/block/mmcblk0p16 of=/sdcard/persist.img
Than copy .img file from root of internal storage to your PC. Although, script doesn't affect that area, backup of this partition may help in case of any problems with mac address etc.
Thank you for this zip!!! It works fine but I used nano package gapps for the face unlock but still does not work on LOS 15.1. Any suggestions
Vendor partition means support for treble.... Right?
---------- Post added at 04:11 AM ---------- Previous post was at 03:44 AM ----------
After flashing a ROM the system partition resizes back to 1009mb...
Can this be fixed?
@sinkoo1979 try bigger gapps, alse, it may be Lineage problem.
@getrooted0019 you didn't read Installation part carefully, did you? You need to use resize option in TWRP to restore original size after flashing ROMs since they are build for 1G /system partition.
getting a message in twrp "this is not a nexus 5" and won't let me switch back to stock.
@sinkoo1979 send me your partition table in bytes
Clamor said:
@sinkoo1979 send me your partition table in bytes
Click to expand...
Click to collapse
Data and vendor partitions in my nexus 5 are 0mb and not present. System showing about 1028mb while cache is on 29mb.
Thank you for your help but can't change the cache storage back to stock. Can't access the internal storage in TWRP. I think I corrupted my partitions on the nexus 5. Nexus 5 boots into TWRP but can't access nothing. Tried to flash different rom with OTG but bootloops. Can't flash stock because the cache partition is too small.
@sinkoo1979 just stop. I'd ask you to create a telegram account and PM it to me here. I'll help you, just don't do anything
Clamor said:
@sinkoo1979 just stop. I'd ask you to create a telegram account and PM it to me here. I'll help you, just don't do anything
Click to expand...
Click to collapse
Thank you for your help
This is fixable! I was a noob and didn't resize my system partition after flashing rom. Flashed the hh repartition to go back to stock in the ua twrp and got a bunch of errors. Then flashed stock recovery and tried again. This is not a Nexus 5 popped up. The backup file is inside the flashable zip. I just used adb shell and parted to execute the commands listed in backup and viola my Nexus 5 is back. So those freaking out that they messed up their phone...don't worry it's fixable just listen to Clamor. Anyone can pm me too if you need help.
@typow102 if repartition pack says "It is not Nexus 5" than you shouldn't continue without asking here. Using scripts from pack on them own is dangerous as well. Currently I don't know how many types of MMC installed in our Nexus 5 and "It is not Nexus 5" on repartition or on returning to stock may indicate a new type MMC chip like it was with Nexus 7 (2013)
Clamor said:
@typow102 if repartition pack says "It is not Nexus 5" than you shouldn't continue without asking here. Using scripts from pack on them own is dangerous as well. Currently I don't know how many types of MMC installed in our Nexus 5 and "It is not Nexus 5" on repartition or on returning to stock may indicate a new type MMC chip like it was with Nexus 7 (2013)
Click to expand...
Click to collapse
That's the thing though It worked perfectly the first time I flashed it. No errors. Luckily I have had quite a bit of experience with terminal and parted so I felt confident in what I was doing. Can I help you in any way with this? There very well maybe a different mmc chip we don't know about yet.
@typow102 feel free to help if you are certain you can.
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
Do I need to resize the partition in twrp every time after flashing any ROM and then flash gapps package?
@bagajohny yeah, till devs decide to support it officially.
When I install the ROM (crDroid 4.6) after change the partitions, when I go to TWRP, Wipe > Advanced Wipe, selecting system and pushing over Repair or Change File System button and then over Resize File System, this message was shown:
Repairing system before resizing.
Repairing system using e2fsck...
Done.
Resizing...
/sbin/resize2fs /dev/block/mmcblk0p25 process ended with ERROR: 1
Unable to resize system.
So no resizing is made.
@froilson resize once more, if fails, change mounting state of system and try once more
@Clamor with this can we have treble support ?