Develop Bugs

[SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR)

The purpose of this thread is to breathe life into the development for the SPH-P100. I have observed a severe lack of development for this device as I am sure many others have. Hopefully the work and tools I have provided in this thread will bring some rom chefs and themers out of the wood work for this device.
Everything in this thread is for the Galaxy Tab SPH-P100. While everything has been tested and the best effort put forth, I am NOT responsible for what you do or what happens to your devices. Flash at your own risk! Lack of reading and following instructions is NOT my problem. Any support should be given in the thread and not PM. When posting a problem please be descriptive as possible as it will cut down on thread pollution. Thanks.
1. Stock Odin/Heimdall Files: Stock EF17 Tars - Recover from a brick or bad flash. Choose between fully stock or pre rooted with ClockworkMod flavors. No more 12,000 steps to get back to stock!
2. Stock EF17 Kernel: Prerooted, ClockworkMod 4.0.1.5 Recovery, RFS & EXT4 Compatible - Included in the prerooted EF17 tar and the full stock EF17 rom. Mostly stock kernel with root, ClockworkMod, and dual file system support. Source provided for custom kernel developers.
3. Full Stock EF17 Rom: ClockworkMod Flashable, Deodexed, Zip Aligned, & Optimized - No bloat removed. Perfect base for themers and rom chefs to use to get started on some killer themes and customized roms.
4. RFS & EXT4 Conversion Tools: Use these tools if you want to convert from RFS to EXT4 or vice versa. Read the instructions carefully because these scripts do NOT back up your device!
5. Addons: Addons and other files any one might need. (CIFS support, etc)
IRC Chat
Feel free to visit the #gtab chat room for general chat, help, or developing questions. You can access from your web browser HERE or if you are familiar with irc:
Server: irc.fossnet.info
Channel: #gtab
All I ask of developers, chefs, and themers is that you always give credit when you use other people's work. Also users please make use of the thanks button and help each other out nicely in the threads.
Thanks to insanity213, tpike, jt1134, DRockstar, chris41g, and any other developers I may have borrowed from to make this happen.

Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
Generally you should not need the .pit file unless you need to repartition your device when you flash it. Unfortunately, ClockworkMod has a difficult time reading the factory flashed partitioning. This will cause issues when you restore a backup from ClockworkMod. I recommend to repartition at least ONCE to prevent this issue. See HERE for more information. I have included the pit in the above zip file.
How to Odin back to stock: (Assumes Windows driver is installed: Sprint_P100_Samsung_GALAXY_Tab_USB_Drivers.msi)
1. Download the zip package from above.
2. Put the Tab into download mode by powering it completely off and then turn it on while holding the volume down button until the yellow download mode screen appears.
2. Extract the zip and open Odin. The first ID:COM box should turn yellow. If it does not turn yellow then check your driver installation.
3. Uncheck EVERYTHING except "Auto Reboot". If you are re-partitioning with the .pit file then check "Re-Partition" as well.
4. Click PDA and select the tar file you downloaded. Also put the .pit file under PIT if you are re-partitioning.
5. Hit start and wait until the device reboots and Odin says "PASS!".
No Heimdall instructions yet. If some one wants to write a guide then I'll put it here.

