Database Users

Is there such thing as "Upload Mode?"

Yeah, so that.

Ya its called mass storage mode.
LOL

Is that what you'd use if you wanted to make a tar of your setup?

The Root said:
Is that what you'd use if you wanted to make a tar of your setup?
Click to expand...
Click to collapse
Hmm...
Make a tar on the phone?
I guess you could system dump your setup?
Or stick all your mods in the rom flash like i do and then restore with titanium.
Sorry i couldn't help i was just joking around.

You can use adb to make direct, bit-for-bit copies of each partition using the dd command, I just can't remember the exact format of the command. But the phone doesn't have a built-in method to do the reverse of what download mode is used for (although I'm not sure what Odin's dump option does, sounds like the right idea but I've never seen a how-to, and, of course, we've always been advised to uncheck all but auto reboot)
Try a google search for "xda epic 4g" and keywords pertaining to making your own odin flashable (using xda as a keyword yields more results from the forum, and using google instead of xda search yields results that actually contain the key search terms, lol). I learned of this from a thread somewhere around here, just can't recall where. Oh, and maybe it would be better NOT to include Epic, I'm starting to doubt myself as to whether the thread was in our section... Hope that helps you find what you're looking for
Sent from my SPH-D700 using XDA App

There is a "kernel panic upload mode" that various Samsung devices can get trapped in after a kernel panic. I've not seen it happen on an Epic, but that's not what you're asking about.
You can dump the flash partitions using adb. It's best done in recovery with the file systems mounted read-only, to guarantee that they're in a consistent state. While you can do it from Android, inevitably changes (particularly to /data) will be made underneath you while dumping, which is bad for restoration.
Anyways, in order to make a proper dump you need a recovery that spawns the adbd service with either ro.secure=0 or ro.debuggable=1 set in default.prop. I think ClockworkMod does this, but it's been a long time since I used it.
Boot into recovery and connect your phone up to USB. Run "adb shell" and make sure you have a root shell ("#" prompt). If you have a user shell ("$" prompt), try running "adb root", wait, then run "adb shell" again. Once at the root shell prompt, run:
Code:
mount -ro remount /dev/block/stl6 /mnt/.lfs
mount -ro remount /dev/block/stl9 /system
mount -ro remount /dev/block/stl10 /data
mount -ro remount /dev/block/stl11 /cache
mount -t vfat /dev/block/mmcblk0p1 /sdcard
mkdir /sdcard/dump
cd /sdcard/dump
sync
cat /dev/block/bml1 > boot.bin
cat /dev/block/bml2 > ries.pit
cat /dev/block/bml4 > Sbl.bin
cat /dev/block/stl6 > param.lfs
cat /dev/block/bml7 > zImage
cat /dev/block/bml8 > recovery.bin
cat /dev/block/stl9 > factoryfs.rfs
cat /dev/block/stl10 > datafs.rfs
cat /dev/block/stl11 > cache.rfs
cd /
umount /sdcard
mount -wo remount /dev/block/stl6 /mnt/.lfs
That remounts all the stl partitions read-only, mounts the SD card, creates /sdcard/dump, dumps all the partitions, unmounts the SD card, and remounts /mnt/.lfs read-write so the phone will reboot properly. At this point you can reboot and once in Android, copy the dump folder over to a computer.
From here you can create a .tar containing the partitions that you want to flash with Odin/Heimdall. In Linux or Cygwin, that would be:
Code:
tar cf foo.tar zImage recovery.bin factoryfs.rfs datafs.rfs cache.rfs
.
You could include param.lfs, but it's not worth restoring unless corrupt, and if it's corrupt it's probably better to grab the version from the latest stock tar. I also wouldn't flash boot.bin or Sbl.bin unless you absolutely have to, and again, I'd go for the stock tar versions.
Also, according to the Galaxy S wiki page, bml12 is supposed to contain modem.bin but I've never had success dumping it.
Disclaimer: I've never actually restored a dump with Odin/Heimdall--I haven't had the need to. But I believe the above should be all that's necessary.

All hail mkasick! Thanks for my daily education
Sent from my SPH-D700 using xda premium

JohnCorleone said:
All hail mkasick! Thanks for my daily education
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I know understand you "ocean of knowledge" metaphor lol
Sent from my SPH-D700

Thanks guys.

whoa I just got edjumicated! that's some detailed info. thanks
Sent from my SPH-D700 using XDA App

I think it should be manditory for mkasick to post once a day minimum
Sent from my SPH-D710 using xda premium

JohnCorleone said:
I think it should be manditory for mkasick to post once a day minimum
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed.
Posted by Mr. Z's Epic 4G Touch+Keyboard

