Related
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
[Resolved ] I5800XXJPF - Custom ROM not booting
Hello eveyone,
It worked before I did a "Factory data reset" with the command
*#*#7780#*#*
best regards,
nsdroid said:
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
Click to expand...
Click to collapse
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
The Dark Lestat said:
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
Click to expand...
Click to collapse
1. Pack to tar "PDA.tar" all the file from factoryfs.rfs (system):
tar -H ustar -c cache.rfs datafs.rfs factoryfs.rfs zImage > PDA.tar
where the factoryfs.rfs is the modified one and other three are the same as in the original JPF's PDA file.
2. Sign the tar (the same name):
md5sum -t PDA.tar >> PDA.tar
3. Rename the tar as a file with extention tar.md5
mv PDA.tar PDA.tar.md5
best regards
When you mounted the rfs, it was mounted as vfat, yes? I doubt that if you modify it as vfat, it will still be a valid rfs. After all, it never was a real vfat file system, as a fsck.vfat will point out (it will throw a lot of errors if you run it on any rfs image). So the result of your modifications will probably be some file system which is neither a valid vfat nor a valid rfs.
Hi,
Thank you. You're right. It's more simple:root the phone, modify all you want, with
dd make an rfs image of the /dev/block/stl6 (system) and pack into pda.tar...
This way the files are not corrupted anymore.
best regards
Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.
it would appear Heimdall does not work on Windows Consumer Preview (zadig fails, saying the OS rejects unsigned drivers)
Good tutorial, thanks.
Is this tool only feasible for Samsung devices, or also for most other Android ones?
Two annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
By the way, your title seems to misspelled the keyword "heimdall".
factoryfs.rfs is the Factory installed filesystem and its the main rom
I have data.img... where I put it? datafs?
I am using heimdall frontend 1.3.1
what to do if wipe cache and recovery fail, the red text mount data? I followed all your steps but still stuck at samsung screen.
How to flash hidden.rfs by heimdall?
Sent from my GT-P1000
goofey2012 said:
How to flash hidden.rfs by heimdall?
Sent from my GT-P1000
Click to expand...
Click to collapse
--hidden hidden.rfs
zeroxia said:
annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
By the way, your title seems to misspelled the keyword "heimdall".
Click to expand...
Click to collapse
heimdall detect
zeroxia said:
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
Click to expand...
Click to collapse
heimdall print-pit --no-reboot
Thanks!!!
heimdall syntax / files confusion
Hello all.
I imagine this is a noob question but I am stuck and reluctant to flash random files in hopes of getting it right.
I have these files from an extracted tar.md5 (T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5).
I'm trying to use heimdall to restore a SGS3 (d2tmo/T999) with a Stock ROM without bumping the flash counter. I only use Linux, so...
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
SS_DL.dll (not needed, eh?)
system.img.ext4
tz.mbn
But I do not know what to do with the "*.mbn" files or the "NON-HLOS.bin"
I'm guessing the syntax is something like:
heimdall flash --primary-boot boot.img --cache cache.img.ext4 --recovery recovery.img --factoryfs system.img.ext4 ...
But I have a lot of files left over. Would someone kindly confirm that part is correct and fill in the rest of the blanks?
$ heimdall version
v1.4 RC1
Thank you for your time,
this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
https://github.com/Benjamin-Dobell/Heimdall/issues/82
look for the last comment
Thank you
priyana said:
this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
look for the last comment
Click to expand...
Click to collapse
Thank you -- and sorry about that.
I just saw the title and didn't pay attention to the device model.
My bad.
Jesus is a prophet
GoSooners345 said:
factoryfs.rfs is the Factory installed filesystem and its the main rom
Click to expand...
Click to collapse
Thanks alot will try
What will happen if in heimdall i choose the 512.pit file with re-partition ticked and flash my SGS?
Will i have to install a stock rom, then a GB and lastely the latest rom of my preference?
Send me link for zadig file .thqnkx in advance
Sent from my GT-P1000 using xda app-developers app
CM 10.1 flashing feedback
espionage724 said:
Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.
Click to expand...
Click to collapse
I flashed GT p1000 GSM through this method. CM10.1 4.2.2 worked really well. No bugs yet. Will feedback further.soon.
Mensreaorder out!
Great
Sent from my GT-I9300 using xda premium
please post a link to the required files
Hi...i downloaded heimdall, but was unable to find all the required files like dbdata.rfs, param etc... Please post a link containing the full package.
But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app
Details on the problem
priyana said:
But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app[/QUOTE
Hi Priyana. I'm using the Galaxy tab p1000 asian version. I was running cm 9.1 on it for the last 6 months without any problems, but recently tried out the bluetooth tethering and the software went into an infinite bootloop. I tried recovery by trying a full wipe, but when i tried to restore one of the old backups it all crashed again. My device is now able to go into download mode with power+vol down button combo. Also when the power button is long pressed, i get the Samsung galaxy tab frozen splash screen and on connecting the charger there is a battery icon but no charging progress.
Odin did not recognize the device despite waiting and watching as recommended, hence i tried flashing with heimdall 1.4 version and the GB stock safe rom by following the instructions. Device drivers get installed and heimdall detects my device.Was able to figure out the files and run Heimdall (my previous question is hence irrelevant), but to no avail. Am attaching the log after the Heimdall run. Please help.
Click to expand...
Click to collapse
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:
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Hi!
is everything works fine after you did this?
I have live demo unit, I'm afraid bricking it.
there is the possibility of making a video demo?
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me [/QUOTE]
Pics pleas??
Verstuurd van mijn GT-I9505
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
s4 demo unit
Deduxma said:
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
[/QUOTE]
please dose it mean my live s4 live demo unit will now behave like a normal phone and make or receive calls? after intalling this rom?
Help!
Just picked up a i9505x live demo unit.....does this process still work??
Demos don't have imeis do they I know our 3 s4s don't so calls can't be made
Sent from my GT-I9505 using xda app-developers app
s4sajii said:
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
Click to expand...
Click to collapse
Flash edited stock rom
Yes
Already did that. As described in the first post.
Br
Works but...
Everything works as it should but no WiFi.When flash Adam Kernel just get a black screen and that's it
I follow all the steps from the first post but at the end of odin flash i get FAIL . Any ideas?
Sirus2012 said:
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
Click to expand...
Click to collapse
i did it but i got this
Dj [email protected]ib ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
mastro:° said:
i did it but i got this
Dj [email protected] ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
Click to expand...
Click to collapse
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
stergios89 said:
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
Click to expand...
Click to collapse
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
mloc33 said:
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
Click to expand...
Click to collapse
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
stergios89 said:
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
Click to expand...
Click to collapse
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
stergios89 said:
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
Click to expand...
Click to collapse
True man, fingers crossed I suppose
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Sirus2012 said:
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
Well I think I figured it out with my S4 demo unit to make WiFi work.
All the steps were followed BUT...
I DIDN'T delete the two files(modem and NON-hlos) and continued with the procedure
The most important step was .17 which redirects you to another thread about TWRP and Adams Kernel...
Following the steps there where enough to solve my issue.
And now my WiFi works pretty good(so far so good at least for the last 2-3 hours )
Let me know if it worked for you too!
Cheers!
Hello All
I just start to work with Android files unpack and repack jobs, So I needed to extract the CSC file for I9500 model.
- I download the CSC tar file and then extract it using 7zip tool, Inside it i got two files cache.img and hidden.img
- I run this command :
/home/tools/simg2img /home/CSC/hidden.img system_.img
- After that i did this command to mount the img:
mount -o loop system_.img /mnt/system
- After that all is ok and i can check what is inside the img and add apk files or remove them.
- After I did what i needed I wanted to repack it to make it hidden.img again, So i run this command:
mkdir temp
/home/tools/mkuserimg.sh -s /mnt/system hidden.img temp 542xxxx (I puthere the original size of the system_.img using ll command)
- I got the hidden.img
- After that i repack it with the cache.img and get the CSC.tar file.
THE Problem is:
When I try to flash the repacked CSC.tar file it flashed the cache.img, but stop and failed at hidden.img
I looked here on the forum and found many post about i9500 repack steps, but all were talking about system.img or so, I only need to know the Right steps or order to repack the hidden.img of i9500 to be able to flash it via Odin flasher.
Notice: I use the same steps to unpack and repack hidden.img of S7582, S7562, and other models too, All were flashed ok with np.
I hope that someone can help me here.