Stock EF17 Kernel: Prerooted, ClockworkMod 4.0.1.5 Recovery, RFS & EXT4 Compatible
I've put together a mostly stock kernel. Only the following changes were made to the stock kernel: Self contained root, ClockworkMod 4.0.1.5 with working redirector, and EXT4 support. The kernel also includes a fix for dpram not initializing in Samsung's EF17 source code. This causes the 3G radio and other stuff to not work when a kernel is compiled from Samsung's original source code. --BAD SAMSUNG for releasing broken freakin' source code!
Flash the kernel with Odin or Heimdall on top of any EF17 installation for ClockworkMod and EXT4 support. (Odin instructions are the same as flashing the stock tar files HERE)
Download stock-ef17-kernel-root-cwm-v2.tar.md5 CWM Flashable: stock-ef17-kernel-root-cwm-v2.zip
--Updated su and Superuser.apk in kernel
Old version(s):
Download stock-ef17-kernel-root-cwm.tar.md5 (Mirror)
--Initial version (see github link below for changes)
ClockworkMod 4.0.1.5 Notes:
-Access ClockworkMod by completely powering off your device and hold volume up when you power it back on. You can also use a program like Quickboot or Rom Manager to reboot into recovery.
-ClockworkMod is a 100% self contained recovery that has been compiled from the latest CyanogenMod source code.
-Key mapping:
Menu Up - Volume Up or Search
Menu Down - Volume Down or Menu
Select - Power or Home
Back - Back
-KNOWN BUG: ClockworkMod has a difficult time reading the factory flashed partitioning. This will cause issues when you restore a backup from ClockworkMod. I recommend to repartition at least ONCE to prevent this issue. If you happen to restore a backup and get stuck at the Samsung screen then simply Odin the kernel again to fix it. See HERE for more information.
Kernel source and change log can be found on github: https://github.com/Rodderik/android_kernel_samsung_sprinttab/commits/master
I will be developing a kernel for the Tab in between life and my other projects. Hopefully it will include things like overclocking, undervolting, voodoo sound, etc. Kernel developers, feel free to fork the kernel to use as a base for your own.

Full Stock EF17 Rom: ClockworkMod Flashable, Deodexed, Zip Aligned, & Optimized
Provided below is a bone stock flashable rom. There is nothing modified or removed except for being deodexed, zip aligned, and PNG optimized. All the bloat is still intact. It is compatible with both EXT4 & RFS file systems. Flash the rom from ClockworkMod to return the Tab back to a stock rooted state.
Themers and rom chefs feel free to use this zip as a starting point for your own roms and themes. Let's see those sick customizations start rolling out the door!
Download stock-ef17-rom-deodex-cwm-v3.zip (Mirror) md5: 8cc28c5840f7b74bf0b0acd20cff870a
--fixed ScreenCaptureService.apk (holding back and hitting power to take a screenshot)
Old Version(s):
Download stock-ef17-rom-deodex-cwm-v2.zip (Mirror) md5: 773dbfc511197551f4ef5a891836c6de
--Updated su and Superuser.apk in kernel
Download stock-ef17-rom-deodex-cwm-v1.zip (Mirror) md5: 78eb0f297f80193d45590da640dd76d9

RFS & EXT4 Conversion Tools
The EXT4 file system provides a boost in performance over Samsung's proprietary RFS file system. EXT4 has become the standard for Android since the release of Gingerbread. Until recently, Samsung uses their own file system on the Tab and many other devices. If you would like to convert your file system please read on.
WARNING: THESE SCRIPTS DO NOT BACKUP OR RESTORE DATA. FAILURE TO FOLLOW THE USAGE INSTRUCTIONS BELOW WILL RESULT IN A SEMI-BRICK THAT WILL REQUIRE ODIN OR HEIMDALL TO FIX! ALSO YOU MUST READ THIS POST OR RISK YOUR RESTORED DATA NOT BOOTING! YOU HAVE BEEN WARNED!
How to convert the file system:
1. Download the appropriate zip below.
2. Reboot into ClockworkMod (Volume up + power)
3. IMPORTANT! Make a backup in ClockworkMod.
4. Flash the appropriate zip from below but DO NOT reboot.
5. Restore your backup or flash a rom before rebooting.
To convert RFS to EXT4 use this zip: rfs-to-ext4_sprint-tab.zip (Mirror)
To convert EXT4 to RFS use this zip: ext4-to-rfs_sprint-tab.zip (Mirror)

ClockworkMod Backup/Restore Issue and Solutions
Issue: Apparently there is an issue with the factory partitioning that prevents ClockworkMod from backing up the kernel partition. This will cause the kernel partition to be corrupted when restoring a backup and the Tab will freeze at the Samsung screen.
Solution: If you get stuck at the Samsung screen, simply reflash the kernel with Odin or Heimdall and everything will work again.
Permanent Fix: To fix the issue I recommend re-partitioning the device. You should only have to re-partition once. After that ClockworkMod will backup and restore 100% from then on. Instructions on re-partitioning can be found in the tar section HERE.
More info: The pit file I pulled off the Tab with Heimdall. It doesn't make sense that re-partitioning with it fixes the restore issue permanently. I personally verified the fix on 4 Tabs. Re-partition once and you shouldn't ever have to again and ClockworkMod will restore properly.