Considering you can't dump the modem (with anything, bmlwrite, redbend_ua, dd) is it safe to assume you can't flash one to it?
remember to thank me if I was helpful

It might be possible to dump the modem, just not with the same method as regular flash partitions. But yes, I think all the modem image we have came from stock Odin tars.
As for flashing the modem, folks definitely do it with Odin. Samsung's recovery also contains a "write_firmware_image" function that a binary diff of the modem and applies it to the current firmware. It's not part of the AOSP recovery sources, so I don't know how it works.
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.

mkasick said:
It might be possible to dump the modem, just not with the same method as regular flash partitions. But yes, I think all the modem image we have came from stock Odin tars.
As for flashing the modem, folks definitely do it with Odin. Samsung's recovery also contains a "write_firmware_image" function that a binary diff of the modem and applies it to the current firmware. It's not part of the AOSP recovery sources, so I don't know how it works.
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.
Click to expand...
Click to collapse
I know you can flash with odin...I mean on-device (if thats a word?) tools. I started looking into the di18-ec05 update.zip. What is the difference between a modem.bin and modem_delta.bin? There seems to be a pretty hefty size difference

The delta contains just the diffs between modems.

mkasick said:
You can dump the flash partitions using adb. It's best done in recovery with the file systems mounted read-only, to guarantee that they're in a consistent state. While you can do it from Android, inevitably changes (particularly to /data) will be made underneath you while dumping, which is bad for restoration.
Click to expand...
Click to collapse
Yes, that was what I was thinking of - thanks for a *much* more detailed explanation, mkasick!
Sent from my SPH-D700 using XDA App

I posted a tutorial on how to mke an odin tar a loong time ago in general.. using dd instead of cat, same **** though...
Also modem patches are redbend bindifs full modems can't be flashed except in download mode.. they aren't actually in bml12, its some trickery involved, they are really in the nvram..
Also epic does have a kernel panic upload mode... little green guy and all, seen it a few times lol
Sent from my SPH-D700 using XDA App

mkasick said:
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.
Click to expand...
Click to collapse
There is an edify script assert for baseband version btw
Sent from my SPH-D700 using XDA App

Holy crap. I found upload mode. Kinda. Get your favorite file manger, and browse to /mnt/.lfs. TELL ME WHAT YOU SEE. Cuz I'm confused

N8000 PIT File - How to save your PIT file

Looking for the old bootloader of N8000 (sboot.bin) I also found what appears to be a rarity for our N8000: the Pit file (Partition Information Table)
1) N8000 - N8013 - PIT file
I examined it with a exheditor and I also found in what block of memory is in the N8000, and that is a small portion in /dev/block/mmcblk0 and exactly after 34 sectors of 512 bytes each, with a length of 2396 bytes,
Don't seems instead, like other cell or samsung devices, there is a dev \ block dedicated.
So now not only we have Pit file but you can also save the file pit of your N8000 and also of 8013
I was able to verify that the pit file I found is exactly the same pit file of my N8000!
I made (based on other examples) a batch file (I tested, but try it for yourself) that save your PIT file in the sdcard automatically by ADB commands; need to have super user rights .
Here the bat file for N8000:View attachment N8000_SaveMyPitFile.zip
Here batch file for N8013 View attachment N8013_SaveMyPitFile.zip
This is the adb commands used:
shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Here instead the file pit found in a Russian site: View attachment Note10_PIT.zip
I hope this will be usefull for those have bricked the N8000, even with the help of the bootloader file sboot.bin.
Here pit file of 8013 View attachment My-N8013.zip
2) N8020 - PIT file
For N8020 start address is the same of pit file of N8000, but has more lenght
This is the command dd for N8020
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8020.pit bs=1 skip=17408 count=2924
This the pit file of N8020 View attachment My-N8020.zip
This the bat file for extract Pit file View attachment N8020_SaveMyPitFile.zip
Edit:
Here can found firmware with every file for Odin (incluse old bootloader ) for bricked note (russian language) http://narod.ru/disk/63365822001.6b115b2c7e18ce43c43f68567fe4d915/GT-N8000_mgt.zip.html
Another thing: If you have last blocked samsung bootloader (sboot.bin), you must make downgrade of bootloader if you want that Triangle away reset count to 0 and not to 1; i have tested it!

Thanks for this (and the warning about the new bootloader and the flash counter!)

