Develop Bugs

Back up EVERYTHING before rooting?

Alright, as some of you know, I really, really, REALLY, messed up on my last root attempt.
Apparently I didn't backup what I was supposed to. That was my own stupid a55 mistake and I have admitted to it.
I DO plan to attempt a root again so that I can get this theme on my phone: http://forum.xda-developers.com/showthread.php?t=1042268
There are things that I need to know before I attempt this (and yes I know there are forums already on this but I need to be 110% sure)
1) How do I back up EVERYTHING on my phone and put it on my computer or SD card or somewhere that I can go to incase I mess up again?
2) What is the EASIEST program/method to root this Samsung Epic 4g?
3) (I'm not too sure what I'm talking about here ((remember, I'm a total noob)))
I tried CWM 3.0.0.5 before... is this a ROM that I attempted to go to?
3ii) If I should'nt be using CWM, what should I use?
4) Is Froyo and CWM the same time of thing? or two different things completely?
and finally:
5) Give me all of your recommendations on this please! I DON'T WANNA MESS UP AGAIN!
And please none of this "You messed up before, dont try it again!" crap, I know I messed up, and I know this is stupid, but the fact of the matter is, I'm trying it again to get this theme on my device. So PLEASE help me out!
Thanks everyone!

cheech92007 said:
Alright, as some of you know, I really, really, REALLY, messed up on my last root attempt.
Apparently I didn't backup what I was supposed to. That was my own stupid a55 mistake and I have admitted to it.
I DO plan to attempt a root again so that I can get this theme on my phone: http://forum.xda-developers.com/showthread.php?t=1042268
There are things that I need to know before I attempt this (and yes I know there are forums already on this but I need to be 110% sure)
1) How do I back up EVERYTHING on my phone and put it on my computer or SD card or somewhere that I can go to incase I mess up again?
2) What is the EASIEST program/method to root this Samsung Epic 4g?
3) (I'm not too sure what I'm talking about here ((remember, I'm a total noob)))
I tried CWM 3.0.0.5 before... is this a ROM that I attempted to go to?
3ii) If I should'nt be using CWM, what should I use?
4) Is Froyo and CWM the same time of thing? or two different things completely?
and finally:
5) Give me all of your recommendations on this please! I DON'T WANNA MESS UP AGAIN!
And please none of this "You messed up before, dont try it again!" crap, I know I messed up, and I know this is stupid, but the fact of the matter is, I'm trying it again to get this theme on my device. So PLEASE help me out!
Thanks everyone!
Click to expand...
Click to collapse
Ok, first things first. Not to be rude, but you are at the first step of enjoying Epic goodness; rooting your phone. It should be obvious that this step is covered ALL over XDA and a simple google search would have lead you to the following page:
CWM 3.0.0.5
There are already wayyyy too many threads asking questions that were answered long before they were ever even asked in the first place.
Okay, now that that's out of the way .
1. If you're absolutely freaked about losing anything, MyBackup and MyBackup Pro will back up all your apps. Then simply plug your phone into your computer and copy the entire contents of your sd card to your harddrive. Mybackup Root can be used once your rooted and is free.
2. Use the link i posted.
3. CWM is not a Rom. It replaces the default recovery subsystem with one you can use to flash Roms. You enter it from the off state by pressing Volume Down+Camera+Power. Do not use CWM 3.0.2.4.
4. Froyo is simply the version of android. The Samsung Epic is on Froyo, or 2.2. Roms come in various flavors like Eclair(2.1), Froyo(2.2), and hopefully soon for the Epic, Gingerbread(2.3).
5. Search around the Epic Android Development for a Rom that makes you excited. A good suggestion for you would be Midnight 5.2. All you have to do is download the Rom .zip file to your SD, boot into CWM 3, Install from SD, and point it to the .zip. Read the forums for how to safely install their Roms like clearing data and making/restoring backups.
Remember, everything you've asked has been asked and answered many times, so please search next time to avoid making unnecessary threads and to gain your answer faster!

