Database Users

Dumping system.img.ext4?

I've managed to patch to MF3 without flashing bootloaders, modems, rpm, and without losing TWRP. All without rooting the device. What this means is, I now have a 100% stock MF3 system partition that I would like to dump into an odin-flashable tarball. To do that, I need to dump my system (while in recovery) to a system.img.ext4, using whatever method is normally used to create an odin-flashable file.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2277127
I wanted to get some feedback from Devs working on the I337, specifically. It appears that the command I want is this:
Code:
make_ext4fs -s -l 2760M -a system /sdcard/system.img.ext4 /system
But... where do I determine what size I need?
Many thanks.

Aou said:
I've managed to patch to MF3 without flashing bootloaders, modems, rpm, and without losing TWRP. All without rooting the device. What this means is, I now have a 100% stock MF3 system partition that I would like to dump into an odin-flashable tarball. To do that, I need to dump my system (while in recovery) to a system.img.ext4, using whatever method is normally used to create an odin-flashable file.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2277127
I wanted to get some feedback from Devs working on the I337, specifically. It appears that the command I want is this:
Code:
make_ext4fs -s -l 2760M -a system /sdcard/system.img.ext4 /system
But... where do I determine what size I need?
Many thanks.
Click to expand...
Click to collapse
I might have found my own answer:
Code:
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table

No go. Perhaps I'm packaging it wrong? Perhaps I'm not pulling the image correctly?
Here's Odin's log:
Code:
<ID:0/020> Added!!
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020> Firmware update start..
<ID:0/020> system.img.ext4
<ID:0/020> NAND Write Start!!
<ID:0/020> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Here's what the screen said:
SECURE CHECK FAIL : system
Here's how I dumped the system (in adb shell while in recovery with /system and /cache mounted):
Code:
make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
make_ext4fs -s -l 2170552320 -a cache /sdcard/cache.img.ext4 /cache
(the above number of bytes were obtained using fdisk against the partitions)
And here's how I packed them into the Odin-flashable tarball:
Code:
tar -H ustar -c system.img.ext4 cache.img.ext4 > mf3.tar
md5sum -t mf3.tar >> mf3.tar
mv mf3.tar mf3.tar.md5
Does anyone see anything wrong with this method? Odin Mode currently shows:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
- Root was never applied, kept the stock MF3 kernel, nothing's been touched in /system - everything 100% absolutely stock...

Check out this article:
http://androidforums.com/continuum-all-things-root/263953-how-make-custom-odin-images.html
Change the partition info to match that of i337

Craptain Krunch said:
Check out this article:
http://androidforums.com/continuum-all-things-root/263953-how-make-custom-odin-images.html
Change the partition info to match that of i337
Click to expand...
Click to collapse
That post is scary-old, though. Doesn't even mention ext4

Aou said:
That post is scary-old, though. Doesn't even mention ext4
Click to expand...
Click to collapse
I mainly linked it because the packaging commands are slightly different.

Craptain Krunch said:
I mainly linked it because the packaging commands are slightly different.
Click to expand...
Click to collapse
I see. I researched it a bit, and the "dd" method stopped working with the S3 and beyond. I tried it anyway, and Odin (on phone) failed, saying:
Unsupport dev_type
I am looking into this: https://github.com/Chainfire/sgs4ext4fs
But not sure if it applies.

Aou said:
I see. I researched it a bit, and the "dd" method stopped working with the S3 and beyond. I tried it anyway, and Odin (on phone) failed, saying:
Unsupport dev_type
I am looking into this: https://github.com/Chainfire/sgs4ext4fs
But not sure if it applies.
Click to expand...
Click to collapse
Check your PM sir.