My N8000 was working normally on the latest official not rooted rom (N8000XXCMD1_N8000RBTCMD1_DBT) and all of a sudden on a normal restart it hang on the samsung screen & when i tried to put it in the downloading mode it gave me the following lines
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
i connected it to my laptop & the ODIN discovered it but when i tried to flash a rom it gave me an error related to the partition. Any idea how this can be solved please.
how can i use this 5 files rom to fix this problem...should i just flash all the files at once through ODIN (and should i include the bootloader)...i really need help here please

dool2002 said:
My N8000 was working normally on the latest official not rooted rom (N8000XXCMD1_N8000RBTCMD1_DBT) and all of a sudden on a normal restart it hang on the samsung screen & when i tried to put it in the downloading mode it gave me the following lines
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
i connected it to my laptop & the ODIN discovered it but when i tried to flash a rom it gave me an error related to the partition. Any idea how this can be solved please.
how can i use this 5 files rom to fix this problem...should i just flash all the files at once through ODIN (and should i include the bootloader)...i really need help here please
Click to expand...
Click to collapse
Can you post the report of Odin?

Added in the first post PIT file of N8020

ghibli3 said:
Can you post the report of Odin?
Click to expand...
Click to collapse
here it is
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Can't open the serial(COM) port.
<ID:0/021> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!

Can you put pit file to n8010

dool2002 said:
here it is
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Can't open the serial(COM) port.
<ID:0/021> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
Click to expand...
Click to collapse
I would try this:
downloaded the file that the link at the end of my first post
You have all in that file: the file pit, modem, bootloader and csc ECCC ... you need to enter in odin each file in the right place; the language is Russian; check repartition so you save the file pit on your N8000
See if you can flash so...
If you have a locked bootloader,It may be that you are unable to flash it; in which case you will need to downgrade the booloader via adb
Ok?

bilal.23 said:
Can you put pit file to n8010
Click to expand...
Click to collapse
You can do by yourself.
Use Framaroot for simple and quick root: with framaroot: you can root and unroot in one click; no new recovery need, your status is always official!
If you have recent firmware framaroot works with the last two options
With your N8010 rooted you can use the bat file in the first post of N8000 and send me
I can look it with an exheditor and tell you if is good and completed, so i can add in the first post your pit file of 8010!

ghibli3 said:
I would try this:
downloaded the file that the link at the end of my first post
You have all in that file: the file pit, modem, bootloader and csc ECCC ... you need to enter in odin each file in the right place; the language is Russian; check repartition so you save the file pit on your N8000
See if you can flash so...
If you have a locked bootloader,It may be that you are unable to flash it; in which case you will need to downgrade the booloader via adb
Ok?
Click to expand...
Click to collapse
i tried to flash them but it still fails...how can i downgrade the bootloader via adb?

dool2002 said:
i tried to flash them but it still fails...how can i downgrade the bootloader via adb?
Click to expand...
Click to collapse
You can use this batch file View attachment 1971542 that write via adb only theold bootloader sboot.bin (german bootloader)
These are the command via adb (thank to Odia xda-user) for all three file sboot.bin tz.img and param.bin
you can look in this post for S3 http://forum.xda-developers.com/showthread.php?t=2081748
> adb push sboot.bin /sdcard/sboot.bin
> adb push tz.img /sdcard/tz.img
> adb push param.bin /sdcard/param.bin
> adb shell
$ su
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
# rm /sdcard/sboot.bin
# rm /sdcard/tz.img
# rm /sdcard/param.bin
# reboot fota_bl

Can i save my .pit file on Galaxy S2 (GT-i9100G)?
Why this and are different?
N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
N8020
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8020.pit bs=1 skip=17408 count=2924
Which command i should use?

Honestly, in our case I'd save the entirety of /dev/block/mmcblk0 somewhere, just-in-case. You can pick out the PIT later, but this way you're covered all ways.

8010 PIT
ghibli3 said:
You can do by yourself.
Use Framaroot for simple and quick root: with framaroot: you can root and unroot in one click; no new recovery need, your status is always official!
If you have recent firmware framaroot works with the last two options
With your N8010 rooted you can use the bat file in the first post of N8000 and send me
I can look it with an exheditor and tell you if is good and completed, so i can add in the first post your pit file of 8010!
Click to expand...
Click to collapse
Here my N8010 16GB PIT file. Can you check it and it to the first post then.
Thx

GeeKey said:
Here my N8010 16GB PIT file. Can you check it and it to the first post then.
Thx
Click to expand...
Click to collapse
Your file is too much big
Looking your pit it seems have the same size of N8000 so you must use the same command for N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Please use this command and repost your pit file to confirm it