RandomKing said:
Ok, first things first. Not to be rude, but you are at the first step of enjoying Epic goodness; rooting your phone. It should be obvious that this step is covered ALL over XDA and a simple google search would have lead you to the following page:
CWM 3.0.0.5
There are already wayyyy too many threads asking questions that were answered long before they were ever even asked in the first place.
Okay, now that that's out of the way .
1. If you're absolutely freaked about losing anything, MyBackup and MyBackup Pro will back up all your apps. Then simply plug your phone into your computer and copy the entire contents of your sd card to your harddrive. Mybackup Root can be used once your rooted and is free.
2. Use the link i posted.
3. CWM is not a Rom. It replaces the default recovery subsystem with one you can use to flash Roms. You enter it from the off state by pressing Volume Down+Camera+Power. Do not use CWM 3.0.2.4.
4. Froyo is simply the version of android. The Samsung Epic is on Froyo, or 2.2. Roms come in various flavors like Eclair(2.1), Froyo(2.2), and hopefully soon for the Epic, Gingerbread(2.3).
5. Search around the Epic Android Development for a Rom that makes you excited. A good suggestion for you would be Midnight 5.2. All you have to do is download the Rom .zip file to your SD, boot into CWM 3, Install from SD, and point it to the .zip. Read the forums for how to safely install their Roms like clearing data and making/restoring backups.
Remember, everything you've asked has been asked and answered many times, so please search next time to avoid making unnecessary threads and to gain your answer faster!
Click to expand...
Click to collapse
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.

cheech92007 said:
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.
Click to expand...
Click to collapse
After reviewing your other posts, I am now aware that you have asked a lot of this and already been answered but are clearly not interested in reading the information presented to you. This should have been continued in the last thread that you started, but what's done is done. Your key problem is rooting with CWM which converts the file system to EXT4. You will have to flash a new rom or kernel immediately following or the phone can't boot. This means that you must have a new rom or kernel .zip file on your sd card PRIOR TO ROOTING. I haven't messed around too much with a rooted stock rom, but at the least you need a new kernel, search for and try VisionKernel if thats all you want.
Please refrain from starting any more threads, you've already been given more information than you need by myself and others. Search around XDA, it can be fun!

RandomKing said:
You will have to flash a new rom or kernel immediately following or the phone can't boot. This means that you must have a new rom or kernel .zip file on your sd card PRIOR TO ROOTING. I haven't messed around too much with a rooted stock rom, but at the least you need a new kernel, search for and try VisionKernel if thats all you want.
Click to expand...
Click to collapse
Alright, I just downloaded the EB13-DUALFS-KERNEL.zip to my desktop...is THIS what you were talking about that I need on my SD card first? I looked inside it and it has a KERNEL file in it... So I put this on my SD card, then ROOT, then UNZIP the EB13 on my devices when Im in CWM Reboot?

cheech92007 said:
Alright, I just downloaded the EB13-DUALFS-KERNEL.zip to my desktop...is THIS what you were talking about that I need on my SD card first? I looked inside it and it has a KERNEL file in it... So I put this on my SD card, then ROOT, then UNZIP the EB13 on my devices when Im in CWM Reboot?
Click to expand...
Click to collapse
There is no unzipping. In CWM, you simply select "Install from sd", point to your .zip file, and tell it to start. CWM is pretty straight forward to navigate. It will probably take a couple minutes, after which you will select the Reboot option and watch your phone load.

cheech92007 said:
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.
Click to expand...
Click to collapse
What randomking said....and
I didn't see what the red angry alien theme was designed for.... it just says ec05...ec05 is the latest build of froyo we have. Because all you want is a theme I'm going to suggest you do the oneclick root cwm version 2.5.5(stock file system).
I assume you'll need to be on a deodexed rom to flash that, but you may want to try it(since you learned how to odin you can just about recover from anything) and see if it works.
After you run the oneclick 2.5.5 root your good to go, just boot back into clockworkmod(2.5.5 is green text and not orange) click down to backup/restore, click on it and then click backup. This is what's called a nandroid. A nandroid is a complete backup of your entire system, including all user data. The only thing it will not backup is the kernel, since your not changing the kernel it won't matter. If you have problems or mess up you just wipe everything/factory reset/cache/dalvik cache and instead of going to backup, you select restore....blaam exactly the way your phone was when you backed it up. BTW backing up and restoring takes about 10minutes and don't try it when your battery is almost dead.
Hope that helps a bit more and don't rush it, the theme will be here for a long while I'm sure.