Addons:
CIFS Addon stock-ef17-cifs-addon.zip (CWM flashable)
Drop Bear stock-ef17-dropbear.01.zip (Mirror) (jocala put together a package to allow SSH on the tab. See his post HERE)
This thread is a cross-post of my original thread on devphone.org here: http://devphone.org/samsung-galaxy-...b-(sph-p100)-mega-development-starter-thread/
Please post any comments, suggestions, problems, or complaints in this thread. Donations and the use of the thanks button are never mandatory but are much appreciated.

Rodderik is my God!
If stock/odexed is your style, here's 2 ROM's that may interest you. Obviously not good for customizing as they are odexed, they should perform well. Both of these ROMs are built off of the stock files with the exception of using Rodderik's kernel.
http://files.devphone.org/gtab7/brickrom-stock-odex.zip (Fully stock odexed ROM)
http://files.devphone.org/gtab7/brickrom-stock-odex-anorexic.zip (Stockish odexed yet majorly debloated ROM)
Also, if anyone is playing with ipv6, you should be able to find most of the files mentioned in this thread here:
http://v6.facebones.net/gtab7/
Our ipv6 infrastructure is still in testing and somewhat unstable but figured I'd throw this link out there anyway.

We have one of these here:
http://forum.xda-developers.com/showthread.php?t=1133053

gsu_golfer said:
We have one of these here:
http://forum.xda-developers.com/showthread.php?t=1133053
Click to expand...
Click to collapse
no you don't everything in this thread is original work...not a compilation of hacked together guides for half working stuff...have a read and you will understand

Rodderik said:
no you don't everything in this thread is original work...not a compilation of hacked together guides for half working stuff...have a read and you will understand
Click to expand...
Click to collapse
Whatever makes you happy. It's the same information, just with much more text. Two threads is better than none, I suppose.

gsu_golfer said:
We have one of these here:
http://forum.xda-developers.com/showthread.php?t=1133053
Click to expand...
Click to collapse
If you'd take the time to read and understand what Rodderik has posted here you'd see that he has clearly taken things to the next level. No more Froyo flashing, a real rooted custom kernel base for people to fork and run with. An actual FULL odin tar for both rooted and bone stock....
Yes, that other thread had some useful information, but its dated now. It's like you're comparing a 1975 Chevy Vega to a 2012 factory supercharged Camaro. If you don't see the value in this post, please move along and make room for the people who will.
gsu_golfer said:
Whatever makes you happy. It's the same information, just with much more text. Two threads is better than none, I suppose.
Click to expand...
Click to collapse
Same information?
- The kernel posted is compiled from source with a 100% functional root and CWM built into it. This is clearly different than anything prior.
- The Odin tar files are FULL tar files complete with modem and bootloaders. The previous GB tars were lacking several parts.
- Previous CWM was buggy, this CWM is fully functional.
I'll stop with those 3... You'll need to comprehend the rest of what was posted on your own.

gsu_golfer said:
Whatever makes you happy. It's the same information, just with much more text. Two threads is better than none, I suppose.
Click to expand...
Click to collapse
intentions are not to take away anything from your thread...if nothing else this thread gives you more information to add to your post in the other section.
new clockworkmod, ef17 tar instead of ea24, no switching back and forth between odin and heimdall, and other tools to help other developers and themers get started on some awesome mods for the sprint tab

As one who has lived in that forum for a while, this is different and much needed. Thanks Rodderik!
Sent from my SPH-D700 using XDA App

Oh, please. Consider a similar thread for us verizon tab owners..
Sent from my SCH-I800 using xda premium

Thanks for this, it's very exciting. A good solid rooted GB is really all the SGT needs, imo, so thanks

