Related
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
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!
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
I have a Samsung S3 L710 on Virgin Mobile.
I've been running a Kitkat ROM; Conquest Singularity; for a very long time and wanted a change. I wanted to try out a ROM running Lollipop.
This is were my issues have started.
I updated to the latest TeamWin recovery and so far have clean flashed 3 different ROMS.
1 ROM the PAC ROM did not stay on the phone long at all because it was having trouble staying connected to my wifi. Wasn't on long enough to see if it has the same problem as the other ROMs listed below.
The other 2 ROMs I've tried, Liquid Smooth and currently on the phone OctOS. Both these ROMs will I think randomly reboot. (I'll get to "randomly" part in a bit.)
One thing I've done that I know is not recommended, is using TiB to replace data on a new flash. My question here is, if you have information in some apps that can not be saved in anyway way, how would one do this without using TiB?
Now onto the random reboots. I know most happened when I was playing Ingress on both ROMs. Ingress uses a lot of resources and being on for a while gets the phone pretty warm. Not sure if it's overheating the phone causing it to be unstable or what.
I have not adjusted any kernel CPU settings on any ROM that I've installed. Everything is left stock. Not sure if the developer has the settings overclocked from an install and maybe this is making the phone unstable.
Basically I'm frustrated to why I seem to be the only person getting reboots, and I know that from what is written no one will have any ideas why. I'm just venting. Now that I've been playing with LP ROMs the past few days, I'd like to keep one on the phone working properly.
Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out
lvpre said:
Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out
Click to expand...
Click to collapse
Well that might explain it.
Haven't tried CM yet because most the ROM's required TWRP recovery and CM takes a different one.
I tried flashing AICP, but the Gapps didn't flash. Said wrong ROM or something. I only had the one Gapps on my internal storage so I flashed the OctOS instead. Just downloaded the Gapps listed on the AICP page. May try flashing that one now. Just so sick of reinstalling all my apps..... :silly:
As for TiB. I'm good then. I never do any system apps. I must have misunderstood about that. Been a long time since I've flashed anything.
Here's how I flashed aicp on my phone, using the modified TWRP that's made specially for Virgin/boost d2spr made by Lrs121. 1. Flash the latest aicp nightly. 2. Flash latest banks gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps. 3. Flash APN fix: http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/ 4. Boot into ROM, and reboot into recovery as soon as it boots up. 5. Reflash the ROM and gapps (but don't wipe anything this time).
That should get you up and running, with LTE and the APNs configured properly.
Thanks all for the help.
Been running the 7/3 build for a few days now without any problems. May flash the 7/7 ver 10 build very soon.
Powered_By_Linux
I tried the APN fix on a Kitkat ROM some time ago and did not help. Found 8SMS messenger with the added line fix and was able to get my MMS messages then. May try the APN fix in the order that you suggested and see if I can go back to the Handscent messenger. I like that app better the 8SMS but was not able to get MMS messages.
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.
elgecko said:
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.
Click to expand...
Click to collapse
Make a backup of AICP. Then you'll have to flash back to a TouchWiz ROM, update PRL, then flash the AICP backup you made. Your updated PRL will stick.
You can also use a PRL from the PRL thread.
http://forum.xda-developers.com/showthread.php?p=35576100
Flash a ROM like Wicked X or Tribute (you don't need your MSL). Download the PRL you want from the many listed in the thread, extract from zip, rename the PRL "TEST.prl" (without quotes), place on your internal SD, open your dialer and press ##DATA# to enter the hidden menu, tap View, scroll down to PRL Write, tap, and select. Your phone will reboot and you'll have yourself the PRL of your choosing.
Some people have good results from using these PRLs while others do not. Personally, I'm on Boost and have been running Sprint PRLs for years lol.
Hope this helps :thumbup:
EDIT......
NOTE- REMEMBER TO FACTORY RESET, WIPE CACHE, DALVIK CACHE, AND WIPE YOUR INTERNAL SD BEFORE RESTORING YOUR AICP BACKUP AFTER EITHER DOING A PRL UPDATE OR FLASHING THE ONE OF YOUR CHOOSING.
Sent from my SPH-L710 using Xparent Purple Tapatalk 2
Hello, this is my first, and most likely stupid post...
I rooted my Epic 4G last night (amazingly) but now when I try to follow numerous guides and discussions on how to update my OS (I have the last gingerbread version) which is the MAIN reason I wanted to root my telephone, it stubbornly (or more likely, I STUPIDLY do something wrong) and it refuses to flash or install any of the CM Mods that I see EVERYONE else is running just fine on their Epic 4G!
I've installed ROM toolkit which LOOKS like it should easily install whatever ZIP file I've DL'd onto my SD card. But in every case with different mods, it comes back with the same error when it tries to install, which is 'Cannot mount the SD card', but it is mounted and seen just fine and it is mostly empty.
I followed these steps with the exception of using the PC interface, instead trying ROM toolkit to flash it which is found here;
http://forum.xda-developers.com/showthread.php?t=2540250&page=77
But, I get the same error when it goes to install. I MUST be doing something wrong. I am really VERY much a newbie, but unless I need to go about this differently, I am REALLY stumped after trying and reading for many hours now.
I would sure appreciate a nice, SIMPLE way hopefully to upgrade my OS from Gingerbread to whatever I can use (I see others saying they are running KitKat just fine!)
Thank you so much!
________________Latheofheaven
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Oh, hey, I am SO glad that you took the time to answer me, thank you!
See, I TOLD you guys that I am not really conversant with this. I figured that I was doing something wrong. I absolutely PROMISE that I have been reading about this and trying to figure it out for like 2 full days STRAIGHT!
Would you mind, please, terribly just listing the basic few things that I have to do? I REALLY am confused by this. Are you saying that I need to install clockworkmod first? What version will my Epic 4G take? All I have installed now that seems related to this is the ROM toolkit PRO and ROM Manager. When I DID try to use ROM Toolkit to install this Rom, I got a long prompt how I didn't HAVE Clockworkmod, but I thought that it came with one of the others, I guess.
Could you PLEASE list precisely what I need to do? Could you kindly list the links for ANY pre-rooted ROM that you would recommend, or ones that work on my Epic 4G? Once I understand the steps, then I probably will know what to do if I want to try others, but I am kind of stumped as to exactly what to do now. I didn't even KNOW that that was an Epic Touch ROM! I'm surprised that I was able to follow the steps just to root the dang thing!
Dude, if you wouldn't mind taking pity on me and show me what I need to do, that would be super nice. It SOUNDS from what you said that I need a version of clockworkmod and I just need the RIGHT Rom and just how to do it, I guess...
Thank you so much for your time and any help that you can give!
Ah, got Clockworkmod!
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Hey, I DID actually get a version of CWM. I installed ROM Manager and then it prompted me to 'update' CWM. Now, I had installed RM before and HAD tried to update CWM, BUT... it never allowed me to do that. However, THIS time, it DID! And now it continued and asked me if I wanted to flash CWM, and I said 'DO I?!!!' And it did. Now, I have a whole new option screen which I haven't looked at yet.
Soooooo, I'm kind of HOPING that now all that I will need is to be pointed toward a rooted ROM for my Epic 4G and just the steps how to do it.
I was TRYING to do this through ROM Toolbox Pro b4, but no go...
Thank you kindly again for whatever help you can give me!
Trying to get rooted ROM for Epic 4G...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Okay, I am now DLing this file:
cm-10.2-20131125-UNOFFICIAL-epicmtd.zip
Which from the page LOOKS like it is for my Epic 4G. I will TRY to see if I can transfer it to my telephone's SD card. Then, I will TRY to, what, 'Flash' it...? ... using CWM that I THINK is now on my telephone?
Anyway, I didn't want you to think I'm being a deadweight. I AM trying to figure this out
Thanks!
Tried, but no go...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Okay, the good news is that this time when I tried to install this package that I mentioned above, at least I didn't get the SAME error about not being able to mount the SD card, so that is SOME progress, I guess.
However, this time as it opened and tried to 'verify update package' it came back with an 'e-Signature verification failed'
Soooooo, did I indeed choose the WRONG ROM again...?
I will wait to hear from you when you have time.
Thank you kindly again!
Naaaa, I think I'm gonna frigg'n give up...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
sigh... well... I think I'm gonna give up. I DLed yet ANOTHER seemingly official rom FOR my device, it appears, from this site on this page:
http://download.cyanogenmod.org/?device=epicmtd&type=stable
The one at the top: cm-10.1.3.1-epicmtd.zip
It says 'STABLE', but it could not verify the signature again.
So, until SOMEONE has mercy on me and tells me what the hell I'm doing wrong, I guess I will give up.
Thanks anyway...
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
Thanks kindly. I saw that many others were having similar troubles.
I will give it a try. And THANK YOU for the link!
Cheers!
Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
My CWM is not Premium, so I don't think it has the option about signature verification. I did see on another thread that a fellow couldn't do it through ROM Manager because he kept getting the signature verification error. So, he was ultimately able to do it through Odin 1.85, which I have. The only thing is that the ROM is a Zip file and Odin will only flash Tar files because I've tried to do that before.
At least now I KNOW that I have a good link for the ROM itself, thank to you!
Now, all I have to do is figure out how to install it. I sure hope that I don't also have to buy ROM Manager Premium, because I just paid for ROM Toolbox Pro, which you would THINK would be powerful enough to do this, but I guess not...
Thanks though...
Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
Heh... I guess I haven't QUITE given up yet...
Anyway, I thought that you should know that through ROM Manager my telephone is NOT booting into CWM's boot recovery. When I choose to boot to CWM recovery it ONLY boots to the stock Android recovery showing a little Android figure with an error sign and then in yellow letters below it says 'Manual Mode'
That may also indicate that something else is wrong...
Got it!
FINALLY! ...after reading about MANY different approaches for other people with different issues, it occurred to me to try using Odin to 'Flash' the actual CWM recovery program since it never seemed to update or EVER back up to it no matter how many times I tried. FINALLY... by holding down the 3 buttons immediately after flashing CWM recovery, it FINALLY actually booted up into the CWM recovery mode! THEN... and only then could I properly install the CM11 version and it all went great!
Now, the only thing I'm trying to figure out is how the hell to sync my Google contacts to get them all back!!! :laugh:
latheofheaven said:
FINALLY! ...after reading about MANY different approaches for other people with different issues, it occurred to me to try using Odin to 'Flash' the actual CWM recovery program since it never seemed to update or EVER back up to it no matter how many times I tried. FINALLY... by holding down the 3 buttons immediately after flashing CWM recovery, it FINALLY actually booted up into the CWM recovery mode! THEN... and only then could I properly install the CM11 version and it all went great!
Now, the only thing I'm trying to figure out is how the hell to sync my Google contacts to get them all back!!! :laugh:
Click to expand...
Click to collapse
Ahhhh... I didn't have ANYTHING Google, and then I remembered from what I read that in just about every case where someone installed a ROM like this one, they also mentioned a GAPPS file! DUH!!!!
So, I'm going to try to find the right one.
Also, something really weird... the Play store says that I already have some apps installed like ROM Manager and ROM Toolbox and others, but darned if they DON'T show up in my apps on my telephone. I wonder where the hell they are...???!
Thanks!
latheofheaven said:
Ahhhh... I didn't have ANYTHING Google, and then I remembered from what I read that in just about every case where someone installed a ROM like this one, they also mentioned a GAPPS file! DUH!!!!
So, I'm going to try to find the right one.
Also, something really weird... the Play store says that I already have some apps installed like ROM Manager and ROM Toolbox and others, but darned if they DON'T show up in my apps on my telephone. I wonder where the hell they are...???!
Thanks!
Click to expand...
Click to collapse
I'm glad that you made it. Never give up on flashing. About playstore it shows, under all apps, ALL apps that has been installed using that account. It's been so long since I rooted my epic, like 4 years ago, that I don't remember how I did it. It's a really strong phone.
I personally prefer slimrom jellybean, with kitkat you will have few storage left and you will have to use app2sd.
ernest-sora said:
I'm glad that you made it. Never give up on flashing. About playstore it shows, under all apps, ALL apps that has been installed using that account. It's been so long since I rooted my epic, like 4 years ago, that I don't remember how I did it. It's a really strong phone.
I personally prefer slimrom jellybean, with kitkat you will have few storage left and you will have to use app2sd.
Click to expand...
Click to collapse
Yep, I've definitely already run into the storage thing. There is only like 500 Megs of internal storage. I already tried 'Move to SD card', but I'm not sure that is the same one. I really couldn't move that much to the SD card, at least from that app.
Basically, after installing the Google Keyboard (to get the voice-input for messages) I THINK I'm done for now
BTW, thanks for the suggestion about Slim Jellybean!
Thanks mate!