RandomKing said:
There is no unzipping. In CWM, you simply select "Install from sd", point to your .zip file, and tell it to start. CWM is pretty straight forward to navigate. It will probably take a couple minutes, after which you will select the Reboot option and watch your phone load.
Click to expand...
Click to collapse
Great, Thank you so much I really appreciate it.
Now all I need to do is get my theme on here xD

cheech92007 said:
Great, Thank you so much I really appreciate it.
Now all I need to do is get my theme on here xD
Click to expand...
Click to collapse
On second thought cheech, go herehttp://forum.xda-developers.com/showthread.php?t=1009997 and watch every single one of these videos and don't ask anything more untill you have.....deal?

epic4GEE said:
On second thought cheech, go herehttp://forum.xda-developers.com/showthread.php?t=1009997 and watch every single one of these videos and don't ask anything more untill you have.....deal?
Click to expand...
Click to collapse
yessir!

cheech92007 said:
yessir!
Click to expand...
Click to collapse
I'll thank that post later if you really watch ALL those videos.....they're really helpful

Can not boot into recovery after rom manager updated my CM9

Hello, Wondering if anyone here could help out. I recently went from MIUI US ICS rom to CM9 and love the latest build of CM9. I had not tried a backup of the rom after flashing to CM9, but noticed that Rom Manager updated at play.google.com and then I decided maybe I should make a backup of CM9 sine it was shaping up pretty nicely as I've been setting up apps,etc.
Well, I can't get into recovery. I can boot into the bootloader and it shows Revolutionary as the boot loader and I can get into Fastboot but if I toggle down to recovery and press the power button it just jumps back to the bootlloader screen. I can't get past this.
I'm tempted to put a different recovery on here now as the rom manager didn't work out even though it came stock on my CM9.
But before I risk bricking my phone, I was hoping someone here could back me up a bit and give me some input. I really don't know that much about this.. I can root phones, install recoveries, etc., but if something goes wrong I'm not knowledgeable enough to actually understand what went wrong and how to fix. I am guessing that recovery is not actually installed here and that Revolutaionary (what I used long ago to get root) wasn't planned to be the boot here.
Help please anyone!!!!!

billagreste said:
Hello, Wondering if anyone here could help out. I recently went from MIUI US ICS rom to CM9 and love the latest build of CM9. I had not tried a backup of the rom after flashing to CM9, but noticed that Rom Manager updated at play.google.com and then I decided maybe I should make a backup of CM9 sine it was shaping up pretty nicely as I've been setting up apps,etc.
Well, I can't get into recovery. I can boot into the bootloader and it shows Revolutionary as the boot loader and I can get into Fastboot but if I toggle down to recovery and press the power button it just jumps back to the bootlloader screen. I can't get past this.
I'm tempted to put a different recovery on here now as the rom manager didn't work out even though it came stock on my CM9.
But before I risk bricking my phone, I was hoping someone here could back me up a bit and give me some input. I really don't know that much about this.. I can root phones, install recoveries, etc., but if something goes wrong I'm not knowledgeable enough to actually understand what went wrong and how to fix. I am guessing that recovery is not actually installed here and that Revolutaionary (what I used long ago to get root) wasn't planned to be the boot here.
Help please anyone!!!!!
Click to expand...
Click to collapse
Just flash a recovery again that should do it same thing happen to me
Sent from my PC36100 using xda premium

Try reflashing recovery
Sent from my PC36100 using Tapatalk 2

CRIME INC. said:
Try reflashing recovery
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
It's been a while since I've done someting like that. By this you mean place a recovery package on the zip card, press the power button at the bootloader, then let the phone install the recovery when it runs thru the fastboot screen?
If yes, great, I remember that, but which recovery should I download? And what about rom manager on CM9? Does it care which recovery is installed?
I appreciate the knowledge here. IT sure is appreciated when things go wrong for folks like myself!
Oh, I should point out that I can stil boot into the phone and use it. The whole issue is limited to getting into recovery to create and/or restore backups of the rom.
Bill

