Issue with booting on 4.3 - Sprint Samsung Galaxy S III

Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!

your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.

Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!

bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?

thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away

Related

[Q] Calkulin's Rom won't allow recovery..

So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..
I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck
If you got it off here, could you show me which stock you flashed..?
Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.
Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.
Recovery and market are now working Thank you Adanorm!
Glad your back up and running

[Q] ROMs Failing, Start Fresh?

Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
From what it sounds, it could be a bootloader problem. Did you ever update to 4.1.2? All 4.3 ROMs require at least the 4.1.2 bootloader, which you can get without Odin'ing 4.1.2 from here:
http://forum.xda-developers.com/showthread.php?t=2321310
As always read, read and read. If this doesn't help, I recommend maybe trying out CWM (I'd restore back to your TouchWiz backup since that backups from TWRP and CWM aren't compatible.) If that still doesn't help, then by all means, Odin to stock, OTA to 4.1.2, root and go on. As always, this is just information from one member to another, so I am in no way, shape or form responsible for anything and everything that could go wrong.
The 4.1.2 ota update just came out today so no. I'll try that in the morning thanks!
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
Fail immediately? As in you're able to flash them but can't boot properly or you have glitches?
Sounds like a hardware issue to me. Hope you got warranty.
I click install, select the zip and it starts working for a couple seconds and fails.
Just updated the bootloader and ProBAM and Goodness failed. Tried Beanstalk and it completed fine. Gonna try it out for a bit. It is 4.3 so not sure what the issue it with the other ROMs yet
Beanstalk is up and running. Thanks drx!!
edit
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Who Am I? said:
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Click to expand...
Click to collapse
Try Task650's rom. It's the most stable and smooth I've used. Also, he has good instructions on what bootloader to use.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Moved to internal and flashed fine. Rebooting now.
Spent most of yesterday on AirDroid moving files back to my external. Came back and it looks like it killed the battery. Plugged in, rebooted and now my ext sd card wont show up. I bought a 64GB Samsung microcard off Ebay. Formatted on the phone and started tranferring files fine. Was going slow but working. Really dont want to format and start over but the phone wont even see it so I cant format it from the phone.

Problem with Flashing Almost Everything!

I am posting this as a new topic because I don't have enough posts to post my concern in the thread of the ROM I use.
I have been using PATB ROM for a while now without any issues. Since updating to the newest version I have run into severe issues trying to flash anything besides doing Restores. Every time I try to flash something new it fails immediately and this includes trying to flash a new recovery. I did some reading and thought I had found the answer in restoring the system to stock firmware via Odin. However after trying this a short while ago the process failed as well as soon as Odin showed Recovery in the process bar. This screwed my phone pretty bad, but I was able to Odin a new Recovery on to the phone which seems to have taken it back to functioning normally. I am still unable to flash anything and the only stuff I can do inside Odin is to put different Recovery zips on the device. But even after doing that I am unable to flash anything, and it jumps to Failed right away.
I am not much more then slightly experienced when it comes to rooting and flashing but I have never come across anything like this before. I was using Xposed Framework and I unistalled it because I thought it might be causing the issue. But still no luck. This is driving me crazy. Any help with this would be greatly appreciated because I would like to try out some new ROMs. By the way my flash count reads as only 4 when taken into download mode even though I am pretty sure I have flashed more then that; unless it only trips when completely changing ROMs which would make it a correct count. So I am hoping somebody out there has seen this before and knows how to help me get past this. Thanks to those who are able to help.
Have you tried flashing the full MK4 firmware? IIRC you can't go backwards. Try this out: http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Use Odin 3.07. If it fails go with 3.09. Please let me know if it works or not. Your partitions may be corrupt but that's a LONG shot. Let's just stick with you're trying to downgrade and the bootloader isn't letting you
Sent from my SPH-L900 using xda app-developers app
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
dragonrider6218 said:
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
Click to expand...
Click to collapse
If you decide to go to MK4 be sure to install Philz Cwm Recovery or your problems will start all over again

[Q] Various problems with phone. Completely restore phone?

As of recent, I've been having a ton of stability problems on my S2 across all ROMs. It will often get sluggish and randomly shut down, the WiFi will completely drop and I won't be able to connect unless I restart my entire phone, and various other problems. I've done a full wipe when installing any ROM and problems only came up when I installed cwm 6.0.4.3 and I was wondering if that may have been the issue. Either way, I was wondering if there was a way to completely wipe my phone and bring it all the way back to factory and how it came in the box so I can completely start over to try to fix these problems. Any other suggests would be greatly appreciated, too.
Currently running BeanStalk 4.4+, last "stable" build was with Cyanogenmod 10.1 nightly.
Thank you to everyone in the XDA Developer community, you certainly are amazing and thank you to the developers of the search function, I may not know how to use it to it's greatest potential but it's certainly helped me a TON. This is the first time I've felt I've actually need to make a post for something going wrong, sorry if the problem has happened in the past and I missed a post.
Dude i had a similar problem a while back switching from TWRP to CWM. Somehow I corrupted my Dalvik partition. I couldn't even get back to recovery.
So I went here. Followed the instructions and completely went back to stock.
Quick Note that I don't see mentioned enough, YOU WILL LOSE YOUR APPS AND SETTINGS, (hopefully thy're all backed up with Titanium), BUT YOU WILL NOT LOSE YOUR STUFF ON YOUR INTERNAL OR EXTERNAL SD CARDS. The first time I went back to Stock I was scared s***less because I thought I was losing all my pics.
When I booted up the first time, I got the "repairing" Android Icon, it rebooted and I was back in business.
Then I had previously grabbed the TWRP odin flashable 2.5.0.0. tar file from over here. I got 2.5.0.0 because I planned to flash a 4.2.2 ROM after all is said and done. I flashed that with Odin from Download Mode.
I didn't even bother logging into Google on the stock 4.1.2 ( I just can't go back TouchWiz after Cyanogenmod). I just rebooted right into TWRP 2.5.0.0 manually with Volume up and Power button.
From there I factory wiped everything, then superwiped and cachewiped ( both can be found http://forum.xda-developers.com/showthread.php?t=2235141), just to be on the paranoid side.
And finally I flashed Cl3Kener's latest 4.2.2 version of his BlackLiquid and his latest 4.2.2 stable Uber Kernel. I personally think this is the most stable, and as close to perfect ROM thats going to come out for this phone. Of course that is just my opinion after my own experiences with 4.3, 4.3.1, and 4.4.
This is a completely streamlined version of the complete cluster f** I did researching, trial and error, and starting over, while I was in the middle of actually doing it. One last tip I can give, is to get all the files you think you might possibly need and put then on your external SD if you got it, or internal SD. Its a real pain stopping and starting cause your missing a zip you forgot.
Hope this helps
Huge thanks to the Developers threads I Linked to.

[Q] Crashing apps and loss of service?!

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!

Categories

Resources