Related
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:
Hi @all
To extract a PIT file from a device like the Note 2 N7100 16GB we can use this on terminal emulator:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176'
and we have the out.pit on Sdcard.
Is good if we use the PIT Magic from @lyriquidperfection DEV. Thanks.
We can extract the pit file to see inside whit this tool.
To Note 3 N9005 32GB:
That command is not compatible. It make also a out.pit but the PIT Magic give us an error and not extract it.
The parameters bs, count and skip must be different to a Device from 32 GB. (The partition is same).
Someone know something about?
The Leaked Rom XXUBMH1 have one Pit file 32 GB, see HERE. The PIT Magic extracted it well, attached #1.
To compare, the Pit extracted from the N7100 16 GB on attached #2.
You can see here more info about this to S4 Mini:
http://forum.xda-developers.com/showpost.php?p=47280556&postcount=10
Thank You
Hi @all
I wait a response about this.
Thank You
I have it now whit this THREAD.
Can someone with rooted stock OK3 (and OK3 bootloaders) please do the following for me?
-busybox dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=1024 count=81920
-alternatively you can run this file in recovery which will dump the necessary files to /sdcard/Unbrick_files/: https://androidfilehost.com/?fid= 23578570567721355
-Upload the unbrick.img and send it to me
here are the guides that I am following (which have some precedent for working with SGS5):
http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419
I recently bricked my phone by accidentally flashing a BOD5 bootloader over a rooted OK3 (and OK3 bootloader) system. This obviously led to a hard brick, and I'm trying to see if I can fix it. Thanks.
I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.
CVertigo1 said:
I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.
Click to expand...
Click to collapse
jrkruse helped me out a lot and I was able to get my hands on an OK3 unbrick.img. IT WORKS. You're right about me posting the wrong code. The file that he used to get me the unbrick.img included the following code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000;
busybox gzip /external_sd/Unbrick_Files/*;
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258
Hariiiii said:
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258
Click to expand...
Click to collapse
you have linked the unbrick-creator.zip rather than the BOK3 unbrick.img
I am almost in the same situation as you. Can you please write the steps and the link for the BOK3.img ?
I think this is the correct link to the BOK3 unbrick img. You'll have to scroll down to the mediafire link
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/page11
Flash the file using win32diskimager.exe onto a microSD and boot into download mode.
Hope that works.
Also, if anyone has a rooted OG5, I would really appreciate an OG5 debrick.img!
Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.
CVertigo1 said:
Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.
Click to expand...
Click to collapse
Yes it does work, I can personally confirm it.
That's great!!! I'm assuming you were on the BOE1 bootloader, right?
CVertigo1 said:
That's great!!! I'm assuming you were on the BOE1 bootloader, right?
Click to expand...
Click to collapse
Yeah, that one is still used for the OK3 firmware, yeah?
Thanks for confirming that I did that right guys
jjdavis699 said:
Thanks for confirming that I did that right guys
Click to expand...
Click to collapse
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...
Hariiiii said:
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...
Click to expand...
Click to collapse
It's fine mate. Just enjoy your reinvigorated phone. I just did the file as something to waste a little time. Glad to see its working fine.
I need the baseband file for m8952_70009.08.03.48b.
Someone please check if they have BASEBAND VERSION as m8952_70009.08.03.48b in settings>aboutphone.
if u have it..
then on terminal emulator
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/NON-HLOS.bin
you will get a file named NON-HLOS.bin in sdcard.. upload it somewhere are ping here.
Your help is much appreciated...
You needed to say what model is expected to have that baseband, just to restrict the circle of "suspects". My US retail has " .45R" in the end.
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.