billagreste said:
It's been a while since I've done someting like that. By this you mean place a recovery package on the zip card, press the power button at the bootloader, then let the phone install the recovery when it runs thru the fastboot screen?
If yes, great, I remember that, but which recovery should I download? And what about rom manager on CM9? Does it care which recovery is installed?
I appreciate the knowledge here. IT sure is appreciated when things go wrong for folks like myself!
Bill
Click to expand...
Click to collapse
1st off, I should shun you for being corrupt with CWM, but I'll help ya out.
Use the search bar and type in "Smelkus recovery" find a themed recovery zip you like and rename it "PC36IMG.zip" and place on the root of your SD card (in no folders) boot to boot loader and let it search, press volume up to update recovery and boom! You have new, better recovery.
As for flashing CM9, check out Jmzs CM9 nightlies. Its better and (supposedly) almost has Wimax working. Once you flash an Amon Ra based recovery, CWM becomes basically useless. So ditch it for the good of everyone. ENJOY
EDIT: Because I'm NICE, here's the link.
http://forum.xda-developers.com/showthread.php?t=1661543
This is my signature.

death-by-soap said:
1st off, I should shun you for being corrupt with CWM, but I'll help ya out.
Use the search bar and type in "Smelkus recovery" find a themed recovery zip you like and rename it "PC36IMG.zip" and place on the root of your SD card (in no folders) boot to boot loader and let it search, press volume up to update recovery and boom! You have new, better recovery.
As for flashing CM9, check out Jmzs CM9 nightlies. Its better and (supposedly) almost has Wimax working. Once you flash an Amon Ra based recovery, CWM becomes basically useless. So ditch it for the good of everyone. ENJOY
EDIT: Because I'm NICE, here's the link.
http://forum.xda-developers.com/showthread.php?t=1661543
This is my signature.
Click to expand...
Click to collapse
Wow, much nicer recovery than any I've used. Thank you for that! I didn't actually intend to put on CWM, but now I'll make it a point to avoid . I did search for JMZS CM9 nightlies. Was going to try it but not getting any hits to lead me where I think you are leading. WOld I find JMZS nightlies here at xda or outside? I did a google search and got nothing other than your post to me above.
Anyhow, thanks for the help folks!
Bill

billagreste said:
Wow, much nicer recovery than any I've used. Thank you for that! I didn't actually intend to put on CWM, but now I'll make it a point to avoid . I did search for JMZS CM9 nightlies. Was going to try it but not getting any hits to lead me where I think you are leading. WOld I find JMZS nightlies here at xda or outside? I did a google search and got nothing other than your post to me above.
Anyhow, thanks for the help folks!
Bill
Click to expand...
Click to collapse
Here you go. Jmzs unofficial CM9 nightlies.
http://forum.xda-developers.com/showthread.php?p=25438778
5+0+4+9 = S+O+A+P

death-by-soap said:
Here you go. Jmzs unofficial CM9 nightlies.
http://forum.xda-developers.com/showthread.php?p=25438778
5+0+4+9 = S+O+A+P
Click to expand...
Click to collapse
Well can I pick your brain once more? I decided to update my wifes phone from MIUI to CM9. She happened to have Clockwork recovery 5.0.2.2. on the phone which I recall was put there by whatever rooting routine I used. Before installing CM9, I tried to update the recovery with Smelkus from the clockwork recovery 5.0.2.2 that's on the phone to smelkus, but when I try to flash it, the smelkus recovery just sits there "parsing" so when I bail out and go back to check, the clockwork version recovery is still there.
This phone was rooted with Revolutionary but I notice that S-ON is still active. I read that S-OFF is not necessary to install a recovery --- at least not the clockwork version that is on this phone. I'm not sure if that's causing the problem or not. Any advice?

Try this one. It should work.
http://db.tt/1Y4xAqiB
This is my signature.

death-by-soap said:
Try this one. It should work.
http://db.tt/1Y4xAqiB
This is my signature.
Click to expand...
Click to collapse
Gave it a try, same result. What do you think might be going on? I wonder if I should try and flash it with the same one that's stuck in the phone first then try the others? Clueless really what's happening.

billagreste said:
Gave it a try, same result. What do you think might be going on? I wonder if I should try and flash it with the same one that's stuck in the phone first then try the others? Clueless really what's happening.
Click to expand...
Click to collapse
You can try through Adb.
This is my signature.

death-by-soap said:
You can try through Adb.
This is my signature.
Click to expand...
Click to collapse
If I were you, I'd run the RUU for your phone and start over

