Develop Bugs

Life after simpleroot?

Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.

I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell

Keep at it!
loztboy said:
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
Click to expand...
Click to collapse
0. Please read everything before doing anything. My post is a little chaotic, but you should be fine if you read everything first.
1/2. The usual disclaimer: I'm not telling you to do anything. I'm just providing information. I'm not liable for anything you do to you phone.
1. ROM Manager is definitely the easiest way, though the "real way" is to load your ROM of choice on the SD card and then flash it from Recovery (more on recovery later).
1 & 1/2. By the way, you should install Titanium backup from the market five minutes ago. Yes, it is that important. When jumping ROMs, you often have to wipe everything out. Without Titanium Backup, you could end up having to repurchase apps and redownload all of your free ones, losing progress in games and settings in apps, etc. The free version of Titanium Backup lets you back up easily enough, but you want the donate version to prevent restores from taking a few hours of user interaction (Yes, I said user interaction, meaning sitting there and pressing buttons for hours). Once you throw $4.00-$50.00 (you can pick within that range, you get the same product regardless of amount) at Titanium Backup (and wait a day or so to get the license key file), you can do a restore in 15 min without any interaction beyond hitting start (or, more accurately, begin batch process). This app has saved my life time and time again. I literally did my first backup out of curiosity for the app and then totaled my phone in the next five minuets. It even backs up your home screen layout. GET IT NOW!!! YOU WILL HATE YOURSELF IF YOU DO NOT GET IT!!! At least get the free version, because, as stated above, it does backups fine. You (like me) will be scared into paying when you realize that you just wreaked everything and really don't want to spend the next few hours restoring. However, Titanium backup will not function until you get Superuser app working, as detailed in point 2 below.
***EDIT: I forgot to mention that Titanium Backup should work after running this program. It should even fix clockwork for you***
2. There are three possibilities for that error: 1: You don't have the superuser app installed. It dishes out the privileges. If you don't have it (if you do go on to potential issue number two and be grateful), you can install it by downloading this file and putting it on the root of the SD card. Then boot into recovery (I'm sure there is a tutorial for getting into recovery floating around here somewhere, just search the EVO section) and flash the .zip Presto! Superuser app is installed. If you prefer not to go around flashing random packages recommended by strangers on the internet, you can research and download superuser app at the source 2: If you found the Superuser app in the app drawer (the screen with all the applications where you scroll down in alphabetical order and pick the one you want to use), open it. You may have bumped "never give superuser access to this app" (or words to that effect) the first time you opened ROM Manager. If so, it will be listed in the Superuser app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as red. Just have the superuser app forget ROM Manager and then try to flash custom recovery from within the ROM Manager again, being sure to say "Yes!" when it asks for superuser privileges. 3: If you have no recovery to flash superuser from or superuser is installed and ROM Manager is green inside and it still fails, the SimpleRoot failed. If you skipped a step in the rooting process, go back and do that step. If not, just start over and run all the steps from the beginning, Also note that if you accepted the over the air update, you need the OTA version of SimpleRoot, not the original one.
3. Now, about total reversal. I'll be honest: There is probably a way to go back to stock that works without finishing the root process (probably something to do with PC36IMG.zip) files, but I don't know it. The way I would do it would be picking the OTA Stock ROM from this page and flashing it after getting recovery installed at the end of a successful root process. However, then you would have succeed in your original endeavor and would have no need to go back. There is a program here that supposedly does just enough tweaking to the phone to give you the recovery you need to flash back to the stock ROM, but I have not used it myself and therefore cannot vouch for it.
dws51 said:
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Click to expand...
Click to collapse
If you both succeed in the root process (and I encourage you to persevere, the reward is spectacular), I personally recommend Cyanogen Mod 6. I believe that you can get the nightly builds of CM6 from ROM manager, but the release candidate is likely more stable. I use the RC myself and have never looked back. My battery lasts forever and my phone is never unresponsive. And because the CM6 ROM is based of of Android 2.2 (Froyo), free tethering is built in to the OS and done so rather elegantly, meaning no more dirty hacks for tethering. Just know that if you go that route, though you have the best of the best, you will need to tinker a bit to get everything working. Also, 4G, the FM Radio, and HDMI output are flat out not working in the RC (I'm sure they will be fully functional in the final release, and the not-workedness is a software thing, meaning that the hardware is fine and will come online when you again install a ROM that supports it). On the other hand, with this ROM you can force the phone to roam on Verizon's network when Sprint's 3G speeds are less than desirable.
I'm not sure where to put this, so I'm sticking it here. As soon as you get custom recovery working, you want to backup with Nandroid. The easiest way is from ROM Manager. Just hit "Backup ROM". This backs up not only your setup (like Titanium Backup), but also all the crucial bits that lie underneath and keep your EVOs humming, bits very very difficult to replace. HOWEVER, this is NOT a replacement for Titanium Backup, because it can only restore to the same ROM. If you attempt to restore to a different one, it will put the one you had at the time of the backup back on.
Whichever way you go, I wish the both of you luck. You're entering into the wild and wonderful world of devices that you actually own!

that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through

The root of the SD card is the 'directory' you're in when you plug the card into the computer & you see folders like ".Mail" "Android" "DCIM" etc.
It's up to you if you think you can handle rooting. I used SimpleRoot & it was incredibly easy, but i have been familiar with modding phones for awhile now.

jdjozwia said:
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
Click to expand...
Click to collapse
The root of something simply means not in a folder, e.g. on your computer it would be just G:/ (or whatever letter your SD card is mounted to). Just open the SD card and put whichever file you are referencing right there, not in any folder.
By the way, anyone can root, so long as you are willing to learn and willing to take a few risks. As long as you stay well informed, you usually don't break anything. And there is usually a way out, even if you make a train wreak, though it may be ugly. Independent developers (not me; smart people like Cyanogen and Toast who actually make these awesome ROMs and roots) have a better track record for keeping dangerous stuff out than some corporations. ***Cough***McAfee antivirus broke thousands of computers with a defective update***Cough*** Scientia est vox. Knowledge is power. Know what you're doing, and you'll be fine. You will make mistakes (I know I have), but stay sharp and know the consequences, how to go back, who to ask when things go South, and you'll do alright. The community here at XDA is one of the best and most helpful I have ever seen. If you're not totally hosed, someone will pull you out of the fire. It probably won't even be me. I'm no pro. But there is no shortage of pros here at XDA.

so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod

See Above
jdjozwia said:
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
Click to expand...
Click to collapse
If titanium backup works, you have root. As for Clockwork, please see my first post, where I went over it in detail.

OK well i installed titanium back up and busy box and it looks like im rooted? Im going to try to flash that superuser app tmw i left my usb cord at work so in about 12 hours ill probly be back with more questions
thanks for the encouragement the answers and most of all your time

Cut the cord
jdjozwia said:
i left my usb cord at work
Click to expand...
Click to collapse
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?

Techrocket9 said:
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Click to expand...
Click to collapse
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?

jdjozwia said:
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
Click to expand...
Click to collapse
It should complain about being unable to acquire root privileges.
___
An army of pacifists can be defeated by one man with the will to fight.

yeah when i open it it doesnt say that and it says my root access is ok,
I DL astro and when i open it one of the folders is clockwork mod and if i search i find super user app on my sd card when i reboot my phone by holding the down volume it goes to the hboot screen and askes me if i want to update my phone i say no and then when i go to recovery it does not give me the option to flash the super user app. it takes me to android system recovery with four options. At the very bottom it says E: cant open/cache/recovery/command
?

Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.

How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
As for CM6, don't get me wrong, I LOVE CM6, but, Fresh 1.0.1 or the latest Damage Control might be a safer bet. For your first rom CM6 needs more coaxing than you might like. Also tethering is installed by default in the 2.1 roms from those guys and it's (imho) easier and more obvious to use.
Keep at it, there will be times you feel like giving up even after you get past this point, just don't take it too seriously and remember that as long as you are still getting phonecalls your phone is still doing it's primary job, the rest is just icing. Icing that gets more delicious with time, like beer, mmmmmm beer.
Where was I?
Oh yeah, good luck!

Crap, forgot, when someone says "put it on the root of the SD card" the easiest way to do that is hook it up via USB, hit the status tray that says "usb connected" and check the Hard Drive option. Then just copy your file to the new drive that will show up in windows (might pop up automatically depending on your windows settings) and boom, it's on the root of the SD card.
As for the "real" way to flash. Do the above, putting the .zip file containing whatever rom you want (for instance CM6, or Fresh 1.0.1 which you can obtain over in Development forum from their respective posts) on the root of the SD card. Safely remove the device (on windows it will be in your status bar, usually looks like a plug with a green arrow, click it, choose Mass Storage Device and then hit Stop, it will tell you when its done, make sure you have the folder closed before you do this or it will grump at you) and switch back over to Charge Only on your phone. Then power off the phone (hold the power button with the phone unlocked, choose Power Off, then Ok) and hold the volume down button. Then press power, don't let go of volume down but you don't have to hold power, just press it to turn it on. A white screen should come up, let go of the volume button, and one option will be Recovery. Use volume up and down to select it and press the power button to select. It should then boot you into recovery which should have an option to "wipe", you want to wipe dalvik cache, then cache, then factory defaults. Then go back up (in AmonRA that means hitting vol-up and vol-down at the same time), then goto "Flash .zip from sdcard" select it, hit power, select the zip file, power again, power one more time to confirm.
Once it's done you hit Reboot System Now and viola, first boot takes FOREVER so don't fret.

alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse

Techrocket9 said:
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
Click to expand...
Click to collapse
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?

jdjozwia said:
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
Click to expand...
Click to collapse
It is possible. The program I mentioned earlier (unrEVOked) should install a custom recovery for you. I can't put a link in this post because I'm on my phone, but a quick google search should find it.
An army of pacifists can be defeated by one man with the will to fight.

jdjozwia said:
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
If you just did SimpleRoot (i.e. didn't download the android SDK) you probably don't have ADB installed on your PC. So then you'd want to go the terminal route. Search the market for Better Terminal Emulator
Click to expand...
Click to collapse

huge adb problemo

Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!

wow 58 views and no one has any ideas? Please help!

Try turning on USB debugging mode?

Yes its always on, always check marked

I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.

gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build

tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App

They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App

well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing

i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...

javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?

yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...

javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one

can't unroot if my device is not seen with adb in hboot / recovery

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps

Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.

Update recovery permanently and AlphaRev start up image.

I followed 2 guides to get my phone rooted and get my HBOOT patched to allow S-OFF - AlphaRev and Clockwork Recovery 2.5.0.1.
I want to get rid of the Joker from start up - had I would of known that I would of remained S-ON till they fixed that. That did permanently add Clockwork Recovery to the recovery area. There is a new version I downloaded and told it to install from ZIP and it reloaded and came to 2.5.0.7 but it never permanently patched it in. I am seriously considering going to AmonRA if it is available - I have done so many searches my head is spinning from lack of finds.
Am I missing something or is this something that needs to be done via ADB/Fastboot? If thats the case, I may need some help.

Permanently flashing recoveries has to be done through fastboot with a .img file, the update.zip way will never permanently flash a recovery, unfortunately. Here is a download link for the 2.5.0.7 recovery image, here's how you flash it (you must have the android sdk installed, and you have to have the fastboot.exe command in either \tools or \platform-tools):
Open up a command prompt window and type this:
fastboot flash recovery C:\location\of\recovery.img
When you reboot into recovery again via hboot, it should be 2.5.0.7.
As for the splash screen, that can be changed too (thank god, I hated the joker screen as well). Follow the instructions on this thread, there are plenty of screens to choose from, including the stock t-mobile screen.
If you need anything better explained, I can try to better explain it.

Thanks for the tips. I did find one I wanted - simple and Tmobile-ish. I do have the SDK installed with all updates from the Java Frontend that it uses BUT I still do not have fastboot.exe
I tried one from a friend but it keeps sticking at WAITING FOR DEVICE. Do I need to be in fastboot first on the phone then do this? It is detecting the phone with ADB devices command.

I'm pretty sure you need to be in fastboot to do this. Why the need for permanent recovery anyway?

I tried fastboot mode on the phone and it worked - Thanks for the tip! Flashed just fine and with help of some of the threads on the themes area i got the splash screen modified. (joker is gone - thank goodness!)
I am wanting to change the boot animation - I know how that works but I can't seem to find any for the MT3GS.
Again, I appreciate the tips. They have been helpful. ( I had to transpose what your talking about to the mac - and find fastboot for the mac - HTC had it on their site with a google search )

Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.

MusicMan374 said:
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
Click to expand...
Click to collapse
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?

thronka said:
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
Click to expand...
Click to collapse
There is no AmonRA recovery for our phone, I don't believe. It was requested of him after we got s-off, but we don't know since he doesn't own a slide, and it's awfully hard to develop for a phone you don't have, haha

Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App

iDaZzLeFatHoeZz said:
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Been flashed for a while now. I did not know this method but it is good to have and try when there is an update.
I have been tinkering with the ArayrayMod Revamped files since Arayray moved on to a MyTouch 4G. (traitor! LOL)
Looks like I may be going into the developing side of roms but I am just waiting for approval to post the rom for public viewing. a .32 kernel with Wifi calling included and thats really it - well retaining OC on that rom as well.
Much more tough than I thought doing this by hand - and I always thought my Unix Administration skills would be wasted.

[GUIDE][ROOT][CWR/TWRP][DEODEX][OVERCLOCKING] SGH-S730M - Samsung Galaxy Discover

Note: This is an old phone. It's no longer being supported by Samsung, and I see that nobody is selling this phone except for eBay or Amazon. I also have a new phone now and my Discover is simply sitting there for me to have fun with. I won't be actively developing for this phone. However, I will provide support with any issues you may encounter. This thread will be kept here for future reference if anyone needs help.
Update (2022): ​I am no longer using Android. This is my last update here.​Copies of the relevant files are shared in this google drive link:​
SGH740M Root Files - Google Drive
drive.google.com
​
Please thank Ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to JohnnyGalto for giving us updated CWM, TWRP, and Partition Tables!
THIS THREAD IS INTENDED TO USE ONLY FOR THE SGH-S730M, AND NOT FOR ANY OTHER PHONE. I CANNOT CONFIRM THAT IT WILL WORK ON ANY OTHER SGH-S730 VARIANTS, SO USE THIS THREAD AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DATA LOSS, OR BRICKING THAT IS A RESULT FROM YOU CHOOSING TO ROOT. HOWEVER, IF YOU SOFT BRICK YOUR PHONE, IT CAN BE FIXED VIA CLOCKWORK RECOVERY. WARNING ABOUT USING ODIN: IF YOU ARE A NOOB, ONLY CLICK ON THE BUTTONS I TELL YOU TO CLICK, AND NOTHING ELSE. I ACCIDENTALLY SOFT BRICKED MY PHONE BECAUSE I HIT THE WRONG BUTTON WHILE USING ODIN - AND DONT WANT YOU TO DO THE SAME THING. AND LASTLY, ROOTING AND MODDING THIS PHONE WILL VOID YOUR WARRANTY. SINCE THERE IS NO OFFICIAL WAY TO RETURN TO STOCK, ONCE YOU MODIFY YOUR PHONE: YOU ARE ON YOUR OWN FATE!
IF YOU HAVE THE 730G VARIANT (Tracfone, Net10), GO HERE: http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
Issues and Bugs (Known Problems)
Okay, with deodexing - sometimes the SamsungIME.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex CWR script that tells about this issue. It does seem to correct itself overtime, so I am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
Rooting, Custom Recovery, and Unbricking Guide (Everyone)
]If you want to root your phone then follow part A.
If you want to root your phone and add custom recovery then follow parts A and B.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a Windows computer and is meant for a Windows computer. Steps will vary slightly or tremendously if it is done on any other OS.
Part A - Rooting the SGH-S730m
1. Download and install UnlockRoot Free on your PC. YOU DO NOT HAVE TO INSTALL BLOATWARE!!! PLEASE READ SETUP INSTRUCTIONS CAREFULLY!!!
2. Download and Install Samsung USB Drivers. If it prompts you to reboot for any reason, then reboot your Computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via USB.
6. Run UnlockRoot on your computer and click the "Root" Button (when it prompts you to install bloatware apps on your device, say no).
DO NOT UNPLUG YOUR PHONE UNTIL UnlockRoot SAYS IT IS OK TO DO SO!!!!
Congratulations, you have should now have a rooted SGH-730m in proximity to your hands! :fingers-crossed:
How to verify your 730M is rooted
If by any reason, you feel unsure as to if your phone is actually rooted or not:
Install a root checking app.
These apps will tell you if your phone has root access or not.
Try Root Checker from the Google Play Store.
Install a terminal emulation app.
In these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try Terminal Emulator from the Google Play Store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the USB port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
Part B - Installing a Custom Recovery
If you are not already acquainted with the idea of Custom Android Recovery, don’t be afraid. It allows developers, tweakers and noobs alike to backup, restore, fix, and to install custom ROMs and Kernels designed specifically for their device. It becomes extremely useful, because it allows people to remove “soft bricks†from their devices (which occurs when someone flashes data to the wrong device, or wrong parts of the device respectively).
I know you probably just want to not read this stuff anyways But I need to pay tribute to the developers Ivdoan and JohnnyGalto for there amazing work at compiling these custom binaries for the Samsung Galaxy Discover. Thanks guys.
So, lets get started – shall we?
Click to expand...
Click to collapse
YOU MUST ROOT YOUR PHONE BEFORE YOU DO THIS!!!!!
1. Download either the SGH_S730M.CWM_6.0.3.1.custom.recovery.tar.zip or the SGH_S730M.TWRP_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
Just to clarify for those noobs out there: CWR stands for “ClockWork Recovery†and TWRP stands for “Team Win Recovery Projectâ€. They both are custom recoveries, and basically do the same thing. Personally, I would recommend the CWR for people that just want simplicity, and the TWRP for people that want more appeal. TWRP for this device is still under development, so be careful!
Click to expand...
Click to collapse
2. Then, download the Odin Flashing Program attached to this post. Extract its contents to wherever you find necessary.
DO NOT MESS WITH ODIN! IT IS NOT A TOY! IT CAN BRICK YOUR PHONE!
Odin, is a flashing tool. It is not made to be user friendly, and is meant for people who know how to use it. I will be very blunt by saying that I AM NOT RESPONSIBLE FOR YOU NOT DOING EXACTLY WHAT I TELL YOU! PROCEED WITH CAUTION!
Click to expand...
Click to collapse
3. Right Click on Odin, and click “Run as Administrator†(if available).
4. CLICK ON THE PDA BUTTON
5. When the file window appears, browse to the desktop directory (your desktop) and select either the S730M-CWR.tar.md5 or the S730M-TWRP.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by Odin, the proceed.
8. Inside of Odin, press the Start button.
DO NOT DISCONNECT, UNPLUG, PLAY WITH ANY BUTTONS, OR CLICK ANYTHING ON EITHER THE PHONE OR COMPUTER UNTIL ODIN HAS FINISHED FLASHING CLOCKWORK RECOVERY ON YOUR PHONE.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be IT! :highfive:
Part C - Soft Brick Recovery (CWM Recovery Only!)
YOU MUST HAVE A MICRO SD CARD WITH AT LEAST 400 MB OF FREE STORAGE SPACE TO DO THIS!
build.prop restore script
You need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
If you messed up your build.prop file (If you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro SD Card.
3. Remove the SD card from the computer, and turn off the SGH-S730M.
4. Remove the back plating from the phone, and insert the micro SD card into the phone. It should be named SGH-S730M CWR stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where I told you to: you should see SGH-S730M CWR stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "Confirm Install", scroll down to "Yes - install".
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE EXECUTING THE SCRIP! YOU COULD MESS UP THE PHONE. DO NOT TURN OFF THE PHONE.
Full Restore (If all else fails)
To reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock CWM Recovery Image (.zip) from here, to your device (preferably a computer). http://forum.xda-developers.com/showthread.php?t=2677332
2. Extract ALL of the contents of the zip file to the root (/) directory of your micro SD Card. The folder should be named "clockworkrecovery".
3. Remove the SD card from the computer, and turn off the SGH-S730m.
4. Remove the back plating from the phone, and insert the micro SD card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way I told you to: you should see a menu option. If you didn't do what I told you to, you may see "No files found". If it says "cant mound /sd" (or something similar), you probably have a bad SD Card, or, forgot to put it in correctly.
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE RESTORING YOUR BACKUP TO THE PHONE! YOU COULD HARD BRICK THE PHONE (BECAUSE CWM RECOVERY WRITES TO THE BOOTLOADER). DO NOT TURN OFF THE PHONE. THE PHONE IS NOT FROZEN IF IT WONT RESPOND FOR A WHILE.
10. If you did this correctly, you should have a rooted, and restored SGH-S730m!
Part E - Removing that annoying triangle from the boot sequence
Use the triangleaway script in the attatchments. (triangleaway.zip)
It resets flash counter and resets binary status to official.
Might have to do a factory reset to return current status to official.
Boot your phone into recovery mode
Extract triangleaway.sh from the zip file.
Open up ADB Shell
push triangleaway.sh /tmp
chmod 755 triangleaway.sh
execute triangleaway.sh
Reboot Phone.
Overclocking and Modding (DEVELOPERS ONLY)
SYSTEM MODS
If you don't know what you are doing, then, please don't read any further. its for your own good
The CSC directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all. Also, If you go to /system/etc/feature_default.xml you can change the phones features. So far, I have done many tweaks to the Messaging, Phone, Settings, People (Contacts) and Lock screen of the phone! If you are a developer (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
Overclocking
FitAmp has made a overclocking script for 1GHz (1000MHz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (S730M-OC-1000MHz.zip)
Custom ROMs
Custom ROMS by atmu5fear. All flashable ZIPs. - http://forum.xda-developers.com/showthread.php?t=2677332
I'm also making one for the Discover. It should be coming soon.
Please click :good: if it works for you!

Where can I find the OC script? Thanks

evertking said:
Where can I find the OC script? Thanks
Click to expand...
Click to collapse
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.

shifattk said:
the op of this post decided to dump this thread and developing, so i decided to take over & repost this, as requested by the op.
I will also organize and add more of my stuff. That might take at least a week or so since everything is a mess right now, but i will do it.
***** original thread is here *****
please thank ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to johnnygalto for giving us updated cwm, twrp, and partition tables!
issues and bugs (known problems)[
okay, with deodexing - sometimes the samsungime.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex cwr script that tells about this issue. It does seem to correct itself overtime, so i am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
rooting, custom recovery, and unbricking guide (everyone)
if you want to root your phone then follow part a.
If you want to root your phone and add custom recovery then follow parts a and b.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a windows computer and is meant for a windows computer. Steps will vary slightly or tremendously if it is done on any other os.
part a - rooting the sgh-s730m
1. Download and install unlockroot free on your pc. You do not have to install bloatware!!! Please read setup instructions carefully!!!
2. Download and install samsung usb drivers. If it prompts you to reboot for any reason, then reboot your computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via usb.
6. Run unlockroot on your computer and click the "root" button (when it prompts you to install bloatware apps on your device, say no).
do not unplug your phone until unlockroot says it is ok to do so!!!!
congratulations, you have should now have a rooted sgh-730m in proximity to your hands! :fingers-crossed:
how to verify your 730m is rooted if by any reason, you feel unsure as to if your phone is actually rooted or not:
install a root checking app.
these apps will tell you if your phone has root access or not.
Try root checker from the google play store.
install a terminal emulation app.
in these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try terminal emulator from the google play store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the usb port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
part b - installing a custom recovery
you must root your phone before you do this!!!!!
1. Download either the sgh_s730m.cwm_6.0.3.1.custom.recovery.tar.zip or the sgh_s730m.twrp_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
2. Then, download the odin flashing program attached to this post. Extract its contents to wherever you find necessary.
3. Right click on odin, and click “run as administrator” (if available).
4. Click on the pda button
5. When the file window appears, browse to the desktop directory (your desktop) and select either the s730m-cwr.tar.md5 or the s730m-twrp.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by odin, the proceed.
8. Inside of odin, press the start button.
do not disconnect, unplug, play with any buttons, or click anything on either the phone or computer until odin has finished flashing clockwork recovery on your phone.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be it! :highfive:
part c - soft brick recovery (cwm recovery only!)
you must have a micro sd card with at least 400 mb of free storage space to do this!
build.prop restore script
you need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
if you messed up your build.prop file (if you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro sd card.
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone. It should be named sgh-s730m cwr stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where i told you to: You should see sgh-s730m cwr stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "confirm install", scroll down to "yes - install".
9. Press the power button.
wait for the phone to be 100% done executing the scrip! You could mess up the phone. Do not turn off the phone.
full restore (if all else fails)
to reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock cwm recovery image (.zip) i made from here, to your device (preferably a computer).
2. Extract all of the contents of the zip file to the root (/) directory of your micro sd card. The folder should be named "clockworkrecovery".
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way i told you to: You should see a menu option. If you didn't do what i told you to, you may see "no files found". If it says "cant mound /sd" (or something similar), you probably have a bad sd card, or, forgot to put it in correctly.
9. Press the power button.
wait for the phone to be 100% done restoring your backup to the phone! You could hard brick the phone (because cwm recovery writes to the bootloader). Do not turn off the phone. The phone is not frozen if it wont respond for a while.
10. If you did this correctly, you should have a rooted, and restored sgh-s730m!
part d - soft brick recovery (twrp recovery only!)coming soon..
part e - removing that annoying triangle from the boot sequence..to a thread near you! (it's already here. I'm just organizing them so it is easier to understand and to use)
deodexing, overclocking and modding (developers only)
deodexing you rom
you must have a micro sd card with at least 100 mb of free storage space to do this!
so, after some work (and tons of patience), i managed to make a deodexed version of this phone. So, ive made a deodex script for cwr, that will remove you old /system/app and /system/framework directories, and makes new ones, with the new deodexed files.*
now, since this is considered a more "advanced" tweak, i am not going to post a step-by-step guide on how to do this.
Why? Well, if you really needed instructions to do this: You probably shouldn't be doing it anyways!
For developers: Make sure you have busybox installed, then install the zip here via cwr (its easy to see what file it is). Remember to wipe dalvik cache. There are some temporary bugs with the samsungime.apk, which wont work right for a while. Mysteriously though, the problem corrects itself after some time using the phone. Reply your findings!
For noobs: Don't do this, it will just make no difference, and i honestly don't feel like solving problems that don't need to be solved (or, ones due to illiteracy). Wait until you know what you are doing (and what an odex file is), then try this yourself.
system mods
if you don't know what you are doing, then, please don't read any further. Its for your own good
the csc directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all.
Also, if you go to /system/etc/feature_default.xml you can change the phones features. So far, i have done many tweaks to the messaging, phone, settings, people (contacts) and lock screen of the phone! If you are a devleloper (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
overclocking
fitamp has made a overclocking script for 1ghz (1000mhz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (s730m-oc-1000mhz.zip)
please click :good: If it works for you!
Click to expand...
Click to collapse
and where is the odin did you the number
thanks

manuelelitaliano said:
and where is the odin did you the number
thanks
Click to expand...
Click to collapse
Hi there,
Sorry for the late reply. I've been quite busy lately.
http://forum.xda-developers.com/showthread.php?t=2189539
^ That thread has the downloads for Odin.

???
Hey guys,
have we found a way to fix my problem with the phone, I still have no access to download, recovery, normal boot and it stays on for 7 secs max. This has ocured because I flashed the wrong file to modem. Let me know as I want to start working on development again.

camvar97 said:
Hey guys,
it stays on for 7 secs max.
Click to expand...
Click to collapse
^ That, to me looks like the battery is not charged (unless I am wrong).
camvar97 said:
Hey guys,
... I still have no access to download, recovery, normal boot and it stays on for 7 secs max. ... This has ocured because I flashed the wrong file to modem.
Click to expand...
Click to collapse
I've searched around a bit, and the best option would be to send it for repair IMO.

shifattk said:
^ That, to me looks like the battery is not charged (unless I am wrong).
I've searched around a bit, and the best option would be to send it for repair IMO.
Click to expand...
Click to collapse
as for the battery thats what samsung says might be the problem and that i need a new one

SGH-730G Users ONLY
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608

TheGeekyNimrod said:
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.

shifattk said:
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.
Click to expand...
Click to collapse
Word. I know some people were confused in another thread. Root methods are basically the same but there are structual differences between them when it comes to mounting points for restore and such. Thanks for addinthe link to the OP. I'll go back in a few and add a link here in my OP for the same purpose.

Does anyone know how to carrier unlock for this phone yet.

question?when i try to install CMW it keeps failing nand rite mode and restarting! any solution or different ay to try,still showing stock recovery but rooted!

Hello guys is there any way to unroot??? thanks

alexandros050 said:
Hello guys is there any way to unroot??? thanks
Click to expand...
Click to collapse
You can use unlockroot software to unroot.
I tested rooted and unrooted.

x1745 said:
You can use unlockroot software to unroot.
I tested rooted and unrooted.
Click to expand...
Click to collapse
Ok thank you very much for your reply

Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.

Restl3ss said:
Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.
Click to expand...
Click to collapse
I tried flashing your ROM, get error status 255, installation aborted...

shifattk said:
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.
Click to expand...
Click to collapse
Phone wont boot past samsung logo after this. Followed your instructions exactly

atmu5fear said:
Phone wont boot past samsung logo after this. Followed your instructions exactly
Click to expand...
Click to collapse
Did you make a CWM backup before doing it? If you did, boot into CWM recovery and flash the recovery package.

Explain like I'm a three year old, I beg of you.

I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.

Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.

I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.

I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.

tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.

I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...

Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs

xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?

tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs

Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs

bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!

So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...

tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.

Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...

tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.