Nice works men, I really appreciated.
Will try this as soon as possible when I get home.
Could I ask u question?
I can't received or send sms.
Is that possible to edit or change sms center number, due to I don't use sprint.
I use local number on my country, I can't find in the message setting.

rejanmanis said:
Nice works men, I really appreciated.
Will try this as soon as possible when I get home.
Could I ask u question?
I can't received or send sms.
Is that possible to edit or change sms center number, due to I don't use sprint.
I use local number on my country, I can't find in the message setting.
Click to expand...
Click to collapse
For MMS, try going into the memo app and type ##3282# in the search box. Tap edit and enter your SPC (aka MSL) lock code. Tap Others and go to the MMSC URL. Change this URL to whatever your provider uses for MMS.
For SMS you'll probably need to use something like QPST to modify the SMS settings. There is probably a dialer code you can enter via the memo app, but I'm not sure how to do it that way.

insanity213 said:
For MMS, try going into the memo app and type ##3282# in the search box. Tap edit and enter your SPC (aka MSL) lock code. Tap Others and go to the MMSC URL. Change this URL to whatever your provider uses for MMS.
For SMS you'll probably need to use something like QPST to modify the SMS settings. There is probably a dialer code you can enter via the memo app, but I'm not sure how to do it that way.
Click to expand...
Click to collapse
thx i'll figure it out,
and 1 more thing, i dont use sprint coz i live in indonesia, i use local operator CDMA called Smartfrend,
If installed this ROM and repartition, will i destroy my unlocked carrier?
Thx for the info

rejanmanis said:
thx i'll figure it out,
and 1 more thing, i dont use sprint coz i live in indonesia, i use local operator CDMA called Smartfrend,
If installed this ROM and repartition, will i destroy my unlocked carrier?
Thx for the info
Click to expand...
Click to collapse
no it should not mess with the modem's nvram (where those settings are stored)

[Q] Installing Arpeggiomod on new 5660m

Sorry if this is a n00b question that has been answered before but I have been reading a lot about rooting/flashing this phone and I am feeling very intimidated. There is a lot of info out there and almost all of it is different in the details.
I will be purchasing a 5660m tomorrow and want to install arpeggiomod and then unlock.
1. Do I have to root the phone before flashing with arpeggiomod? If so can I root with superoneclick?
2. Do I just follow the V0.9 instructions posted here http://forum.xda-developers.com/showthread.php?t=1263025 to install arpeggiomod? I flash the zip file using odin right? Do I need to restore factory defaults before flashing?
3. I need to unlock the phone since I want to use it with Rogers. Do I just use the bml5 unlock method?
Thanks a lot.

1. No. Arpeggiomod Rom comes with Root
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
3. Yes you can use BML5 Method. Guide Here
Either click on:
EDIT 7 nov 2011: BML5 method guide
or
EDIT 31 aug 2011: Now Supersafe (BML5) method
Both guide works fine.
If this helped please click Thanks!

Peteragent5 said:
1. No. Arpeggiomod Rom comes with Root
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
3. Yes you can use BML5 Method. Guide Here
Either click on:
EDIT 7 nov 2011: BML5 method guide
or
EDIT 31 aug 2011: Now Supersafe (BML5) method
Both guide works fine.
If this helped please click Thanks!
Click to expand...
Click to collapse
Should I flash arpeggiomod first and then unlock? If not what order of operations do you propose?

Flash first then unlock. But if your phone does not say it's locked
then don't try to unlock it!

Peteragent5 said:
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
Click to expand...
Click to collapse
Still a bit confused about this step.
So is the following process correct:
1. Format sd card from RFS to ext4 using the ext4 converter on this page http://forum.xda-developers.com/showthread.php?t=1263025
2. No need to run the v0.9 Backup and Restore User Data Scripts since I will have no data on the phone.
3. Install px-CWM-v2.zip http://forum.xda-developers.com/showthread.php?t=1493932 on this page in recovery mode. Should I use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz) instead since arpeggiomod uses phiexz kernel?
4. Wipe factory defaults
5. Use the 0.9 ROM on this page http://forum.xda-developers.com/showthread.php?t=1263025 and flash using the cwm recovery tool.
6. Do i need to wipe factory defaults again after arpeggiomod rom is flashed?