camer across this
Hello... d-b-s
By chance have you seen this recovery located here:
http://forum.xda-developers.com/showthread.php?p=29266458
I have a spare evo that is sorta-bricked or sorta screwed, not sure which... It has a SD slot that seems to be locked out. Nothing can be read from it but I did get it working once but lost it. ANd it also doesn't boot unless I have a power plug in it, but otherwise, it works, flashes, etc.. it's got CM9 right now in it but again somewhat useless without the SD memory.... anyhow, it's been a plaything for me figureing I'll either fix it, learn or kill it. None has happened yet.. but in searching for getting a recovery installed that uses the screen hard buttons versus the volume (this rocker switch on volume is broken too), I installed this recovery and it's different than anythign else... fully menuized .. real customized, and thought I would mention it to you.
If you have a look at it, let me know what you think.
Bill.

billagreste said:
Hello... d-b-s
By chance have you seen this recovery located here:
http://forum.xda-developers.com/showthread.php?p=29266458
I have a spare evo that is sorta-bricked or sorta screwed, not sure which... It has a SD slot that seems to be locked out. Nothing can be read from it but I did get it working once but lost it. ANd it also doesn't boot unless I have a power plug in it, but otherwise, it works, flashes, etc.. it's got CM9 right now in it but again somewhat useless without the SD memory.... anyhow, it's been a plaything for me figureing I'll either fix it, learn or kill it. None has happened yet.. but in searching for getting a recovery installed that uses the screen hard buttons versus the volume (this rocker switch on volume is broken too), I installed this recovery and it's different than anythign else... fully menuized .. real customized, and thought I would mention it to you.
If you have a look at it, let me know what you think.
Bill.
Click to expand...
Click to collapse
I'm familiar with twrp. I don't much care for it though. A dew tricks with smelkus is it has touch scrolling, and the bottom buttons work as up+down+back+select..
Also I might know of a fix for the SD card not being read. I'll get back to you with that.
http://forum.xda-developers.com/showthread.php?p=6696983
V3ndetta Is Rising.....

death-by-soap said:
I'm familiar with twrp. I don't much care for it though. A dew tricks with smelkus is it has touch scrolling, and the bottom buttons work as up+down+back+select..
Also I might know of a fix for the SD card not being read. I'll get back to you with that.
http://forum.xda-developers.com/showthread.php?p=6696983
V3ndetta Is Rising.....
Click to expand...
Click to collapse
d-b-s,
That would be fantastic if you had a clue on the SD card. I did try a FastBoot string that reset it once the first time and it worked, but somehow I lost it again. I think a corrupt or defective SD card started the whole problem and restarted it when I put it's data SD back in.
Do you ride a motorcycle or have a boat? If so, stop by here please www.streetglo.net and pick yourself out something. I'd like to send it to you. You have helped me more than you know. I can't reciprocate with knowledge but I have other ways.. Let me know what you see you like. Thanks!!!!
Bill
P.S. Yea, I know you don't want anything for your help.. Just pick out something you can use and I'll be a better man for it. At least I think it works that way!

billagreste said:
d-b-s,
That would be fantastic if you had a clue on the SD card. I did try a FastBoot string that reset it once the first time and it worked, but somehow I lost it again. I think a corrupt or defective SD card started the whole problem and restarted it when I put it's data SD back in.
Do you ride a motorcycle or have a boat? If so, stop by here please www.streetglo.net and pick yourself out something. I'd like to send it to you. You have helped me more than you know. I can't reciprocate with knowledge but I have other ways.. Let me know what you see you like. Thanks!!!!
Bill
P.S. Yea, I know you don't want anything for your help.. Just pick out something you can use and I'll be a better man for it. At least I think it works that way!
Click to expand...
Click to collapse
I really appreciate the kind gesture but I wouldn't like anything in return. Helping people with their problems and teaching them what I know is enough of a reward.
Please do me a favor and enjoy yourself. Best of wishes to you.
-soap

[Q] Help I deleted a system file

Hey I got my phone rooted, so I installed Titanium Backup, and then I uninstalled the stock browser, the download manager, and also android.downloader or something like that. And I broke my phone - now Google Play just crashes instantly.
I've tried reinstalling the firmware, and resetting to factory, but it's still the same.
Is there anything I can do, other than take it back to the store?
Help!!!!!
EDIT: It gives the error "Unfortunately the process com.google.process.gapps has stopped."

