All the CWM files from the official website are *.img but odin3 is asking for a tar file.
there has to be some reason why all the files are IMG that its the right file (its the only thing available form their site...). Where can I find a tar file from CWM?
Additionally, do you have to root to flash CWM from stock?
[ 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?
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.
Hello the community,
i'd like to ask you for help because i don't manage to make it.
Here is the problem :
1/ i flashed last firmware for the phone
2/ then root it, install latest busybox....
3/ dump from my phone cache & system using this :
dd if=/dev/block/platform/13540000.dwmmc0/by-name/CACHE of=/sdcard/cache.img
dd if=/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM bs=4096 of=/sdcard/system.img
I check it using linux reader. No problem at all
4/ Then repack those 2 files with others files which are on stock tar file (boot, hidden...)
5/ Launch Odin, put my tar on AP then flash.
- All were ok until it came to cache.img then fail
On stock tar, there is a system.img (not .raw). Don't know if it is sparsed but....i suppose as it needs to be converted to bre used with linux reader.
So i dunno what to do to have a valid cache.img & system.img
If you can help me, i will be grateful.
Thanks for all.
Hi
I'm trying too making a pre rooted stock rom flashable through odin. But i get everytime a "failed" from Odin.
However why are using your cache instead of cache.img present in stock firmware?
Try unpack stock firmware and replace only custom "system.img" that contains root and finally repack stock firmware!
Well some info i need is in cache
why don't you make a flashable zip since you know the partions then add root
malbert16442 said:
why don't you make a flashable zip since you know the partions then add root
Click to expand...
Click to collapse
A stock firmware pre-rooted flashable through odin is more comfortable whenever you wanna reset your phone isn't need to using FlashFire or Mobile Odin. IMHO
I went to install a custom OS for the very first time. I rooted my device with KingRoot and tried installing custom recovery via Flashify and i used a image file to flash the device and now when i boot the device it comes up with Samsung logo and then a blurred color screen and then blank screen. What should i do know... PLEASE SOMEONE HELP ME.
Two chances
1. You might have chosen boot image instead of recovery image option in flashify. boot image is kernel. device won't boot without kernel.
2. You have flashed wrong recovery image. you have to flash a working recovery image. make sure you downloaded right file.
Solutions
*If you have flashed Boot Image, then you have to download stock rom and flash it via Odin using a computer
*If you are flashed wrong recovery image then you can fix it by flashing right recovery.tar using odin
in both case you need a computer.
I suggest that you should go for an experts help.
You can find stock rom link and recovery.tar files at grand 2 general forum.
JitDevHacker said:
Two chances
1. You might have chosen boot image instead of recovery image option in flashify. boot image is kernel. device won't boot without kernel.
2. You have flashed wrong recovery image. you have to flash a working recovery image. make sure you downloaded right file.
Solutions
*If you have flashed Boot Image, then you have to download stock rom and flash it via Odin using a computer
*If you are flashed wrong recovery image then you can fix it by flashing right recovery.tar using odin
in both case you need a computer.
I suggest that you should go for an experts help.
You can find stock rom link and recovery.tar files at grand 2 general forum.
Click to expand...
Click to collapse
Thank you for your response. I installed the stock ROM using ODIN. And now, my phone is doing well. Fortunately, I upgraded from Jelly Bean to Kitkat. xD