Related
what method is best "cwm", samsung, or OTA. anybody notice any differences between the 3? which one is best if there is a best one?
i am also wondering why my header for the thread dissapeared? well i guess someone else will probably ask the same soon.
For me its cwm since it comes out of devs.
the update.zip will leave your apps and settings, but requires you to be on stock di18 with stock recovery and still have the stock apps and so on.
the odin image wipes everything.
the pre-rooted cwm flashable update also requires di18, but not full stock and will leave your apps and settings as well as give you root.
The "best" way is up to you.
I used the odin method straight to eb13 because I was already using dk28 with ext4 and the genocide kernel. Worked like a charm. Now all I have to do is get ext4 working again.
I used the 200mb tool from samsung. Works best imo.
I was already running dk28, so I just used the Odin tar for the modem, and flashed the genocide kernel. Now just waiting for some devs to release eb13 based roms
I did the sammy method on my phone and it worked without a hitch compared to the ODIN pain in the lucky if you get it to work after 10 times method. my wife had the OTA method. both of our GPS worked really good before and now after it takes up to 10 minutes to get a lock. is this to be expected? is there a fix now that sprint ruined my wifes gps, mine is in violation of the warranty now and is the tester phone.
How is your phone in violation of the warranty? If you odin to stock your in warranty unless you dismantled your phone....? Just curious
Sent from my SPH-D700 using XDA App
I did oden it back to stock but it never really seemed like it did before. I see that the sammy uninstalled cwm so I think its legit again, and ready to send back if the gps doesnt fix itself.
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
crud accidentally posted this in general
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
R1ptide said:
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
Click to expand...
Click to collapse
How man? lmao
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
daneurysm said:
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
Click to expand...
Click to collapse
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
squshy 7 said:
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Oh no I'm not worried about being rooted. I can simply unroot and plug in the jig and im set. What i want is root and no LOS haha
locoboi187 said:
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
Click to expand...
Click to collapse
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
daneurysm said:
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
Click to expand...
Click to collapse
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
R1ptide said:
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
Click to expand...
Click to collapse
How has this worked for you?
locoboi187 said:
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
Click to expand...
Click to collapse
then wipe it, lol. Or not, try it without wiping first. If problems persist the only stuff that is left is in /data has to be the source of problems... but, after you flash that you can flash the pulled stock kern+CWM and nandroid just to be safe.
if after that still no dice, well, it's the phone or a very very very unlucky location...but that theory is still up in the air. (I don't buy it)
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
locoboi187 said:
How has this worked for you?
Click to expand...
Click to collapse
I've also done that too. Worked great for me.
I will report back. I only get LOS when I'm in school. It appears when i go to an area where i get no bars, a circle with a slash will appear. So far so good.
Lol, I just got an LOS on 00001.PRL (alltel/verizon towers) with full bars. I haven't seen an LOS in weeks, I haven't seen it happen with full bars though.
I can confirm for the first time I do not suffer from LOS. I used R1ptide's instructions and all went well. I went to a party where no one ever got signal, so when my bars went empty i received a circle with a slash for a second. HOWEVER, it went back to the bars and didnt stay stuck on that stupid circle.
Everything is definitely good
Sent from my SPH-D710 using xda premium
Ok. So I see there is a system update. I wanted to make sure if there's anyway I can check to see that it's ok that I install this update. Will it interfere with anything? Mainly pertaining to my root and unbrickness of my phone.
Will I lose root? Will I become bricked? (Though I doubt the later) I just wanted to know are we in the clear on installing this.
Sorry, but this is the first time this has happened to me, being rooted with some type of OTA.
you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.
btate0121 said:
you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.
Click to expand...
Click to collapse
So... shouldn't I update through the OTA, loose my kernel, use ODIN to flash back my CWM and kernel? That sounds like a viable solution.
Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.
btate0121 said:
Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.
Click to expand...
Click to collapse
Alright, that sounds like a safer route. Ima go check around the ROMS. Maybe they've added the update as part of their ROM.
Expecting this update to fix many of my problems.
Hello,
I am new to this forum, so If this is the wrong place I do apologize.
Ive recently purchased a new ET4G and decided to root it. I had another one rooted with no problems. Ive been using a couple different roms and this random reboot has became more frequent and has followed me with each ROM.
I have tried to ODIN back to a stock ICS build with Root and then flashing ROMS over again. I still received the same problem.
I am currently using FD26 stock with the addition of root. When the reboots happen. It seems to drain my battery drastically.
Example:This morning at 50% phone reboots and I am at 9% when it comes back on. After a couple reboots it becomes stuck and only a battery pull will allow it to reboot once again.
Anytime I flash a ROM I always follow the recommended flashing method. I do all the appropriate wipes. Id usually think It was the kernel, but even after trying different kernels the issue still happened.
If anyone could shed some light on what could be happening. I would be very appreciative.
do you do complete wipes prior to flashing?
Yes, I do. I usually wipe Davlik and then will run Caulkins format all zip before I flash any Rom. I always odin back to EL26 w/ CWM to flash through to avoid any conflicts with that.
I have no idea what to try next. I've went back to stock a couple times.
This same thing was happening to me honestly about 10 reboots a day and sometimes it would drain me down about 50% battery. I odined back to stock gingerbread using sfhubs latest method, reinstalled clockwork mod and have not had one reboot since. I think I may have heard though that the fd26 build has reboot issues so I would look into that as well. Though I see that you have tried what I have said not sure if you used sfhubs method or not but if so I would just take it back to sprint.
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
someguyatx said:
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
Click to expand...
Click to collapse
+1
Seriously, if you're having problems, to narrow it down you should not be on a leaked Android OS that is still in the testing stages. Always odin back to stock rooted to troubleshoot any issues, report back and we can get go from there.
Edit: If you need help getting back to stock rooted, please ask for help too.
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
I'm still stock EL29 till ICS comes out, but I get a reboot every couple days. It actually happened last night about 2AM and woke me up when the Sprint sound came on. Thought maybe there was some update (ICS?) that had caused it, but i didn't see any reason for it. It wasn't charging at the time and the battery was pretty full... Was hoping ICS update was going to fix this, but it doesn't sound promising.
RaheemA said:
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
Click to expand...
Click to collapse
On a previous phone (Samsung Moment) I had that issue and it turned out to be a bad battery. They let me borrow a battery in the store and it went away.
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
revamper said:
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
got reboots in GB as well so I don't think its solely ICS related... IMO
Yeah... I still was hitting the problem while on Complete stock GB. The phone could have honestly had the problem prior to rooting and flashing. I didn't keep it stock long enough to know for sure haha
Probably not related, but I was having reboot problems due issues with App2SD, so i figure it is worth mentioning just in case...
Issue 25563: OS keeps rebooting when lots of apps are moved to SDcard! HUGE BUG IN ANDROID OS 2.3.5 (and higher)!
So when diving into the world of modifying a smart phone, there is a lot of learning one must do reading threads and watching videos prior to getting started. Otherwise instead of rooting your phone, you may end up bricking it.
So lets talk about some of these things.
First off, if you are looking to open your phone up to unlimited modification, the quintessential step is rooting it, which is to say, unlocking root access so everything can be changed from fonts and colors to CPU overclocking.
If I understand this correctly, Rooting is done by flashing a modified kernel onto the phone. I wont try to pretend I know that with any confidence, these are the terms I'd like better explanations for. so... A release comes from the manufacturer and contains everything from the operating system to the firmware and the modem. A ROM is a pre-customized variation of a release, dunno exactly what a TAR, MD5, or a kernel is. A modem is a part of a release, but just the software part that deals with how your phone uses its radios. NANDroid is a way to completely backup your phone as a NAND. Clockworkmod is a utility set that can load and manage ROMS, NAND's, themes, and all kinds of other stuff. Recovery is actually usually used as a term for a built in function for restoring your phone back to a pre-loaded state (if it's not bricked, which means something went wrong and the phone won't turn on, which is different from soft-brick which means the phone is in a startup-boot-loop) I don't know what a bootlogger is. ODIN is a program 'leaked' by samsung used for flashing updates onto phones. Download Mode or Odin mode is used for updating and what you boot into by turning off your phone, then turning it on while holding the volume down button. a OneClick is a pre-made ODIN update that that automatically updates your phone. Stock means the release is unmodified from the manufacturers original. A Tweak is a modification that can be flashed onto a ROM? A Theme I assume is an aesthetic style that can be applied to even a non-rooted phone. But I think it requires the phone to be Deodexed, which is something that can be done to a release... otherwise the release is odexed?
GA10, Fk23, FL16, etc etc. You're probably wondering what that is. It's a coding system for the date of the release. Because android released in 2007, the coding system starts at 2007. That first letter represents the year, the second letter the month, and the number represents the day of the month. So a release from january 1, 2007 would have been AA01. febuary 15th 2007 would have been AB15, which is why a release on december 16 2012 got FL16.
This may not be the end, but to wrap up the small bit that I've learned in 17 hours of reading FAQ's and stickies, cutting edge threads and archives. The last 4 things we need to talk about are the flash count, or odin counter, which tracks how many times your phone has been flashed by an external source. Then there is the yellow triangle which is an indicator thrown during startup by a phone which has detected that it is not running a stock ROM. these 2 indicators can be reset on our e4gt by using a USB Jig, a small piece of hardware which can be bought online specific to our phone, which when plugged into the microusb port, resets the odincount and gets rid of the yellow triangle. And finally, there are some special procedures that must be observed when flashing around from release to release. Flashing to the same release is relatively safe, it sounds, but flashing down or up should be done without preserving data. (restore vs nodata).
Honestly, I've spent a lot of time on learning just this, and I still feel like I'm writing words that don't add up. In fact, I know I am. So I'd honestly appreciate it if someone could take what I've tried to do here, edit it for readability, proper word usage, accuracy, add any or all missing information, and post a new sticky. One that explains these things. Because there are a lot of stickies that provide instructions for how to do things, but very few are written in a way a beginner can understand. I've bolded words that are regularly used but dont make complete sense to non-developers and novice power-user hopefuls.
Hey, I might add some of the terms and what they mean to the FAQ thread. :good:
Am I getting it? or am I wasting my time.? I feel like some of this is for advanced root users only, (like maybe flashing just a modem while using older releases ROMS) and some of this is for beginners only, like one-clicks. I'd love if somebody made just 3 very simple, very useful beginner wikis/stickies. ONE is a 'terminology' post, like the one I've haphazardly attempted to put together above. TWO is an "everybody knows you're supposed to blah blah blah" post, for things like mobile odin and modems, making a backup, how to stick to the basics if you're new, not flashing backwards with ROMs, and knowing how to recover back to warranty eligible stock (odin counter and everything), finally THIRD would be the thread that explains how to do each of the different kinds of flashes, but not just instructions, but what it means to do them.
I've combed through these threads for a day straight and I've got more questions than I started with.
So, if someone doesn't want to put these together, Questions I'd love to know definitive answers to, so this thread can continue to be helpful to others....
A) If I flash anything, or everything, a hundred times, ROMs, modems, kernels, recoveries, roots, can I find a stock release of whatever-is-current-OTA to flash and then use TriangleAway to reset everything back to warrenty elligible? if not, what about the USB jig? Is this even possible.... If so...
B) Since my phone is not rooted now (first timer), Am I able to make a complete backup of my phone un-rooted so I can flash back to it if I ever need to become warrenty elligible again. If so, do I use nandroid, or titanium backup? don't both of these require root? Can I flash back to undetectable stock?
C) obviously, disclaimers everywhere show that it is never safe to flash anything, everything is at your own risk, but is there a general rule of thumb for whether a stock release is more reliable than a customized ROM. or do ROMs tend to be more stable with problems fixed.
D) Does a phone need to be already rooted, (or already flashed up to a release number or with a release modem) in order to flash a ROM onto it, or does it just require Odin and the TAR. Is a ROM a TAR? is a ROM a Kernel? or does a phone need to be rooted to some version first, then using CWM to load a same-version ROM?
I would say stock is more stable, on average. Think about what your goal is, why you would want root, and why you would use a custom rom. Rom choice, for me anyway, is based on customization availability, and tweaks. If you are simply driven by curiosity, and that is a good thing, read, and read some more. Patience and knowledge will keep you from trashing your phone, but most importantly attention to detail when performing any of these activities. Good luck, we all started somewhere.
.: :: Sent from USC-GS2~PACman via Tapatalk 2 :: :.
Triangle away will reset the counter now even in jellybean. Just not gingerbread. For going back to stock for warranty, dont worry about that. You can use a tar file or a one click. If you want a stock backup for yourself to rely on, I need to know what version number you want so I know what to do. Yes titanium backup as well as m.o. require root. For anything below ga10 touchwuz roms, use exynos abuse.apk you can root your phone no computer needed.
sent from MY BAD A$$ ET4G
I don't understand how a recovery is different from a backup. but somehow is independent of a ROM, and build, but is included in a kernel? Apparently I need a CWM recovery kernel to flash Kobridges GA10 ROM. I see that there are repositories of all kernels, and modems, and roms. So a build is a TAR which contains a kernel, which contains a recovery, but also is the original ROM, after which other ROMs are built?
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
I'll try to help with with what I understand. Clockworkmod or any recovery in general is packed up with the kernel. So if you want to make a backup just Odin a kernal with a recovery and it would be fine (I.e Kuban kernel). The thing is when you use Odin to flash kernel's it will cause the Samsung binary counter to increase and you will get a yellow triangle on boot. This is an easy fix but you need root access to run an app called triangle away which can be found in these forums or you can buy it off the play store if you want to support the dev. I would suggest getting the Directboot el29 kernel as it boots up directly into recovery. El29 or el26 are gingerbread kernels so if your running stock your phone won't boot up unless you are on gingerbread but you can always access recovery. I would suggest also getting an app called mobile odin (same deal as triangle away on how to get it)you can flash anything you can with regular Odin except it won't cause the counter to increase. Now for root.. I can be stock and have custom recovery just from using a custom kernel through Odin. Now 1 clicks are amazing let's say I have to take my phone in for repairs or warranty reasons. All I have to so is use the triangle away app (if I have the yellow triangle on boot) then boot my phone into download mode and use the FI27 stock no root data wipe. You can run a 1 click from your phone in any ROM ect... And bam you can take your phone to sprint for repairs or warranty. When you get your phone back just flash a 1 click for root access or a custom kernel for the recovery and then restore a nandroid and return to how your phone was. Now this is why I bought mobile Odin to support the dev.. Like in your case you want ga10. What I would do is just drag the download to my phone run mobile Odin and flash the ROM through mobile Odin.. Why? Because it can inject root to stock as it flashes. Just be careful and remember to back up your data because most jellybean leaks wipe internal data like pictures etc.. This doesn't happen when you flash a ROM and they ask you to wipe data. Now for modems stock jellybean modems don't work on ICS. You need a jellybean modem (if you do use the mobile Odin route you will have to flash a jellybean modem using regular Odin because mobile Odin doesn't seem to flash modems for our phones). When you Odin modems it will not increase the binary count and trigger the yellow triangle. Gingerbread modems and ICS modems interchange with each other so I wouldn't fear odining them.. Just see which works best. Hope this helps... I'm pretty sure you will read this cause you took the time to write a very long post lol.
Sent from my SPH-D710 using XDA
Thanks! That answers a number of my questions, now that the 1click for ga10 is out, i think ive finally got enough figured out to mess with it a bit with relative confidence.
Sent from my SPH-D710 using xda app-developers app
jt323bd said:
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
Click to expand...
Click to collapse
You can still flash a kernel with a custom recovery using desktop odin if you are not rooted. You can they boot into custom recovery and make a nandroid of your unrooted stock rom.
Your flash counter only increases if you flash unofficial stock files using desktop odin. So if you flash a modem.bin in the phone slot in desktop odin, your flash counter will increase. If you flash a kernel.tar file in desktop odin, your flash counter will increase. Thats why you go to rwilco12's repo in dev forums and use the one-click.exe files. Oneclick.exe files do not increase flash counter. You only need jib to reset flash counter or boot to download mode if you can't normally boot to download mode.
You could flash EL26 CWM kernel in desktop odin and boot to CWM recovery to flash any rom zip file you want even if you are not rooted. Don't jump to jelly bean roms from ics without first flash a stock jellybean oneclick.