did you do a nandroid backup?> if not we need to know the exact application you deleted. future reference DONT DELETE. just freeze then its just a simple unfreeze and a freeze also stops the app from running. you will not get more available memory by doing this because this is on a different partition. Also never delete or freeze anything referring to com.android they are core funtions that are required for your device to run properly.

You deleted a process?!
My money would be that android.download or whatever process you deleted was required for Google Play to work. Hopefully you made a Nandroid before modifying processes. If not, you'll have to flash a stock ROM to get it back.
Alternatively, if you backed up system data with Titanium Backup, you might be able to find the process in there and restore it.
Echoing drksilenc, don't uninstall things through Titanium Backup unless you're positive it won't mess something up. How can you be positive? One, deleting processes always causes problems. Even freezing them can be messy. Don't do it. Two, in the case of an app, you'll know it's ok if you've had it frozen for a week or so and the phone hasn't acted up. Even with system apps, though, I recommend freezing rather than uninstalling. It's safer, and you never know if you might want/need that app again.

It gets worse.
I went down to the Bell store (my phone's actually from Bell, but they're similar to the AT&T ones, right?) and they wouldn't exchange it. So I tried going into the Clockwork Recovery, and wiped all of the little folders in "Advanced Settings." Because I noticed that Bell's add-on apps kept coming back, why weren't the other ones I deleted? And now it's a useless brick, says SAMSUNG and that's it.
Brand new one-day old superphone, totally wrecked. I don't even think there are any stock ROM's out there for this thing yet.
I'm a meathead.
I'll try reinstalling the firmware again that I did before, maybe I'll get lucky.

Nope, still nothin'.
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
I went to samsung-updates.com and searched for the Note 2, and sure enough, it's on their list of ROMs for the Note 2. So I'm downloading the GT-N7105, and I'ma gonna install it, unless someone here tells me different!

d3fau1t said:
Nope, still nothin'.
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
I went to samsung-updates.com and searched for the Note 2, and sure enough, it's on their list of ROMs for the Note 2. So I'm downloading the GT-N7105, and I'ma gonna install it, unless someone here tells me different!
Click to expand...
Click to collapse
I wouldnt do that!!! The boot.img will brick you im pretty sure! You cant download and flash a rom in development section? And I thought I saw a stock tar floating around?

truth77 said:
I wouldnt do that!!! The boot.img will brick you im pretty sure! You cant download and flash a rom in development section? And I thought I saw a sti c k tar floating around?
Click to expand...
Click to collapse
I found a Cyanogenmod ROM but even that says it's for the n7100. I can't seem to find anything for the sgh-1317m.

d3fau1t said:
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
Click to expand...
Click to collapse
Don't do that. For one, flashing a ROM for a different device is virtually always Detroit Brick City. Two, the guy's got two whole posts. Don't do it.

d3fau1t said:
I found a Cyanogenmod ROM but even that says it's for the n7100. I can't seem to find anything for the sgh-1317m.
Click to expand...
Click to collapse
Any rom in our dev section should fix you try clean rom ans stop using titanium vackup. Why are you debloating roms when devs did it for you already and obviously you see you have no clue what you're doing?

[/COLOR]Lol... that didn't work at all... I thoughtbthe links would copy over... look in the android dev section theres a rom there for you. .. 8)
Sent from my SGH-I317M using xda premium

Just flash any rom in the android development section usinf twrp or cwm, it will rebuild /system and fix any issues. In the future dont delete or uninstall system apps, just freeze them if you think yiu dont need it. Freezing stops the app from running ans taking up any cpu or memory so its almost as good as deleting (it still technically takes up space but this phone has plenty of space) with nine of the dangers. If something stopped working like play store, youvcan defrost the apps yiu froze easy enough.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

glitchsys said:
Just flash any rom in the android development section
Click to expand...
Click to collapse
Is that going to be ok even though I'm on a Bell phone and it's sgh-i317m? Cuz I don't see any ROM's that end in M...
Big thanks to everyone trying to help.

d3fau1t said:
Is that going to be ok even though I'm on a Bell phone and it's sgh-i317m? Cuz I don't see any ROM's that end in M...
Big thanks to everyone trying to help.
Click to expand...
Click to collapse
Yes we promise lol and dont freeze or delete anything just leave it to the devs and only download stuff from this forum i317/i317m