1.correct
2.correct
3.Use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
4.Correct
5.Yes
6.Yes

Peteragent5 said:
1.correct
2.correct
3.Use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
4.Correct
5.Yes
6.Yes
Click to expand...
Click to collapse
Thank you very much.
Can I also say that you are doing a great job and that you should keep up the good work. I know that this compliment may not carry much weight since I am new around here but I come across your helpful posts a lot in other threads and you are doing a bang up job.

Thanks man!

FusiveR said:
Still a bit confused about this step.
So is the following process correct:
1. Format sd card from RFS to ext4 using the ext4 converter on this page http://forum.xda-developers.com/showthread.php?t=1263025
2. No need to run the v0.9 Backup and Restore User Data Scripts since I will have no data on the phone.
3. Install px-CWM-v2.zip http://forum.xda-developers.com/showthread.php?t=1493932 on this page in recovery mode. Should I use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz) instead since arpeggiomod uses phiexz kernel?
4. Wipe factory defaults
5. Use the 0.9 ROM on this page http://forum.xda-developers.com/showthread.php?t=1263025 and flash using the cwm recovery tool.
6. Do i need to wipe factory defaults again after arpeggiomod rom is flashed?
Click to expand...
Click to collapse
Welcome on the board, you'll start getting the hang of things in due time. You're researching a good deal, which is an excellent way to do things.
Let me correct some things from Peteragent5's reply though:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
The ext4 converter does not touch your MicroSD card at all. It formats the internal /data, /system and /cache partitions to ext4.
If you want an additional ext4 partition on your SD card (often referred to as /sd-ext) to use scripts such as Darktremor Apps2SD or S2E, the Phiexz kernel included with ArpegGioMod 0.9 supports those.
SIM-unlocking requires root to read the BML5 partition. Since ArpegGioMod is already rooted, you might as well do it after you've installed the ROM, this will save you from having to root only to wipe that ROM immediately afterwards. (Or do it from CWM, which is also rooted.)
2. Correct
You only need to wipe once in CWM, either before or after flashing the ROM. In the specific case of a new ArpegGioMod 0.9, CM7 or CM9 installation, the formatting of the user data partitions to ext4 wipes them at the same time. To be honest I don't really know where this whole "wipe twice" thing comes from nor what its based on.

Darkshado said:
Welcome on the board, you'll start getting the hang of things in due time. You're researching a good deal, which is an excellent way to do things.
Let me correct some things from Peteragent5's reply though:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
The ext4 converter does not touch your MicroSD card at all. It formats the internal /data, /system and /cache partitions to ext4.
If you want an additional ext4 partition on your SD card (often referred to as /sd-ext) to use scripts such as Darktremor Apps2SD or S2E, the Phiexz kernel included with ArpegGioMod 0.9 supports those.
SIM-unlocking requires root to read the BML5 partition. Since ArpegGioMod is already rooted, you might as well do it after you've installed the ROM, this will save you from having to root only to wipe that ROM immediately afterwards. (Or do it from CWM, which is also rooted.)
2. Correct
You only need to wipe once in CWM, either before or after flashing the ROM. In the specific case of a new ArpegGioMod 0.9, CM7 or CM9 installation, the formatting of the user data partitions to ext4 wipes them at the same time. To be honest I don't really know where this whole "wipe twice" thing comes from nor what its based on.
Click to expand...
Click to collapse
Thanks a lot for the details.
I see that you have posted detailed instructions for the n00bs in your master arpeggiomod post. Should I follow these? It seems like it because what you wrote above complies with your instructions.

Either. I answered your questions more directly here and figured the first thread post could use some clearer instructions, which I did afterwards.

Complete noobie here. This thread saved my life LOL thanks Shado and Furious. I DID brick my phone, trying to Odin flash a ZIP file (smart one...), but got unbricked just as quickly... it wasnt like this in the PSP Homebrew and CFW days LOL
Just another question for the Droid Gurus: How do I get a2sd up and working on ArpegGio? It seems like a very useful and simple app but I'm having trouble finding specifics... I read somewhere you can only use upto 1gb for apps, not to mention I have Windows 7 so I don't know if I am able to format in ext4... Thanks in advance for anyone who points me in the right direction!!

