Related
[Q] Help flashing [ROM]Bonsai4All EXT4/Clockworks 3.0.0.5 support V2.0.1 >02/03/2011
Ok guys, im gonna attempt a flash([ROM]Bonsai4All EXT4/Clockworks 3.0.0.5 support V2.0.1 >02/03/2011) today on my friends samsung epic 4g which is fully stock at the moment, i already have read the instructions but i need a little guidance in the right direction. I have flashed clockworkmodrecovery using
http://http://forum.xda-developers.com/showthread.php?t=782300
& http://http://forum.xda-developers.com/showthread.php?p=7933592#post7933592
so now i can boot into clockworkmod recovery, but b4 i flash anything im going to do a backup through the clockworkmod recovery, i read in the Bonsai4All thread that i need to "Odin the dk28 modem first", can someone tell me how i can do that, like give me a link to the required files and how i would go about installing them. Also is there anything else that i am not doing that is required to flash to the Bonsai4All ROM from a stock samsung epic 4g , all feedback is greatly appreciated, thanks in advance guys.
This is the Epic wiki. Scroll down to Odin Stock Flashing and follow those instructions. Under Official Roms (just above Odin Stock Flashing) is the dk28 file. It's titled 'SPH-D700-DK28-8Gb-REL.tar.md5 Stock DK28 (Leaked).' That's what you put in Odin to flash to stock dk28. Scroll down further to Community Roms and you will see the Bonsai4All rom. Once you are on stock dk28, have cwm3 installed, and download the Bonsai rom to the SDcard, you can flash Bonsai through cwm.
running_the_dream said:
This is the Epic wiki. Scroll down to Odin Stock Flashing and follow those instructions. Under Official Roms (just above Odin Stock Flashing) is the dk28 file. It's titled 'SPH-D700-DK28-8Gb-REL.tar.md5 Stock DK28 (Leaked).' That's what you put in Odin to flash to stock dk28. Scroll down further to Community Roms and you will see the Bonsai4All rom. Once you are on stock dk28, have cwm3 installed, and download the Bonsai rom to the SDcard, you can flash Bonsai through cwm.
Click to expand...
Click to collapse
The wiki says I have to "Select the victory_8G_100528.pit on the right in the pit section" on step number 4, do I have to do that to flash to Bonsai, or do I just do what you told me.
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
kdunn1994 said:
The wiki says I have to "Select the victory_8G_100528.pit on the right in the pit section" on step number 4, do I have to do that to flash to Bonsai, or do I just do what you told me.
Click to expand...
Click to collapse
When I flashed to stock dk28 , I used the Victory pit along with the SPH-D700-DK28.tar. So, I would do both.
I have used it without victory BUT I was already on dk28. I had a 2.2 rom and I was flashing back to stock dk28.
So, final answer, for the first time going to dk28, I would use both the pit and tar.
On a side note, make sure only the reset time and auto-reboot check boxed are checked. There shoud be three total check boxes. For the first time, only check those. If you install a rom and want to go back to stock dk28 in the future, then only check auto-reboot.
So basically what you're saying. Is all that I really need to do is substitute the dk28 tar u told me instead of the one used on step 5?
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
kdunn1994 said:
So basically what you're saying. Is all that I really need to do is substitute the dk28 tar u told me instead of the one used on step 5?
Click to expand...
Click to collapse
You got it.
Nice ill give it a try when I get out of school.
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
ok, one more question before i begin is, do i backup with clockworkmodrecovery before i flash dk28, or if im correct the flash will delete everything including root, and upgrade the phone to 2.2, so the backup would be irrelevant until b4 i flash the bonasi?
kdunn1994 said:
ok, one more question before i begin is, do i backup with clockworkmodrecovery before i flash dk28, or if im correct the flash will delete everything including root, and upgrade the phone to 2.2, so the backup would be irrelevant until b4 i flash the bonasi?
Click to expand...
Click to collapse
Yes, using flash with ODIN will erase everything including root. So, backup everything before you start. It should backup to your SDcard. When you do the stock flash, root, install cwm3 and flash your 2.2 based rom, you should be able to boot into cwm, go to backup/restore- advanced restore and restore data.
I would install My Backup or something similar before attempting though. Just in case cwm doesn't keep your backup after the flash. It's worked for me in the past. After backup, you can also move the backup file to your computer's hard drive for safekeeping. It's in the root of the sd folder under Clockwork recovery.
thumbs up picking bonsai rom. ive tried midnight, viper, nebula already and none of them even compare to the speeds of bonsai. if your going for speed and no force closes choose bonsai.
to kind of answer your question, always backup, it wont hurt anything.
running_the_dream said:
Yes, using flash with ODIN will erase everything including root. So, backup everything before you start. It should backup to your SDcard. When you do the stock flash, root, install cwm3 and flash your 2.2 based rom, you should be able to boot into cwm, go to backup/restore- advanced restore and restore data.
I would install My Backup or something similar before attempting though. Just in case cwm doesn't keep your backup after the flash. It's worked for me in the past. After backup, you can also move the backup file to your computer's hard drive for safekeeping. It's in the root of the sd folder under Clockwork recovery.
Click to expand...
Click to collapse
ok, thanks, i think i got the steps down, after i have this installed, i root it using(insert link and awesome advice here)?
I'm on my phone now so I can't see the links and so forth. I think the bonsai rom will install root, cwm, convert to ext 4 file system and install bonsai. Double check the rom thread though. If not, theres a one-click root w/ cwm3 in the dev section
running_the_dream said:
I'm on my phone now so I can't see the links and so forth. I think the bonsai rom will install root, cwm, convert to ext 4 file system and install bonsai. Double check the rom thread though. If not, theres a one-click root w/ cwm3 in the dev section
Click to expand...
Click to collapse
So everything worked out great, and it was much easier than i thought, all i needed was some guidance in the right direction and you gave me that "running_the_dream" and for that i can not emphasize enough how much Thanks i have for you, i really appreciate the help, thanks for all the support
kdunn1994 said:
So everything worked out great, and it was much easier than i thought, all i needed was some guidance in the right direction and you gave me that "running_the_dream" and for that i can not emphasize enough how much Thanks i have for you, i really appreciate the help, thanks for all the support
Click to expand...
Click to collapse
Great! Enjoy!
Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity
Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App
Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.
Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.
onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.
I tried to post this on the actual thread about this Update, but I was not allowed because I had not posted 10 times previously.
Anyway, I am new to rooting Android phones….new to android phones for that matter. I have had the Samsung Epic 4G for about a month. I have been looking into rooting the phone, finally decided to go for it. I downloaded the filre for Clockwork Mod version 3.0.0.5/6 - UPDATED FOR EB13 from this site. After doing one run of that bat file and getting stuck on the startup screen, I realized I needed to find a compatible ROM and Kernel and install them before rebooting.
I reset the phone to default settings, using the info on http://forum.xda-developers.com/showthread.php?t=909384 and then I used the kernel
from the original update thread, Default Stock Dual FS kernel For EB13, and the Bonzai ROM from their website. This time, the install worked properly, and when my phone rebooted, the firmware is listed as Bonsai/Kernel_v4.01. So I wanted to backup and uninstall some Samsung Bloatware from the phone,and as I understand it, the Titanium Backup is the best way to do it. Well, I installed it, and it has consistently said the program could not acquire root status. I clicked on the “problems” icon, got busybox and upgraded superuse, and that did not effect anything. I even reflashed the Bonzai Rom, but the end result is the same, I am still getting that same message. Since I have replaced my Rom and have installed Superuser, I have to assume I have rooted the phone, so what could be the problem here? The app SetCPU also says I do not have Root Access. So I am not sure what to do at this point.
Sounds like a failed root:
Root again with the oneclick 3.0.0.6, power off, 3 finger boot and ext4 will be put on automatically. After ext4 installs install bonsai before rebooting.
Sent from Bonsai 7.0.3
Is there a difference between onclick 3.0.0.6 and the one in the thread http://forum.xda-developers.com/showthread.php?t=897612,which is labelled 3.0.0.5/6? Because, if not, that is pretty much what I have done already.
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. Http://www.bonsaigeeks.com
Sent from Bonsai 7.0.3
Top Nurse said:
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. www.bonsaigeek.com
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
This exact thing happened to me after trying everything from the EC05 OTA. Just run the bat file again on the phone...nothing else and it will work fine.
Hello,
I was going to try out a near stock root but it requires clockwork mod. The only overwrite of my previous stock was using Odin and a tar file.
Can someone help me out and explain why or if there is much a difference between a tar overwrite and using CWM?
Also can you just install CWM on the stock and then flash it?
tar files are what ODIN uses to flash your phone. ODIN is an application that runs on your PC and communicates with your phone over the USB cable using ODIN protocol. ODIN can pretty much flash anything on your phone, so just saying you used ODIN to flash your phone doesn't tell folks trying to answer your question anything useful. You need to tell use which tar file you flashed.
CWM is a recovery program that runs on your phone. It takes signed zip files and installs them. It can also flash things like kernel and ROM, and with some versions of the kernel can flash full modems as well. It can't flash as much as ODIN can, but it can flash most of what you would find useful.
If you started from stock, you can root your phone and install CWM using the Auto Root thread in my signature.
I've been using sfhub's scripts for the last few weeks. Highly recommended and well documented.
Sent from my SPH-D710 using Tapatalk
sfhub said:
tar files are what ODIN uses to flash your phone. ODIN is an application that runs on your PC and communicates with your phone over the USB cable using ODIN protocol. ODIN can pretty much flash anything on your phone, so just saying you used ODIN to flash your phone doesn't tell folks trying to answer your question anything useful. You need to tell use which tar file you flashed.
CWM is a recovery program that runs on your phone. It takes signed zip files and installs them. It can also flash things like kernel and ROM, and with some versions of the kernel can flash full modems as well. It can't flash as much as ODIN can, but it can flash most of what you would find useful.
If you started from stock, you can root your phone and install CWM using the Auto Root thread in my signature.
Click to expand...
Click to collapse
Thanks. The file I think I ran before was acs-eg30-stock-kernel-pulled.tar. My phone got the OTA update to 2.3.6 and I'd like to root it again so I can tether again. I was going to install Calkulin's Stock Rooted EL13 Rom as I think that will enable to me to tether again.
boe said:
Thanks. The file I think I ran before was acs-eg30-stock-kernel-pulled.tar. My phone got the OTA update to 2.3.6 and I'd like to root it again so I can tether again. I was going to install Calkulin's Stock Rooted EL13 Rom as I think that will enable to me to tether again.
Click to expand...
Click to collapse
That would root you but you would need to root your current version first and install CWM (you would have lost root after the EK02 OTA upgrade) before you could install that.
If you want a complete EL13 system, my suggestion is you use Titanium to backup your user data, then ODIN the FULL EL13 rooted system. This will give you EL13 Modem, Kernel, and ROM (pre-rooted) in a single operation.
[ODIN][TAR] SPH-D710.EL13_CL806482 (EL13 Modem/Kernel/ROM - Full Restore - Rooted)
Then restore your data.
There is also a "NoData" version of the ODIN tar file, which is the same as above, but doesn't reset your User Data (meaning you keep your existing User Data). I would suggest the latter for folks who know what they are doing because you may need to clear dalvik-cache and possibly android market data.
The full install that resets your user data is a "cleaner" install but both will work.
You'll be rooted after installing that. If you want CWM, just use the Auto Root thread:
[ROOT][NCIQ][EG30/EG31/EK02] Auto root your existing stock ROM (w/o ODIN/ROM Flash)
and choose Option C to install EL13+CWM.
Thanks - I'll try to do that today.
sfhub said:
That would root you but you would need to root your current version first and install CWM (you would have lost root after the EK02 OTA upgrade) before you could install that.
If you want a complete EL13 system, my suggestion is you use Titanium to backup your user data, then ODIN the FULL EL13 rooted system. This will give you EL13 Modem, Kernel, and ROM (pre-rooted) in a single operation.
[ODIN][TAR] SPH-D710.EL13_CL806482 (EL13 Modem/Kernel/ROM - Full Restore - Rooted)
Then restore your data.
There is also a "NoData" version of the ODIN tar file, which is the same as above, but doesn't reset your User Data (meaning you keep your existing User Data). I would suggest the latter for folks who know what they are doing because you may need to clear dalvik-cache and possibly android market data.
The full install that resets your user data is a "cleaner" install but both will work.
You'll be rooted after installing that. If you want CWM, just use the Auto Root thread:
[ROOT][NCIQ][EG30/EG31/EK02] Auto root your existing stock ROM (w/o ODIN/ROM Flash)
and choose Option C to install EL13+CWM.
Click to expand...
Click to collapse
Thanks for all your help.
Just so I'm sure I know what you think would be best for me, I should pretty much do this http://forum.xda-developers.com/showthread.php?t=1394332 and then I won't need to do the CWM thing?
boe said:
Thanks for all your help.
Just so I'm sure I know what you think would be best for me, I should pretty much do this http://forum.xda-developers.com/showthread.php?t=1394332 and then I won't need to do the CWM thing?
Click to expand...
Click to collapse
Given where you are currently at and considering you want to end up with a rooted el13, that would be the fewest steps.
So far no real issues. I did have the marketplace issue which is mentioned in the thread and clearing it took care of it. I've only played with my phone for about 30 minutes since flashing but I should know more by tomorrow.
Thanks for your help.
After using this one for a day, I'd probably recommend not using it quite yet. I've had lots of dropped calls, inability to use the internet on a regular basis and GPS seems way off. I've been using my phone for a few months now and haven't had this kind of bad luck in the past even with my previous rooted version of this phone worked great. While it was certainly easy, I don't think this version of the ROM is ready yet.
I'm sure the person who created it knows 1000 times more about android than I do but this one has problem with voice/data that needs a little work still so I'd hold off on it until that is tweaked. Or it could be that Sprint is having some serious issues with their network in Connecticut.
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.