Sadly, failure
I downloaded CleanROM Lite 1.0.zip, put it on the SD card, and used Clockwork Recovery to install it. The installation went without a hitch, but trying to boot the phone, all I get is the SAMSUNG logo still. So I did a factory reset, wiped the cache, wiped the Dalvik cache, and did "fix permissions", but it's the same.
So I'm downloading the other ROM ("Stock Root - De-Odex") and will try that presently.

d3fau1t said:
I downloaded CleanROM Lite 1.0.zip, put it on the SD card, and used Clockwork Recovery to install it. The installation went without a hitch, but trying to boot the phone, all I get is the SAMSUNG logo still. So I did a factory reset, wiped the cache, wiped the Dalvik cache, and did "fix permissions", but it's the same.
So I'm downloading the other ROM ("Stock Root - De-Odex") and will try that presently.
Click to expand...
Click to collapse
These roms take a while to boot how long did you wait. Look you didnt break your phone from deleting apps just flash the rom and wait it will boot. Remember these roms are 750-800 mb worth of data to boot not 250mb like aosp roms, takes few mins to boot

truth77 said:
These roms take a while to boot how long did you wait. Look you didnt break your phone from deleting apps just flash the rom and wait it will boot. Remember these roms are 750-800 mb worth of data to boot not 250mb like aosp roms, takes few mins to boot
Click to expand...
Click to collapse
You might have been right. I'm so used to it just freezing up that maybe I wasn't patient enough and just assumed.
But it works now! I flashed the Stock ROM, and it booted up with no problems. Then I flashed the lite one again, and it works too. So now I'm going to try the other ROM on the dev page, see how it looks.
And it's still rooted, so hooray!
Thanks for all your help.

you REALLY need to do ALOT more READING, and ALOT LESS Flashing...

S3 Rogers - Looking for ROM/info

I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:

http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

saj222 said:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Instead of linking me to something I've already read, how about actually saying something.
I'm finding too many "this might work for rogers, this might not"
Last time i followed a tutorial meant for an AT&T unit, I hard bricked the phone, and ended up tossing it
Sorry if it was in the wrong section before Kenny.

How about me not responding at all next time? I know no one is forcing me but its simple enough to find this info by searching. I understand your hesitance... No one wants an expensive brick.
I'll put something together for you later today unless someone else beats me to it. Deal?

js593 said:
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Click to expand...
Click to collapse
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506

saj222 said:
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
Click to expand...
Click to collapse
Thank you very much. I';ll be looking this over and attempting this tonight.

js593 said:
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
Click to expand...
Click to collapse
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.

thecoach1999 said:
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
Click to expand...
Click to collapse
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)

js593 said:
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
Click to expand...
Click to collapse
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.

saj222 said:
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
Click to expand...
Click to collapse
I believe i ran into the issue blindly.
I forgot to update the bootloader before flashing it. Will try again when i get home and report back with anything.

..