db416 said:
Complete noobie here. This thread saved my life LOL thanks Shado and Furious. I DID brick my phone, trying to Odin flash a ZIP file (smart one...), but got unbricked just as quickly... it wasnt like this in the PSP Homebrew and CFW days LOL
Just another question for the Droid Gurus: How do I get a2sd up and working on ArpegGio? It seems like a very useful and simple app but I'm having trouble finding specifics... I read somewhere you can only use upto 1gb for apps, not to mention I have Windows 7 so I don't know if I am able to format in ext4... Thanks in advance for anyone who points me in the right direction!!
Click to expand...
Click to collapse
Oh. It seems like you can just install DT's A2SD right away cause of the kernel right? So just download Dt's A2SD from his Facebook page or somewhere in XDA Forums if you find the latest... Then put in root of SDCard and install from Recovery

I just about asked "where's the thanks button" ... why did it take me so long to convert from Blackberry? I'll never miss BBM... XDA rules and can't wait to stay tuned for future progress

Darkshado said:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
Click to expand...
Click to collapse
Hello all.
I've been lurking on the forums for over a week now, reading tons of stuff, and learning all I can about my new Android phone. I'm a "Windows guru" but new to the 'droid scene. I think I'm ready to flash my phone and really start delving into the custom goodness available to us.
I've read almost every post by Darkshado and Peteragent5 about the Gio S5660M, and would like to try out ArpeggioMod until a version of CM is out of development.
My big question is which CWM Recovery do I flash and how. Instructions say to use Peteragent5's modded CWM, but there are 4 versions in this thread. I have a rooted stock phone on the Solo network. Do I use the Odin version, or one of the other ones via Download/Recovery mode? I'm a little paranoid about bricking my phone.
Thank you in advance for any info provided. A huge thank you to Darkshadow and Peteragent5 for their ongoing work for the Canadian Gio!

Usually you're gonna have to start with the Odin version.
A more "unorthodox" method that should also work would involve flashing the recovery.img file directly to bml9 with the dd command on a rooted phone.
I did not include an assert line to check the model of phone reported in my updater scripts, so it shouldn't matter which version you flash. As long as that recovery supports etx4 properly. (Not all do, such as the older builds by Hyriand, which were configured for RFS only.)
In the case of Peteragent's ROMs, his scripts check for the presence of a 5660M and not just a 5660 from the build.prop included in the recovery ramdisk. Hence the need for the modified build prop compared to Phiexz's original builds which report as 5660.

Maelmord said:
My big question is which CWM Recovery do I flash and how. Instructions say to use Peteragent5's modded CWM, but there are 4 versions in this thread. I have a rooted stock phone on the Solo network. Do I use the Odin version, or one of the other ones via Download/Recovery mode? I'm a little paranoid about bricking my phone.
Click to expand...
Click to collapse
Use the "My ROMS" ODIN version. It should be the same as this link http://www.mediafire.com/?uxzesrnfswxxwes but don't use this link forever because if the file gets updated you will be using a deprecated version.

FusiveR said:
Use the "My ROMS" ODIN version. It should be the same as this link (cut due to posting restrictions...) but don't use this link forever because if the file gets updated you will be using a deprecated version.
Click to expand...
Click to collapse
Thank you. I have spent most of this day playing with flashing and formatting.
This is the file I used to get CWM installed. From there I used Darkshado's directions from Arpeggiomod. I found that if I run the re-odex script, several apps force close on boot (like the CPU clocker and samsung.singin(?) ) so as long as I don't run that, everything works great.
I then installed darktremor's a2sd after partitioning and formatting my sdcard. When I load dt's A2SDGUI it shows 24MB sd-ext (even though i formatted it to 1GB). When I load Titanium Backup it shows the 1GB /sd-ext but none of my apps got installed there. I'm not done playing with this part yet, lol.
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.

