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.
Related
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
internetpilot said:
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
Click to expand...
Click to collapse
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.
That's what I recall from when I still had stock about 9 months ago...
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.
Sent from my buttered S3
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
internetpilot said:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
Click to expand...
Click to collapse
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there.
Click to expand...
Click to collapse
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
internetpilot said:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
Click to expand...
Click to collapse
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
Click to expand...
Click to collapse
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
internetpilot said:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
Click to expand...
Click to collapse
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
flastnoles11 said:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
Click to expand...
Click to collapse
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
internetpilot said:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
Click to expand...
Click to collapse
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
flastnoles11 said:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
Click to expand...
Click to collapse
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).
In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.
Sent from the future via Tapatalk 4
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
internetpilot said:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
Click to expand...
Click to collapse
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
edfunkycold said:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
deutscher3891 said:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
Click to expand...
Click to collapse
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
internetpilot said:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
Click to expand...
Click to collapse
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
deutscher3891 said:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Both directly from Sprint.
lvpre said:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
Click to expand...
Click to collapse
The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.
Hi,
this is my first post and I'm very sorry if it's a repeat, but I've searched all over and cannot seem to find anyone with my issue (which I find very hard to believe).
I'm trying to install a custom recovery (which I've done successfully before) using Odin. trying to use Philz Touch, cause it looks awesome, but now, I'm just trying to get anything to work.
The issue is I CANNOT format my /data partition. every time I try, it crashes. I have NO idea why. it can format anything else, I can mount/unmount /data, I just can't format it. cwm freezes and quickly crashes.
The particularly annoying thing is that this happened the last time I installed CWM too, but updating to the most recent version solved that. This time, I'm trying for the most recent version right away and nothing's happening. ALSO, today, I installed PhilzTouch and it WORKED!! so I installed my custom rom (Carbon) and went to reboot. This got stuck at the boot screen, and never loaded, so I booted back into recovery and whadayaknow, I can no longer format /data.......... I have no idea what is going on. I've followed all the instructions to the letter.
I'm on d2spr (sprint galaxy s3), trying to install cwm 6.0.4.5 (or philz 6.15.4) so that I can install CarbonROM v1.8 (which I also cannot get to work. I've happily been on SlimBEAN and then SlimKat for a while and wanted to try Carbon for the extra features).
Any help would be GREATLY appreciated. (also, I can't restore a backup because that includes writing to /data, which I can't do. I can get halfway through the backup so that I end up with a clean slimKat (which I don't really want, cause I have a lot of data), but that's it. CWM reboots the second it tries to write /data.
EDIT: This issue happens when I try to flash CarbonRom, but goes away if I flash something like CM or SlimBean. Once one of those roms is installed AND BOOTED, I can touch /data again, but once I try to get CarbonRom running, I can't. So it seems it's an issue with CarbonROM specifically. Any advice?
Update: It's only Carbon Rom
Hey, so apparently, I can flash literally every other ROM I've tried (cyanogen, slimbean, slimkat, beanstalk) and they all work fine, but when I flash Carbon (the release version, v1.8), I get to the "Samsung Galaxy S3" screen with the "C" logo and it hangs indefinitely. When I give up and pull the battery, the /data partition is untouchable like before, but that now seems like a symptom, not the problem, because it only happens with Carbon and it's fixed by flashing another rom and letting it boot. And yes, I've given it quite a long time to boot, but it never even gets to a legitimate boot screen (with some sort of moving animation). It just freezes and and never unfreezes.
Anyone, any help would be really appreciated. It's VERY frustrating....
pianoman1645 said:
Hey, so apparently, I can flash literally every other ROM I've tried (cyanogen, slimbean, slimkat, beanstalk) and they all work fine, but when I flash Carbon (the release version, v1.8), I get to the "Samsung Galaxy S3" screen with the "C" logo and it hangs indefinitely. When I give up and pull the battery, the /data partition is untouchable like before, but that now seems like a symptom, not the problem, because it only happens with Carbon and it's fixed by flashing another rom and letting it boot. And yes, I've given it quite a long time to boot, but it never even gets to a legitimate boot screen (with some sort of moving animation). It just freezes and and never unfreezes.
Anyone, any help would be really appreciated. It's VERY frustrating....
Click to expand...
Click to collapse
Just FYI, that version of Carbon is really old, you will probably want something more current like their KitKat builds or at least the 4.3.1 builds from November. Sounds like you are probably flashing 4.4 GApps, which would be a mismatch for the version of the ROM you are flashing, which is why things are hanging for you. Also, if you are using Philz Touch (highly recommended!), then the only wipe you need is "Clean to Install New ROM" and nothing more.
Mr. Struck said:
Just FYI, that version of Carbon is really old, you will probably want something more current like their KitKat builds or at least the 4.3.1 builds from November. Sounds like you are probably flashing 4.4 GApps, which would be a mismatch for the version of the ROM you are flashing, which is why things are hanging for you. Also, if you are using Philz Touch (highly recommended!), then the only wipe you need is "Clean to Install New ROM" and nothing more.
Click to expand...
Click to collapse
Thanks for the reply!
Actually, I want flashing any gapps at all specifically so that it didn't conflict. Should have mentioned that.
Also, I was under the impression that 1.8 was a 4,3 build, but if that's not true, I'd certainly want a later build. However, I'm looking for a stable room with lots of features, so I was only looking at release builds.... And 1.8 is the only release build for d2spr. Any suggestions on which later build is the most complete/stable?
And yes, I'm using philz touch. Latest version.
pianoman1645 said:
Thanks for the reply!
Actually, I want flashing any gapps at all specifically so that it didn't conflict. Should have mentioned that.
Also, I was under the impression that 1.8 was a 4,3 build, but if that's not true, I'd certainly want a later build. However, I'm looking for a stable room with lots of features, so I was only looking at release builds.... And 1.8 is the only release build for d2spr. Any suggestions on which later build is the most complete/stable?
And yes, I'm using philz touch. Latest version.
Click to expand...
Click to collapse
So Carbon never released a stable version of 4.3, just nightlies. It is hard to tell from how they restructured their downloads page, however, it is one of those things you would only know from following their progress since last fall. As far as stable, that is almost subjective, a lot of the newest nightlies are really good. I would recommend one of the Snapshots from CM11 or any Carbon nightly from 2/18 or earlier (2/4 was really nice) if you want something that should work well. As always, YMMV.
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!
Okay this is really getting on my nerves and I've never had this much problem from a phone. I've been modding and helping develop for years, but I've never had this issue. So for five days now, I've been playing around with my old DINC that my daughter messed up somehow, and I can't install a ROM and make it work to save my life. I've run countless ROM's on this thing in the past with no issues. The problem now is, no matter what recovery I use or what I wipe, all of the old apps keep showing up on boot and crashes the phone. Meaning while it says "Android is upgrading" it shows every app that has ever been installed on this phone, even though I wipe and format every partition, and I haven't installed a single app. Heck... I can't even get into the system to install an app. The furthest I've gotten on a clean install is to pick a launcher in Carbon, but then it reboots.
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
ludeawakening said:
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
Click to expand...
Click to collapse
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
BrettApple said:
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
Click to expand...
Click to collapse
I've tried every recovery you can think of for this device. All versions of the CWM and TWRP touch and non-touch, including CWM 5.0.2.0. And I use HBOOT to flash all of the recoveries. It doesn't matter what ROM or recovery I flash, I still get the same results. And the ROM I used the most on this phone was Condemned CM7.2, but like I said, it won't matter how stable a ROM is, I can't get it to boot to even use it now. For some reason there is a partition somewhere that will not wipe. I've used VR Superwipe, which was recommended on some ROM's in the past, but it doesn't help at all either. No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot. All of the apps crash even if I go back completely stock by flashing a PB31IMG of stock firmware with HBOOT. That includes trying it with S-ON and S-OFF. As you can tell, this isn't my first rodeo at all. Lol
I've been doing this for years and have helped develop ROM's on a couple of sites, but I've never seen or heard of anything like this. Thanks for the input though.
I guess I'll risk completely bricking it, and manually re-partition the device and push the bootloader and everything else to it with ADB Shell. I've got nothing to lose, it's already a paperweight that just lights up. Haha
ludeawakening said:
No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot.
Click to expand...
Click to collapse
Sounds like a bad NAND to me (like one partition is fried and is now read-only). Good luck with the repartitioning. If you're feeling adventurous, you could try this. If you're feeling really adventurous, I seem to remember reading a post from someone who had actually unsoldered the NAND chip and got the phone to boot using only an sdcard. I can't find the post right now though.
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!