hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
Related
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.
Posting here since I cannot yet post to the actual ROM forum.
I'm running the Synergy ROM, RC1 and have a couple of issues. First though, thanks to the DEVs for all of their time and efforts, this looks to be a very good ROM!
I've been through most of the 200+ pages on the ROM's thread and did not see any information that may help (except turning off auto rotate of the home screen), but it's possible I missed.
The main issues I have are slow response issues. They are:
Slow response when I pull down the navigation bar.
Slow response when hitting one of the soft buttons (i.e., the + button to launch the app specified by the settings in Rosie).
Very slow response when I come out of a game that was in landscape mode. It takes a couple of seconds for the screen to switch from landscape back to portrait (after flipping the phone to portrait) and then another few seconds for it to put all the icons back on the home screen (home screen is blank when I come out of the game). I did turn auto rotate off and that has helped, but was wondering why there was such slow response without it.
Google apps such as Maps and Calendar that are started by another application, but do not shut down the starting app exists. This, of course, drains the battery and was not an issue on the stock rom.
When I flashed the rom, I did do a factory reset and erased all other caches. My apps and app data (not system data) were restored via TB.
I have also frozen the following apps via TB:
Flash
All live wall paper apps
Stocks
Flickr
FM Radio
News
Stocks
Smoke & Visualization Wallpapers
Voice Dialer
Voice Search
Thanks!
Mike
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
My thought was that when restoring an app, such as WSOP Texas Hold'em, I also wanted to restore the data so it restored games won, amount of money, etc.
Is that data what you are saying I should lose when flashing new roms?
Thanks,
Mike
0soPolar said:
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
Click to expand...
Click to collapse
Quite a few of my apps are on the SD card. I have 313MB free on the internal storage. Should that be enough to reduce some of the lag.
Thanks!
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Give the phone a minute. It will let you move it. I just keep hitting volume down. It will work.
Sent from my ADR6300 using XDA App
dysfunkshun said:
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Click to expand...
Click to collapse
If you can boot into recovery, you did not brick your phone.
I've had this problem before and I don't even use Titanium. I also had plenty of free space on internal. Ram never seems to free up though. It's the strangest thing.
Sent from my ADR6300 using XDA App
Does anyone else have issues with anything that requires data syncing (Facebook, Twitter, SMS, etc) stopping unexpectedly? It seems to happen at around 30% battery and the only way I've consistantly stopped the problem is to wipe and reflash Synergy Rom.
Any ideas?
Yea Idk what's going on with it after about an hour I would get android.process has stopped and needs to force close. I can't even use any app as that constantly pops up. Great ROM but unusable at this point.
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
jlokos said:
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
Click to expand...
Click to collapse
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Edit: I've also noticed that the GPS is locked on and I cannot shut it off.
Chindogg said:
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Click to expand...
Click to collapse
Yea I also did a full wipe two different times. I didn't notice it happening once the battery gets to a point I just know that after an hour or so of use it was unusable.
1. If you use DualRomX2 would that possibly speed it up? Because doesnt it install Roms on EMMC?
2. Im also really frustrated by the slow response on alot of things like right rosie button and notification pulldown.
3. Video recording for me is just awful. Im not sure about actual quality but the framerate for sure is horrible. I compared a video i shot on stock and with Synergy and there is a HUGE difference. Synergy video being much worse.
Great Rom just plenty of little annoyances.
Synergy ROM loading issue
Flashed Synergy ROM last week and was very impressed. However, saw where 3.0 Sense items were missing and realized after reading several other posts that the carousel +widgets.zip should have been loaded with the ROM. So I reloaded the ROM and widgets through AMON-RA Recovery (Followed all of the original instructions I had followed the first time I loaded the ROM). Everything looked fine until I rebooted the system. Now Synergy ROM start-up screen loops over and over. At this rate the fill battery I started with will run out, and I'm not sure what will happen at that point.
Anyone have any suggestions for this issue? Any help would be appreciated. Thanks.
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Yeah I don't have too many issues with it... last night it got kinda squirrely so I fixed permissions in recovery and re-flashed the Warm Theme without wiping any data, it's been all good ever since.
The ROM is my daily driver... I really do think that these issues are app-related. There is something that certain apps do that this ROM is not built for, I'm just not sure what it is. It's been real good to me overall though, battery life and all.
SlimSnoopOS said:
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Click to expand...
Click to collapse
SlimSnoopOS, as it turned out I pulled the battery and rebooted into Recovery after a few hours, but thanks for the direction. These were the exact things I did. The reason I used AMON-RA instead of CWM is that Synergy says in a number of places that it only loads with AMON-Ra (and I'm a coward!),
Awesome, glad everything is functional again!
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?
I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.
Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.
All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?
So the other day i go put on a new rom and boot into TWRP to wipe and install. so i do my normal thing (wipe data/system/cache then install rom and gapps then wipe cache again. then reboot. i let it do its 10 min thing. then start to use the phone again. same problem as before (launcher constantly crashing) so i do my wipe and install again. this time i notice i have significantly less room on my data partition. so i go and do another wipe and install to check. this time even less space. i do it a couple more times to see if maybe it will fill up the space and then maybe completely wipe everything. no such luck. no my phone is basically useless with no way to install an OS or boot into the current one. any help on actually doing a real full wipe so that i have room again? i prepared to use odin or whatever i need to do to revert back to full stock then start all over again with the root process just to refresh my skills and get everything brand new again.
please any info would be great since id like to have a working phone again (pulled out the old iphone 4 in the mean time)
thanks guys!
Did you try a full system wipe using Infamous or Dark side to begin with? Try that first before doing anything else and see what happens.
mlbinseattle said:
Did you try a full system wipe using Infamous or Dark side to begin with? Try that first before doing anything else and see what happens.
Click to expand...
Click to collapse
ok ill try that out and let you know
update: seems to have worked have a new rom installed. hopefully it keeps running without a hitch. thank you very much. i wish i had known twrp had a crappy delete function and that it could be cast aside in favor of darkside or infamous.
olyvaha said:
ok ill try that out and let you know
update: seems to have worked have a new rom installed. hopefully it keeps running without a hitch. thank you very much. i wish i had known twrp had a crappy delete function and that it could be cast aside in favor of darkside or infamous.
Click to expand...
Click to collapse
TWRP has a Dalvik cache wipe which, IMO, is basically a factory reset. There may be more to it than I'm aware of. I'm not a dev, so I really can't say one way or another. Infamous and Darkside both have the full wipe which does everything. Anytime I flash a new ROM, I'll run Infamous followed by the TWRP wipe. Haven't had a problem, yet.
Glad it all worked out for you. I know what it's like to be in a situation like that. Been there, myself, a couple of times.