I made this because the existing rom (package_us2.3.5.tar.md5) being distributed around the fourms isn't working right for devices like mine.
Your phone should be rooted prior to doing this.
Make sure you have the same device info as mine before proceeding. I will not be responsible if you decide to flash this to a device that does not match my own. You have been warned.
DOWNLOAD HERE: http://www.sendspace.com/file/1y2ogi
This is for the Samsung Galaxy Player 4.0 (USA) (YP-G1CWYXAA)
Model Number: YP-G1
Firmware Version: 2.3.5
Kernel version: 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build number: GINGERBREAD.UEKI8
Steps for flashing.
1.) Attach USB Cable and Put your device in Downloading mode (Hold Power + Vol Down)
2.) Download and run Odin 1.85
3.) Click on the button marked PDA and select the file named "yp-g1cwyxaa.tar" that you downloaded from the link above.
4.) Make sure that ONLY "Auto Reboot" and "F. Reset Time" are checked. (NO OTHER OPTION SHOULD BE CHECKED!!)
5.) Click on "Start" and wait for the process to finish. The process should take about a minute or two and finish with a green box saying "PASS!"
6.) When it has successfully finished, the device itself should reset. At this time you may unplug your USB cable.
7.) OPTIONAL: Press menu button > Settings > Privacy > Factory data reset (This will reboot your device, enter recovery mode, wipe all settings and reset everything to defaults, and then reboot your device once more automatically.)
8.) Enjoy your 100% working Samsung Galaxy Player 4.0 (YP-G1CWYXAA)
This is my first time doing something like this. I hope this works for all of you. Let me know if you have problems. Feel free to click the "Thanks" button if it works for you. =)
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
I downloaded and installed your stock rom and it worked perfectly. The clock works find and the widgets that weren't working before are now working.
The only step I skipped was step 7 because I wanted to keep my apps/data. And I'm certainly following step 8.
Thanks a lot for your effort Kwipper (and the thanks button was clicked).
I am happy to see that this is working. I am actually quite surprised with myself that I was able to do this. About 10 days ago, I didn't even have an android device, or know anything about the platform. =)
Don't be so modest. You've solved a problem that I've had for over a month now.
I'm curious how you did this. Did you use adb from your PC to run the 'dd' command? I ran the 'dd' command using the Terminal Emulator app. Maybe this is why my factory.rfs didn't work.
I did a bit of searching around the fourms and came across this post.
http://forum.xda-developers.com/showpost.php?p=15804185&postcount=15
Then I used a program called Cygwin. Used it to navigate over to where my files were stored and typed in these commands.
tar -H ustar -c factoryfs.rfs zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Then I flashed it using odin.
I also noticed that if you were using the previous "package_us2.3.5.tar.md5" file to restore from, the MD5 of my file would not match up, and Odin would give off an error. So I removed the .MD5 from the extension of my filename and it worked.
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Kwipper said:
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Click to expand...
Click to collapse
They are all right here: http://forum.xda-developers.com/showthread.php?p=20259805
Important: if you are going to flash this ROM, make sure you do NOT choose repartition in Odin with the PIT file. This only contains the /system and the kernel, so repartioning the whole device will make your device unable to boot past recovery. Still waiting for a full stock recovery ROM with all the partitions and can use the PIT file...
Kwipper said:
...
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
Click to expand...
Click to collapse
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Hmmm... Is there anyway to confirm if it's rooted or not? I suppose that if I remove the root and then reflash it using odin, it should remain unrooted right?
WT Ho said:
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Click to expand...
Click to collapse
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Kwipper said:
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Click to expand...
Click to collapse
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
WT Ho said:
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
Click to expand...
Click to collapse
Yeah, just imagine what it would be like to have your computer crash while you were flashing the bootloader!
Can you make a backup of that?
so i can test if it works, cause my device is bricked at the moment.
Woah there, careful what you post! unless you do a factory reset before dumping, the cache.rfs, dbdata.rfs, and data.rfs should NOT be included in a rom as they contain all your personal information!
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Tecardo said:
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Click to expand...
Click to collapse
I don't think you need data partition. In normal operation, you can format the /data partition clean and the system will recreate your new settings there.
For those of you that have used this, can you confirm that this removes root? I going to guess it does.
It's not really a problem since you can use super one click again, but I just wanted to be sure.
Thanks again for doing this, Kwipper.
hey i need to flash factoryrfs form odin. but im not sure how, any help?
minimeofctown said:
hey i need to flash factoryrfs form odin. but im not sure how, any help?
Click to expand...
Click to collapse
Tar it and then flash it with Odin just like how you flash a ROM.
Use terminal (or cygwin for Windows) :
cd (directory of factoryfs.rfs)
tar -H ustar -c factory.rfs > something.tar
Can you make such a ROM? I really think, it will work for me…
I don't know the Problem so i feed to flash the hole ROM
Related
I figured I would put this out there for those who have flashed or are thinking of flashing CM7/MIUI/OMFGB/OMGB or any mtd rom for that matter. If you have flashed one of the aforementioned roms, then you will need to use odin if/when you choose to go to another non-mtd rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly. *Note* This method will also work to unbrick your device from pretty much anything. ***PERFORM ALL OF THE FOLLOWING STEPS WITH THE BATTERY IN YOUR PHONE, DO NOT REMOVE BATTERY***
STEP 1. Open odin (http://www.mediafire.com/download.php?73ta726ghelw381) and place the linked file below in the "PDA" section and WAIT. You will need 7zip or the like to extract the tar image from the zip file below. This particular type of odin file is the only kind that I know of that contains the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
Link removed. My dropbox account was suspended due to excessive traffic. I'll figure out another place to upload and then post the link.
STEP 2. Then, place this file in the "PIT" section in odin and WAIT.
http://dl.dropbox.com/u/20070269/atlas_v2.3.pit <---*Atlas_v2.3 Re-partitioning "PIT" file*
STEP 3. And place a check in the "Re-partition" box in odin.
STEP 4. At this point you need to power off your phone. Then, enter download mode by holding the volume down button and continuing to hold it while you plug the cable into your phone, you should then see a yellow "downloading" screen popup. If/when this happens, go to step 5.
STEP 5. When you have done the first 4 STEPS, THEN hit the "START" button in odin and wait about 5-10 minutes until you see the green "PASS" in odin and profit. ***You must allow the phone to boot fully one time after running this odin process so that it can wipe the phone and complete the the re-partitioning.*** However, when the phone boots, you will be on stock, binged, bloated, unrooted TouchWiz. So odin a recovery and remedy that situation quickly!!! And just in case there are any misconceptions, you do NOT need to be rooted to install a custom cwm recovery.tar file with odin. So unless you plan on staying stock, you don't need to root again because any rom you flash will already be rooted. So just odin a recovery and boot immediately into the recovery via the 3 finger method (holding both volume up and down buttons and the power button at the same time and continue to hold them until you see the samsung logo). YOU MUST DO IT THIS WAY BEFORE THE PHONES BOOTS UP NORMALLY OR YOU WILL LOSE THE RECOVERY THAT YOU JUST ODINED! Then, as good practice, follow the instructions of the next paragraph.
And as a good suggestion, if you want voodoo converted partitions (in others words, if you want to flash a voodoo kernel) after odin does it's thing, flash this package (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom in conjunction with a voodoo kernel you were wanting to flash after coming from CM7 MTD/GB MIUI. Here is the link, flash this if you want voodoo partitions (ext4): http://dl.dropbox.com/u/20070269/ext4_formatter_all.zip . This will help to insure that you obtain a clean install of whatever rom/voodoo kernel you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in eventual problems down the line and/or a bricked phone and you will have to follow this guide to fix it.
Thanks for the info.
Sent from my SCH-I500 using Tapatalk
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
I will have to give this a try since I just chewed out Big Red for screwing up my phone with their ED04 OTA, wich I odin'd back to stock from JT's CM7 to get it.
I vote for a sticky
Sent from my SCH-I500 using XDA Premium App
Moved to the development section and temporarily stuck for now.
yep big +1
If you do all this and Odin hangs or something else fails to work, make sure you are using an OEM data/charge cord to do this. I did this exact beautiful brick a month ago was stuck believing for a good 8 hours that I had done it this time, because I was using a data/chord that was supposed to be an upgrade from the OEM chord. Fun times
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
Bro, just a thought...But for people who follow these steps and STILL get issues, like force closes, the phone not saving your contacts or settings, etc. Then go to http://forum.xda-developers.com/showthread.php?t=1090127&highlight=ext4+formatter. Most of us, I think, use ext4, but RFS is the default for Samsung phones. Ext4 is what VooDoo converts your file systems to. Download the file system .zip of your choice, flash it in CWM, then re-flash your ROM, kernel, theme, etc. and it should fix your issues. I had many issues, this killed them all.
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
solido888 said:
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
Click to expand...
Click to collapse
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
You HAVE to let it boot into stock recovery once after flashing the full Odin. Stock recovery needs to do an automatic data wipe before it boots into the OS. Which is why if you were to flash cwm right after flashing the full Odin, you'd get the datadata/dbdata issues.
Sent from my SCH-I500 using XDA App
krispuniq said:
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Click to expand...
Click to collapse
Wow, I don't know how you didn't lose root seeing as how neither one of those Odin packages are rooted and it does a complete data wipe.
Sent from my SCH-I500 using XDA Premium App
Good advice! regarding that ext4 formatting...
kidserious said:
I figured I would put this out there for those who have flashed or are thinking of flashing CM7 MTD or GB MIUI...
[...]
And as a good suggestion, after odin does it's thing, flash one of these two packages (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom you were wanting to flash after coming from CM7 MTD/GB MIUI. Flash this one: http://forum.xda-developers.com/attachment.php?attachmentid=614756&d=1307095153 if you want voodoo partitions (ext4) or this one: http://forum.xda-developers.com/attachment.php?attachmentid=614757&d=1307095153 if you want nonvoodoo partitions (rfs).This will help to insure that you obtain a clean install of whatever rom you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
[...]
Click to expand...
Click to collapse
This was essentially the process I followed a few days ago when I reluctantly reverted back to touchwiz framework for reliable call operation (CM7 MTD is getting so close).
After letting the DL09 image boot for the first time, I odined Times_Infinity's CM3 and booted straight into it with the intention of running navenedrob's ext4 formatter utility. I immediately heard the familiar scary voodoo lady reporting the lagfix conversion operation, backing up & restoring DL09 system and data files that I had no interest in keeping around, etc. Once it finished and I had TI's CWM on screen, I flashed navenedrob's ext4 utility to reformat.
So, to save some time and an unnecessary format cycle, here's a reminder to create a "/sdcard/voodoo/disable lagfix" file before starting this process .
FWIW, the latest imnuts PBJ kernel has a modified CWM (in yellow) that reportedly incorporates navenedrob's ext4 formatting enhancements, but I've had other issues with that kernel and there's no version to apply via Odin...
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
I hear you and that may be true, but it is just safer to post it the way I did.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
times_infinity said:
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
What problems should I be anticipating since I didn't use it? I haven't had any problems yet.
Edit: I am under the impression the DL09 tar repartitioned for me.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
landshark68 said:
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
Click to expand...
Click to collapse
And I'll reiterate, what problems will I be experiencing? Since I haven't had any yet?
i want to use the MODEM.BIN of my provider's ROM in the cognition 1.31 ROM.
how can i extract it from the provider ROM and then flash it to the cognition?
is there a way to get to it from root explorer and just replace it or i need to extract from the provider ROM and flash to cognition?
what is actually the path of the MODEM.BIN in the sgs 2?
i tried looking for it manually but i couldn't find it.
Sent from my GT-I9100 using XDA Premium App
Unzip extract modem.bin.
Flash modem via Odin as phone.
JJEgan said:
Sent from my GT-I9100 using XDA Premium App
Unzip extract modem.bin.
Flash modem via Odin as phone.
Click to expand...
Click to collapse
im not sure you quite got it.
i need to extract the modem file out of a ROM that i will install on my sgs 2 that's is the official ROM of my service provider.
and i dont know how to find it inside the phone
I've got it right? You do have an official ROM, you wonna take modem.bin out, save it, then install another custom rom and flash it back then? Right?
Ivan_Belarus said:
I've got it right? You do have an official ROM, you wonna take modem.bin out, save it, then install another custom rom and flash it back then? Right?
Click to expand...
Click to collapse
exactly!
got any idea how can i do that?
Nope, as I know it's impossible - modem.bin is an image to flash hardware part and you cannot take it out. Even CWM doesnt backup and restore modem.bin.
It's like a new firmware for modem - you can flash it, but you cannot restore it back.
And what is your reason to do that?
im know that if ill ba able to change this modem my battery will improve dramatically.
how do i know that?
the service provider ROM is 2.3.3 and full of things that make your battery drain.
mine is cognition 1.3.1 and very slim with almost no battery drain apps and juice defender and setcpu on(which saves a lot of battery).
now i compared mine with a regular one that has their official ROM and i get maybe 2 hours more on regular use. also there's a big problem with all radio waves and reception.
now if you look at this:http://www.villainrom.co.uk/forum/s...II-Shipped-Radio-Collection?p=42051#post42051
pulser somehow extracted modems so people would be able to flash it. i wonder how he did it
As I C, he extracted modems from flash packages and reuse them in other reassembled packages then. It's pretty easy.
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Click to expand...
Click to collapse
Electroz said:
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
Click to expand...
Click to collapse
Yep, it works well! I don't need it, but tried successfully. Good job,man. I didn't know.
Electroz said:
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
Click to expand...
Click to collapse
now i just need to learn how to use adb
well its worth it, ill get going to it.
btw, if i did that command from (CMD)adb shell, what happens then?
or its much more complicated than this to extract it.
thanks anyway
You would need to do:
adb shell
su
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
exit
exit
Click to expand...
Click to collapse
your modem.bin file will then be on your internal phone storage.
Electroz said:
You would need to do:
your modem.bin file will then be on your internal phone storage.
Click to expand...
Click to collapse
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
eeebbr said:
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
Click to expand...
Click to collapse
It would be easier to just use 7zip (or similar) tar compress the modem.bin (-> moden.tar) file so you can use ODIN to update your radio on the ROM of your choice. Once you have modem.tar - add that to the PDA field on ODIN and START. Of course all of the prequisites are required. Reboot your phone to download mode, ensure you have working USB drivers, etc.
Google search will reveal all you need to know about creating the file you can flash from recovery. Honestly I think it is way easier to just do this through ODIN. Good luck.
eeebbr said:
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
Click to expand...
Click to collapse
You may flash it with Odin
Generally, all files are to be added to tar must be zipped with following commands:
tar -H ustar -с modem.bin > modem.tar
Then, if you'd prefer to have md5 signed file do the following
md5sum -t modem.tar >>modem.tar
mv modem.tar modem.tar.md5
That's all, then you may flash it with Odin as phone part
Extract modem from file put modem in Phone flash via Odin .
Worked ten times today .
jje
This is interesting thanks so If I root my phone and then still with provider ROM installed I can extract the modem.bin file and use it another ROM as well?
What are the pre-requisites in ODIN you mention when flashing it?
eeebbr said:
im know that if ill ba able to change this modem my battery will improve dramatically.
how do i know that?
the service provider ROM is 2.3.3 and full of things that make your battery drain.
mine is cognition 1.3.1 and very slim with almost no battery drain apps and juice defender and setcpu on(which saves a lot of battery).
now i compared mine with a regular one that has their official ROM and i get maybe 2 hours more on regular use. also there's a big problem with all radio waves and reception.
now if you look at this:http://www.villainrom.co.uk/forum/s...II-Shipped-Radio-Collection?p=42051#post42051
pulser somehow extracted modems so people would be able to flash it. i wonder how he did it
Click to expand...
Click to collapse
Dear,
modem.bin is the combine file,when we flash it, it is extract to the hardware of device. you can't fine modem.bin from the phone but if you want to get it, use mtk droidtool for backup. this software gives you modem.bin but you can't flash it via odin. you can flash via sp flashtool with scatter file.
Try mtk droidtools software but it was made for MTK android devices may be it work for you.
but it confirm you can get modem.bin only way of backup which create complete backup. but you can find modem.img from phone.
system/etc/firmware/modem.img
Why are you necroing a 2.5 yr old thread ?
What I did was even simpler. I just unpacked the modem.bin file from zipped samsung image.
Ok, I am currently using the Samsung Galaxy S Fascinate from Telus. I did some research and i figured I might as well root it. I did that successfully and that's where i should've stopped. I thought I was able to download the mod CyanogenMod but that was a failure. I have no idea what any of the technical terms mean (modem, kernal, how to open random files ie .tar, .rar .md5, flashing, etc). I tried to follow the Guide on http://forum.xda-developers.com/showthread.php?t=923712. I got to step 5, and tried to download the .exe file but then installation failed. I am able to get into download mode and recovery mode but my phone won't reboot past that. Did I just break it..? Any help is appreciated but small simple steps are also appreciated
i'm looking to do the same thing but i'm not sure if i should be flashing the initial ROM (or where to find it) or a nightly
i'm no expert for sure but it sounds like you aren't totally screwed if you can get to recovery or download...not sure if you can just try reflashing the ROM (.zip)again from recovery in order to fix the problem (don't see in the guide where to use a .exe) but you can at least recover to stock using odin...just use step 2 in that guide...again no expert but this is what i have sorted out reading around here trying to figure out how i want to proceed
I have tried many things and yes sorry, the CM I used was in a .zip file, not .exe, my fault. I have attemped to go back to stock mod using that step 2 and those files provided but everytime odin fails. It's looking bad.
StruggletoSucceed said:
I have tried many things and yes sorry, the CM I used was in a .zip file, not .exe, my fault. I have attemped to go back to stock mod using that step 2 and those files provided but everytime odin fails. It's looking bad.
Click to expand...
Click to collapse
You should at least be able to go back to STOCK ROM by following Step 2.
If you are failing in ODIN, make sure the files were downloaded correctly. Using 7zip, try to view the files to verify they are OK. Also, be sure to place each file in the correct section.
Good luck!
Unfortunately, it still fails. 7zip says everything is fine but there is one thing i noticed, the file I'm supposed to place into the "phone" slot is under a WinRar file whereas the rest are a .md5 (or .pit in pit). Would this be a problem.. and how would I fix it?
StruggletoSucceed said:
Unfortunately, it still fails. 7zip says everything is fine but there is one thing i noticed, the file I'm supposed to place into the "phone" slot is under a WinRar file whereas the rest are a .md5 (or .pit in pit). Would this be a problem.. and how would I fix it?
Click to expand...
Click to collapse
Err.. if the file is a .rar, you need to uncompress first!
Odin only takes .tar or .tar.md5 or .pit files !!
Hmm.. fail. How would I uncompress a WinRar file?
The file name ends in .tar but when I go to properties, the file type says WinRar..
StruggletoSucceed said:
Hmm.. fail. How would I uncompress a WinRar file?
The file name ends in .tar but when I go to properties, the file type says WinRar..
Click to expand...
Click to collapse
I use a free program called 7Zip. It's best, IMHO. It can uncompress/compress lots of different formats.. http://www.7-zip.org/
Once you have 7Zip installed, find the file with Windows Explorer, then right-click the file and select "Open Archive".. if you can view the contents, then that means the file is good.
Which file are you having problem? If the file already has .tar extension, then you don't need to uncompress. Only do so it's a .zip, .rar or .7z
Thank you for telling me to use 7Zip. I was using WinRar before and that automatically changed a file into an extension Odin couldn't use. So now I have all my files in eaither .tar or .md5 but Odin is still failing at
<ID:0/007> cache.rfs
<ID:0/007> modem.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Everything is in the correct box and Odin is opened before I plugged in my phone
StruggletoSucceed said:
Thank you for telling me to use 7Zip. I was using WinRar before and that automatically changed a file into an extension Odin couldn't use. So now I have all my files in eaither .tar or .md5 but Odin is still failing at
<ID:0/007> cache.rfs
<ID:0/007> modem.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Everything is in the correct box and Odin is opened before I plugged in my phone
Click to expand...
Click to collapse
I have a Fascinate, but ODIN should work the same. I just downloaded the .zip file you mentioned in your 1st post and unzipped and checked all the files. They seem OK. Have you verified each file is OK?
Do you know which file is it failing? Also, the ODIN included in that .zip file is quite old.. only V1.0. Try this version v1.83 (uncompress first).
Also, did you check the "Repartition" checkbox in ODIN? And put the .pit file in the PIT section?
You sir, are my hero. This is the first time I've seen my home screen in a week!! I would hit that thank you button a thousand times. Although it did delete my Titanium Backup and unrooted my phone, it works!
Any advice towards if I attempt to "flash" a new Mod again?
Would the fact that I tried to flash CM7 (which I understand is Gingerbread) and the kernal it has me downloading is Froyo be a factor? Where would I get a replacement kernal?
StruggletoSucceed said:
You sir, are my hero. This is the first time I've seen my home screen in a week!! I would hit that thank you button a thousand times. Although it did delete my Titanium Backup and unrooted my phone, it works!
Any advice towards if I attempt to "flash" a new Mod again?
Would the fact that I tried to flash CM7 (which I understand is Gingerbread) and the kernal it has me downloading is Froyo be a factor? Where would I get a replacement kernal?
Click to expand...
Click to collapse
I'm so glad I could help! That image you flashed through ODIN is the stock, so it's probably not rooted.
Now that you know how to restore to original stock, you can experiment more. But always remember to read the instructions carefully..
Installing CM7 is a bit more complicated, specially for people who never done it before. I'm not even sure if CM7 or other MTD based ROMs can be installed on a Telus, but I'll do some research. I'm running JT's vanilla Gingerbread myself and it's a great ROM. If you want, I'll tell you how tomorrow..
Well thanks to you, I successfully installed CM7 on my telus following this new guide - http://forum.xda-developers.com/showthread.php?t=1115090 - (with a couple restoring back to original), the only problem now is that i'm unable to get service. It says if I can't then just flash back to original and try again. I did that a few times but same outcome, no service (or 3g). I also noticed my home button no longer works.. that might be a problem too but I'm sure it's just a bug. Any extra assistance is always appreciated!
StruggletoSucceed said:
Well thanks to you, I successfully installed CM7 on my telus following this new guide - http://forum.xda-developers.com/showthread.php?t=1115090 - (with a couple restoring back to original), the only problem now is that i'm unable to get service. It says if I can't then just flash back to original and try again. I did that a few times but same outcome, no service (or 3g). I also noticed my home button no longer works.. that might be a problem too but I'm sure it's just a bug. Any extra assistance is always appreciated!
Click to expand...
Click to collapse
Did you wipe Data & Devik Cache when installing CM7?
In my experience, sometimes, you can fix the Wifi/3G issues by toggling Airplane mode, wait a bit and try again. You don't have service at all or is the signal icon just white instead of green? Also, maybe try 1st with just installing the stock CM7 without the glitch kernel..
Yes, i wiped my system, dada and cache (which the instructions said). Toggling airplane mode didn't fix anything unfortunately. When i looked into mobile services available, my phone can only pick up a rodgers signal (which my sim card cannot not connect to it for obvious reasons). Once I downloaded CM7, the guide says that CM7 has a default kernal already in place so i believe i don't have the glitch kernel running. My screen shows 3/4 white bars but no signal or mobile internet.
StruggletoSucceed said:
Yes, i wiped my system, dada and cache (which the instructions said). Toggling airplane mode didn't fix anything unfortunately. When i looked into mobile services available, my phone can only pick up a rodgers signal (which my sim card cannot not connect to it for obvious reasons). Once I downloaded CM7, the guide says that CM7 has a default kernal already in place so i believe i don't have the glitch kernel running. My screen shows 3/4 white bars but no signal or mobile internet.
Click to expand...
Click to collapse
you may need to flash the stock TElus modem back...some of the guides here have a link to the file in it...srry don't have a link to it
moosehead11 said:
you may need to flash the stock TElus modem back...some of the guides here have a link to the file in it...srry don't have a link to it
Click to expand...
Click to collapse
That would make sense but once i install CM7, if I go into recovery mode my power (aka enter) button doesn't function so once CM7 is flashed, i can't flash anything from there.
StruggletoSucceed said:
That would make sense but once i install CM7, if I go into recovery mode my power (aka enter) button doesn't function so once CM7 is flashed, i can't flash anything from there.
Click to expand...
Click to collapse
You can still boot into CWM, but either using ADB, type: adb reboot recovery on a command prompt, assuming you have ADB working..
If not, another way to get into CWM is by using ROM Manager, which is included by default in CM7.
Like I said, I have a Verizon Fascinate, so I don't really know anything about a Telus Fascinate.
Best of luck...
neozen21 said:
You can still boot into CWM, but either using ADB, type: adb reboot recovery on a command prompt, assuming you have ADB working..
If not, another way to get into CWM is by using ROM Manager, which is included by default in CM7.
Like I said, I have a Verizon Fascinate, so I don't really know anything about a Telus Fascinate.
Best of luck...
Click to expand...
Click to collapse
would any stock telus modem (where ever i would find one) work properly on CM7 or would there be a certain model/version that's needed? I'm so close to getting this >.<
StruggletoSucceed said:
would any stock telus modem (where ever i would find one) work properly on CM7 or would there be a certain model/version that's needed? I'm so close to getting this >.<
Click to expand...
Click to collapse
OK. Here is the thing.. As far as I know, CM7 doesn't flash a modem, so when you restored to stock TLJL3, that's the modem that you still have. You can verify by going into Settings, then About Phone. The Baseband version is your modem version. What does it say? What about the Kernel? What's the kernel version? And what version of CM7 did you flash? is it the latest nightly?
Also, when you flashed CM7, you didn't flash another kernel right?
Last thign, although unlikely, I've heard people here having success after reflash CM7 again, after wiping DATA and Dalvik cache..
I've attached the TLJL3 Tulus modem here just in case, flash it in CWM
Multiupload links removed - MU seems to be gone forever. I will repost an unrooted UCKH7 package in the next week along with a modem package - Until then, use the rooted package and then remove:
/system/xbin/su
/system/bin/su
/system/app/Superuser.apk
And then reboot
I have uploaded Heimdall/Odin flashable kernel ,rooted system, and modem images to dev-host. This should be sufficient to unbrick most hosed-up phones, as long as you didn't flash a bad .pit. Note that after flashing this, you might need to wipe data depending on what ROM you were coming from. If you bootloop or things behave wacky, enter 3e recovery (stock kernel means stock recovery) and do a Wipe Data/Factory Reset. If you are reverting from UCKK6 back to UCKH7 you MUST perform this step or wifi will not work. If you're coming from a 100% stock ROM and only using this to gain root, you should be able to keep all your data and not need to wipe.
The kernel is 100% bone stock, the system image is stock except that it is pre-rooted (su binary and Superuser.apk)
I am including the modem in a separate package since that goes in a separate modem slot, and I don't want to reupload a 200+ MB file if I don't have to.
The kernel + rooted UCKH7 system package is here: http://dev-host.org/UWm
Kernel + cache + rooted UCKK6 system package: http://dev-host.org/8LA
Download, extract the package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html, then either:
1) (Tested on Linux, should work on MacOS) - Extract the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
for the kernel + system package, and:
Code:
heimdall flash --modem modem.bin
for the modem package
I've never had good results with the Heimdall Frontend GUI.
2) (Tested by Jivy26 for kernel + system, untested for modem) - Flash the .tar in Odin. I'm a Linux user, so I have only tested this with Heimdall so far.
Kernel + system package goes in PDA slot I believe, modem package in Phone slot.
If you are wondering why I used 7-Zip to compress the archive:
7-Zip provides better compression ratios than Zip
7-Zip is open source unlike RAR
If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.
Also - great thanks goes to Jivy26 for providing a stock /system dump. Without that it would not have been possible to make the system image or get a kernel dump.
Coming in the next few days - stock unrooted /system package.
Also just added - a param.lfs backup from my device. This is NOT contained in an Odin-flashable .tar file yet, I'll work on cleaning up my packages when I'm feeling better. I came down with a nasty cold a few days ago.
UPDATE:
creepyncrawly has written an EXCELLENT step-by-step guide for flashing this with Odin. The guide is at:
http://forum.xda-developers.com/showthread.php?t=1313659
In addition, he posted an Odin-flashable tar package for just the stock kernel, for those who want to do a ! removal. I have mirrored the file (I don't trust Dropbox for long-term hosting) at http://www.multiupload.com/MD7SMMNG24 - his original post is at http://forum.xda-developers.com/showpost.php?p=18535109&postcount=174
Awesome, thanks. Downloading now.
*If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.*
LOL! Enough said right there. Thanks Ent!
Worked great with odin, thanks.
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
dayv said:
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Flashed from CM7 using just the PDA
jivy26 said:
Flashed from CM7 using just the PDA
Click to expand...
Click to collapse
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
With a good .pit file, yes it could recover from a bad .pit flash.
As far as going back/forth to CM7 - I believe that differences in architecture between the original GS and the GSII (mainly no FSR/RFS proprietary modules) make going to/from CM7 much less painful.
dayv said:
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yes without a .pit file
thank you for all your work and for educating me. I will make sure and hit the thanks button next time I'm on a PC.
Wish we could hit thanks button from xda app.
Sent from my SAMSUNG-SGH-I777 using XDA App
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Drew489 said:
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Click to expand...
Click to collapse
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Entropy512 said:
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Click to expand...
Click to collapse
thank you!!! worked
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
not rooted
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
+1 thanks
10char
Not able to access the download site, could you please attache here?
mjgspr95 said:
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
Click to expand...
Click to collapse
No, shouldn't hurt anything. Should only need to wipe if coming from a significantly different ROM such as CM7 or an I9100 ROM.
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
Yes, but I figured this would be more popular and uploading one of these takes an hour. I'll put up the unrooted stock in a day or two as I'm doing kernel work. However it's easy enough to unroot, just remove the two following files:
Code:
/system/app/Superuser.apk
/system/xbin/su
keeploading said:
Not able to access the download site, could you please attache here?
Click to expand...
Click to collapse
It's WAY larger than XDA's attachment limit, sorry, no can do.
You end up getting the phone Entropy? Thanks for this btw.
Hey kids! Don't know if anyone here knows me, but I am an ex avid Captivate user. But I've been out of the game for so long (exploring webOS and BBOS7) that I am very behind. Anyone kidn enough to post a link to the newest Odin? Also, what slot do .tar files go into? The first one, PDA?
EDIT: Opened the file, definitely PDA Still, anyone have a good link to a working Odin? I remember at one time some Odin versions worked really badly, and I used the original 1.00 but I heard there is a 2 and I'd prefer to use that with this new phone.
First, thank you to the anonymous source who provided us with this build and thank you to @garwynn for posting it here.
This Odin One-Click.exe contains the Stock NI3 Bootloader, Kernel, Modem and ROM for the Sprint Samsung Galaxy S5 (SM-G900P). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole phone to the stock NI3 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your phone's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your phone, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the NI3 Stock ROM One-Click.
http://www.rwilco12.com/forum/showthread.php?tid=938 (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the SM-G900P_NI3_Stock_Unrooted.exe was saved upon extract from the 7Zip archive.
Double-click on SM-G900P_NI3_Stock_Unrooted.exe. *On Vista or newer, you may need to right-click on the file and select Run as Administrator.
6: Place phone in Download Mode.
- Power phone completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and phone.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your phone should automatically reboot.
The boot process will take slightly longer than usual during which time you'll see the Sprint 4G/Spark logo screen.
Congratulations! You've flashed the Factory Restore NI3 build!
XDA:DevDB Information
[ROM][ODIN][OC] SM-G900P NI3 (Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Sprint Samsung Galaxy S 5
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-10
Last Updated 2015-02-10
Download: http://www.rwilco12.com/forum/showthread.php?tid=938
Could you post just the bootloader tar
Sent from my SM-G900P using XDA Free mobile app
@rwilco12
Been doing a lot of reading/research as I'm new to the Samsung game. But I've been every else besides Sony. I read your unpack tutorial on your website, and jumped all over reading unpacking how-to's. Seems to me the recommended an easiest way to create a "no-wipe" package is via SplitFUS2. Most of what I've read is for older devices, and I was wondering if that's the way you recommend doing it, and if you know whether or not it works with S5 packages?
Will normal root process work on it. I'm tempted to do it only cause I want the modem
AOD_Corwin said:
Will normal root process work on it. I'm tempted to do it only cause I want the modem
Click to expand...
Click to collapse
+1
AOD_Corwin said:
Will normal root process work on it. I'm tempted to do it only cause I want the modem
Click to expand...
Click to collapse
rhyme187 said:
+1
Click to expand...
Click to collapse
Chainfire's autoroot does work but I don't believe Towelroot does.
gokart2 said:
@rwilco12
Been doing a lot of reading/research as I'm new to the Samsung game. But I've been every else besides Sony. I read your unpack tutorial on your website, and jumped all over reading unpacking how-to's. Seems to me the recommended an easiest way to create a "no-wipe" package is via SplitFUS2. Most of what I've read is for older devices, and I was wondering if that's the way you recommend doing it, and if you know whether or not it works with S5 packages?
Click to expand...
Click to collapse
My guess is you're referring to my tutorials on how to build your own flashable TAR?
Honestly I've never used the SplitFUS2 utility so I can't give you a 100% answer there. However, what I can tell you is that Samsung devices use one of two methods to wipe a device when flashing a TAR. Generally the method involves wiping a partition and overwriting it with a partition file included in the TAR. There are several different partitions and each of them governs a different aspect of the device's functionality. There is generally a specific file that governs the data partition, once you extract the TAR you would then recompile it without the data partition file and flash the final resulting TAR.
The other is script based and that area I'm not an expert on. My BFF @garwynn is pretty good though and might be able to walk you through fixing the scripts if necessary.
Now one other thing to keep in mind is that this thread is for a one-click not the actual TAR. There are ways to decompile an Odin one-click but I would recommend just using the original TAR which can be downloaded in @garwynn's original TAR thread at http://forum.xda-developers.com/showthread.php?goto=newpost&t=2885005
Good luck!
rwilco12 said:
My guess is you're referring to my tutorials on how to build your own flashable TAR?
Honestly I've never used the SplitFUS2 utility so I can't give you a 100% answer there. However, what I can tell you is that Samsung devices use one of two methods to wipe a device when flashing a TAR. Generally the method involves wiping a partition and overwriting it with a partition file included in the TAR. There are several different partitions and each of them governs a different aspect of the device's functionality. There is generally a specific file that governs the data partition, once you extract the TAR you would then recompile it without the data partition file and flash the final resulting TAR.
The other is script based and that area I'm not an expert on. My BFF @garwynn is pretty good though and might be able to walk you through fixing the scripts if necessary.
Now one other thing to keep in mind is that this thread is for a one-click not the actual TAR. There are ways to decompile an Odin one-click but I would recommend just using the original TAR which can be downloaded in @garwynn's original TAR thread at http://forum.xda-developers.com/showthread.php?goto=newpost&t=2885005
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. I was talking about your "How-To" on your site, and I replied there too. It was very helpful and informative. I found Splitfus2 doesn't seem to work with KitKat, only JB and before. After getting everything ready to go to try your method, extracting the files from the TAR, etc. I found the Kitkat file names differ a bit from the JB ones, according to the TAR BALL flashing order you have listed on your site. Which shouldn't matter since all I need to make is a stock system and recovery TAR. Assuming I use the method you have posted, only making a separate system and recovery TAR, a data wipe shouldn't happen......correct? Only other thing I'm not sure of is after extracting the files from the original TAR, the system is in system.ext4.img...... I assume I leave that the way it is, correct? Only time I've seen it that way is when extracting a system.img and converting it to a flashable rom.
When is the script wipe used? I'm pretty good with scripts. Thanks for your time and help, it's greatly appreciated!
Unrooted/Rooted
rwilco12 said:
Chainfire's autoroot does work but I don't believe Towelroot does.
Click to expand...
Click to collapse
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
localpagefirst said:
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
Click to expand...
Click to collapse
I flashed, then rooted with cfroot. My Knox was already tripped before flashing this. Not sure what you mean by repercussions, but flashing this should not trip Knox, its the cfroot part that would.
localpagefirst said:
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
Click to expand...
Click to collapse
When you say "no repercussions" what exactly are you looking for?
"no repercussions"
rwilco12 said:
When you say "no repercussions" what exactly are you looking for?
Click to expand...
Click to collapse
Meaning problems after the rom has settled Like System UI, Context Issues,ECT.
Rwilco12 I fully trust your work and thank you and all whom have helped . I am as one could say very apprehensive about changing complete systems. Roms and modems. I was in no way referencing this to and thing bad.
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
Bottom line is I am going for it even though Android "L" will be here first week of November.
Been following you since the Epic Touch days..... anywho, any chance of getting some love for the S5 Sport? Thx!
For anyone that has installed this...Any noticeable difference in the radio?
Sent from my SM-G900P using XDA Free mobile app
Jay5583 said:
For anyone that has installed this...Any noticeable difference in the radio?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Service at my house literally went from 1 bar to 2, YMMV. I did switch to the bmfr cm11 build a day after flashing this, service has remained the same.
recovery
thanks so much for posting this - been trying to find an easy way to odin back to stock after trying a few ROMs.
Will this also take us back to stock recovery or does it only do the system/rom part? if not, do you know how to get back to stock recovery?
thanks so much!
hi is there a ni3 modem with out system i can flash?
Serious Problem
i downloaded this on my dads new s5, just an hour old.
Flashed in odin, now im getting the "firmware upgrade encountered an issue" error message.
i tried going on to sammobile and downloading sprint stock firmware and flashing that, but odin is rejecting it.
theres also a bunch of versions on sam mobiles site, so im downloading 2 more versions, 1 from april and 1 from june (NCD & NE5)
could it be because im running odin on windows xp vmware thats making odin not take the tar file?
also, i dont know what version im coming from, the only thing i remember seeing when i allowed it into developer mode is that it was on 4.4.2.
please help!!!!
XP under VMware. Yeah, probably asking for trouble.