[REQUEST] Stock Captivate boot.img - Captivate Android Development

I'm trying to test a theory about flashing a kernel in recovery. Apparently, using AnyKernel Updater by Koush doesn't work, so maybe my hunch will change that.
Upload to MediaFire or something similar and send me a link. Thanks!

These don't have a boot.img
cache.rfs
dbdata.rfs
factoryfs.rfs
modem.bin
param.lfs
zImage
I am guessing you are looking for ths stock kernel?
If so, thats the zImage

edit: Apparently the structure of the filesystems is different from my familiar nexus one...damn...
Back to the drawing board I guess.

Related

[Q] Latin American Tab Different Digitizer?

Hi,
I have a GT-1000N Tab
I cannot flash Roto's JME because I loose the touchscreen, I suppose the drivers are different from european or usa Tabs.
On Samfirmware there is a JM2 for my Tab, but I don't want to end up with a signed bootloader.
My current firmware is P1000NUBJJ3, on Sam's the newest is P1000NUBJM2
I'd prefer to use Roto's. Do I flash Roto's with NUBJM2 kernel and modem?
If not, do I just delete the boot.bin and Sbl.bin from P1000NUBJM2?
On that .tar there is also a hidden.rfs and a .pit Do I leave them in?
Thanks!
Edit: One reason I want to use Roto's is to use XEU CSC
jgaviota said:
I'd prefer to use Roto's. Do I flash Roto's with NUBJM2 kernel and modem?
Click to expand...
Click to collapse
I haven't tested that configuration, but it may work. Theres no harm in trying.
jgaviota said:
If not, do I just delete the boot.bin and Sbl.bin from P1000NUBJM2?
On that .tar there is also a hidden.rfs and a .pit Do I leave them in?
Click to expand...
Click to collapse
The hidden.rfs may contain extra programs that you may want, but you can just remove it, as well as the pit, boot.bin and Sbl.bin.
If you have done a Roto Backup, perhaps you can post your boot.bin and Sbl.bin here for me to look at.
Thanks for stopping by Roto, I really admire all the work you are doing with the Tab!
I opened the hidden.rfs with UltraISO and it only contains data for some dictionaries, nice to have but not essential.
rotohammer said:
If you have done a Roto Backup, perhaps you can post your boot.bin and Sbl.bin here for me to look at.
Click to expand...
Click to collapse
I did do a Roto Backup, it saved me from having a Tab without touchscreen , btw would the same procedure work on a Galaxy S?
Attached are the stock boot.bin and Sbl.bin
Are all the hardware drivers in the zImage or are some files from the rest of the rom needed?

Installing I9100 Rom on a Galaxy S2 M250s/k/l (aka Korean S2)

