Related
So I'm still pretty new on the E4GT forums, having recently come over from a Nexus one, which was quite a bit easier to mess with as far as ROM's are concerned, and much less easy to brick. About the only thing that could brick an N1 was flashing a radio, and new radio's didn't come out that often, so no big deal.
I'm currently running Calkulins EL29 mod with an FC14 modem on my E4GT, but I'm really wanting to mess with the testing builds of CM9, I really miss CM. All the steps seems to spread out across multiple threads, so I want to make sure I do it correctly so as not to brick.
1. nandroid backup, backup, backup
2. boot to download mode
3. load stock cwm el26 through odin
4. flash cm9 zip
5. mess around with it.
Where I'm a little confused is how to get back to where I was should I decide to wait some more. How do I get back to the EL29 CWM so that I can then restore the nandroid backup? Also, will I need to flash different modems again, or can I stick with the fc14 modem through all of this?
Please understand that I'm not a total n00b at all of this, been flashing all kinds of ROM's on my old Nexus one for two years, just don't have much experience with Sammy devices.
You just want too flash roms and themes?
Sent from my SPH-D710 using xda premium
I would also like to know the answer to this.. I'm terrified to flash or odin any ics-based roms because I don't want to brick my phone like a lot of others have
Sent from my SPH-D710 using XDA Premium App
ScubaSteev said:
You just want too flash roms and themes?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Themes, not really, but ROM's yes. It's just a bit confusing cause I see things like, you need this CWM for this, you need to flash this, or you need to Odin that, you need this specific CWM for this, or you need to get back to stock before you fan flash or Odin this or that.
But what I'm really wanting help with at this moments, is the testing build of CM9, and then how to get back if I don't like it at this time.
Ok....I download roms straight from xda app and then I go to recovery......do a full wipe....wipe data/wipe dalvic/wipe cache/wipe battery stats.........then I install .zip (rom) then reboot.....that's all I do,its pretty simple
Sent from my SPH-D710 using xda premium
ScubaSteev said:
Ok....I download roms straight from xda app and then I go to recovery......do a full wipe....wipe data/wipe dalvic/wipe cache/wipe battery stats.........then I install .zip (rom) then reboot.....that's all I do,its pretty simple
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The problem is that CM9 is an ICS ROM, you can't just flash willy nilly as there are a lot of reports of people bricking their phones cause they didn't use the right recovery. How to flash CM9 on is not my problem, it's how to get back to EL29 if I don't like the current testing build of CM9.
Ohh yeah....I don't mess with that stuff lol,can't take a chance.......but everyone says don't.
And I love cm7 can't wait for cm9 to be stable
Sent from my SPH-D710 using xda premium
Check out QBKing77 on YouTube. He has very simple videos about how to get back to stock after flashing ROMs, his guidance taught me everything. But don't let my noob-ness detour you, they are great videos.
Sent from my SPH-D710 using xda premium
xerxax said:
Check out QBKing77 on YouTube. He has very simple videos about how to get back to stock after flashing ROMs, his guidance taught me everything. But don't let my noob-ness detour you, they are great videos.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
People, please read my OP, I'm already rooted and running a custom gingerbread rom and recovery. I'm wanting to run CM9, but it may not be stable enough for me, so I'm wanting to know what the steps are to get back to my custom gingerbread rom should I decide to go back.
garfnodie said:
People, please read my OP, I'm already rooted and running a custom gingerbread rom and recovery. I'm wanting to run CM9, but it may not be stable enough for me, so I'm wanting to know what the steps are to get back to my custom gingerbread rom should I decide to go back.
Click to expand...
Click to collapse
The guy you just quoted... just told you where to find that information. :what:
This has been discussed ad nauseum all over the forums, and if you do a bit of research you will find the exact procedure. Since I'm on my phone, kinda a pain to type it all out. But he's right, the point is to get back to stock GB rom before restoring any GB nandroids. (specifically before wiping any partitions, but that's yet another long explanation.) This issue And procedure is the same for ICS leaks, for cm9, for AOKP.
Look for a sticky thread in general titled "how not to brick your phone" or something.
Or, god forbid, actually read one of the ICS/cm9/AOKP/leak threads. I swear, every third page you will see someone ask this and the process described.
And QBKING77s videos have a step by step explanation for this as well. Really the best way.
And yes, you can keep the modem, no matter what rom/kernel you run. Same thing as a "radio".
Sent from my calculator watch.
kingdazy said:
The guy you just quoted... just told you where to find that information. :what:
This has been discussed ad nauseum all over the forums, and if you do a bit of research you will find the exact procedure. Since I'm on my phone, kinda a pain to type it all out. But he's right, the point is to get back to stock GB rom before restoring any GB nandroids. (specifically before wiping any partitions, but that's yet another long explanation.) This issue And procedure is the same for ICS leaks, for cm9, for AOKP.
Look for a sticky thread in general titled "how not to brick your phone" or something.
Or, god forbid, actually read one of the ICS/cm9/AOKP/leak threads. I swear, every third page you will see someone ask this and the process described.
And QBKING77s videos have a step by step explanation for this as well. Really the best way.
And yes, you can keep the modem, no matter what rom/kernel you run. Same thing as a "radio".
Sent from my calculator watch.
Click to expand...
Click to collapse
I did some searching, and everything I found says to get back to stock, I didn't see where it said that you have to get back to stock first before you can then restore a nandroid.
This is not how it was done on the Nexus One, so it's new to me.
garfnodie said:
I did some searching, and everything I found says to get back to stock, I didn't see where it said that you have to get back to stock first before you can then restore a nandroid.
This is not how it was done on the Nexus One, so it's new to me.
Click to expand...
Click to collapse
Ics kennels with cwm have been bricking phones ....some just by wiping data ...they corrupt your data partition making it impossible to write to ..jtag doesn't even work on it...so we have been Odin back to stock GB and go from there
Sent from my SPH-D710 using xda premium
You may want to read this if you haven't already:
How Not To Brick Your E4GT
Now that it has been stickied the OP went through and updated the first post to cover most of I believe you are trying to find out. Hope this helps!
Epix4G said:
Ics kennels with cwm have been bricking phones ....some just by wiping data ...they corrupt your data partition making it impossible to write to ..jtag doesn't even work on it...so we have been Odin back to stock GB and go from there
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That's what I've been seeing, which is why I want to make sure I do it right. I don't even know what jtag is, had to look it up. Some kind of debugging tool from I found.
garwynn said:
You may want to read this if you haven't already:
How Not To Brick Your E4GT
Now that it has been stickied the OP went through and updated the first post to cover most of I believe you are trying to find out. Hope this helps!
Click to expand...
Click to collapse
I'll definitely give it good read. Thanks.
Hi.. just moved from the Samsung Vibrant S to the Epic 4G touch. I am confused on how to get Clockwork Mod recovery on my phone. Flashing it via the ROM Manager Premium app doesn't seem to work. I reboot into recovery, and no Clockwork Mod.
What is the appropriate and correct way to get Clockwork Mod on the phone? It seems for now, the only way I can play with ROMS is to find an ODIN version of the ROM. I am willing to use that if necessary, but a lot of ROMS are not released in ODIN format. Can someone help? Thanks!
Recovery is packed with kernal. So you have to flash a kernal with the recovery of choice. I think the consensus is to use Odin or MobilOdin for now.
Agat63 has some nice kernals and CM9 folks are making some safe ones.
Make sure you read the stickies on how not to brick your phone. There's some dangerous stuff that can brick you permanently, especially if youre used to flashing stuff on other phones. Theyre not just for noobies. Definitely read the stickies here. And did i mention to read the stickies?
Sent from my SPH-D710 using XDA
Please tell me you are on a Gingerbread rom!
Also, do not use Rom Manager, ever.
We can help you with this, but tell us what you flashed so far so we know how to proceed. Tnx
Edit: Its ok to be on ics, but please don't do any rom or kernel flashing yet until we're sure its done the safe way.
Sent from my SPH-D710 using XDA
thanks guys. Right now, I haven't flashed a new ROM as of yet. Is there one that you would recommend. I'd rather wait till CM is in beta stage, and I have checked out Phantom's rom.
I did try installing a kernel FE22 i believe, and thought it would have recovery in it, but getting into recovery mode, I don't see Clockwork mod. Am i doing it incorrectly? Which kernel would u recommend. Thanks!
Heed tdunham's advice about ROM manager or you'll paperweight your shiny new phone. Here are the kernels http://forum.xda-developers.com/showthread.php?t=1662295 Read through some of the threads. I would recommend using the EL26 CWM or one of the latest ICS versions (FF11 FF18) from Agat63; they have not failed me or others. Being new to this device I'd recommend using one of sfhub's one-clicks then odin a kernel with recovery (again Agat would be my choice). Be careful to choose a recovery and install method that is expressly laid out by the developer. Using the wrong format, kernel, wipe, install method can also paperweight your phone.
Good luck.
dvargas2000 said:
thanks guys. Right now, I haven't flashed a new ROM as of yet. Is there one that you would recommend. I'd rather wait till CM is in beta stage, and I have checked out Phantom's rom.
I did try installing a kernel FE22 i believe, and thought it would have recovery in it, but getting into recovery mode, I don't see Clockwork mod. Am i doing it incorrectly? Which kernel would u recommend. Thanks!
Click to expand...
Click to collapse
I'm not sure what you've done so far but this is the method to install stock rooted and also CWM:
http://forum.xda-developers.com/showpost.php?p=24158551&postcount=9980
From there, you can flash anything you want. I would REALLY recommend sticking with a Gingerbread rom for a while. Flashing over to the leaked ICS builds can be pretty hazardous if you're not absolutely certain of how it's done.
I prefer Calkulin's 3.0 GB rom found here:
http://forum.xda-developers.com/showthread.php?t=1332837
It may look stock but believe me it is not. There are a few themed GB roms around to try also.
Wicked sensations is an awesome ICS ROM by Team Venum.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
I have what may appear to be a pretty dumb question. I am running EL29 stock but rooted with Rogue Recovery which states it is CWM 5.0.2.7 I believe. I've been told that Rogue is not currently a safe recovery. I would like to know if there is a way to get my phone to where when I boot into recovery it is CWM and not Rogue ?? Hope this makes sense. I've searched for delete Rogue recovery to no avail. Any help would be appreciated.
thanks in advance.
Longball said:
I have what may appear to be a pretty dumb question. I am running EL29 stock but rooted with Rogue Recovery which states it is CWM 5.0.2.7 I believe. I've been told that Rogue is not currently a safe recovery. I would like to know if there is a way to get my phone to where when I boot into recovery it is CWM and not Rogue ?? Hope this makes sense. I've searched for delete Rogue recovery to no avail. Any help would be appreciated.
thanks in advance.
Click to expand...
Click to collapse
Here is the Kernel Repository maintained by RWilco. Just pay attention to the notes and the descriptions for each group and then read the threads linked for each.
:edit: Side note - Do NOT use Rom Manager to apply kernels/recovery for this phone.
If you need directions and helpful information, and if you haven't already, read this. [TUT] What Is ClockworkMod And How To Use It [Complete Guide] [VeNuM]
I'm so very confused as to what to do right now. I just bought an e4gt phone that I was told was rooted and flashed to cricket already, but when I get home, no custom recovery and I su doesn't respond to auto allow requests from superuser.apk, so I figure it lost root on that ics update. It's saying it's Fl24, and upon following various threads and stickies and videos, I'm absolutely overwhelmed, especially considering e4gtauto-sfx.exe and e4gtauto.zip are missing from their download links in a monster thread here in xda, so any help would be appreciated...
GrimeSyndicate said:
I'm so very confused as to what to do right now. I just bought an e4gt phone that I was told was rooted and flashed to cricket already, but when I get home, no custom recovery and I su doesn't respond to auto allow requests from superuser.apk, so I figure it lost root on that ics update. It's saying it's Fl24, and upon following various threads and stickies and videos, I'm absolutely overwhelmed, especially considering e4gtauto-sfx.exe and e4gtauto.zip are missing from their download links in a monster thread here in xda, so any help would be appreciated...
Click to expand...
Click to collapse
Don't necro post. And go read the stickies in the general section.
Sent from my SPH-D710 using xda premium
graydiggy said:
Don't necro post. And go read the stickies in the general section.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Okay, now I would just like to say, as long as you necro post in a thread relevant to your isssue/question you shouldn't be responded to in that manner^^^
If it's already there and they post a new one they get flamed like hell for it, at least they took the initiative to actually search obviously!
Sent from my SPH-D710 using Tapatalk 2
H4rryTipp3r said:
Okay, now I would just like to say, as long as you necro post in a thread relevant to your isssue/question you shouldn't be responded to in that manner^^^
If it's already there and they post a new one they get flamed like hell for it, at least they took the initiative to actually search obviously!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
That's the problem, his questions don't pertain directly to CWM. He just says that there is not one on his phone. Basically, he is asking about how to get root back on a device that sounds like it actually wasnt rooted, and that is a completely different subject. And even if he was directly asking about CWM, the answer is in the post right above his. So he my have searched, but he isn't reading.
Sent from my SPH-D710 using xda premium
All sorted out now, and you're right, it was all there for me to find. The issues with this phone regarding bricked devices and various unsafe recoveries and kernels WAS overwhelming, but after a couple days of lurking the stickies and all the other related threads I believe I've got at least a working awareness of the situation. For anyone else who comes after me, agats tREC CWM based recovery combined with the fl24 kernel as compiled by garwynn is a good place to begin, and qbking77's video tutorials will go a long way to getting you up to speed. Thanks (for nothing ) folks, this e4gt will live to see another day!
Sent from my SPH-D710 using xda app-developers app
GrimeSyndicate said:
All sorted out now, and you're right, it was all there for me to find. The issues with this phone regarding bricked devices and various unsafe recoveries and kernels WAS overwhelming, but after a couple days of lurking the stickies and all the other related threads I believe I've got at least a working awareness of the situation. For anyone else who comes after me, agats tREC CWM based recovery combined with the fl24 kernel as compiled by garwynn is a good place to begin, and qbking77's video tutorials will go a long way to getting you up to speed. Thanks (for nothing ) folks, this e4gt will live to see another day!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Easiest way is to Odin full restore (rooted) the desired ROM. As of now I'd say GB27
http://forum.xda-developers.com/showthread.php?t=2191954
[LINK][ROM][ODIN][TAR]SPH-D710 GB27 (GB27 Modem/Kernel/ROM - Root/Stock)
Sent from my SPH-D710 using Tapatalk 2
Well, while that is the newer repack, i wouldn't day it's the EASIEST method, because the vast majority (dare i say all?) of AOSP based ROMs specifically instruct you to "not use with a JellyBean modem." Following your method, they'd have to Odin flash to gain root, mobile Odin their CWM recovery, then follow ir up with flashing back to an ICS modern, re updating their carrier data & PRL (as well as nv items n all that) then get on to the ROM flashing business. If they start with FL24, they're able to side-step the whole modem compatibility consideration and jump right into flashing their custom OS of choice. Unless, of course, they decide to go with something that's TouchWiz based. But having been new to this device not that long ago, i can say with confidence that the AOSP based ROMs that reside in the "Android original development" thread are much more appealing to someone who's just gained root and is settling down to tweak their device to the fullest extent that modern development safely allows. So, yes, that is the most updated method, but easiest? Gotta say that was covered in my post...
Sent from my SPH-D710 using xda premium
GrimeSyndicate said:
Well, while that is the newer repack, i wouldn't day it's the EASIEST method, because the vast majority (dare i say all?) of AOSP based ROMs specifically instruct you to "not use with a JellyBean modem." Following your method, they'd have to Odin flash to gain root, mobile Odin their CWM recovery, then follow ir up with flashing back to an ICS modern, re updating their carrier data & PRL (as well as nv items n all that) then get on to the ROM flashing business. If they start with FL24, they're able to side-step the whole modem compatibility consideration and jump right into flashing their custom OS of choice. Unless, of course, they decide to go with something that's TouchWiz based. But having been new to this device not that long ago, i can say with confidence that the AOSP based ROMs that reside in the "Android original development" thread are much more appealing to someone who's just gained root and is settling down to tweak their device to the fullest extent that modern development safely allows. So, yes, that is the most updated method, but easiest? Gotta say that was covered in my post...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
You have no idea what is the easiest method... Your method had a ton of steps and nothing to do with what was even asked or brought up by the other user.
Sent from my SPH-D710 using xda premium
graydiggy said:
You have no idea what is the easiest method... Your method had a ton of steps and nothing to do with what was even asked or brought up by the other user.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I was a bit cheeky. Apologies. That's what i get for drunk posting... His post was written with the best of intentions. That was no way of me to show my gratitude. However, graydiggy, I'm guessing you weren't hugged enough as a child.... As for what you said about his post, you're half right, the GB27 method would be a fine choice for some purposes. And to clear up the mess i was in when i first posed my question to this thread, that'd have given me root and gotten me back to a happy place. But i didn't expound on my end purpose... I wanted to be able to flash Cyanogenmod, AOKP, etc, etc... And perhaps without the bundled recovery that'd still be a fine route to go, except for the JB modem issue i mentioned, but that's just an extra step. But, on a side note, Garwynn just uncovered some real troubles with the GB27 kernel and custom recovery repack he put out, in case anyone wants to look over it you can find the thread here http://forum.xda-developers.com/showthread.php?p=40218765. But, for flashing aosp ROMs, sidestepping the jb modem issue does save a step, so for that purpose, I'd still go with the fl24 one click. In my opinion and for my purposes. So again, sorry for my cheeky-ass post.
Sent from my SPH-D710 using xda premium
I don't know how many times I was hugged... Who cares? Some people do like me and some don't, because I am brutally honest 95% of the time. When a user offers advice that is lacking or more work than what needs to be done, I tend to let them know how dumb it is and I have no problem doing it. I am not always trying to be a d**k about it, but it comes out that way sometimes...
Sent from my SPH-D710 using xda premium
Boohoo, I gave bad advice and got called on it, I'm going to pout now :stompsfeet: :sly:
☆SoA: Son's of Android™☆
I like to break stuff!
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
crawlgsx said:
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
Click to expand...
Click to collapse
I lost my IMEI on my first Sgs3, went flash happy (only AT&T ROMs) but still had data and cell. Not sure where I lost it, but I noticed when I was flashing back to rooted stock from early CM10 preview (official) is when I noticed.
So far with my new phone, I've done the same and still have it. I'm now running Aokp jellybean.
I've had no problems as of today but the fear of losing my imei has definitely caused me to not experiment as much as I would like to! I've rooted, installed CWM-Touch, flashed Ktoonsez Kernel, and flashed back to the AT&T Kernel. I'm honestly afraid to try CM as it seems that ALOT of the people who have lost their IMEI had flashed CM10 or CM9. I bought a Galaxy Tab 2 7" a few months back and it's become my tinker toy to flash ROM's and mess with. I don't want to screw up my $500 Galaxy S3, I like it too much!
I voted as flashed a few, but really it is probably closer to many. Only AOSP based ROMs though. CM9, CM10, and AOKP plus updates for each. Also both Faux and Ktoonsez kernels at various times. IMEI still present.
I do make sure that I flash the EXACT same way every time though since it has worked so far. Only thing I have changed now is moving from latest non-touch CWM (installed through ROM Manager) to latest TWRP (through Goo Manager).
If I end up losing my IMEI without adding variables to my flash process, I will start to believe it is a random occurrence. Until then I have to think partial user error coupled with a bad update script or recovery.
I ALWAYS download the file straight to my phone via WiFi.
Reboot into recovery. Wipe>Factory reset.
Flash ROM.
The last couple days since moving to TWRP I have felt more ballsy and did things a bit differently.
For the first time, I also wiped cache and Dalvik before flashing JB AOKP last night
Still no issues.
Today I decided to flash the ktoonsez JB kernel. I usually only download via WiFi at home (just to keep minimal variables in flashes) but today I did it at work via WiFi. Still have IMEI.
I have NEVER done a Format System so not sure if that might break something.
My process has been if it isn't breaking, try to keep the process as consistent as possible. If something does go wrong, I can say what I did differently. I also haven't had any trouble with the ROMs I flashed despite only doing factory reset then flash.
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
spacecasespiff said:
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I know you found out, but when it happens you will know.
In some cases it seems as though you only get Edge at your maximum speed, in others your mobile data completely died. Generally speaking, there was a lot of confusion and some issues with clarity regarding the issue.
It's possible that there are several different (but vaguely related) issues going around, now that we have our own carrier based forums that should actually help clear it up in my opinion.
Hopefully we will all reach a general consensus on the acceptable recovery (my vote is TWRP!) and method of flashing. The only thing I've personally considered is that it might be an issue with the files transferring via MTP (only because I've never used a phone with MTP instead of mass storage).
I don't think people should be THAT afraid to flash though. If your flash counter is at 0, Samsung should do a warranty swap for you. In addition, it seems like 2 in 25 people (read: NOT FLASHES, but people.) seem to get the issue based only off of the very small number of people in this poll so far.
The reason the issue is so feared is because those that do get it will inevitably be far more vocal than those that don't as they try to find a solution and vent their frustration. Most of the people in the major thread about it didn't have the issue, but were afraid they might lose their IMEI.
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
I'm about to root and cwm what's your guys input on the best ways
Sent from my SAMSUNG-SGH-I747 using xda premium
yokken said:
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
Click to expand...
Click to collapse
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
As always, check your apn before freaking out! It may have gotten deleted while flashing a rom. It happened to me
Yes, I freaked out.
Sent from my SGH-I747M using xda premium
tyshemi said:
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
yokken said:
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
Click to expand...
Click to collapse
Yea I have read that many times there guy thanks for input just solidifying it all
Sent from my SAMSUNG-SGH-I747 using xda premium
ppl who scared to flash
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
I have to use Odin for root initially don't I ? Then use it for cwm or u recommend Rom manager ? Im just wanting stock Rom like yours for now
Sent from my SAMSUNG-SGH-I747 using xda premium
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
codycorexxx said:
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
Click to expand...
Click to collapse
Ive done this, not once but twice. Once coming from Aokp and once from cm10. Imei still intact :good:
Lmao, funny thing is i was deathly scared of the imei issue and very well versed on it, and i never knew it was "dangerous" till i read your post just now.
So what is this?
I have always wondered would it be safe and easier to flash custom roms using Odin if we had odin packages for custom roms. So I started to poke around and research. Rwilco12 has been a great help. I was working on this before new year and was getting somewhere. I had created quite a few full Odin tars for couple ROMs but none of the packages had successfully flashed the whole ROM. These tar packages are similar to the stock .tar files that sextape posts but they are rooted and are not stock Sprint builds.
As some of you may know, I got sick and caught flu on new year so had to stop working on this and hasn't worked on this since 27th Dec plus now new college semester has started so I am somewhat short on time.
So the reason I am posting this here is that I want to know from you whether you would be interested in using Odin to flash custom roms? OR Would you rather continue to flash custom ROMs using CWM?
If more people are interested in this and would seriously use these to flash custom ROMs then I will continue to work on it. I want honest responses. I wouldn't mind a bit if you think Odin custom ROM flashing is not the way you would go. Also you can use the poll for your response.
I will appreciate any useful responses.
Im actually working on something similar for my Note 2 rom. Gonna have the choices of a zip, tar or aroma install. Going the extra tar route to include files for people rolling back from higher firmware with errors so they dont have to flash modems and the fix separately and can just odin 1click back. It would actually probably work well for any rom it makes it much easier for a noob to flash without fear of using an unsafe kernel on et4g and without having to learn everything all at once before they can try something out. Odin has been fairly safe for me minus one incident with a leak when I flashed an incomplete tar and bricked nyself but other than that never had a single hiccup using odin with complete files. It would make it easy for people to flash without recovery as well since they could mobile odin the new rom instead :thumbup:
I give this idea :thumbup::thumbup:
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
It has its ups of convenience but is not practical for developers. From my understanding, it is much easier to break into a zip file to update stuff for the new builds fix bugs and find bugs to fix, as well as it being easier to build a zip to flash. Also, as the end user of a ROM, I like to go in and add or remove things before I flash my ROM. I can't do that easily if at all if it is Odin based.
Sent from my SPH-D710 using xda app-developers app
I've been talking about this for months, since we had the eMMC super brick issue. No one listened...
Sent from my SPH-D710 using xda premium
graydiggy said:
It has its ups of convenience but is not practical for developers. From my understanding, it is much easier to break into a zip file to update stuff for the new builds fix bugs and find bugs to fix, as well as it being easier to build a zip to flash. Also, as the end user of a ROM, I like to go in and add or remove things before I flash my ROM. I can't do that easily if at all if it is Odin based.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I hear you but its only couple linux commands to unpack the system folder and then you can make any changes.
Mattix724 said:
I've been talking about this for months, since we had the eMMC super brick issue. No one listened...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I heard you, I just had no clue how to pack a tar for odin yet lmao. I know how to create one in linux in place of a rar or zip file but didnt have the first clue what I needed to pack for odin to pick it up and flash. Now I have a nifty little tool that builds the oneclicks for me
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
-EViL-KoNCEPTz- said:
I heard you, I just had no clue how to pack a tar for odin yet lmao. I know how to create one in linux in place of a rar or zip file but didnt have the first clue what I needed to pack for odin to pick it up and flash. Now I have a nifty little tool that builds the oneclicks for me
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Is this the tool you use that came from the N2 forum?
http://www.xda-developers.com/android/package-odin-roms-with-gzip-compression-hidden-menu-gets-an-update/
And Blues - I was attempting this for the deodexed and couldn't get it to clean flash properly. I'd be interested in seeing if odexed/deodexed can be used in this manner since there were people asking for it.
MoHoGalore said:
Is this the tool you use that came from the N2 forum?
http://www.xda-developers.com/andro...-gzip-compression-hidden-menu-gets-an-update/
And Blues - I was attempting this for the deodexed and couldn't get it to clean flash properly. I'd be interested in seeing if odexed/deodexed can be used in this manner since there were people asking for it.
Click to expand...
Click to collapse
Might be im not at my pc to check the package name atm. But if its the one garwynn told me about then yeah that be it
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
BluesRulez said:
I hear you but its only couple linux commands to unpack the system folder and then you can make any changes.
Click to expand...
Click to collapse
But how many of the average users have either a dedicated Linux box or even a VM to do that? On top of that, How many of the average users that don't have either want to set all that up then learn those commands to unpack the tar, edit what they extracted, re-pack it, then re-sign the tar? Yeah there are programs that will pretty much do that for you, but like I said, it is more convenient to keep the official and unchanging builds for Odin and and keep the custom ROMs that are changing every week in the zip format.
Why try to fix something that isn't broken and is much easier to do?
Am I saying "no you can't do it."? Not at all. If you want to spend the time to do all that, go for it. But I can bet you money that half of the developers that are pushing weekly and nightly builds will not want to do all the extra stuff. Look at the bigger picture, most people want pure convenience. There are also big risks with flashing ROMs via Odin.
Bricks being the biggest one.
This topic has been brought up quite a few times in many device forums including this one, and what I have said has been said by many others.
It's just not logical.
That's why im giving 3 install options. Zip tar and aroma. You choose how you wanna install each have their own pros and cons. The biggest pro for odin is I can pack fixes that cant be flashed in a typical zip and can AIO everything so its a single flash and not a zip stack to get it working
I like to break stuff!
If a developer wants to offer tar files for their ROMs then they can do it. It is their decision, not the end user.
Just because you want to dissect someone else's work, does not mean that they are going to cater to your every desire.
Yes, there are risks in flashing via Odin such as flashing the wrong pit, boot.bin, data... but if the developer has tested the tar like all developers should always be testing their own work before releasing to the general public. The only other issue would be bad downloads, which it is entirely up to the user to always check the MD5 before flashing.
Sent from my SPH-D710 using xda premium
Ok I want to clarify something. I am not saying rom devs have to do this.
I will be creating them for the various roms.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Ok I want to clarify something. I am not saying rom devs have to do this.
I will be creating them for the various roms.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
And you have my approval for my FK23 and any future ROMs that I may or may not make.
Sent from my SPH-D710 using xda premium
My thoughts are that it is great for a noob. That is they only want to flash a rom and run with. If you are a dev or like me trying to get the hang of theming and more the zip is the way to go. It its possible to brick your phone ether way. But its is much easer for the noob to do a one click than installing a cwm zip. That they tend to mess up and post after post about all the problems. LoL
But for a dev I can see the problem. I say yes sofpr the noobs. We were all anoob at one point in time. Thanks op I was thinking of this too.
monkeytools said:
My thoughts are that it is great for a noob. That is they only want to flash a rom and run with. If you are a dev or like me trying to get the hang of theming and more the zip is the way to go. It its possible to brick your phone ether way. But its is much easer for the noob to do a one click than installing a cwm zip. That they tend to mess up and post after post about all the problems. LoL
But for a dev I can see the problem. I say yes sofpr the noobs. We were all anoob at one point in time. Thanks op I was thinking of this too.
Click to expand...
Click to collapse
Well, in the words of garyd (search if you don't know to whom I refer to), it seems that 75%, or more, of people aren't here to dev.
I'll be honest; when I first came here a short time ago, I wanted to root so I could add all the tweaks and themes because a fellow co-worker showed me what could be done. Then the inner geek came out and now I am like a dog on a squirrel going tree to tree trying to soak up all I can. Just gotta focus..
My point = this is a place for "stuff". I'm not taking away from the roots of XDA nor it's intentions because I now understand what a dev told me (Venum, cough, cough, good guy, cough) - This is a place to learn.
I hope Blues follows through with this because he can help me figure out where I may have failed or vice versa.
Who cares about the "numbers" that want it..
Ask a teacher - "If you can reach one.. " What they'd say..
My 2 cents... I have always kept a blu kuban nandroid that is a fully functional backup that's ready to go if I crap up the phone and don't have time to rebuild before say going to work. Even if it's out dated, it's ready to go. To turn said backup into a one click would be that much cooler if the recovery is blown too. Could a script be made to turn a nandroid folder into a one click?
As for the roms being released for odin, it sounds cool but I would miss adding stuff like swype and other system apps myself.
Sent from my SPH-D710 using xda premium
Hey Blues, if you need any help building tar files for the vast number of ROMs out there, I am waiting for more work to be available before I can go back to work... damn construction.
I have at least this week maybe some of next week available to help.
Sent from my SPH-D710 using xda premium
Mattix724 said:
Hey Blues, if you need any help building tar files for the vast number of ROMs out there, I am waiting for more work to be available before I can go back to work... damn construction.
I have at least this week maybe some of next week available to help.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks. So far I have used couple ICS roms. Took the system folder and packaged that into factoryfs.img and then a blank data.img and zimage with all remaining files which are standard in stock .tar such as boot.bin, param.lfs etc to create a full rom .tar. It flashes all the parts but when the time comes for it to boot, it goes to samsung flash screen. Tries 2 times to boot and then boots into custom recovery (agat for the zimage I used).
Rwilco has suggested couple things but haven't had a chance to try those so may be I will get on it!
Hey Moho. How much have you done yet?
BluesRulez said:
So what is this?
I have always wondered would it be safe and easier to flash custom roms using Odin if we had odin packages for custom roms. So I started to poke around and research. Rwilco12 has been a great help. I was working on this before new year and was getting somewhere. I had created quite a few full Odin tars for couple ROMs but none of the packages had successfully flashed the whole ROM. These tar packages are similar to the stock .tar files that sextape posts but they are rooted and are not stock Sprint builds.
As some of you may know, I got sick and caught flu on new year so had to stop working on this and hasn't worked on this since 27th Dec plus now new college semester has started so I am somewhat short on time.
So the reason I am posting this here is that I want to know from you whether you would be interested in using Odin to flash custom roms? OR Would you rather continue to flash custom ROMs using CWM?
If more people are interested in this and would seriously use these to flash custom ROMs then I will continue to work on it. I want honest responses. I wouldn't mind a bit if you think Odin custom ROM flashing is not the way you would go. Also you can use the poll for your response.
I will appreciate any useful responses.
Click to expand...
Click to collapse
Yessssssss do it!!! It will be less bricks out there cuz ppl don't know wat safe recovery to use! Like certain peeps like to flash using blu Kuban kernel! Then wonder why the ROM don't boot!!! Do it BluesRulez
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
BluesRulez said:
Hey Moho. How much have you done yet?
Click to expand...
Click to collapse
Slightly different way of making the fs.img and only doing a Rom flash.
Was working with deoxdexed flashing on top of a stock base.
Boots but ui crashes. Like a blank ui..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Hey Guys,
I know it is probably not possible, but in case it is, I wanted to post the question.
I have been working with MotoDefier for a few days now learning about the new model S3 (SGH-T999L). Because there is no firmware available for download yet, we are trying to find a way to either pull the stock recovery before rooting, or figure a way to root without flashing CWM or TWRP first.
The ultimate goal here is to pull all of the parts that are included in firmware updates, and create the firmware from there. This way, if anyone runs into problems, they will be able to Odin back to stock.
Moto has already tried several different rooting methods, including CF-AutoRoot, and has had no luck so far. So if anyone has any ideas on how we can get this done, please do share!
Thanks!
Doc
This may be out of place but perhaps the 999l is closer recovery to the s4? I don't know. But have you tried to pull it with the paid version of the s3 toolkit?
I wish I could help. Sorry Doc
Sent while sleeping in chair.
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Aerowinder said:
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Click to expand...
Click to collapse
I was actualy thinking the same thing about the kernel. Just sent a PM to one of the guys who already rooted to see if they would pull the boot.img for me. Im not worried about losing the kernel, as I will still have the original copy after setting it to insecure.
Moto already tried getting the firmware through kies, but it didnt work. We figure that its because there is no publicly released firmware to begin with. As to the uselessness of Kies......completely!
.......I was just thinking, when you flash CM, it flashes its own kernel with it, right? (Its been a long time since Ive messed with CM, sorry). If thats the case, i wont be getting the kernel from the guy I PM'd.
Does anyone else have the new model T999L? If so have you rooted yet, or do you plan to? If so, please PM me if you are willing to help us out with this.
And by all means, hit me with any other ideas you guys may have!
Yes, it flashes it's own battery hog kernel.
Well, I hope I dont jinx anything by announcing too early, but I think we got it!
It appears that using the motochopper exploit did the job. It was originally created for a Motorola device, but as it turns out it will work on a number of Qualcomm based devices.
I got the info from the S4 forums.
It appears the main thread is in the ATT forum here:
http://forum.xda-developers.com/showthread.php?t=2252248
Here it is reposted in the Tmobile S4 forum:
http://forum.xda-developers.com/showthread.php?t=2258633
Just wanted to share in case anyone's interested in taking a look.
Note: it looks like the latest updates may have been patched against this exploit. Just fyi.
Sent from my SGH-T999 using xda premium
I love you Doc. (Hetero)
Sent while sleeping in chair.
Lol!
Be sure to hit thanks when you see MotoDefier. He took all the risk and did all the hard work! I mostly just helped with ideas and such. (Most of which didnt work!)
Ill be working tonight and tomorrow on getting some sort of flashable firmware put together so you guys have a way back to stock if need be.
Also I have a deodexed rom based on the T999L almost ready in case anyone wants to mess with it. Just got to double/triple check my work and test first. There are a few differences from the original T999 so im curious to see if any of it is noticeable while its running.
Let the fun begin!
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What I meant was pulling files from device without pushing anything to it. I believe this is an option within the toolkit, not sure if paid version required. Hmmm.
Sent from my Transformer Prime TF201 using xda premium
What I was getting at, was that we didnt want to use the toolkit because it flashes recovery. And I could be mistaken, but Im pretty sure the toolkit requires you to root first, then it can pull system firmware for you. Either way though, we got what we needed. I am uploading files now and will post shortly.
Note that most of what I am doing is currently untested. I do not have a T999L, and I dont want to take the chance of flashing certain parts of the T999L to it. I am confident that it will work, or i wouldnt release any of it, but just for full disclosure.....!
I dont believe it needs root and it wont do anything you dont want it to do unless you tell it to do it. All of that aside, I wasnt trying to pimp the toolkit, I just thought it might work, but as I have little knowledge about that which I am talking, I'll just defer to you fellows as you seem to know a thing or two about a thing or two.
:screwy:
Sent while sleeping in chair.
I have the T999L, I used the Toolkit to flash TWRP and then updated it to 2.5.0.0 from Doc's page, I then flashed SuperSU 1.30, wiped Cache and Dalvik, then rebooted. Bam, Rooted. But it not 100%, ROM Manager doesn't seem to have root, but Adfree Android, TiBackup and ES File Explorer. I'm going to uninstall ROM Manager and then reinstall to see if that helps.
Thanks again to DocHoliday77 for his help.
EDIT: I found out why ROM Manager was failing, BusyBox was not installed. I installed it and everything works.