Does this latest rom have "true" removal of CIQ, including all of the calls made for it? If so, wouldn't that make it better than any of the mods we currently have?
Better is in the eye of the beholder. It might be "cleaner" but functionally it is the same. If CIQ isn't running and and isn't submitting your information is it any different than CIQ not being there?
I make this distinction simply because you might pick up some other baggage you aren't interested in by getting the release that has CIQ removed by Samsung. If you like everything you get, the EL13 is probably a good solution for you. If you don't then you need to decide whether the cleaner excising of CIQ is worth the baggage.
Is it functionally the same, though? As far as i can gather, with the mods the files are deleted but calls to them are still being made, potentially using battery. So it doesnt use ciq but battery could be used requesting the absent files. If this new samsung leak eliminates those calls then it is better, right?
satur9ine said:
Is it functionally the same, though? As far as i can gather, with the mods the files are deleted but calls to them are still being made, potentially using battery. So it doesnt use ciq but battery could be used requesting the absent files. If this new samsung leak eliminates those calls then it is better, right?
Click to expand...
Click to collapse
From the standpoint of the privacy, if it isn't being sent or recorded, they are functionally the same.
There are some residual actions left over but personally I doubt you will notice any battery difference. I see a failed attempt to start up CIQ (failed because CIQ has been disabled) in the logs probably once or twice a day. Those are easily dwarfed by the other battery bugs yet to be fixed.
For me, I'm ok with just disabling CIQ in the current ROMs. If I'm happy with everything in EL13, I might migrate to it, but chances are there are things I won't like about it. It appears they modified the bootloader so a USB jig no longer resets the ODIN flash count (obvious workaround). They've gotten rid of bouncy effect due to the Apple lawsuit, but that has been there since EK02. Some people are saying they are seeing LoS but it isn't clear if they are mixing and matching.
So yes, as I previously mentioned, EL13 has a cleaner no CIQ, but would you be willing to deal with let's say LoS to get that? Those are the types of tradeoffs I'm talking about. If you don't see LoS or LoS turns out to be an artifact of mixing and matching, then maybe EL13 is worth going to. It all depends on the baggage you get.
sfhub said:
It appears they modified the bootloader so a USB jig no longer resets the ODIN flash count (obvious workaround).
Click to expand...
Click to collapse
Well this blows.......
Sent from my SPH-D710 using xda premium
sfhub said:
It appears they modified the bootloader so a USB jig no longer resets the ODIN flash count (obvious workaround).
Click to expand...
Click to collapse
It seems this is a YMMV type of thing. Others have mentioned their USB jig works fine, and I know that mine does as well, attached is my about screen.
Mine worked also. I have eb13 rom, kernel and modem.
Sent from my SPH-D710 using xda premium
t3hpyroboy said:
It seems this is a YMMV type of thing. Others have mentioned their USB jig works fine, and I know that mine does as well, attached is my about screen.
Click to expand...
Click to collapse
Did you flash the bootloader? That is where they implemented the counter. If you didn't flash the bootloader, then you won't notice any difference, which is why I said "obvious workaround"
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
crawrj said:
Mine worked also. I have eb13 rom, kernel and modem.
Click to expand...
Click to collapse
Same as above.
As stated above, don't flash the bootloader and your JIG will work fine.
How do you get around this? Simple: Don't ODIN the .tar instead use the EL13 rom that's flashable through CWM. There's no bootloader in it so the current one doesn't change. They're using the bootloader from the GSM SGSII from what I've read, and it doesn't support using a JIG. I'm just restating what I've read here.
KCRic said:
They're using the bootloader from the GSM SGSII from what I've read, and it doesn't support using a JIG. I'm just restating what I've read here.
Click to expand...
Click to collapse
To be more accurate, they do support using a JIG. What they removed in more recent builds is support for resetting the flash count, something which they used to support as well.
It isn't a functionality gap between GSM and CDMA (if anything, CDMA usually lags GSM), it is an active change to remove functionality.
Obviously it isn't as much an issue ONCE YOU REALIZE what is going on. Most of the work was in figuring out what was causing the behavior change. Once you know that, the workarounds are trivial.
As an aside, at some point Sprint will switch to the new bootloader on phones from the factory so people buying the E4GT later in the production cycle will get the new bootloader automatically. They won't have the opportunity to say no, only the opportunity to say downgrade.
That is why it is useful to have discussions and come up with workarounds.
Still looking for the download link to Calks tweaked EL13
Related
After hours on the phone with Sprint and being transferred to multiple departments, I received a call back today explaining the following:
Samsung has delivered the MR with the LOS update for Sprint. SPRINT WILL NOT BE PUSHING THIS MR OUT UNTIL MID TO LATE DECEMBER POSSIBLY JANUARY.
Please keep in mind this information did not come from a customer service rep or a sprint store rep.
Sent from my LOS 4G Touch
********************UPDATE*********************
*******************10/27/2011*******************
Just wanted to post an update...
Since the original post I have exchanged my E4GT for a new one... I have had the new phone for several days now and although I have not had any LOS issues (specifically circle with line through it) I have lost several calls (Message with "Call Lost)
Spoke to the escalation managers boss and this is what I was told...
-The MR is still in testing at Sprint and the absolute earliest release date will be in December.
- The update will address LOS issue, maintaining wifi connections, and something about refreshing 3g/4g after losing signal (my phone was breaking up and missed some words here and there)
- They are also aware of some minor bugs ie phone dialing wrong people in certain cases and some resource leaks???? (not sure what he was talking about gain) assuming it has to do with battery drain... but there is no guaranteed that the issues will be addressed in the MR and that it may be addressed in the next version of the OS (I'm assuming ICS)
He went on to explain that the service in my area (Southern California) will get worse before it gets better. He said old towers are being replaced with new multi-band towers in the area which means at any given time we will have less towers in service till the upgrades are completed.
Now take everything with a grain of salt... I know that this is not concrete information but the guy is one out of a million at sprint who seems to actually know what he is talking about.
It's time for either EVERYBODY PANIC or SPECULATE WILDLY.
I'll start with the wild speculation:
It's because that's the ICS update and they can't roll that out before the the Galaxy Nexus release due to some sort of exclusivity agreement with Google and Verizon (and maybe Sprint)...
SOMEONE LEAK SOMETHING ALREADY PLEASE FOR THE LOVE OF GOD LEAK SOMETHING.
Okay, NOW EVERYBODY PANIC
daneurysm said:
Okay, NOW EVERYBODY PANIC
Click to expand...
Click to collapse
lol
10 char
Wonder what it'll break on phones like mine that never had any issues to begin with lol.
Sent from my SPH-D710 using xda premium
daneurysm,
Actually in passing the person who contacted me explained that although SGSII will receive ICS it will not be till May or June and that the MR will be separate from ICS
poppygt said:
Wonder what it'll break on phones like mine that never had any issues to begin with lol.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ive been thinking the same thing the last couple weeks lol
Im going to take pass on it for a couple week after release
neverends said:
daneurysm,
Actually in passing the person who contacted me explained that although SGSII will receive ICS it will not be till May or June and that the MR will be separate from ICS
Click to expand...
Click to collapse
To be honest that seems like a reasonable time frame. For me? No...but from a major carrier, yes. I mean reasonable as in "reasonable to expect." I, personally, find it downright insulting since working (if alpha/beta) builds of it almost certainly exist.
All snarkyness aside, thanks for the heads up.
Sounds like the author is making this stuff up.
Did you forget to mention the important information about ICS release in the OP, OP?
I call BS.
Who cares? We have XDA for stuff like this.
nabbed said:
Sounds like the author is making this stuff up.
Did you forget to mention the important information about ICS release in the OP, OP?
I call BS.
Click to expand...
Click to collapse
My call was not to Sprint to get ICS it was a call to get out of my contract in regards to LOS. The person that responded to me gave me solid information about the LOS MR. He had information about the MR and the rest was speculative. I posted the facts and omitted the speculation in my OP.
Call BS if you like... When you have to wait till the end of the year to get an LOS fix from Sprint just remember you were warned.
_MetalHead_ said:
Who cares? We have XDA for stuff like this.
Click to expand...
Click to collapse
That is what I hope for as well... However we don't have the actual E4GT Kernel yet. Thus far I had 0 LOS prior to root - about 50 instances of LOS after root - and only 5 LOS after restoring to stock thanks to ACS
neverends said:
That is what I hope for as well... However we don't have the actual E4GT Kernel yet. Thus far I had 0 LOS prior to root - about 50 instances of LOS after root - and only 5 LOS after restoring to stock thanks to ACS
Click to expand...
Click to collapse
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
neverends said:
He had information about the MR and the rest was speculative. I posted the facts and omitted the speculation in my OP.
Click to expand...
Click to collapse
I don't see any facts here... its all speculation.
lafester said:
I don't see any facts here... its all speculation.
Click to expand...
Click to collapse
Fair enough. Though the time frame seems reasonable in carrier-logic.
Either way I think it's safe to say that it's enough so that EVERYBODY PANIC.
nabbed said:
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
Click to expand...
Click to collapse
I rooted with the Zedomax pre-rooted kernel and went back to stock by using stock rooted kernel, factory reset, and odined this http://forum.xda-developers.com/showthread.php?t=1273647
then factory reset again and I updated profile after resetting...
lafester said:
I don't see any facts here... its all speculation.
Click to expand...
Click to collapse
that's fine - the information was received from people directly responsible for releasing sprints MR's. Also I contacted Samsung prior to calling sprint and was told that the issue was resolved and the fix was "in the pipeline"
nabbed said:
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
Click to expand...
Click to collapse
I have not rooted my phone and I get LOS pretty frequently. Factory resets and whatnot do not fix the issue. There is a real issue here, and they're being very quiet and slow about fixing it.
neverends said:
I rooted with the Zedomax pre-rooted kernel and went back to stock by using stock rooted kernel, factory reset, and odined this http://forum.xda-developers.com/showthread.php?t=1273647
then factory reset again and I updated profile after resetting...
Click to expand...
Click to collapse
You obviously messed something up, since you were not getting any los before rooting. You can try a couple of things:
1) Flash cwm kernel of any kind (I prefer cwm4, because it doesn't require external sd card for nand operations.)
2) Wipe system/data/cache, flash a stock rom (as stock as you can find).
3) Power off and flash stock-pulled from bubby, or lostkernel (I think both are los free).
4) Reboot and immediately update profile and prl.
You can also try to ask someone at sprint to reprovision the phone. Or do it yourself with hands-free activation data reset. In case zedo kernel somehow messed up provisioning data.
Another idea (just came up with it, don't know if it makes sense) is to program the phone yourself with qpst app. Compare qpst programming data of your own phone to that of someone else without los. Maybe there's an obvious discrepancy, and you can fix it.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
awesomeindeed said:
I have not rooted my phone and I get LOS pretty frequently. Factory resets and whatnot do not fix the issue. There is a real issue here, and they're being very quiet and slow about fixing it.
Click to expand...
Click to collapse
Where did you get your phone?
nabbed said:
You obviously messed something up, since you were not getting any los before rooting. You can try a couple of things:
1) Flash cwm kernel of any kind (I prefer cwm4, because it doesn't require external sd card for nand operations.)
2) Wipe system/data/cache, flash a stock rom (as stock as you can find).
3) Power off and flash stock-pulled from bubby, or lostkernel (I think both are los free).
4) Reboot and immediately update profile and prl.
You can also try to ask someone at sprint to reprovision the phone. Or do it yourself with hands-free activation data reset. In case zedo kernel somehow messed up provisioning data.
Another idea (just came up with it, don't know if it makes sense) is to program the phone yourself with qpst app. Compare qpst programming data of your own phone to that of someone else without los. Maybe there's an obvious discrepancy, and you can fix it.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
Where did you get your phone?
Click to expand...
Click to collapse
I got the phone from Best Buy and I re provisioned it myself using ## code and MSL
I rooted early on so it it possible that I never notices LOS prior to rooting
neverends said:
I got the phone from Best Buy and I re provisioned it myself using ## code and MSL
I rooted early on so it it possible that I never notices LOS prior to rooting
Click to expand...
Click to collapse
Are you saying the hardware is defective?
Exchange it.
So far I have zero complaints about this phone, there are some ui things I would like fixed, and I know can be fixed via rooting, but they just don't seem to be enough to push me over the edge. I have files downloaded and ready to go, but just can't seem to take the plunge. I thought I had my first los today, but the phone recovered as soon as I was back in signal(if it hadn't that would have done it).
So why should I root?
Sent from my SPH-D710 using Tapatalk
You can always revert back to the stock kernel if you have an issue (or have them that frequently that you can't stand it). Anybody who thinks that once you root there is no way to go back is an idiot. "lol, I got no LOS then I rooted and even though I put stock kernel back its all [email protected] lol" not true.
I got 2 LOS in the first week stock...rooted...got a bit more than usual, but nothing crazy. Flashed stock kernel back, still rooted, didn't have another for a few weeks until I flashed a new kernel...flashed back, have had none...etc etc etc, YMMV, but, umm, I don't think you have anything to be afraid of. Just know what you are doing...don't just flash stuff and figure it out later. Know why you want something and how to 'put it back'...also having/making a USB jig would be a good idea, but not necessary.
You can get them for like $3 on amazon or build one with a microUSB cable and $1 worth of stuff from radioshack.
I don't know about you but I certainly didn't get this phone to NOT mod it.
I didn't get the phone to keep it stock, not really worried about los, it recovers after flying for 2 hours with no signal, rooting shouldn't make much difference., planning on using viperom and lostkernel.
Maybe tomorrow I will root
Sent from my SPH-D710 using Tapatalk
flyboy1100 said:
I didn't get the phone to keep it stock, not really worried about los, it recovers after flying for 2 hours with no signal, rooting shouldn't make much difference., planning on using viperom and lostkernel.
Maybe tomorrow I will root
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
The only thing I can tell you is that read the directions and understand ODIN for all of the ODIN stuff you do. That is one of the ways you can brick the fnck out of this phone...not paying attention in ODIN. Don't write a partition if you are not told to...and try to only use it to flash a kernel+CWM and flash everything else from CWM if and when possible.
If you aren't worried about LOS (and it is real and under the right circumstances it'll effect every phone...reboot...no big deal...if it is flash a pulled stock kernel) then go for it.
I haven't tried ViperROM on this phone yet, but, I can tell you from my time with the E3D that kid knows what he's doin'....I'm sure this ROM is no different and I've heard nothing but great things about the LoST kernel.
If you don't want to root, don't. Why would anyone want to pressure you?
Sent from my extra sensory space modulator while performing the slippery cricket
Tell us how it goes. You won't be disappointed.
Sent from my HTC Glacier using xda premium
If U need convincing, you probably don't need it.
Sent from my Galaxy S2
Someone convince me to strangle my puppy. I love him and all and he is very well mannered but if you guys can talk me into strangling him, I will.
ravizzle said:
If U need convincing, you probably don't need it.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I agree. You root cause u want to. If u want someone to convince u then maybe u shouldn't.
Sent From My Evo Killer!!!
I don't understand why some people view this almost like losing their virginity, trying a drug or robbing a liquor store. It's a very well understood technical process with very specific pros and cons that are also very well understood.
Yep. First android phone for me, and I bought it with the full intention of making it MY phone. After all, they are basically an additional limb for most people, no? (I'd say if you're registered with xda that is most likely the case! ) So you might as well go balls to the walls, right? If you're not into that kind of thing, then keep it stock! This phone is AMAZING just sitting at the home screen...it looks awesome! It is a great piece of technology, with plenty of great features and capability, and will serve you very well whether its rooted or not. Good luck with whatever you do!
buggerritt said:
If you don't want to root, don't. Why would anyone want to pressure you?
Sent from my extra sensory space modulator while performing the slippery cricket
Click to expand...
Click to collapse
Not looking for pressure. I will probably root it tomorrow or next week
Sent from my SPH-D710 using Tapatalk
Because all the cool kids are doing it!
I broke down and did it yesterday when someone said viper ROM solved his app freezing due to using a ton of CPU usage bug. So far, so good.
Sent from my SPH-D710 using XDA App
OP if you are on EG30 baseband could you extract the modem.bin file for us so we could test it?
I would just stay stock. Honestly, no offense to the developers, but there is just nothing substantial out there. If you want a couple of different themes, you could consider rooting, but other than that every ROM I have flashed provided close to nothing really.
I mean, what? Battery percentage mod? Removed CIQ? "Speed" tweaks? A reboot option?
Nothing made this phone faster or more efficient than stock touchWiz. There is no real difference except that people like to flash, so they would flash anything.
Sorry. That's just my take on it.
Wait for MIUI or CM.
I gotta say i miss root, I was finicky on rooting my epic 4g ad once I did, oooh lord I never looked back , of course I've stumbled into troubles but following directions, I got back on track and learned a few this gs along the way, now what's stopping me on rooting the ET4G is not having the actual way to go back to full true stock,like we were able to do on the epic 4g with using Odin, giving you a factory full stock phone , or any older device, since we don't have true stock roms and kernels, unless I'm wrong g of course and I've been missing out! If so direct me!
Kikoshi said:
I gotta say i miss root, I was finicky on rooting my epic 4g ad once I did, oooh lord I never looked back , of course I've stumbled into troubles but following directions, I got back on track and learned a few this gs along the way, now what's stopping me on rooting the ET4G is not having the actual way to go back to full true stock,like we were able to do on the epic 4g with using Odin, giving you a factory full stock phone , or any older device, since we don't have true stock roms and kernels, unless I'm wrong g of course and I've been missing out! If so direct me!
Click to expand...
Click to collapse
We have stock roms to ODIN, but it's not factory stock. We have the factory stock kernel that was pulled from a stock phone. What we lack is an OEM RUU to make it 100%-in-every-way-stock.
That said, I have trashed my 4G and wifi somehow on multiple occasions due to rampant recklessness on my part. I just factory-wiped (apparently...I don't remember that part but I must have) and flashed the ODIN rooted stock (with stock kernel) and it fixes everything every time.
daneurysm said:
We have stock roms to ODIN, but it's not factory stock. We have the factory stock kernel that was pulled from a stock phone. What we lack is an OEM RUU to make it 100%-in-every-way-stock.
That said, I have trashed my 4G and wifi somehow on multiple occasions due to rampant recklessness on my part. I just factory-wiped (apparently...I don't remember that part but I must have) and flashed the ODIN rooted stock (with stock kernel) and it fixes everything every time.
Click to expand...
Click to collapse
So then you recommend rooting this early?
i rooted so i could have wifi tethering and control over CPU speeds (via setcpu) in addition, there's some neat functionality that starburst ROM allows:
- better lock screens
- motion controlled silencing of phone
- battery % viewing
some people care about the speed tweaks (i haven't noticed any speed increase) and ciq (i don't really care for this), but there are several reasons to root. that being said, if you don't need the additional functionality of the phone, then preserve your phone's warranty!
Yea I'd say stay stock in terms of the ROM and kernel, but hell yea why not root? Right now I'm running stock kernel with CWM (http://forum.xda-developers.com/showthread.php?t=1305099) and the stock ROM with root and busybox (http://forum.xda-developers.com/showthread.php?t=1282415) and I love it. I was running Midnight ROM but I went back to stock to see if that helped the LoS issues at all. If you're like me and really just want control over the hotspot feature and CPU underclocking (things of that nature) then def go stock rooted fo shoski.
Well, I stopped on the way home from work today to see what was new at Sprint. I've been thinking about getting the EVO 3D... I came home with a Touch.
So. I want to root, so I can run root apps like um, Ad Free etc. What do I need to know about rooting this before I jump in head first? Do these phones have any stupid security etc or anything I need to know about?
I just wanna make sure I don't mess anything up.
What do we have for a recovery etc?
Any tips would be GREAT!
E4GT doesn't have all the locked bootloader stuff to worry about like EVO 3D.
You can start off here:
[ROOT][EG30] Automated root of your existing stock ROM (w/o ODIN or ROM Flash)
That will get you rooted on stock and won't involve flashing anything. It doesn't use ODIN.
There is also a tool called ODIN which lets you flash stuff to the phone outside of Android. It provides fastboot-like functionality. Using ODIN, if you flash unsigned kernels, your boot screen will get a yellow triangle and there is a flash count that gets incremented. Also it'll identify the phone in the boot screen by the real model name (I9100...) rather Galaxy S2. Other than that it'll still boot and work.
Question about this ODIN flasher thingy and the unsigned kernels. Why the increment count etc? What is the point to that?
Thanks for the info btw. I think the link you sent will be a good start. Don't need to flash any custom roms yet. I wanna get the hang of the stock one first. This Samsung has a very different feel then the HTC EVO/Sense stuff.
Need to ask Samsung.
Probably they want to keep track of whether you installed non-standard software, possibly for service reasons.
---------- Post added at 01:43 AM ---------- Previous post was at 01:35 AM ----------
BTW you can use a USB jig to get rid of the Yellow Triangle and reset the flash counter.
If you just want to get rid of the Yellow Triangle, you can flash back the stock kernel, then use other methods like the Root Installation Kit I pointed to earlier.
Once you get CWM, flashes through that won't affect the Yellow Triangle and flash count.
Just watch the roots right now the odin has an issue with LOS from what I have seen. I am currently using a direct root which roots the rom.
I assume LOS means loss of service?
OK! Noted.
duced said:
Just watch the roots right now the odin has an issue with LOS from what I have seen. I am currently using a direct root which roots the rom.
Click to expand...
Click to collapse
Stock phones suffer from LOS too. Rooting and some kernels MAY make it worse. I've flashed nearly everything available for this device in the last month and have not had 1 serious unexplainable LOS.
Sent from my SPH-D710 using xda premium
OK! Well I did the MOST important thing I wanted to do which was to get root in there so I could use Adfree!
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
kdoggy said:
OK! Well I did the MOST important thing I wanted to do which was to get root in there so I could use Adfree!
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
Click to expand...
Click to collapse
If it were me, I would use the phone as is for a few days to get some feel for whether your situation will get LoS and what the battery life is. Then you have a baseline to compare to after you start making changes.
It is easy to get really excited and install a whole bunch of stuff and all of a sudden you get LoS or really bad battery life, and then you can't figure out what caused it or even what to expect with the stock phone.
This could lead you to think the phone is at fault when it is actually something that was installed later.
Also with the official Samsung rom out now most of the roms in development will be getting reworked shortly.
Sent from my SPH-D710 using xda premium
Can someone point me to a thread that explains LOS and what do you do if you get it?
kdoggy said:
Can someone point me to a thread that explains LOS and what do you do if you get it?
Click to expand...
Click to collapse
As far as I know the only thing you can really do is reboot the phone. going back to a stock kernal also helps.
kdoggy said:
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
Click to expand...
Click to collapse
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
N00dle said:
As far as I know the only thing you can really do is reboot the phone. going back to a stock kernal also helps.
Click to expand...
Click to collapse
clearing ram fixes it sometimes too
MoMatt said:
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
Click to expand...
Click to collapse
completely agree. been underclocked to 800mhz for a while. No difference in performance and battery increased probably 20%
MoMatt said:
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
Click to expand...
Click to collapse
I'll have to give that a try. I've never been into overclocking these phones. I don't game, I don't use them for video either. I just use them for work to look up help desk tickets while I'm going building to building.
Beats the hell out of lugging my MacBook around just to read some notes on the go.
Maybe a stupid question but I ordered a jig and haven't received it yet but how would I check if it works to leave positive feedback.. I'm stock rooted with Odin no custom recovery.... Would I just turn the phone off take the battery off put it back in and connect the jig? If it goes to download then it works?
Sent from my SPH-D710 using xda premium
Power down the phone, plug in the jig, turn on the phone. It shoudl go into ODIN download mode directly and say something about stats being reset. If it doesn't do the latter, you are probably on a new bootloader and it isn't the fault of the jig.
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
dante32278 said:
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
And from there, are you free to just turn the phone back off by taking out battery?
You don't need to take out the battery. Just press and hold the power button until it resets.
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
It will work with the ICS ROMs as long as you have the original (EG30/31) bootloader. If you flashed the raw leaked tar from Samsung/Sprint, then the reset of flashing data might not work (but it should still put you in ODIN D/L mode). If you flashed one of the ODIN OneClick packages I put together, then all the features will work.
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
rsalinas1 said:
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
Click to expand...
Click to collapse
I didn't read that thread very closely, but MTD is sometimes an overloaded term and could mean different things to different people.
If used to compare flash memory types, we actually have eMMC rather than MTD. eMMC memory are block devices. MTD devices are similar to but not really block devices so they created a new category in the kernel to deal with them.
To get an idea about MTD, read this post:
http://www.linux-mtd.infradead.org/faq/general.html
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes the epic 4g a much better phone versus BML. Oh and it just said that they are types of partition maps, mtd being open and bml being closed source.
Sent from my SPH-D710 using Tapatalk
rsalinas1 said:
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes your phone better versus BML, whatever that is lol.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Ok, I read the thread a little more closely.
It seems the 2 main benefits from switching to the kernel supporting MTD partition format over the stock BML are you can resize the partitions easier and use ext4 (because those new kernels support ext4)
Our kernels already use ext4. w/r/t resizing partitions perhaps some people need more space in /data but most people seem to be ok with it.
It is always nice to have more options, but there is probably less demand for it on this phone than Epic.
I gotcha, maybe we will see it once our devices get older and we need something new lol. So just asking again now that you've read more closely, our phones dont use either of these partition maps correct?
Sent from my SPH-D710 using Tapatalk
I'm actually not sure which partition map we are supporting. I initially read the thread as MTD vs eMMC memory technology, which is different than the purpose of that thread.
I see, maybe you can figure that out for us in your spare time lol (if it really even makes a difference.) The E4GT is a beast of a phone anyways lol.
Sent from my SPH-D710 using Tapatalk
Just an FYI:
I got my jig and put it right in the slot while my phone was still on... it shut down my phone and put it directly into download mode and showed that my counter had been reset.
On a side note, for what ever reason, my GPS started working when I restarted the phone. It hadn't been working for days.
rsalinas1 said:
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
Click to expand...
Click to collapse
If you "brick" your phone, a JIG is not going to help you.
Drumrocker said:
If you "brick" your phone, a JIG is not going to help you.
Click to expand...
Click to collapse
Depends what kind of brick. The /data nonwritable brick still allows you to write every other partition as well as use the jig to reset the counter
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.