I've been using m250 for several weeks now but I am bothered of its capabilities specially with SMS messaging... It's limited. After few tries and mistakes, I have found a perfect way to install I9100 rom on a Galaxy S2 M250 without error.
PS: quite time consuming but worth doing since this will eliminate limits from the current M250 rom specially SMS.
NOTE: FM Radio off course will not work since M250 uses DVB radio and TV
Things to have:
1. Siyah Kernel 2.6.13 korean version (you can get it from siyah's site; thanks!)
2. Odin (latest version)
3. Mobile Odin (search this forum... credits to Chainfire... this is the most important soft on this tut)
4. M250S rom. Search for the torrent of [Root]HOME_M250S.EI21.1035_CL566114_REV02_user_low_ship
5. An I9100 DX rom. Search for GT-I9100_THL_I9100DXKL3_I9100OLCKL2_I9100DXKL1.tar (2.3.6)
----LET'S Start!!!----
NOTE1: Make a copy of the i9100 rom / m250 rom / siyah kernel on a microSD... we'll going to use this later...
NOTE2: the i9100 rom should be on the "firmware" folder of the microSD card...
NOTE3: insert the microSD card on the phone...
1. Do a full factory reset of your phone (settings).
2. Put the phone on download mode and flash it with the m250rom above.
3. After flashing with the m250 rom, flash the siyah kernel.
4. After the phone restarts and proper setup has been done, open CWM and select "Flash Stock Firmware". Don't worry CWM will not flash the IBL/PBL and SBL. This will restart the phone doing the flah on the recovery screen... (have some chips and beer!!!)
5. After the restart, the phone should now be running the i9100 rom but remember, kernel and modem is stock from the i9100 so signal might not be that great. (ALSO NOT ROOTED)
6. Put the phone in download and flash the siyah kernel.
7. Restart the phone and you should now have the root goodies from siyah. (WAIT: WHY AM I SEEING THE YELLOW TRIANGLE ON BOOT??? --- NO WORRIES MATE --- FOLLOW THE NEXT INSTRUCTIONS) INSTALL MOBILE ODIN.
8. Select open file on Mobile Odin. Select External SD and look for the i9100 Rom. Enable --- EverRoot / Inject Superuser / Inject Mobile Odin / Inject CWM Manager. Then click, "Flash Firmware". (Need to drink some beer again!!!)
9. The yellow triangle should be removed by now after restart but signal is quite poor since we are using the i9100 modem. Open Mobile Odin again, select open file and look for the i9100 rom. Select kernel and look for the siyah kernel. Select modem and look for the m250 rom.
10. Enable everRoot, superuser, mobile odin, cwm.
11. FINALLY... CLICK "FLASH FIRMWARE".
12. Continue drinking beer.
---
will i be able to install custom i9100 as well?
thanks for the guide!
it would be great if you can post the links to the files..
my question is that if I did all of these, will there still be a problem regarding phone signal reception?
I've used my m250s since 2011 and using official I9100 ROM since the first time i bought it, straight without any problems and now i'm using Official ICS XWLP4 with ICS domination theme, without any problems too
You'll need CWM to install custom ROMs most are flashable zips, so the only problem you might have is the yellow traingle, else flash any stock I9100 ROM then flash the Siyah kernel and through CWM flash the custom zips.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
smdc1981 said:
I've been using m250 for several weeks now but I am bothered of its capabilities specially with SMS messaging... It's limited. After few tries and mistakes, I have found a perfect way to install I9100 rom on a Galaxy S2 M250 without error.
..............................
---
Click to expand...
Click to collapse
To the OP:
To save time you could you use heimdall, it would greatly reduce the time required for this procedure, in case you wish to add I can provide you with the instructions through heimdall.
swapnilraj said:
You'll need CWM to install custom ROMs most are flashable zips, so the only problem you might have is the yellow traingle, else flash any stock I9100 ROM then flash the Siyah kernel and through CWM flash the custom zips.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
To the OP:
To save time you could you use heimdall, it would greatly reduce the time required for this procedure, in case you wish to add I can provide you with the instructions through heimdall.
Click to expand...
Click to collapse
it would be great if you can make an updated tutorial about flashing i9100 roms to m250 variants.. please include the link to the files needed too..
darkzorn said:
it would be great if you can make an updated tutorial about flashing i9100 roms to m250 variants.. please include the link to the files needed too..
Click to expand...
Click to collapse
Resources-
Kernel: Download from here [the TAR file!]
ROM: I couldn't find the torrent the OP mentioned, sorry. But in my method you wouldn't need it.
FlashTool: I'd recommend Heimdall
Procedure-
1. Flash The Kernel-
Ubuntu: sudo heimdall flash --kernel zImage
Windows: heimdall flash --kernel zImage
2. Flash I9100 ROM-
Ubuntu: sudo heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
Windows: heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
Note- You do not need to flash the kernel per se I included it so you can root the phone, if you wish not to just skip it. In case you find the CUI methods confusing feel free to ask.
swapnilraj said:
Resources-
Kernel: Download from here [the TAR file!]
ROM: I couldn't find the torrent the OP mentioned, sorry. But in my method you wouldn't need it.
FlashTool: I'd recommend Heimdall
Procedure-
1. Flash The Kernel-
Ubuntu: sudo heimdall flash --kernel zImage
Windows: heimdall flash --kernel zImage
2. Flash I9100 ROM-
Ubuntu: sudo heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
Windows: heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
Note- You do not need to flash the kernel per se I included it so you can root the phone, if you wish not to just skip it. In case you find the CUI methods confusing feel free to ask.
Click to expand...
Click to collapse
thanks a lot for this!
my questions would be are:
1. is heimdall really better than using odin? and can i use odin since i'm more used to it?
2. is flashing the i9100 .pit file really important?
3. can i flash siyah kernel .zip file using samsung's stock recovery?
4. after flashing siyah kernel can i flash custom rom on it already or just stock roms first?
thanks in advance..
darkzorn said:
thanks a lot for this!
my questions would be are:
1. is heimdall really better than using odin? and can i use odin since i'm more used to it?
2. is flashing the i9100 .pit file really important?
3. can i flash siyah kernel .zip file using samsung's stock recovery?
4. after flashing siyah kernel can i flash custom rom on it already or just stock roms first?
thanks in advance..
Click to expand...
Click to collapse
1. Yes, it really is better, odin is a leaked POS, while Heimdall is a wonderfully engineered software, I suggest it because, it allows you to flash only specific files instead of a complete ROM, if you use odin with single PDA it would flash the bootloader and the modem too, which I skipped in my commands, which skips the need of a stock Korean ROM download too, win!
2. No you don't need the pit file, explicitly if you want to re-partition your device,
heimdall flash --repartition --pit [Name of the pit file] --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
3. No.
4. Yes, you may flash any ROM just be sure it doesn't change the modem, if it does, delete the modem.bin file in the zip or get a copy of your Korean to modem to flash separately.
EASIEST METHOD:
You can also use the GUI if you find the CUI hard, but IMO CUI is much faster, and less tedious.
To flash custom ROMs-
Step 1:-
Download the custom ROM and the kernel extract the tar file you should get a file named 'zImage', open up the command prompt use the CD command to navigate to the folder where you extracted it.
then copy paste this statement
heimdall flash --kernel zImage
Step 2:-
Boot to recovery clear cache, wipe data, format system, dalvik cache, install ROM you are good to go.
To flash stock I9100 ROM-
Step 1:-
Download the kernel and the stock ROM, extract the ROM first!
You should have the following files
zImage
factoryfs.img
cache.img
hidden.img
modem.bin
boot.bin
Sbl.bin
param.lfs
Delete the modem.bin, param.lfs, boot.bin, Sbl.bin (bootloader files) and zImage (I9100 stock kernel), you won't require them.
Step 2:-
Extract the siyah kernel you should have the zImage file then.
Make it sure that all the files are in the same folder, you should now have the following files.
zImage // The Siyah one
factoryfs.img
cache.img
hidden.img
Open up command prompt, use CD command to navigate to where you extracted the files and use this statement.
heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --kernel zImage
thank you
@swapnilraj
you totally rock dude! you should make a new thread that has your full guide on it.. It would really be helpful with people who have korean units but want to use i9100 roms..
just wanna ask you if i can still use the gingerbread siyah korean kernel if i wanna try out some ICS..
also can i ask you what ROM and kernel are you currently using?
sorry if i have too many questions..
darkzorn said:
@swapnilraj
you totally rock dude! you should make a new thread that has your full guide on it.. It would really be helpful with people who have korean units but want to use i9100 roms..
just wanna ask you if i can still use the gingerbread siyah korean kernel if i wanna try out some ICS..
also can i ask you what ROM and kernel are you currently using?
sorry if i have too many questions..
Click to expand...
Click to collapse
No the Siyah GB kernel won't work with ICS.
To use Siyah kernel; after flashing any of the ICS firmwares flash the new ICS Siyah kernel, though I am not sure it is supported on the Korean device you may ask gokhanmoral to make a compatible kernel.
I am currently using the 4/11 CM9 nightly stock CM kernel. I'll try a kernel when the CM9 reaches RC status (removes the stubs etc), about a new thread, I'll do it soon enough.
Please help
Can any S2 rom be installed on to m250s?
im just about to buy this phone so i need to know if im about to do a big mistake
melakamc said:
Can any S2 rom be installed on to m250s?
im just about to buy this phone so i need to know if im about to do a big mistake
Click to expand...
Click to collapse
Refer to the Korean thread in the General section if that helps, but I believe they are compatible with all of the international ROMs
swapnilraj said:
1. Yes, it really is better, odin is a leaked POS, while Heimdall is a wonderfully engineered software, I suggest it because, it allows you to flash only specific files instead of a complete ROM, if you use odin with single PDA it would flash the bootloader and the modem too, which I skipped in my commands, which skips the need of a stock Korean ROM download too, win!
2. No you don't need the pit file, explicitly if you want to re-partition your device,
heimdall flash --repartition --pit [Name of the pit file] --factoryfs factoryfs.img --cache cache.img --hidden hidden.img
3. No.
4. Yes, you may flash any ROM just be sure it doesn't change the modem, if it does, delete the modem.bin file in the zip or get a copy of your Korean to modem to flash separately.
EASIEST METHOD:
You can also use the GUI if you find the CUI hard, but IMO CUI is much faster, and less tedious.
To flash custom ROMs-
Step 1:-
Download the custom ROM and the kernel extract the tar file you should get a file named 'zImage', open up the command prompt use the CD command to navigate to the folder where you extracted it.
then copy paste this statement
heimdall flash --kernel zImage
Step 2:-
Boot to recovery clear cache, wipe data, format system, dalvik cache, install ROM you are good to go.
To flash stock I9100 ROM-
Step 1:-
Download the kernel and the stock ROM, extract the ROM first!
You should have the following files
zImage
factoryfs.img
cache.img
hidden.img
modem.bin
boot.bin
Sbl.bin
param.lfs
Delete the modem.bin, param.lfs, boot.bin, Sbl.bin (bootloader files) and zImage (I9100 stock kernel), you won't require them.
Step 2:-
Extract the siyah kernel you should have the zImage file then.
Make it sure that all the files are in the same folder, you should now have the following files.
zImage // The Siyah one
factoryfs.img
cache.img
hidden.img
Open up command prompt, use CD command to navigate to where you extracted the files and use this statement.
heimdall flash --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --kernel zImage
Click to expand...
Click to collapse
hi swapnilraj
thank you for the wonderful instructions you have provided.
however, I am a bit of a loss. Can you point me to the i9100 custom rom that you are referring to?
I am currently using an m250k variant of sgs2. I have it rooted and running stock firmware with gingerbread.
Two things that I want to aim right now.
1. Convert my phone to i9100
2. Install an ICS custom rom.
Thank you very much for your helpful posts.
unamepword said:
hi swapnilraj
thank you for the wonderful instructions you have provided.
however, I am a bit of a loss. Can you point me to the i9100 custom rom that you are referring to?
I am currently using an m250k variant of sgs2. I have it rooted and running stock firmware with gingerbread.
Two things that I want to aim right now.
1. Convert my phone to i9100
2. Install an ICS custom rom.
Thank you very much for your helpful posts.
Click to expand...
Click to collapse
I was referring to any custom ROM in general for GB, for ICS ROMs you need to have an ICS compatible kernel for the M250K with CWM support, do you have any such kernel? If so only then can you flash ICS ROMs.
If you have any ICS compatible kernels give me a link, you could also ask Siyah to build one like he did for GB.
swapnilraj said:
I was referring to any custom ROM in general for GB, for ICS ROMs you need to have an ICS compatible kernel for the M250K with CWM support, do you have any such kernel? If so only then can you flash ICS ROMs.
If you have any ICS compatible kernels give me a link, you could also ask Siyah to build one like he did for GB.
Click to expand...
Click to collapse
hi swapnilraj
thanks for the fast reply.
so if I get you correctly, there's no current way of installing an ICS custom rom to an sgs2 m250k/s/l variant?
thanks.
Yes, without a compatible kernel its tough but you can 'try' in theory it should work, mind it in theory I don't have one so I cannot confirm.
If you have CWM installed on your phone try flashing the latest nightly build from codeworkx CM9 page, if you do not have CWM installed you can do so by using the Korean Siyah kernel, then through the recovery install the CM9 ROM with gapps. Mind you its only theory, so there is a possibility that you may soft-brick your device, but that's recoverable.
Siyah-v2.6.13-kor kernel
hi can anyone give me a link on where to get this kernel Siyah-v2.6.13-kor.. siyah's website is down i think
you mean that....
"GT-I9100_THL_I9100DXKL3_I9100OLCKL2_I9100DXKL1.tar" is sort of stock rom?
so... it is ok to flash any stock rom rather than that??
What I want to do is to flash I9100 custom roms.(I'm using M250s)
I found "[Root]HOME_M250S.EI21.1035_CL566114_REV02_user_low_ship.zip" file that you informed above.
But I can't find "GT-I9100_THL_I9100DXKL3_I9100OLCKL2_I9100DXKL1.tar".
and I have one more question.
I said that I got "[Root]HOME_M250S.EI21.1035_CL566114_REV02_user_low_ship.zip"
and you said, go onto download mode and flash the rom.
To flash the rom, we need tar or md5 file. Not the zip file.
So, I unzipped it and there are two files with .tar &.md5.
I think .md5 file won't be needed to flash rom.
Please tell me specific informations. Thank you

[Q] Idea for reverting to old Bootloader GT-I9505

Hi,
First sorry for my bad English.
I'm not a dev and i don't know hot to make flashable zip's and all other stuf, but i thing it's possible to make one thing to revert back to old bootloader.
First in new roms we have two new files, one is persdata.img.ext4 and i think here is some knox app files. Other is sbl1.mbn and that file i thing is for bootloader to show knox in download mode. In previous roms we dont have sbl1.mbn, we have only sbl2 and sbl3 files.
In Es File Explorer i see that sbl1.mbn is in /firmware-mdm/image folder
First i think to delete that file and after that to test flashing BMGA rom with odin to replace other two sbl files, but i don't know if i delete that file do i have a download mode.
And if its possible some dev to make one flashable file with some script to delete that file with instalation and replacing sbl2 file in /firmware-mdm/image and sbl3.mbn with that from BMGA rom (i don't know where is placed sbl3, i don't find them in root directory.)
Odin got fail after trying to replace aboot.mbn if found any way way to flash or repace aboot.mbn in phone i think we go back to previous bootloader.
mitky82 said:
Hi,
First sorry for my bad English.
I'm not a dev and i don't know hot to make flashable zip's and all other stuf, but i thing it's possible to make one thing to revert back to old bootloader.
First in new roms we have two new files, one is persdata.img.ext4 and i think here is some knox app files. Other is sbl1.mbn and that file i thing is for bootloader to show knox in download mode. In previous roms we dont have sbl1.mbn, we have only sbl2 and sbl3 files.
In Es File Explorer i see that sbl1.mbn is in /firmware-mdm/image folder
First i think to delete that file and after that to test flashing BMGA rom with odin to replace other two sbl files, but i don't know if i delete that file do i have a download mode.
And if its possible some dev to make one flashable file with some script to delete that file with instalation and replacing sbl2 file in /firmware-mdm/image and sbl3.mbn with that from BMGA rom (i don't know where is placed sbl3, i don't find them in root directory.)
Odin got fail after trying to replace aboot.mbn if found any way way to flash or repace aboot.mbn in phone i think we go back to previous bootloader.
Click to expand...
Click to collapse
Is not posible. I tried to do this ... But the thing is that the new bootloader is eFused with the soft. Anyhow i managed yo get MF8 on my baseband and MF8 as rom . but no luck to change the bootloader
Sent from my GT-I9505 using xda app-developers app

[Q] how to create ODIN package with Modem and Bootloader from Stock rom?

Hello,
I am on Cyanogenmod 13. and I have outdated Modem and Bootloader. which effect my network signal
I have downloaded the latest stock firmware which is for my specific device .
from reading all over XDA this is what i understand is the procedure:
1. getting the right stock rom <- done
2. extracting the required files <- my main question
3. create 2 tar packages for Modem and for Bootloader
4. creating MD5 checksum of both file.
5. flashing using ODIN while placing modem file to CR slot and Bootloader to BL slot. (flashing it twice before boot as it might be reset)
now i know how to do all this steps but my problem is to understand which files are required to Modem tar and Bootloader tar.
the available flash-able files made by the community are not consistent. for example some of the modem tar file people made contain modem.bin and NON-HLOS.bin while others only modem.bin.
this are the files in the original stock rom:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
which of them i need to place in the Bootloader tar (BL) and which in the Modem tar (CP)?
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
allidea said:
I've also searched around hoping to find answer to this question
Click to expand...
Click to collapse
Which one? About Odin's slot? Use AP slot for everything.
bbsc said:
Which one? About Odin's slot? Use AP slot for everything.
Click to expand...
Click to collapse
I'd like to know which files to extract from stock FW. I don't want to end up in boot loop or something worse.
From what I've seen my stock ROM has following files as shown on 1st attachment and most custom modem + bootloader tarballs have files (below files are from PhoeniX ROM v13.6) as shown on 2nd attachment.
There is one particular file named sdi.mbn which can be found in custom modem+bootloader tarballs and which is not present in stock rom.
Ok, I don't know if it's correct or no, but I used for bootloader/modem/kernel update on SM-G900V such a file as shown on the picture.
The original (HOME) .tar.md5 was renamed to .tar.
The next files from it were deleted:
- cache.img.ext4;
- system.img.ext4.
Pit-file was added.
The resulting file was flashed via Odin's AP slot.
Result:
- bootloader, recovery, kernel and modem updated;
- Binary: Official; System: Official;
- all data on /data remain untouched.
allidea said:
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
Click to expand...
Click to collapse
All described here: https://jdrch.wordpress.com/2017/01...ions-without-breaking-custom-rom-or-recovery/
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
allidea said:
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
Click to expand...
Click to collapse
Are you still trying to figure this out??
bobbylo said:
Are you still trying to figure this out??
Click to expand...
Click to collapse
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
allidea said:
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
Click to expand...
Click to collapse
ok,so you created a .tar?Not a .tar.md5? why did'nt you need the sdi.mbn?
bobbylo said:
ok,so you created a .tar?Not a .tar.md5?
Click to expand...
Click to collapse
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
For the bootloader select BL and browse to your bootloader file.
For the modem select CP and browse to your modem file.
Click to expand...
Click to collapse
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
why did'nt you need the sdi.mbn?
Click to expand...
Click to collapse
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
allidea said:
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
Click to expand...
Click to collapse
Ok,was just wondering...I have an xda page where i created bootloaders and modems for the S5 G900T t-mobile.I use a program called cygwin64 to create the .tar.md5 files.It involves some command line input..Maybe yours is easier....Anyway,don't think i'll need to make any more,as i think there done with updates for the G900T,and maybe all the S5's

Issue faced in flashing kernel compiled from source

Hi Guys,
I have compiled a kernel for note 4 from opensource samsung.
I have got zimage in two locations , one in output which is less than 10mb and one in main kernel boot folder which is 20 mb.
When i try to flash using odin i , get the error , unsupported dev type.
I have firmware N910GDTS1DRH2 N910GODD1DRD1 downloaded from sammobile.
Also after compiling i have got some modules which i didnot touch.
I downloaded source from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n910g
I have tried 3 mm versions, but all give same error.
Any help will be appreciated.
I also tried making boot.img with perl script but phone doesnot boot up using that.
Thanks and Regards,
Ankit
I use AIK to unpack the stock boot image. Take the zImage from output/arch/arm/boot/ and replace the original one in the new split_img folder that AIK creates. Be sure to rename it what AIK names it (boot.img-zImage if I remember right). Then repack it flash the new image via TWRP. The new-image should be close to 15.8 mb.
Edit- forgot to hit reply button @xdauserherewithnote4
Is TWRP neccessary
kevintm78 said:
I use AIK to unpack the stock boot image. Take the zImage from output/arch/arm/boot/ and replace the original one in the new split_img folder that AIK creates. Be sure to rename it what AIK names it (boot.img-zImage if I remember right). Then repack it flash the new image via TWRP. The new-image should be close to 15.8 mb.
Edit- forgot to hit reply button @xdauserherewithnote4
Click to expand...
Click to collapse
Thanks for your reply, i was wondering if i can flash using odin or i have to use twrp? zimages are convertible to tar files that odin can flash but the problem i am facing is odin mode showing unsupported dev type.
xdauserherewithnote4 said:
Thanks for your reply, i was wondering if i can flash using odin or i have to use twrp? zimages are convertible to tar files that odin can flash but the problem i am facing is odin mode showing unsupported dev type.
Click to expand...
Click to collapse
Yeah, you could make it in to .tar if you'd like but it needs to be in a boot.img form. The only way I know how to directly flash a zImage is with anykernel or a tool similar to that.
Kernel flash was success but phone is not stable now !
kevintm78 said:
Yeah, you could make it in to .tar if you'd like but it needs to be in a boot.img form. The only way I know how to directly flash a zImage is with anykernel or a tool similar to that.
Click to expand...
Click to collapse
Ok i was able to flash boot.img by converting into tar (having new zimage) , but system is rebooting again and again after sometime.
I was able to flash after making boot.img using AIK. Thanks for advice.

Categories

Resources