Database Users

Kies problem after custom rom, Solved.

After some problems to get Kies to recognize my SGT7 rom after custom rom tour i solved it like this.
Get the software CheckFusDownloader v2.1
Download at fus.nanzen.se
Open and choose: android, GT-P1000 and your region.
Then press firmware check and download.
You'll get a zip file, unpack the .zip and put the .tar file in a easy to remember place.
Flash the Restock Package from TeamOvercome (use odin v1.7 supplied in the .zip)
Download at teamovercome.net/
(Use Re-Partition, Auto Reboot and F.Reset Time)
Then do factory reset/wipe in recovery mode. (Power + Volume up at boot)
Then flash the .tar file you downloaded with CheckFusDownloader v2.1
NO re-partition, just klick PDA and choose the downloaded .tar file, and flash.
Then again factory reset/wipe.
Then flash the Restock Package again with and factory reset/wipe at boot
After that Kies recognise my SGT7 as original Samsung rom.
Can somebody tell me if there is a easier way?

I hex edited /efs/nv_data.bin, and flashed a Froyo ROM which included the CSC with the right country code. Kies recognised my Tab straight away and updated it to GB 2.3.6 successfully. See my more detailed post in the other thread (help me i have only 2 weeks left on my garanti!).
I'm not sure it's an easier way though.

[HowTo] SM-G900FD with Android 5.0 Root if all seems to fail

[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.

[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven

Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks

I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.

free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.

Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?

af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar

This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?

AryaMod ROM help

Hello, want to download this ROM, but I'm a bit confused because I always flash the new roms manually using a cwm recovery only. I'm not an expert in these tar md5 files.. Anyways im running a stock lollipop N9005XXUENC2 and my question is can I flash AryaMod using the cwm only and without downloading the 2 tar files the developer mentioned in the main thread? If not, can you tell me exactly what I should do using Odin? Thanks..

here you go!
MohamedBmb said:
Hello, want to download this ROM, but I'm a bit confused because I always flash the new roms manually using a cwm recovery only. I'm not an expert in these tar md5 files.. Anyways im running a stock lollipop N9005XXUENC2 and my question is can I flash AryaMod using the cwm only and without downloading the 2 tar files the developer mentioned in the main thread? If not, can you tell me exactly what I should do using Odin? Thanks..
Click to expand...
Click to collapse
the thing is,
1. Make all necessary backups, install ODIN and Samsung drivers in PC, also download the necessary files (BL, CP and ROM).
2. remove battery and insert after 10 secs.
3. Directly boot into Download Mode via key combo (after getting into Download Mode, Open ODIN and also connect phone to PC).
[download both files, select "BL tar file" in BL and "CP tar file" in CP in ODIN]
4. Flash the BL and CP from OP via ODIN (after selecting two files, click Start, it will automatically restart and it will show Success)
5. Now after the phone is ON (Success message), disconnect from PC and enter Recovery Mode and flash ROM.zip
6. Select your Options in Aroma and enjoy.
The Dev recommended to use TWRP and also I had TWRP from start. You can check in the ROM thread whether anyone is doing this via CWM.
Good luck.

[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

Downgrade to previous version & SW REV. Check Fail

Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.

Hello, So basically we need to remove all .bin files? ok
I also need to downgrade my modem.bin because I'm facing Wi-Fi and Bluetooth issues (they don't turn on). So is it possible to flash those files separately after? Will it work?

x.shayan.x said:
Hello, So basically we need to remove all .bin files? ok
I also need to downgrade my modem.bin because I'm facing Wi-Fi and Bluetooth issues (they don't turn on). So is it possible to flash those files separately after? Will it work?
Click to expand...
Click to collapse
Yes you can flash

Afzal922 said:
Yes you can flash
Click to expand...
Click to collapse
I removed the files you mentioned and I flashed marshmallow on Nougat successfully but i have constantly getting error message ""Unfortunately, Touchwiz has stopped"" and "Unfortunately, The process. Android.process has stopped" and I can't boot in my mobile. Please help..!

alipezu said:
I removed the files you mentioned and I flashed marshmallow on Nougat successfully but i have constantly getting error message ""Unfortunately, Touchwiz has stopped"" and "Unfortunately, The process. Android.process has stopped" and I can't boot in my mobile. Please help..!
Click to expand...
Click to collapse
Try another firmware.

Afzal922 said:
Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.
Click to expand...
Click to collapse
mind telling us how to flash the .bin files to get back signals and wifi and other stuff?

if we not going to flash the CM and modem, i dont think the Wifi and the mobile signal is going to work....
Regards

i try this wat downgrade samsung 51 and its not work

Afzal922 said:
Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.
Click to expand...
Click to collapse
Hello, this is a well old post. Would this work with the Note 20 Ultra Snapdragon version?

N1NJATH3ORY said:
Hello, this is a well old post. Would this work with the Note 20 Ultra Snapdragon version?
Click to expand...
Click to collapse
Yes