I have never done this before, so I can't be of much help. The part I don't understand is why the size of the partition must be specified. My first question would be, does it need to specified accurately?
Even though this is for the Epic 4G, it may help
http://forum.xda-developers.com/showthread.php?t=2154762
It may allow you to do what you want without knowing the partition size since you would use a system dump as your source (see post #2).

upndwn4par said:
I have never done this before, so I can't be of much help. The part I don't understand is why the size of the partition must be specified. My first question would be, does it need to specified accurately?
Even though this is for the Epic 4G, it may help
http://forum.xda-developers.com/showthread.php?t=2154762
It may allow you to do what you want without knowing the partition size since you would use a system dump as your source (see post #2).
Click to expand...
Click to collapse
Thanks. Looking into this now.
By the way, the "sgs4ext4fs" program by chainfire seemed to do what it advertised, but still doesn't flash.
UPDATE/EDIT:
Code:
error: file_write: write: File too large
It seems that I can't use their method to create an ext4 file to add to the tarball... Still looking into it though...

Aou said:
Thanks. Looking into this now.
By the way, the "sgs4ext4fs" program by chainfire seemed to do what it advertised, but still doesn't flash.
UPDATE/EDIT:
Code:
error: file_write: write: File too large
It seems that I can't use their method to create an ext4 file to add to the tarball... Still looking into it though...
Click to expand...
Click to collapse
Sorry for lifting up an old thread, but did you eventually get it working? Thanks in advance.

Also would like to know
Sent from my ATT S4 MF3 using Tapatalk

jball said:
Also would like to know
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
The best I can remember it did not work. It resulted in an ODIN flash-able TAR that wouldn't flash due to the bootloader not being signed. It really doesn't matter anymore because there is a ODIN flash-able MF3 file available now.

Sorry I thought you were trying to push a version of TWRP.of course I use Safestrap but I would love to be able to use a straight up custom recovery.thank you for a reply
Sent from my ATT S4 MF3 using Tapatalk

tys0n said:
Sorry for lifting up an old thread, but did you eventually get it working? Thanks in advance.
Click to expand...
Click to collapse
scott14719 said:
The best I can remember it did not work. It resulted in an ODIN flash-able TAR that wouldn't flash due to the bootloader not being signed. It really doesn't matter anymore because there is a ODIN flash-able MF3 file available now.
Click to expand...
Click to collapse
scott14719 is correct - the only images I was ever able to create were not accepted by the device due to signatures.
So there's an MF3 odin out there now? I haven't been paying attention. That's awesome.

Aou said:
scott14719 is correct - the only images I was ever able to create were not accepted by the device due to signatures.
So there's an MF3 odin out there now? I haven't been paying attention. That's awesome.
Click to expand...
Click to collapse
Ok, thanks. I was just asking because sm-g730a is also without official firmware. Trying to find a way to make one

tys0n said:
Ok, thanks. I was just asking because sm-g730a is also without official firmware. Trying to find a way to make one
Click to expand...
Click to collapse
Gotcha. Check out my other thread here: http://forum.xda-developers.com/showthread.php?t=2378946
Look at File #5 and File #6. Might guide you in the right direction. These "Odin-flashable" files don't actually work on the I337 because of the signature verification that's built-in the bootloader, but perhaps you might have better luck on the other device. As always, be careful doing any of this stuff.

[DEV] Recover of EFS without Backup

Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired

darkspr1te said:
Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired
Click to expand...
Click to collapse
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks

I'm curious with the solution..
Cause many people had problem with efs and not having efs backup...
Sent from my GT-N7100 using xda app-developers app

starscream0 said:
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks
Click to expand...
Click to collapse
I've only just got my first bricked S4 in yesterday and only completed it's screen replacement today. The screen is only damged due to owner giving up on it and litting it sit on his desk util something was dropped on it.
Anyway, my point of this is I am not ready to do S4 debrick as I 'am still working on S3.
The key behind my 'possible' recovery method is my solution involves searching for certain MAGIC's in the /EFS backup and also knowing exactly where in the efs image data would be.
For example, key areas of a EFS are in the same sector of the memory each time when looking at a mmcblk0p3 backup image,
i will use mac address as a example.
in the 5 so far efs backups i've examined the mac address is at offset 0x30000, so even if you cannot read the actual efs partition and using fsck on the mmcblk0p3 fail, my part one trick involves just going to 0x30000 and reading the data back. without the efs file system being involved. The same trick i used to recovery the blown boot sector and partition table of the SHV-E160L.
the second trick is to look for keywords within the backup img, example lets say the IMEI always had 0xAA 0xAA 0xAA before it, and the data required was 400 byte, we simply look for 0xAA 0xAA 0xAA in the file and copy it and the next 400 bytes.
the final trick I wont release yet, jumping the gun (as people do) will result in a JTAG brick, it's not perfect, its not a one click solution that we all want, but it's early days yet, but the method does work, i've 5 sammy's in front of me to prove it.
My rep in the Korean galaxy note section should prove I am not threading for likes too
Final note, Its a work in progress and I am using the forum to post my thoughts and look for Guinea pigs and attract other developers to documents the Samsung /efs system.
I am aware that parts are hashed and encrypted, the goal is not decrypting it but to recover the information to revive the device.
I am expecting users to share their /EFS backups with me, but I will not share those files with others to protect the users IMEI,
my issue is i don't have enough differing /efs files to build a bigger picture, what if the file locations was just luck ?
oh, if anyone has a copy of testdisk for arm, please share, i am fighting to get it to compile for arm-eabi-none- grrrrrr.
darkspr1te

Another note: I've not taken into account fragmentation of data in my above post, i was keeping that out of it for now, but i am aware of the EXT2/3 file table setup, how nodes can be split up.

Repartitioning the internal/app partition

I have a Eonon GA2114 (Android 4.4.4 RK3188 KLD) ROOTED car stereo.
I have searched this forum and cannot find what I am looking for so hoping someone can help or point me in the right direction?
I don't have many apps installed, but it seems as though the latest updates to Google, Maps, Sygic, etc. has resulted in an "insufficient storage" alert. I am quite happy with the stock ROM and don't really want to update to some of the custom ROMs that are available, but I do have a very technical background and have only ever owned Android devices.
Does anyone know or can point me towards instructions to change the system partition size? The system ships out with more than 8GB of internal space that I do not use and so would like to either repartition to a single large partition or reverse the size.
Thanks

I think you mean the /data (userdata) partition, and i'm pretty much in the same seat.
Got a brand new 16gig device that ships when a lousy 1gig of /data to store apps on, talk about drunken monkeys making the rom
got about 10 gig on the internal_sd that i'm guessing could be used instead.
I might try to remap that later, i guess you could root it and then either make a symblink there or look at the fstab and see if you could just remount it.
Could also flash Malaysk rom with gives you 2 gigs of userdata, not much more but alot better than 1gb

Yes, I mean the /data (userdata) partition and I checked, while driving to work, I actually have 13GB of userdata. I haven't used this space, but knew it was there when exploring the system when I first got it and for some reason I remembered 8GB. Regardless of the size, it's a waste of space if not utilised.
The system is already rooted.
I have considered Malaysk ROM, but I quite like the stock ROM, especially after installing my preferred launcher. I have already decreased the dpi from 240 to 180 so a lot better looking and a lot more screen space. Have got rid of bloat and so have a stock ROM to my liking.
These systems are well known for their mic troubles and I have taken this up with the manufacturer as I do work in the computer industry, but identifying electrical components and soldering is not something I am too confident with. The manufacturer did however, send me an updated update.img file. I've installed this and it made some improvement, but nothing so significant that I have actually started using the mic. It also has a new wallpaper and noticed that the default apps have been updated, but not sure how?
Anyway, if I don't like Malaysk I can revert back using the update.img file the manufacturer gave me, but 2GB still isn't enough. Hence, wanted to know how to do this myself.

Found this post: http://forum.xda-developers.com/gal...od-increase-partition-size-t3011162?nocache=1 by gsstudios
Obviously, connecting my system to a PC is not as easy and was wondering if anyone would know a bulletproof method of applying the instructions to my system given that it is a stereo with different hardware to a phone?

In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.

I also found a way to choose where the apps get installed, google a bit for "adb shell pm set-install-location" I belive #1 would be the right choice here.
If that works to redirect everything to the big partition it would be a wonderfull solution.
Download a terminal for the rom and type in there instead of having to connect a computer to the HU etc etc.

Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
I would prefer rickthecabbie's solution, but in order to unpack the IMG file, I would need a Linux system (I have tried on Windows and couldn't do it). If all else fails, I'll dual-boot my PC or get a VM if that works? I would be really grateful if you can point me towards a tutorial/instructions if you know any or get the time, but appreciate your help as at least I've got somewhere to start my "Googling"

Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk

lotherius said:
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I asked the guys I bought the stereo from; if they had released an updated ROM or if they can provide me a download for the existing ROM. Their customer service so far, has been excellent; their English is not great and it can take a little extra time sending and waiting for messages, but they gave me a link.
At least, I know that if I mess things up, but haven't bricked it, I have got something to revert to.
You could try asking the seller/manufacturer for a link to the stock ROM?

rickthecabbie said:
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
Click to expand...
Click to collapse
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.

tariqkhan.co.uk said:
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
Click to expand...
Click to collapse
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.

Hey rickthecabbie, that would be awesome.
Do you have the parameter file by any chance?
I recently made a change to the screen density. I have an 800x600 system and you can only fit 2 rows of icons across the screen so changed the build.prop file to 180dpi and now it looks much like a normal tablet. Having restored the system after making this change; it restored with my changes to the build.prop file intact. I was thinking, could I possibly do the same? I can modify the parameter file using ES Explorer/Terminal and then restore the system, which should update the partitions?
Saves on all the packing and unpacking and mainly; installing dual-boot/debian on my Windows PC.

tariqkhan.co.uk said:
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
Click to expand...
Click to collapse
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.

treech said:
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
Click to expand...
Click to collapse
Yep, thought it would be something simple. Do you know of a command which would print which partition 0 and 1 and 2 is?
Don't really want it to set the install location to a partition that I wouldn't want it set to. Also, some apps are not movable so I don't think this would solve the issue right?

Not sure, you'll have to google it
And well best is to install a few bigger apps and see what happens i guess.

rickthecabbie said:
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Click to expand...
Click to collapse
I don't mean to bug you and do appreciate the advice so far, if you haven't got time to do the tutorial, do you know of a link to an existing tutorial?

Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230

jbleasdale said:
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
Click to expand...
Click to collapse
Thanks for the link.
Gave it a go and didn't work for me; I'm sure I've made a simple mistake somewhere although I tried twice.
As my system had already been wiped, I thought I would give DSA ROM a go and for anyone looking for a stock ROM, this is perfect. Any MODS included are a necessity in my opinion and some you will probably not even notice, but it has the 2GB system partition.

N9005 changing boot name img param.bin

Hi all I've read some guide to extract param.bin with terminal emulator but nothing work. Anyone give me the correct procedure to extract param.bin modify boot image and save it?
Thanks.

freejtd said:
Hi all I've read some guide to extract param.bin with terminal emulator but nothing work. Anyone give me the correct procedure to extract param.bin modify boot image and save it?
Thanks.
Click to expand...
Click to collapse
Maybe you are querying the wrong block. Try this :
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/param.bin

zlazaar said:
Maybe you are querying the wrong block. Try this :
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/param.bin
Click to expand...
Click to collapse
I've tried that block but it's 10mb
The dimension of param.bin it's about 1mb right?
P8 block is 530 kb
Really I don't know what is right block to export.

freejtd said:
Maybe you are querying the wrong block. Try this :
I've tried that block but it's 10mb
The dimension of param.bin it's about 1mb right?
P8 block is 530 kb
Really I don't know what is right block to export.
Click to expand...
Click to collapse
Size is different on each device.
On the S4 for exemple, it's about 4mb.
According to the stock partition table of N9005, param is located on 10th block.
Edit: you can also use ibs, obs or bs options of dd command to limit the size dumped from that partition.
The content never occupy the exact full size of a partition.

zlazaar said:
Size is different on each device.
On the S4 for exemple, it's about 4mb.
According to the stock partition table of N9005, param is located on 10th block.
Click to expand...
Click to collapse
Ok well I will try add new boot img in block p10. I've read a guide for note 4 but when launch tar command it give me error. I'm not expert, simply follow guide at letter.
Do you have another type of command to add new img on param.bin?
Thank you for reply at this thread it's most appreciated.

freejtd said:
Ok well I will try add new boot img in block p10. I've read a guide for note 4 but when launch tar command it give me error. I'm not expert, simply follow guide at letter.
Do you have another type of command to add new img on param.bin?
Thank you for reply at this thread it's most appreciated.
Click to expand...
Click to collapse
Can you please explain what do you want to do exactly.
The only boot.img i know is the kernel it self.

zlazaar said:
Can you please explain what do you want to do exactly.
The only boot.img i know is the kernel it self.
Click to expand...
Click to collapse
Just changing img note 3 with img note 7. When you boot device you see the name..

Look at this http://forum.xda-developers.com/note-4/themes-apps/tutorial-edit-note-4s-boot-splash-screen-t3223157

freejtd said:
Just changing img note 3 with img note 7. When you boot device you see the name..
Click to expand...
Click to collapse
The guide is very clear, use the provided script if needed.
Make sure you replace 08 by 10 in block name.
Your modified image must be =< 200kb and exactly 1920x1080px.
Sorry can't help more.

Thanks for your help.
I tried block p8 tar xf give me error.

freejtd said:
Thanks for your help.
I tried block p8 tar xf give me error.
Click to expand...
Click to collapse
Take a look here : http://forum.xda-developers.com/showpost.php?p=47675405&postcount=35

zlazaar said:
Take a look here : http://forum.xda-developers.com/showpost.php?p=47675405&postcount=35
Click to expand...
Click to collapse
Thank you I can't untar param.bin it give me error I think isn't my job :crying:

freejtd said:
Thank you I can't untar param.bin it give me error I think isn't my job :crying:
Click to expand...
Click to collapse
Install Busybox (if not already done) then use "busybox tar" instead of "tar"

zlazaar said:
Install Busybox (if not already done) then use "busybox tar" instead of "tar"
Click to expand...
Click to collapse
Installed busybox untar not working
Invalid tar format.
Ahhh my patience it's ended grrrr

ls -l /dev/block/platform/msm_sdcc.1/by-name
will show you the right block.
block 10 is right.
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
i pulled it and opened it in a hex editor. it's empty.
any more ideas?

I have no ideas. Just follow guide but nothing to do.

freejtd said:
I have no ideas. Just follow guide but nothing to do.
Click to expand...
Click to collapse
The last time I read in note 4 forum it's only for exynos.
Sent from my SM-G925F

Rosli59564 said:
The last time I read in note 4 forum it's only for exynos.
Sent from my SM-G925F
Click to expand...
Click to collapse
:crying:

@freejtd If I remember correctly, you once posted on Phronesis rom thread that you have the note 7 param.bin file. I would like to have that, I'm gonna try to edit Note 3 param.bin with Note 7. I'm also stuck a param.bin untar. I have no errors everything goes perfect but I get no images in param folder (strange). But I'm still trying and need note 7 param.bin

immi said:
@freejtd If I remember correctly, you once posted on Phronesis rom thread that you have the note 7 param.bin file. I would like to have that, I'm gonna try to edit Note 3 param.bin with Note 7. I'm also stuck a param.bin untar. I have no errors everything goes perfect but I get no images in param folder (strange). But I'm still trying and need note 7 param.bin
Click to expand...
Click to collapse
open param.bin with a hex editor. it's empty. this is why you don't get anything after untaring. logo must be located elsewhere i guess. but maybe param.bin from another model would be helpfull for finding the data we are looking for.

PIT for 1GB /system partition

I would have posted this in Android Development, but apparently I lack the rank to do so. Maybe a mod can move there it if it is more appropriate?
Need a larger /system partition for newer ROMs? The attached PIT file will push you up to 1GB. Not including instructions, PIT files are for advanced users and crazy dumbasses like myself only! If you don't know what it is or how to use it, you're in the wrong place.

HiltonJ said:
I would have posted this in Android Development, but apparently I lack the rank to do so. Maybe a mod can move there it if it is more appropriate?
Need a larger /system partition for newer ROMs? The attached PIT file will push you up to 1GB. Not including instructions, PIT files are for advanced users and crazy dumbasses like myself only! If you don't know what it is or how to use it, you're in the wrong place.
Click to expand...
Click to collapse
Thanks for the 1G pit file. Needing some instructions.
Despite being new to this android "guts tweaking",
I have followed successfully your guide "Stable AOSP 7.1 setup w/ working Google and Voice - ACHIEVED!". It worked fine (no 1Gb /system repartition, as you advised). Many thanks for that.
However, after a while my GT-P7500 /system partition got full (568Mb), and could not install the xposed framework mod.
Could you please post some guidelines on how to clean flash the @decatf AOSP Nougat 7.1, onto the GT-P7500, including the 1GB expansion, through this pit file.
Thanks.

HiltonJ said:
I would have posted this in Android Development, but apparently I lack the rank to do so. Maybe a mod can move there it if it is more appropriate?
Need a larger /system partition for newer ROMs? The attached PIT file will push you up to 1GB. Not including instructions, PIT files are for advanced users and crazy dumbasses like myself only! If you don't know what it is or how to use it, you're in the wrong place.
Click to expand...
Click to collapse
I'm in desperate need of help because at first i was able to flash the pit file but then now when i flash it gives me an error telling write complete repartition failed. any ideas?i really have tried for many hours ussually i can manage to load twrp or clockwork mod recovery or any custom rom but now all i can do is just get to the download function to use odin..... even recovery is not available to me...help pls.