fffft said:
If that sorts your issues, then call it done and thank the people that helped you.
The earlier suggestions were good and not to be faulted. However there is more than one way to do most things. So if you are not happy for whatever reason here is a slightly different approach. There are some very stable custom ROMs that are very snappy and have a similar no lag, fluid feel (Google calls this "butter") to them vis a vis the Nexus. So a simple approach to that result would be:
1. Download and install the Samsung S3 V7.0 toolkit (program)
2. Start the toolkit program
Choose "n" when asked if you want to update the program
Choose your phone version. This is probably "53" for you
Choose option #1 from the main menu to install the necessary USB driver to your PC
After the driver is installed, connect your phone to your PC with the Samsung USB cable.
If your phone is currently stable, you can skip steps #3 + 4.
If you are uncertain, then steps #3 + 4 will restore a stock Rogers firmware as a starting point:
3. Go to Samsung updates and download a stock Rogers firmware
4. Install the stock firmware. This is toolkit menu option #8, 4, 2
5. Download the custom Wicked Aroma ROM v10 (main thread here)
6. Copy the Wicked Aroma ROM to your phone. You can do this in windows by going to file manager and drag and drop the Wicked file (leave it zipped) on the "Samsung Mobile MTP Device - Phone/Data" folder icon.
7. Flash the Wicked ROM from "recovery mode"
Ensure that your battery is at least 80% charged. Then turn your phone off and disconnect the USB cable
Push and hold the home button, volume up and power button at the same time until you feel the phone vibrate and see blue text on screen in the upper left hand corner. Then release the buttons.
On the onscreen phone menu, choose wipe (factory reset)
Then choose install and select the Wicked_v10. zip file
The rest of the install will be automated on your phone screen. It will ask you to select a number of options. If you are uncertain, then just leave them at the default settings. Ensure that you leave the wipe cache setting as is when asked. And I'd recommend the stock theme and stock kernel to start. The rest you can leave as is or change to what sounds attractive to you.
Note that the wicked ROM will change your boot splash screen. Most people won't care and it's not that hard to revert if you don't like the logo for some reason. This is the logo that appears for a few seconds when you first power up a phone.
This is a very snappy, pretty much zero lag and stable ROM. I think that you'd like it.
.
Click to expand...
Click to collapse
Thanks for the lengthy reply.
I tried putting the new bootloader on there, and tried re-flashing, but it did the same thing. So, in the mean time i'm going to use the Dandroid rom (didn't install the Gapps) and it seems to be working okay. I just fear a bit as the phone seems to be running much warmer then it usually does....
In the mean time, ill use this one, and see if it makes a difference (it could still be loading all my settings and whatnot, so we'll see what happens. I love the look of this rom though. Very simple, very clean. Exactly what i was looking for. Those samsung stock themes are terrible.... Thanks a bunch for the help people. Greatly appreciate it!

Personal taste varies a lot and there are a lot of themed ROMs on this site. So you should be able to find something that you like. It sounds like you want something snappy and Spartan looking. If you like your results so far, then no need to go any further.
If you end up trying the Wicked ROM, perhaps choose the Miui or Holo launcher and ASOP lock screen options.
There are an endless variety of home screen themes to be discovered. And no way to know what you might like. A few random screen shots:
http://media02.hongkiat.com/cool-android-homescreens/Clood.jpg
http://media02.hongkiat.com/cool-android-homescreens/evening.jpg
http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/09/jb_holo_launcher.jpg
http://i380.photobucket.com/albums/oo248/jb-dan/DroidInc/d4281332.jpg
http://mycolorscreen.com/wp-content/uploads/homescreens_2012/270592/KLPOS7.png
http://desktopspotting.com/wp-content/uploads/2011/12/Minimal-Android-Home-screen.png
.

Just installed the Wicked rom on my S3. NICE! Need to play with the settings a bit to get it configured the way I like, but a definite keeper.
Very nice job.....Kudos!

[Q] Error 7 with XM.10-2

First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.

MTSL_Mantra said:
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
Click to expand...
Click to collapse
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.

Mr. Struck said:
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Click to expand...
Click to collapse
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.

MTSL_Mantra said:
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
Click to expand...
Click to collapse
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.

Mr. Struck said:
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Click to expand...
Click to collapse
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..

MTSL_Mantra said:
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
Click to expand...
Click to collapse
Did you install Philz as well or are you still using CWM?

Mr. Struck said:
Did you install Philz as well or are you still using CWM?
Click to expand...
Click to collapse
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..

MTSL_Mantra said:
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
Click to expand...
Click to collapse
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal. All I can say is that, in my opinion, Philz is far superior, I would say give it another shot.
Sent from my SPH-L710 using Tapatalk

Mr. Struck said:
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I misspoke, I meant sdcard1 (or ext_sdcard or however the other recoveries reference it). None of them have been able to do it with their respective names. But that's (possibly) another issue, I just mean that's why I'm not positive switching would help. I could definitely be wrong though, I can try it if nothing else next time I get to a computer with Odin send it over.

There is a flashable zip as well just FYI. As to your backup location issues, I don't know what to tell you, I've never experienced that problem.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
Also, I know some users have had better luck renaming one of the bootloader assert lines to match the MK3 boot loader instead of deleting all the lines.
Sent from my SPH-L710 using Tapatalk

Maybe I'll try philz out then but if not I'm stumped.. I know it sholdn't be this difficult to do this crap, I'm glad that I'm learning some of the pitfalls, but some of these pitfalls don't seem like things other people have been encountering so I don't know what the deal is.