ghibli3 said:
Your file is too much big
Looking your pit it seems have the same size of N8000 so you must use the same command for N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Please use this command and repost your pit file to confirm it
Click to expand...
Click to collapse
Anyone got a PIT file for the 8013? I've looked everywhere. My tablet gets into Odin and nothing else. Won't flash any rom, keeps saying that there's no PIT partition. I even tried flashing a 8010 PIT file out of desperation, but it failed with the same message.
Help?

Dileas said:
Anyone got a PIT file for the 8013? I've looked everywhere. My tablet gets into Odin and nothing else. Won't flash any rom, keeps saying that there's no PIT partition. I even tried flashing a 8010 PIT file out of desperation, but it failed with the same message.
Help?
Click to expand...
Click to collapse
How have you tried flashing pit file? By Odin?

ghibli3 said:
How have you tried flashing pit file? By Odin?
Click to expand...
Click to collapse
Yep, with Odin. And I tried all the usual steps. Made sure the port was USB2, installed a 32 bit version of windows, tried different ports, etc. At this point I think either I need the 8013 pit file, or the MMC might be completely screwed.

in serious need of the n8013 pit if anyone has it

Have Your Pit file on Terminal Emulator. Type this:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/N80xx-out.pit bs=8 count=481 skip=2176'
This only to devices from 8 and 16GB. Not to 32 GB.
Attached the Pit analyzes from PIT Magic:

Anyone Please compile LP for T530NU

as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.

LGMONO said:
as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.
Click to expand...
Click to collapse
There are three different cyanogenmod 12 (lollipop) ROMs listed in the development section compatible with the t530nu which are all better than stock anyway. I have the exact same model as you and have been on lollipop for months now and loving it

i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks

LGMONO said:
i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks
Click to expand...
Click to collapse
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.

Dudash said:
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.
Click to expand...
Click to collapse
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.

thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m

moonbutt74 said:
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m
Click to expand...
Click to collapse
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)

thisisapoorusernamechoice said:
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)
Click to expand...
Click to collapse
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m

thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu

LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
moonbutt74 said:
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m
Click to expand...
Click to collapse
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight

LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m

thisisapoorusernamechoice said:
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight
Click to expand...
Click to collapse
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks

moonbutt74 said:
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m
Click to expand...
Click to collapse
Thank you i will try this and thanks to all that is participating in this thread.. i have a lg g3 i just updated to lollipop and i like it, but remember for you guys out there newbees so to say at least try and give support for AOSP and Cyan roms i am a huge fan. Give them devs the credit they work hard for

LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Chainfire said:
- Join the G+ community using the same Google account as you're using for Play on your phone/tablet here: https://plus.google.com/communities/116661625291346007584
- Sign up to receive the BETA versions from Play here: https://play.google.com/apps/testing/eu.chainfire.flash
- Use the link provided after sign-up to download the app. Note that it may take minutes to even hours before the provided link actually works.
Click to expand...
Click to collapse
Link to Chainfire's FlashFire thread: http://forum.xda-developers.com/showpost.php?p=59959596&postcount=1

LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Here
But try what moonbutt74 is saying first, he's smarter than I. I'm just thinking aloud about all the (probably almost certainly stupid) stuff I'm going to try to get this working

T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m

yeah the link on google play is dead lol

nevermind i got it thanks

moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
^^This guy is very smart ^^ i will try that as well i really wanna get these guys the lp for t530nu here in America we are being neglected with the official lollipop update samsung is slacking here i say less talk and more work for them people lol. we would probably all have our lollipop by now. jk

moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
Thanks M I'll get started once I get back from my daily run (I refuse to be a fat American stereotype :silly: )

modem.bin

Anyone know what block does the modem.bin write to?

azpunkster said:
Anyone know what block does the modem.bin write to?
Click to expand...
Click to collapse
do you mean "which partition does Odin write the "modem.bin" file to during flashes?
If so, then
ls -l /dev/block/platform/msm_sdcc.1/by-name
will give you the answer, e.g.
lrwxrwxrwx 1 root root 20 1971-06-12 13:06 modem -> /dev/block/mmcblk0p2
(Note that partition mapping is not universally the same on every phone; the above applies to the SM-N900V. It might be also true of other Note 3 variants, but you shouldn't take that for granted)
If you mean "when the code in modem.bin is running on the CP, where does it store its' private data?", well that's a different question altogether. I know that there are two partitions (can't remember right now but can find it in my notes if you like) that seem to get modified with jibberish every time the phone boots, but I don't think the answer to the 2nd question is completely known (it may involve the rpmb - a hardware "protected" area of the flash chip).
.

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.