AT&T SGH-I337 UCUEMK2
Long story short, company is rolling out airwatch and I need to get rid of root. It's their phone, their policy. My issue is that all I have is a Mac. I've seen a few threads that link to the recovery firmware but it seems to be formatted only for Odin. Being on Mac, i'm limited to Heimdall which seems to use different files that I cannot find.
Can someone let me know where I can get the Heimdall firmware for my phone?
Thanks
Actually, you use the same firmware with Heimdall that you use with Odin. What you will start with is an "Odin flashable .tar (or .tar.md5) file". To use it with Heimdall, you will need to extract all the individual components from the tar archive. For example, you will then have files like boot.bin, sbl.bin, factoryfs.img, boot.img, data.img, hidden.img, modem.bin, etc. I'm not sure of the specific files for the S4, and I didn't open a tar archive to look, so whatever you find in the stock distribution is what you will need. Then you use them with Heimdall. There is a graphical interface and a command line tool. The command line tool may be a little more reliable. Some have had issues using Heimdall on certain versions of MAC OS.
Just wanted to post a followup. I used the instructions from here and I've got my phone back.
Thanks
Related
Anyone have the ota JI6 update that will flash via Clockwork?
Sent from my SGH-T959 using XDA App
ultra spikey said:
Anyone have the ota JI6 update that will flash via Clockwork?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Try this http://www.multiupload.com/GYZT0YH5DZ
@chichu_9, that file is a .rar for Odin I think. I'm running Linux (Ubuntu Lucid) so can't use Odin nor Kies (I don't have access to MS Windows). I tried installing Heimdall, but it requires a .pit file, and the JI6 rar file from the link you provided doesn't have one (it does have a DLL, what is that for?). Is there another JI6 that does have the .pit file? Is there a way to flash with adb instead?
Or is there a JI6 ROM that can be flashed from Clockwork ROM Manager? I'm new to this and have a stock phone that somehow hasn't gotten the over the air update since I got the phone in August. I have rooted the phone (z4root) and made a Nandroid backup and a Titanium Backup, and my phone doesn't appear to be hardware-locked (I can go into download mode). I've been reading xda for hours and can't figure this out. Any advice?
Pretty certain the development section bible has a link to a flashable version.
@s15274n, thanks for the quick reply! I may have missed it, but I checked the bible before posting and just checked again, and all I found was this:
*(ROM)JI6 OTA deodexed with stock JI6 kernel and modem --s0niqu3***new(10/24/10)***
http://forum.xda-developers.com/showthread.php?t=808830
^The .zip ROM was removed, causing problems for people.
and the odin .tar.
I also searched through the forum and didn't find it, but like I said, I'm new so maybe I missed it? Maybe I'll just skip it though and just dive in all the way and flash a 2.2 ROM like Master's Axura Final coming out in the next few days.
Apologies, thought there was a flashable zip there.
You will not be disappointed with axura. Just hope Master keeps developing for the Vibrant (he got a my touch I here).
[Deleted!] oopps sorry misread the OP.. nvm
i was saying check TeamWhiskey Downloads for flashable JI6 but that's only the modem
This work?
http://forum.xda-developers.com/showpost.php?p=8430280&postcount=1
stock jk2 for future reference
http://forum.xda-developers.com/showthread.php?t=833563
Is there a system dump for JI6 around?
@Moped_Ryder, the zip you linked to contains Odin, which I can't use (no MS Windows) and contains the same JI6 tar as above, but also includes the 512.pit file. I tried to flash via Heimdall by typing this (I untarred all the files to a subdirectory of Heimdall called T959UVJI6):
heimdall flash --pit T959UVJI6/512.pit --factoryfs T959UVJI6/factoryfs.rfs --cache T959UVJI6/cache.rfs --kernel T959UVJI6/zImage --modem T959UVJI6/modem.bin
But I got this error message:
Local and device PIT files don't match. Functionality for this is yet to be implemented.Ending session...
So no JI6 for me. Thanks for all the help, but I think I'll just go directly to Axura once Final (2.0.6) is released to the general public so don't worry about troubleshooting this further.
I wanted to post my experience with Heimdall. I suspect that many readers of these forums think that heimdal is easy to use: infact it is, from the little I have used it, but reliable information on its use is sparse. I hope therefore, other new users, who want to use Linux will find this helpful. Please remember these tips are just my experiance, I hope they are helpful but I can't say if they will work for you or not.
Heimdall is in fact ridulously easy to use and I feel a bit a of a fraud writing this down but the lack of examples of use is what held me back from using it for several days (that and I'd need to use my wife's windows laptop to use odin and if something went wrong, who knows when she gets it back!).
I've installed:
Overcome_Kernel_v2.1.3_ODIN.tar and
Overcome_v1.4.4_Full.zip
The Overcome guide is uesful but is written for Odin. The bare process is however simple:
Return to a safe rom/kernel image (I couldn't find the one specified but I was on a rooted stock so I don't think that would be necessary)
Connect the Tab via usb
Put Overcome_v....._Ful.zip into your sdcard
Put the Tab in download mode
Flash the kernel
Wait for the reboot
Reboot and put in CWR
Clear some stuff stuff out and update the rom from the Overcome zip file.
Nearly all of this can be followed (follow the guide this is just a summary from memory) using heimdall instead of odin.
The kernal flash can be done using heimdall so simply. The method I used was: extract the zImage (a compressed kernel image file) from the tar file (into the current directory for example) and flash (as long as the tab is in download mode):
tar -xvf Overcome_Kernel_v2.1.3_ODIN.tar
heimdall flash --kernel zImage
I believe the modem can be flashed in a similarly simple way but I haven't tried it yet, since I don't know if I need to (I have read, some stock modems are very queit and this fixes it):
unzip JMF-Modem.zip
heimdall flash --modem updates/modem.bin
One important thing I have gathered: please (for the most part and unless you know better) ignore any instructions for using heimdall which include the --primary-boot or ---secondary-boot options. You don't need them if you Tab is working properly and have never overwritten the boot loaders. Overwriting the boot loaders seems to be one of the few ways to properly brick you Tab.
Just flashed the JMF modem recommended in the installation guide if you have quiet in call volume, which I started experiencing (along with quiet ring tone on outgoing calls) after an update using CWM 1.4.5_Update & 2.1.4_CUV_CWM.
The command:
heimdall flash --modem modem.bin
worked fine for me (and fixed the volume problem).
As anyone running OS X or Linux would know, the only truly "supported" way of rooting an S4 talked about on XDA is using CF Auto Root and Odin to flash it. There used to be Motochopper, but that no longer works with recent versions of the S4 firmware.
I actually am familiar with the concepts of how flashing a device works, and upon seeing videos or pictures of selecting the CF Auto Root .tar.md5 file for "PDA" in Odin, I wondered if what was going on behind the scenes was as simple as just performing a regular flash to recovery or whatnot.
I downloaded CF Auto Root and extracted the .tar.md5 file. Why it has the .md5 extension, I'm still not sure. Perhaps it's just because Odin requires that extension? I don't know if it's actually important. Inside though, I found 2 files. They were cache.img.ext4 and recovery.img.
I did some research before posting, but didn't find anything definitive. However, I'm assuming that using Heimdall to flash would work. Because Heimdall interfaces with the device the same way Odin does, only Heimdall actually supports OSes other than Windows. Only problem is, Heimdall doesn't have a one-click "PDA" button to flash the .tar.md5 like Odin does. But would using Heimdall to flash the cache and recovery image files work? Is that all that needs to happen for the S4 to be rooted? Or does Odin also perform some additional function, some function which Heimdall wouldn't do automatically?
To make a tl;dr I guess, has anybody tried flashing cache and recovery image files from the CF Auto Root .tar.md5 file to a S4? Did it work? If so, was there anything special you had to do in order to get it to work? Any answers or insight from someone else would be greatly appreciated. If I could get this working with my S4 I might make a video tutorial so that then there's a good tutorial out there that works for OSes other than Windows.
I did it in heimdall. Worked perfectly
Sent from my SPH-L720
xchampx13 said:
I did it in heimdall. Worked perfectly
Sent from my SPH-L720
Click to expand...
Click to collapse
You just entered in the recovery.img and cache.img.ext4 files as they were and flashed? You didn't do anything else?
superriku11 said:
You just entered in the recovery.img and cache.img.ext4 files as they were and flashed? You didn't do anything else?
Click to expand...
Click to collapse
Please follow this link. I just did it a few mn ago, and it worked good. Had to do it twice (don't know why). Flash process takes only a few seconds. In case Heimdall hangs too long (> 1 mn) at " Releasing device interface" with no progress bar, power off your device and start again the process.
http://www.all-things-android.com/content/how-root-samsung-mobile-device
[ 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,
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