Maelmord said:
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.
Click to expand...
Click to collapse
1. Install Root Explorer.
2. Go to /system/app
3. Mount filesystem as r/w (in the upper right corner)
4. Delete ADW Launcher (Make sure you still have TouchWizLauncher)
5. Reboot and test.

Maelmord said:
Thank you. I have spent most of this day playing with flashing and formatting.
This is the file I used to get CWM installed. From there I used Darkshado's directions from Arpeggiomod. I found that if I run the re-odex script, several apps force close on boot (like the CPU clocker and samsung.singin(?) ) so as long as I don't run that, everything works great.
I then installed darktremor's a2sd after partitioning and formatting my sdcard. When I load dt's A2SDGUI it shows 24MB sd-ext (even though i formatted it to 1GB). When I load Titanium Backup it shows the 1GB /sd-ext but none of my apps got installed there. I'm not done playing with this part yet, lol.
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.
Click to expand...
Click to collapse
Would you mind clearing Dalvik cache and then running the re-odexing script? See if that still causes force closes?

[Q] Correct Upgrade Path from 3.2 Gen2 to Custom ROM

Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks

You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App

NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.

Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked

Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.

From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App

masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!

I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...

Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip

Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip

I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium

toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.

Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.

NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.

This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.

NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.

Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.

NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.

I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.

[Q] Rooted but need HELP with ROM & Recovery Plz!

Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!

Making progress but still confused...?
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
BrianN_Cols_OH said:
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Click to expand...
Click to collapse

Success - Finally got CWM - Ready to play with ROMs
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
BrianN_Cols_OH said:
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
Click to expand...
Click to collapse

BrianN_Cols_OH said:
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
Click to expand...
Click to collapse
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.

More updates...
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
nikon120 said:
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
Click to expand...
Click to collapse

New issues - need help with CM 10.1...
OK, I've made progress and learned a lot. Essentially restored the bricked phone by going back to stock. Then, I started my process again.
- Used ODIN to flash rooted kernel with CM 5.0.2.7
- Flashed Cyanogenmod 10.1.3
- Flashed correct Gapps (dated 8/12 I think)
Software great, but modem not working. So, then I found the forum for the NS4G modem patches. I've tried several and I did get one to work. But, the latest version of CM 10.1 has SU built-in. When I do the modem repair, it breaks my SU root.
I've tried the nitest kernal (by the way, I like the TWRP recovery better than CM - it). I've tried several of the modem patches.
Do I need to go back to a certain stable version of CM 10? What order to I need to apply things?
Here's what I have on the phone at the moment. It has SU/root but no modem.
- Android 4.2.2
- 3.0.79-JB42-nitest-nr kernel
- CM 10.1-20130526-NIGHTLY-epicmtd (although I've tried several other builds)
I was sooooooo close. Please help? How do I get my modem working AND keep my SU/root?
BrianN_Cols_OH said:
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
Click to expand...
Click to collapse

ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.

Modem issues...
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
nikon120 said:
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Click to expand...
Click to collapse

More info...
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
BrianN_Cols_OH said:
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
Click to expand...
Click to collapse

Modem.bin
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse

BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
BrianN_Cols_OH said:
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
Click to expand...
Click to collapse
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4

Thanks!
Great, thanks so much. I will look for the modem files a little later.
nikon120 said:
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse

BrianN_Cols_OH said:
Great, thanks so much. I will look for the modem files a little later.
Click to expand...
Click to collapse
Ok, all Epic modems and NS4G modems are reuploaded. I also included the swap files for each. Everything with (Flashable) means to be flashed within recovery. Those swap files are the blob changes I mentioned earlier. This way you can swap modems using recovery, rather than relying on Odin.
Everything in the Odin folder can be placed in the phone slot and flashed as-is. (No need to extract the .bin file from the archive.)
As for the built-in root manager in CM, I'd try reflashing the rom first, and then messing with the modem.

One of my first ROM flashes, could you please double check?

Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works

You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.

viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.

Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.

viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.

dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.

viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.

dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF

I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.

viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.

dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.

viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.

dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!