Related
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Scribes said:
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Click to expand...
Click to collapse
Technically, not really.
The official way to do it is flash calks fb17, boot up, and then odin rogues fb17 kernel/recovery.
HOWEVER.... Once booted into calks fb17 you can download rom manager,
Flash recovery from there selecting sgs2 as the phone and NOT e4gt
Boot into recovery from rom manager
Flash Rogue's fb17 kernel/recovery
Worked well for me.
ics
There have been many many bricks when trying to flash from ics back to gb .. The data partition on several phones has been fried leading to unrecoverable brick .... so far most going back to gb from ics have been using odin to be safe .... dont touch the cwm touch recovery with ics .... it leads to bricks .... The safest so far has been odin a gb rom then odin cwm recovery and then run your nandroid from there ..Be safe
I am running the ICS FB17 pre-rooted leak and flashed the zip with rouge, it had the stock ics recovery so i went back to this page (http://forum.xda-developers.com/showthread.php?t=1342728) and downloaded the latest auto root and ran option D and the option A to flash the rouge for the FB15 modem.
Scribes said:
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Click to expand...
Click to collapse
If you are concerned about having to "touch" Odin again, then you shouldn't be flashing any of this stuff for now..
ICS/CWM
did just as RigorousNinja went back to GB 4.0 by PhathomHacker no problemshttp://forum.xda-developers.com/showthread.php?t=1342728
The oneclick installer will put cwm on any ics build I have seen so far. I just used it on FB21 Rooted in fact. Just run letter D then CWS-15;Rogue
http://uperoo.com/index.php?r=dl&a=1293311
Sorry to whoever for reposting but I have no idea where I got it from now..
Thanks to Steady Hawkin for FB17+CWM-Rogue(repack)
It is available in the Auto Root sticky in Development or in my signature.
The latest one includes FB17+CWM-Rogue as well.
Epix4G said:
There have been many many bricks when trying to flash from ics back to gb .. The data partition on several phones has been fried leading to unrecoverable brick .... so far most going back to gb from ics have been using odin to be safe .... dont touch the cwm touch recovery with ics .... it leads to bricks .... The safest so far has been odin a gb rom then odin cwm recovery and then run your nandroid from there ..Be safe
Click to expand...
Click to collapse
Can you elaborate why it is bad to flash back to GB through CWM? I've done it twice already due to overheating in ICS and haven't had any issues. I just want to know if damaging my phone by doing that :/
SuperSwagSauce said:
Can you elaborate why it is bad to flash back to GB through CWM? I've done it twice already due to overheating in ICS and haven't had any issues. I just want to know if damaging my phone by doing that :/
Click to expand...
Click to collapse
It isn't bad to flash back to GB through CWM per se.
It is bad to fake flash CWM Touch onto an ICS linux 3.0 kernel and do a restore or wipe. The combination of CWM Touch and the ICS linux 3.0 kernel has caused many people to hose their /data partition in such a way that even repartition using ODIN doesn't allow /data to be written to anymore.
sfhub said:
It isn't bad to flash back to GB through CWM per se.
It is bad to fake flash CWM Touch onto an ICS linux 3.0 kernel and do a restore or wipe. The combination of CWM Touch and the ICS linux 3.0 kernel has caused many people to hose their /data partition in such a way that even repartition using ODIN doesn't allow /data to be written to anymore.
Click to expand...
Click to collapse
Ahh so it's a CWM Touch issue you say? That's a relief
SuperSwagSauce said:
Ahh so it's a CWM Touch issue you say? That's a relief
Click to expand...
Click to collapse
That's the one people happen to have had bad experiences with, but the general issue is "fake/temporary" flashes which end up pairing recoveries with kernels they may not have been intended to work with or may not have been tested with, then trying to operations on your phone which may overwrite sections that are hard to recover from.
CWM Touch if integrated (ie repacked with) and tested with a kernel it appears to work ok.
Honestly, just take the time to get to know Odin... its really safe and useful when you invest the time (which is very little). and this is coming from a 'noobs' perspective. As for CWM i have used it as well (not touch) and been okay, but like everyone else has warned... be careful.
sfhub said:
That's the one people happen to have had bad experiences with, but the general issue is "fake/temporary" flashes which end up pairing recoveries with kernels they may not have been intended to work with or may not have been tested with, then trying to operations on your phone which may overwrite sections that are hard to recover from.
CWM Touch if integrated (ie repacked with) and tested with a kernel it appears to work ok.
Click to expand...
Click to collapse
Gotcha, so my steady hawkin FB17 kernel/recovery should be good.
I have a few questions... I am coming from using a Nexus One and am intimately familiar with flashing Modems/Kernels/ROMs... modifying framework and other APKs for custom features... and all kinds of other fun stuff. I have been running into videos and such that I am sure their procedure works but I don't really trust that all their information is accurate. Seeing as some people putting up how-to info say I need to install 7-zip to run a self-extractable archive... they obviously don't know what they are talking about... no offense meant to them as it is a very good instructional video... I just do not feel comfortable asking them detailed questions.
With the E4GT I keep seeing people saying that you can brick your phone by flashing between GB and ICS ROMs without wiping and such. Now I would like to get a few things strait. On Nexus One the recovery kernel was held in a different partition than the normal OS. Then there was an initial bootloader that would load either the recovery or the normal OS. Now if you were to shoot yourself in the foot and do something you shouldn't with your normal OS you could always boot to recovery and start from your latest nandroid or just flash w/e you felt like. Is this not how the E4GT works? If you flash a kernel (which I would assume would goto your normal OS's boot partition being seperate from the bootloader and recovery) does it actually "brick" your phone? Do ICS ROMs mess with something in the bootloader or recovery that could prevent you from going back to recovery and reflashing whatever you want?
The permenant bricks are happening with the partitions getting screwed. Even ODINing over a stock tar will fail at that point. Normally with any device we would JTAG and write new partitions.
Only 2 things I know are. The partitions between GB and ICS are different. Our phones recovery is packed into the kernel and since we don't have the source for the ICS kernel yet I would expect their to be issues with CWM repacks on our phone with ICS.
Ive been one of the ones with no issues flashing around in ICS. But I would not dare try to flash a GB rom back. SFHUB's One Click ODIN's are a quick way to flash over an EL29 or prior tar but you can do it the old fashioned way as well.
Read here, On how to avoid
http://forum.xda-developers.com/showthread.php?t=1525495
xST4T1K said:
Read here, On how to avoid
http://forum.xda-developers.com/showthread.php?t=1525495
Click to expand...
Click to collapse
I really appreciate your informational thread. The problem is... I went through all this information as well as some other stuff prior to posting this. While the information is nice it is basically "follow these procedures and things should work according to my experience". What I am looking for is detailed information as to what is causing tons or people (relative to what i saw in the N1 community) mentioning these bricking issues. I am trying to gather and consolidate this information as I can not find it readily available.
RainMotorsports said:
The permenant bricks are happening with the partitions getting screwed. Even ODINing over a stock tar will fail at that point. Normally with any device we would JTAG and write new partitions.
Only 2 things I know are. The partitions between GB and ICS are different. Our phones recovery is packed into the kernel and since we don't have the source for the ICS kernel yet I would expect their to be issues with CWM repacks on our phone with ICS.
Ive been one of the ones with no issues flashing around in ICS. But I would not dare try to flash a GB rom back. SFHUB's One Click ODIN's are a quick way to flash over an EL29 or prior tar but you can do it the old fashioned way as well.
Click to expand...
Click to collapse
This is more along the lines of what I am looking for. So... from what I gather here:
1. As far as it is known... something having to do with partition allocation information is different between GB and ICS ROMs.
2. E4GT version of Android's recovery is not held seperate from the running OS and is dependent on the Initramfs (and contained within) that is used by the actual running OS.
3. In order to flash back to GB you must use SFHUB's One Click ODIN which uses a known procedure that works. (Why does this work where others methods do not? Possibly, when update script runs from package used in recovery [modified ICS recovery] it has to do with partition information the recovery is expecting is different from actual? ICS kernel source so its exact method of actually executing an update script is unknown?)
Please correct post to correct any information you see here which is incorrect or acknowledge what information you believe to be correct.
EDIT: Correction to 3 as I didn't read post properly and also in response to RainMotorsports post. Also, changed SGS2 in 2 to E4GT
EDIT: Changed "kernel" in 2 to "initramfs" Detailed information about all this can be found in Sfhub's detailed explanation post within this thread which you can find here:
http://forum.xda-developers.com/showpost.php?p=24398615&postcount=13
You can go back to gingerbread as many times as you want, just use the one click odin el29 above. That's the safest and simplest way. I've done it countless times.
Goblinlord said:
2. SGS2 version of Android's recovery is not held seperate from the running OS and is dependent on the kernel (and contained within) that is used by the actual running OS.
3. If you flash to ICS do not flash back to GB??? (though this goes against the information contained in xST4T1K's post)
Please correct post to correct any information you see here which is incorrect or acknowledge what information you believe to be correct.
Click to expand...
Click to collapse
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.
RainMotorsports said:
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.
Click to expand...
Click to collapse
Perfect ^^... thanks for the information this is exactly the type of information I was looking for.
OP, check PM.
There was actually some talk from a few that were using JTAGs to unbrick only to find out that the NAND was fried in a way you would only expect to see from something hit by an EM surge. While odd, it's not impossible and we can only speculate at the changes in 3.0.15 ICS kernels from Samsung vs. the GB ones. I'm no electrical expert so I won't speculate on what would cause it.
I know how the Nexus was coming from a G2/Desire Z a lot of things were very similar. This phone is completely different. So far as I can tell the recovery and kernel share the same space. While you could flash 4EXT as your recovery and never change it but constantly change kernels - you must flash the recovery w/ the kernel on this. Probably has something to do with us having ODIN - that might be taking up residence where the recovery or fastboot would normally reside. I could be completely wrong though. As far as the 7zip thing. I don't know what videos you're talking about specifically but I do know a lot of people tell others to install it just because it's one of the most useful things when modding. Whether it be an apk or an entire rom. This is of course when your speaking about Windows. Linux has its own built-in goodies.
KCRic said:
There was actually some talk from a few that were using JTAGs to unbrick only to find out that the NAND was fried in a way you would only expect to see from something hit by an EM surge. While odd, it's not impossible and we can only speculate at the changes in 3.0.15 ICS kernels from Samsung vs. the GB ones. I'm no electrical expert so I won't speculate on what would cause it.
I know how the Nexus was coming from a G2/Desire Z a lot of things were very similar. This phone is completely different. So far as I can tell the recovery and kernel share the same space. While you could flash 4EXT as your recovery and never change it but constantly change kernels - you must flash the recovery w/ the kernel on this. Probably has something to do with us having ODIN - that might be taking up residence where the recovery or fastboot would normally reside. I could be completely wrong though. As far as the 7zip thing. I don't know what videos you're talking about specifically but I do know a lot of people tell others to install it just because it's one of the most useful things when modding. Whether it be an apk or an entire rom. This is of course when your speaking about Windows. Linux has its own built-in goodies.
Click to expand...
Click to collapse
Thanks for the info KCRic. If you could provide a link for the thread you refer to about the NAND memory being fried it would be great. Also... I completely agree with 7-zip being useful as I have used it now for many many many years... my point was more... the person didn't even know the difference between an self-extracting executable and an archive file.
Please look at the following thread for background on the problem and speculation as to technically why the bricks are happening:
http://forum.xda-developers.com/showthread.php?t=1504808
My theory on to why restoring a gingerbread and is that the fact that on ICS the recovery actually has access/see add'l hidden partitions that the gingerbread recovery does not access or see (example the triangle away tool which needs ics) Most likely when the restore is done the nand gets rewritten to the wrong partitions due to new hidden partitions not accounted for and in a sense overwriting something crucial and ends up in either destroying the partition and bricking the device. I'm no expert on the matter though so take this with a grain of sand.
I am reading from mobile so only skimmed through this. Some questions are probably already answered. Excuse the typos, it is a pain to type long replies on mobile.
The 7zip thing is probably because i package everything as 7zip self-extractors, which on windows means you just double-click on the *-sfx.exe and choose the directory to unpack to. The roms are relatively large so compressing them makes sense and 7zip does a better job compressing and is cross platform. Anyway on platforms other than windows you just treat the -sfx.exe file like a regular 7zip archive and use 7zip or other archive tool to unpack, similar to if zip or rar was used to compress.
Regarding why there are bricks, there are two more prevalent ways of bricking this phone.
1) flashing an intl gs2 factory or leaked rom that includes the intl bootloader. On our phone, the intl bootloader disables the usb port so you can no longer recover using any tool that uses the usb port. If you happen to have custom recovery still on the phone, you can use an update.zip to update your rom, kernel, and modem, but your usb port is still useless.
2) using an ics kernel combined with a custom recovery to wipe, restore, or otherwise do partition operations that affect /data. This is not a deterministic brick in that you can have the same operation work fine many times, but then suddenly have it fail. There were some more deterministic variations of this type of brick involving a temp flashed cwm touch, where wiping/factory reset would very frequently cause the /data brick.
So what is the /data brick? Apparently a change in the ics kernel combined with certain custom recovery operations can cause a hardware failure in the emmc memory for the data partition section. This will cause all future attempts to format, overwrite, restore, the data partition to hang or fail. We know it is a hardware failure because even using jtag to bit blast the proper software fails. Often people don't realize their data partition has bricked right away because they are in the midst of wiping/factory reset or restoring a backup. Then something isn't working right so they go and use odin to get back into a known state, but find odin hangs on the data partition. This may lead them to think odin is not working right or even that odin caused the problem, but in reality, odin is just the messenger that your emmc is screwed. The damage was done earlier. We know that to be the case, because
1) in all instances it was traced back to on operation with an ics kernel and custom recovery
2) this type of brick never existed before the ics kernels (linux 3.0 kernels came out)
3) galaxy note on ics has the same type of emmc brick
4) we know there were changes to the emmc code because different areas of emm are exposed in ics kernels which were not exposed in gb kernels
Your only recourse for this type of brick is to return for replacement, as even jtag fails.
Regarding odin, if you are coming from another platform, it is basically like fastboot in that it is a failsafe type flash using low-level bootloader routines which do not depend on working kernel or rom. Most types of soft brick can be easily addressed by odin. As to why it is safer, it is using low-level bootloader routines so doesn't depend on the ics kernel which we have found to be problematic in certain situations listed above.
Regarding recovery, I also came from a platform where recovery was a separate partition. This made sense to me. Alas, this phone does not use a separate partition for recovery. Instead reckvery is packed into the initramfs of the normal android kernel. if you flash a new kernel, that comes with a new initramfs, and you will get whichever recovery was packed into its initramfs, whether that be stock or custom recovery.
Ironically, there is a separate partition labelled recovery.bin that for some reason is not used. The contents are exactly the same as the kernel, so in the current state it just serves as a backup of the active kernel.
In closing, I would suggest treating this phone as a new platform and don't make assumptions based in past experience. Being android, there are similarities, but there are also important differences/quirks to be aware of which are easily missed if assumptions are made.
RainMotorsports said:
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.
Click to expand...
Click to collapse
Coming from the Evo this is all new to me so I am sorry but I just wanted to double check. Right now I am still on eg30 and rooted. It is ok then to just use the odin one click to flash el26/29? Then I have to also flash cwm again correct? Sorry for the noobish questions, just trying to avoid any problems.
Sent from my SPH-D710 using xda premium
Natedog1 said:
Coming from the Evo this is all new to me so I am sorry but I just wanted to double check. Right now I am still on eg30 and rooted. It is ok then to just use the odin one click to flash el26/29? Then I have to also flash cwm again correct? Sorry for the noobish questions, just trying to avoid any problems.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wow your on EG30 nice lol.
Yes you can one click or regular odin straight to EL29 if you want. There are one clicks for ICS up to FC24 (No FD02 yet) so if your not going to a custom rom just stock rooted you can use those too.
EL26 - http://forum.xda-developers.com/showthread.php?t=1416477
EL29 - http://forum.xda-developers.com/showthread.php?t=1433101
FC24 - http://forum.xda-developers.com/showthread.php?t=1573752
You can go from EG30 to EL29 using the no data ones and not lose anything. Going to ICS or going backwards you should always use the normal ones that erase your data.
You still need custom recovery to flash a rom. You can use sfhubs autorooter on a rooted install to gain it or odin over a kernel.
RainMotorsports said:
Wow your on EG30 nice lol.
Yes you can one click or regular odin straight to EL29 if you want. There are one clicks for ICS up to FC24 (No FD02 yet) so if your not going to a custom rom just stock rooted you can use those too.
EL26 - http://forum.xda-developers.com/showthread.php?t=1416477
EL29 - http://forum.xda-developers.com/showthread.php?t=1433101
FC24 - http://forum.xda-developers.com/showthread.php?t=1573752
You can go from EG30 to EL29 using the no data ones and not lose anything. Going to ICS or going backwards you should always use the normal ones that erase your data.
You still need custom recovery to flash a rom. You can use sfhubs autorooter on a rooted install to gain it or odin over a kernel.
Click to expand...
Click to collapse
Yeah I just picked up the phone the other day after my evo crapped out. It is like learning a new language going from the evo to this. Modems, odin, triangles.... Trying read as much as I can before doing much. Thanks for your help. I appreciate it a lot.
I am a little apprehensive about flashing an ics rom after reading about all the issues everyone is having. I do miss the hell out of cm but I think I should hold off on flashing that for now. Is it "safe" to flash fc24 one click even though it is ics?
Sent from my SPH-D710 using xda premium
Yes if your going to ICS its as safe as it gets. ODIN is samsungs fastboot. The firmwares are stored on tars. SFHUB packages tars in a one click setup for odin so you dont have to deal with odin itself. Writing a full tar with odin write a whole firmware rather than just the rom or just the modem etc like when using recovery.
The other option is to flash an ICS rom through custom recovery preferably EL26 or EL29.
As far as triangles go if you want to know about those. If you flash a custom kernel or anything else not signed by samsung through ODIN it will show a triangle at boot as well as increase the counter shown in the download mode. This is just there to tell the phone company you have been messing with it.
I have never tripped the triangle myself but a USB jig on older bootloaders or the Triangle away app on ICS will take care of it.
Using ODIN to flash the FC24 + rooted is not a bad place to start *in my opinion* to try out ICS on the E4GT. But there are lessons to this too - please make sure you are using a good quality USB cable (such as the Sammy one), don't flash if your system is at risk of shutting down in the middle (such as a laptop with a sketchy battery and no A/C) and by all means, if it looks like it is hanging... give it time before resorting to unplugging the USB cable. The last part is the modem and takes several minutes, no matter how fast your PC is.
No matter what you decide, good luck and don't be afraid to ask any questions. It is far better to err towards caution and ask for advice than go on our own and risk ending up with a paperweight instead of a phone.
Thanks garwynn i was actually just coming back to add that. Yeah I always recommend to people to flash with a laptop if they have it in case of a power outage.
Thanks for the tips and the advice guys. Much appreciated. Right now the ics roms are pretty much all leaks correct?
Sent from my SPH-D710 using xda premium
Well new company gave me 20% Sprint discount and have become sick of my Tmobiles poor coverage. However I fear wimax might be sucky too here in Seattle. Anyway, long time member here and have been involved in the HTC Sensation and One forums. Both with very very stable roms and kernals.
I was excited to pick up a couple Sprint Galaxy epics and the guy at Sprint had his all rooted and claimed it was smoking fast.
However I came to this forum and see all kinds of complaints of loss of stability just from simple Root of the Epic? Also have not read any stable ICS roms and I have read all of the threads. Plus read this phone is very easy to brick under clockwork. With sensation we use Aroma and it rocks!
So before I move on, I am not looking to break rules on asking ROM questions. I simply would like some input on what ICS rom is stable and supported still as I see many devs have moved on the the sg3 here.
What kernal and radio or what you call modem is stable and how do you find what is for your phone match?
Lastly, what is safest way to ROOT and flash ROMS for this phone?
I did read the stickies but am still confused.
I may be just happy at first to simply ROOT and install the fix for Hot Spot Wi fi and go from there.
Thanks so much.
Not even sure if phones will arrive with stock ICS tomorrow or GB...
Ice
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
rovar said:
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
Click to expand...
Click to collapse
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
iceshark said:
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
revamper said:
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Click to expand...
Click to collapse
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
Thats what it seems from hours reading each ROM thread. Reminds me of the Sensation when GB and or ICS first leaked. Will most likely just root stock and go from there.
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
revamper said:
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
Click to expand...
Click to collapse
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
iceshark said:
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
Click to expand...
Click to collapse
I know I personally use Mijjahz's "GOODNESS" ROM and it runs smooth. Many mods and add ons with more added daily. I flashed agat's 2.2 kernel because I don't like the 2.3 that version 16.6.1 comes with.
I also flashed FF18 over my EL26 modem. Modems don't change between flashing I believe. Those you update yourself. A lot of folks stay on EL29 or find something that works perfectly in their area.
Sent from Konnor the E4GT.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
QFT.
ICS ROMs are very stable at this point.
iceshark said:
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
Click to expand...
Click to collapse
you're quoting some of my new user guide here, and i haven't updated it since the OTA came out so it somewhat overstates the danger of bricking (not a bad thing really, made you read, didn't it!?) which was much easir to do before we got kernel source, since then agat63 and chris41g have been killin it in kernel development since they got ICS source... their ICS kernels are safe to flash from and can be found in the dev section, if you're on the stock FF18 rooted with stock kernel i would personally ODIN (mobile or desktop) back to EL26, and from there flash whatever custom ICS rom you like, as far as I'm aware all of the roms come with a safe kernel these days but do be sure to double check and flash one if it does not... at that point going forward should you wish to flash something else you can just do it via cwm as per usual without having to odin back to gingerbread....do note however that you can't use touchwiz kernels with AOSP roms, there asr safe AOSP kernels as well however...
edit: oops, just noticed revamper addressed most of this on the last page, to answer another one of your questions though you can try as many modems as you like and decide which one works best for you, its varies phone to phone and area to area... the modem is not at all required to match the build number of the rom, (example: may people still use the el29 modem with ICS) you can use ANY modem with ANY rom
Ive flashed this phone hundreds of times. Put your rom and any other zips you have on external card. Then to do a full clean wipe go to privacy. then factory data reset then check usb storage. You can skip this step, but this is how to get it factory fresh. Download the el26 cwm kenal. Its posted everywhere. Next open Odin go to pda and select EL26 cwm kernal. Uncheck auto reboot. Have battery cover off! Flash kernal pop battery out when it starts to boot. or says pass. then use the vol up and power combo hold them down until boot screen pops up then let off. Next flash calkulins wipe all or wipe no data. . Never brick never fail. Then flash your rom and tweaks and be happy. Ive done this driving down the road its that easy. Laptop sitting in passenger seat with odin up lol. Plus i drive a 5sp full size truck. Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob. I,ll be making multi scenario flashing youtube movies soon. Like mobile tech videos does.
Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob.
Click to expand...
Click to collapse
That's all there is to say.
I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.
RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium
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.