Ok... so if you saw my other thread, I couldn't get Odin to work. Turns out, I couldn't get Mass storage to work either. And neither windows nor osx (heimdall) was recognizing my phone in DL mode!
So I bought Mobile Odin off the market (thanks chainfire!) and tried to rollback using that. While the Kernel and ROM flashes were sucessful, no matter what I do, my phone still reports it's on FB27 Baseband.
So, my current status is, DL mode isn't working, and Mobile Odin is having trouble flashing the modem back to EL29 modem. Anything over my USB doesn't work right now (MHL, Mass Storage, Download) but the phone does charge over USB.
Did you verify that ##8778# is set to "All"?
"All" allows me to connect usb storage... Download mode still a no go. Thanks!
but
Just a long shot, did you happen to flash an International GS2 ICS release? I don't think you did or the USB port would be completely not functional.
Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.
sfhub said:
Just a long shot, did you happen to flash an Internation GS2 ICS release? I don't think you did or the USB port would be completely not functional.
Click to expand...
Click to collapse
absolutely not! phone would probably be beyond bricked... but thanks for the suggestion
Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.
Click to expand...
Click to collapse
Ah... since it's signed... I'll give it a try!
jfcooley said:
Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.
Click to expand...
Click to collapse
He would have to install CWM first. Unlike the stock recovery in ICS test builds, the stock recovery in GB builds will only install files signed by Samsung.
sfhub said:
He would have to install CWM first. Unlike the stock recovery in ICS test builds, the stock recovery in GB builds will only install files signed by Samsung.
Click to expand...
Click to collapse
correct... didn't work. I'm beginning to wonder is something is wrong with the hardware.
Got an idea though, since you got USB working for me... I turned on usb debug, and used autoroot to install the EL29 Rouge Kernel, which game me CWM recovery. I'm trying to flash Calk's EL29 modem.zip through there now...
wait for it... says success... rebooting now.... firmware report says... EL29. Thank god!
Thanks for everyone's help!
EDIT: AHAHAHAHA ODIN WORKS!!!!
I have been attempting to flash this modem with no luck the past couple of days. I am on AOKP, so I have been using Mobile Odin to flash back to EL26 with CWM to flash the modem zip. Every time I try this, it hangs on flash for a LONG time, and eventually errors out. I then tried to Mobile Odin the modem.bin I pulled from the same zip and it gave no error, but didnt change anything.
Has anybody else had this problem? Is the zip on the official modem thread bad? If anyone has any tips for upgrading to FE22, I would appreciate it. I try to avoid desktop Odin as much as possible, so if you have a "mobile" solution, it would be best for me.
Thanks!
jmlott said:
I have been attempting to flash this modem with no luck the past couple of days. I am on AOKP, so I have been using Mobile Odin to flash back to EL26 with CWM to flash the modem zip. Every time I try this, it hangs on flash for a LONG time, and eventually errors out. I then tried to Mobile Odin the modem.bin I pulled from the same zip and it gave no error, but didnt change anything.
Has anybody else had this problem? Is the zip on the official modem thread bad? If anyone has any tips for upgrading to FE22, I would appreciate it. I try to avoid desktop Odin as much as possible, so if you have a "mobile" solution, it would be best for me.
Thanks!
Click to expand...
Click to collapse
If you want to try by other than CWM you'll need to use the desktop ODIN as mobile can't support CDMA modem updates (at least based on previous posts.)
Redownload the modem.zip. it sounds like a bad download. Its happened to me before.
Sent from my SPH-D710 using XDA
I've re-downloaded a couple of times and got the same thing, that's why I was wondering if the actual file was bad on the site. I guess I'll have to go the Odin route. I run nothing but linux though, so it's a pain for me to setup a windows machine to work from for 5 minutes. I've read bad reviews of the FF02 modem, but maybe I'll give that one a try anyway through CWM first.
Thanks guys.
I've never been able to flash a modem with mobile odin. Always regular odin.
So I actually encountered this issue when attempt to flash a different modem that basically was not part of an original leak. So in my case I am running leak FF18 that was fresh ODIN'd was experiencing wifi issues (like a lot of people currently are on the ICS builds) and attempted to flash a different modem (FD26) to remedy the issue. On a side note the FD26 did remedy my wifi issues HOWEVER it introduced the beloved "couldn’t install on USB storage or SD card " error when attempting to install certain apps. The app I was testing with was Crackle. Anyways knowing that this was the only change I had made to my system I tried to flash back the FF18 modem. That was a not go So after a bunch of research I came across an article that basically said to permanently remedy the situation you needed to reOdin. So I figured how about we half ass it the the odin that still preserves data. Cause frankly I am getting tired of rebuilding my device. BINGO! that did the trick. After that I reflashed my custom ROM I am running (Blazer ICS edition) and was able to install all apps.
So now that we are done with the long drawn out story. The take away from this is:
-flashing different modems (and possibly kernels) other than what comes bundled with leak can cause this issue
-grab a copy of the ODIN bundle for your specific leak that preserves data if you dont want a data loss and reflash
-install any app to your liking
I hope this helps somebody
Cheers!
I found something a little different. I figured out a couple of ways to change the modem for ics. If you are already on ff18 and have ff18 modem and want to change to a different one, there are a few ways to go about it. One is to mobile odin flash agat's repack for ff18. Boot into his recovery, wipe cache and dalvik then flash whatever modem cwm zip. After that, boot back into system, update profile then prl then reboot. Use mobile oding to put back the original stock ff18 kernel and that will fix the unable to install thing. Another way is if you're coming from gb and know which modem you want, boot into recovery in gb and flash the desired modem. After that, use mobile odin to flash ff18 one click full wipe version. It won't install the modem so that snafu can work for your benefit. I could say more but it's time for bed for me.
This isn't the case. Agat63 has been working extensively with this error.. It has to do with the zimage file. I Odin every time I update and at this moment I cannot install apps to sd and SB Nation won't install unless I unmount my card. I am glad you've have success with your method, but I'm pretty sure if you install a repacked kernel right now you'll be back to the same situation.
The Root said:
This isn't the case. Agat63 has been working extensively with this error.. It has to do with the zimage file. I Odin every time I update and at this moment I cannot install apps to sd and SB Nation won't install unless I unmount my card. I am glad you've have success with your method, but I'm pretty sure if you install a repacked kernel right now you'll be back to the same situation.
Click to expand...
Click to collapse
I was able to reproduce this issue about 4 times last night without fail. Amd every single time I reOdined my phone issue was resolved everytime
Sent from my SPH-D710 using XDA
I had this same problem and couldn't find the answer I wanted anywhere. I tried factory reset and formatting the SD but it didn't work. Phone isn't rooted or anything. In the end I unmounted the SD card and then I was able to install the game then mount the SD card and it worked great.
thank you that totally worked
zoey said:
I had this same problem and couldn't find the answer I wanted anywhere. I tried factory reset and formatting the SD but it didn't work. Phone isn't rooted or anything. In the end I unmounted the SD card and then I was able to install the game then mount the SD card and it worked great.
Click to expand...
Click to collapse
thanks, that totally worked for me.
Do you think this is a ROM issue that will be fixed?
I forgot to wipe data, factory reset, and so on. I tried wiping everything data and factory reset... and reinstalling the rom. I am on Team Rogue.
Be careful with the factory reset.
Did you try to use one of sfhubs one click to end the boot loop issue?
Providing you can get into download mode?
:edit: Took about 20 mins to search on your issue and from what I gather, if you can get to Odin mode (download), what I suggested should end the boot loop. Its because cache and delvik weren't wiped from what i'm seeing. Maybe some one has a better answer for you.
Sent from my SPH-D710 using xda app-developers app
It's funny because I soft bricked last night.. But the information I'm about to provide, it may be a shorter easier route but I will just state what I did
I got into odin mode
Once I was in odin mode I connected my phone to my pc.. Let drivers install and my phone was recognize
I had a sfhub one click package (el29 stock rooted) used that.. Phone reset and I was stock rooted again
After that I ran the el29 cwm option from the epic 4G Touch package
Now I wanted to get back to ICS..
So I got into clockwork mod recovery
Flashed Rujelus format x2 zip (calkuins works as well)
Restored my Nandroid (or you can flash a rom(
Before I rebooted I flashed a ics kernel and then rebooted my phone and I'm back running the Blu Kuban.. No issues
*Posted this in another thread..,so this should help you as well.. Thanks to MoHoGalore for pointing me to this post..*
Seemed to be two at the same time with similar issues and your answer fit well.
Sent from my SPH-D710
MiguelHogue said:
It's funny because I soft bricked last night.. But the information I'm about to provide, it may be a shorter easier route but I will just state what I did
I got into odin mode
Once I was in odin mode I connected my phone to my pc.. Let drivers install and my phone was recognize
I had a sfhub one click package (el29 stock rooted) used that.. Phone reset and I was stock rooted again
After that I ran the el29 cwm option from the epic 4G Touch package
Now I wanted to get back to ICS..
So I got into clockwork mod recovery
Flashed Rujelus format x2 zip (calkuins works as well)
Restored my Nandroid (or you can flash a rom(
Before I rebooted I flashed a ics kernel and then rebooted my phone and I'm back running the Blu Kuban.. No issues
*Posted this in another thread..,so this should help you as well.. Thanks to MoHoGalore for pointing me to this post..*
Click to expand...
Click to collapse
Was the sfhub what you used to root your phone with at first?
Again I was using Team Rogue's CWM and I forgot to wipe everything off. So I connected my Phone to my PC and my drivers werent there. So I tried reinstalling Kies but apparently they are under maintenance, bummer. So I tried to restore everything with odin3excution v1.81, this whatt I used to root my phone. It wasnt appearing. So I wiped factory reset,cahe, dalvik and so on.... and restarted. Nothing. So I downloaded Odin3 "Android + SLP "v1.85 and my device showed up on odin mode.
VetoHero said:
Was the sfhub what you used to root your phone with at first?
Again I was using Team Rogue's CWM and I forgot to wipe everything off. So I connected my Phone to my PC and my drivers werent there. So I tried reinstalling Kies but apparently they are under maintenance, bummer. So I tried to restore everything with odin3excution v1.81, this whatt I used to root my phone. It wasnt appearing. So I wiped factory reset,cahe, dalvik and so on.... and restarted. Nothing. So I downloaded Odin3 "Android + SLP "v1.85 and my device showed up on odin mode.
Click to expand...
Click to collapse
Correct I used sfhub's one click at first to root my phone (and get out of a soft brick).. I was on team rogue cwm as well, I believe it doesn't make a difference tho .. And yesterday my device showed up in odin as well but it wasn't successful installing.. As far as Kies.. Hmmm I didn't use Kies.. I installed the samsung drivers to my pc.. I forgot where I downloaded them.. At work right now so I can't provide a link... But a little searching you should be able to find them
MiguelHogue said:
Correct I used sfhub's one click at first to root my phone (and get out of a soft brick).. I was on team rogue cwm as well, I believe it doesn't make a difference tho .. And yesterday my device showed up in odin as well but it wasn't successful installing.. As far as Kies.. Hmmm I didn't use Kies.. I installed the samsung drivers to my pc.. I forgot where I downloaded them.. At work right now so I can't provide a link... But a little searching you should be able to find them
Click to expand...
Click to collapse
I found a link and installed them. Phone is working great after odin. Installed Team Rogue CWM and now on AKOP's ICS rom. Thank you.
Best Wishes,
Diego
VetoHero said:
I found a link and installed them. Phone is working great after odin. Installed Team Rogue CWM and now on AKOP's ICS rom. Thank you.
Best Wishes,
Diego
Click to expand...
Click to collapse
Sweet. Could you change your OP title to include answered or resolved?
With new e4gt owners, due to the cheaper sells, might help someone who's looking too. Just a thought.
Sent from my SPH-D710
Glad you are back on track.. Happy flashing my friend
You flirted with bricking your phone by doing a factory reset with CWM Rogue. Glad it worked out but I suggest you don't do that again. Use Calkulin's format all zip instead or flash the stock EL26 kernel and do your factory reset with that, then flash your new Rom
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.