Database Users

firmrware JMC csc? e pda?

hello, I put the JMC (sanfirmware) and everything went well, but I 'under pda I vacuum, I was with JMA before flashing to the JMC and now I only have one option if I do: # imei * # 272 * I ITV only (I'm in Italy and Italian), but samsung apps gives me only one application? and I can not change or replace the CSC, has anyone figured out how to do?

not sure but flashing csc from jm6 may fix it as it is a multi csc. the part i am not sure is does csc needs to be specific for that rom but i dont think so because the roto-jmc doestn have a cache.rfs in it. and still am not sure if csc is cache.rfs but i know that jm6 csc tar contains only cache.rfs in it.

ok
full jm6 CSC flash e ok all 16 application on samsung app

ok, i experienced, if flashing roto-jmc from jma you will not have shown all under *#1234#. but this is not a big thing. for the samsung app you have to fash after the update the file dbdata.rfs (csc only in odin) and after flashing this power and volup button until it reboots and all should be fine.

so do we flash tarred dbdata.rfs from csc in odin? not in pda

yes, with odin mark csc and select dbdata.rfs.tar or with heimdall the dbdata.rfs

[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?

i need help dor galaxy note

hello i have a big problem
i have the 2.3.6 android and the basement version says unknown
what i must do to fix this ?also dont find sim
pls help

flash modem.bin with cwm or odin
Phone.tar with Odin
Or make an update.zip of modem.bin and flash it with CWM Recovery.

tids2k said:
flash modem.bin with cwm or odin
Phone.tar with Odin
Or make an update.zip of modem.bin and flash it with CWM Recovery.
Click to expand...
Click to collapse
where i can find the flash modem ?
i must modem fhlash and phone .tar ? or one of this 2?
thank u !!

PIT File Needed for SM-G900F EVR (EE) Firmware

Hi all,
I'm trying to flash from BTU firmware to EE (EVR) firmware. I need the corresponding PIT file.
Can anyone link me to this? I've had a look around and I can't find it.
Thanks!

You just need the G900F PIT file, nothing to do with the carrier
http://forum.xda-developers.com/showthread.php?t=2737448

Tried this, didn't work. Same issue.
I used the G900F PIT, which is the model of my S5. I do think the EE (EVR) version must have a different ext4 size, however I can't find a PIT file for this anywhere.
Odin fails on
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Ext4)

Is there any solution to this yet? Still can't find the correct EE (Everything Everywhere) PIT File,
Any help is appreciated,
XPGTomo.

XPGTomo said:
Is there any solution to this yet? Still can't find the correct EE (Everything Everywhere) PIT File,
Any help is appreciated,
XPGTomo.
Click to expand...
Click to collapse
You don't need a pit file. It's the hidden.img bug.
You must extract the hidden.img file of your firmware rename it to hidden.img.tar and then flash the hidden.img.tar file. I don't know why but sometimes the hidden.img file can only be flashed when it's alone

Help
Emre67511 said:
You don't need a pit file. It's the hidden.img bug.
You must extract the hidden.img file of your firmware rename it to hidden.img.tar and then flash the hidden.img.tar file. I don't know why but sometimes the hidden.img file can only be flashed when it's alone
Click to expand...
Click to collapse
How do I install this with Odin?
Where do I put the hidden.img.tar file?
I have the Firmware under AP

XPGTomo said:
Is there any solution to this yet? Still can't find the correct EE (Everything Everywhere) PIT File,
Any help is appreciated,
XPGTomo.
Click to expand...
Click to collapse
You can't find it because it doesn't exist, as I have already told you, PIT file is model specific, not carrier
If you knew what a PIT file did, you'd understand that

XPGTomo said:
How do I install this with Odin?
Where do I put the hidden.img.tar file?
I have the Firmware under AP
Click to expand...
Click to collapse
The hidden.img.tar file also comes under AP. After you flashed it it takes some minutes to boot so don't be shocked

I have a solution
I have found and put together a solution to the problem,
If anyone else is having this issue then click the link and install with Odin3.
http://www.sammobile.com/forum/showthread.php?t=31977

[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