Database Users

Is my phone near death?

I've been flashing this thing left and right since November (when I got it, teehee). It's been through over 10 Odins and 100 custom rom/kernel flashes. Even so, Odin has never failed me, nor has the ROMs. But lately, my phone has been freezing non stop, I thought I flashed Syndicate Frozen wrong so I reflashed after wiping and it still froze. I changed the kernel prefixes to 1000/200 instead of 1000/100 to see if it's the 100 scale being stupid, but no dice. I decided to flash MidNIGHT rom to see if that would fix the problem and it worked fine, but now another problem arose. My recovery can't find internal or SD storage anymore...I fixed the problem before by booting the phone up, then going into settings > Privacy > factory reset (although that froze the phone and I had to manually pull the battery) but once I rebooted, all was good...but I Odined back to DI18, automatically updated to EC05, then ran the EXT 4 one click root and it was fine, then I flashed Syndicate 1.1 again, froze on me, restored my working version of midNIGHT rom, now it's giving me that internal storage problem again in recovery.
Is my phone about to die??? I took a picture of the recovery error with my brother's phone.

Those aren't big-deal errors - but I've seen them before when I flashed CWM3 and entered it early (I can't tell you exactly what I did). Just Odin again, flash CWM3, let it convert, and restore the backup. You should be fine. But no, your phone is fine.
And, see the SRF thread. The freeze fix has been posted many times.

Perhaps you should try something other than Syndicate for a while...maybe try an RFS based ROM. Sounds like all your problems start with flashing Syndicate.
Stock EC05 RFS with Genocide 0.5a kernel has been rock solid for me and unbelievable battery life.

I'll give it a try, thanks!

I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?

Tortel1210 said:
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Click to expand...
Click to collapse
It was Quick Boot app.

Overstew said:
It was Quick Boot app.
Click to expand...
Click to collapse
There's your issue.

k0nane said:
There's your issue.
Click to expand...
Click to collapse
Why would that be the issue? It makes that app obsolete then.

Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk

Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
MysteryEmotionz said:
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not only that, but something just doesn't set right when you do it - I can't tell you exactly what, but that's definitely the cause right there.

Had both of these same issues as well on SFR 1.1 and also thought my phone was in trouble. Quickboot caused problems in CWM3 and data corruptions, so had to wipe and reflash. Then, like a number of others, I started having the freezing problems on SFR. Unfortunately, hadn't made it through all the pages of issues in the thread (and freezing issue wasn't yet noted in 2nd post when I downloaded the rom), so ended having to do several battery pulls, which caused more data corruption that required wiping and formatting sd card. Since the posted fix is to flash a kernel that is said to break the camcorder, which I use, I decided to flash back to midnight and all is working again.
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.

mis3 said:
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
Click to expand...
Click to collapse
It is resolved. Search the thread. Use the posted kernel.

k0nane said:
It is resolved. Search the thread. Use the posted kernel.
Click to expand...
Click to collapse
I'd totally use that fix if my camera worked with it. :S

any kind of quick reset (quickboot or pulling battery with power on) is bad news on a non-journaled ROM.

Overstew said:
I'd totally use that fix if my camera worked with it. :S
Click to expand...
Click to collapse
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.

k0nane said:
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
Click to expand...
Click to collapse
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App

mis3 said:
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try the APK from EB13 before you say that.

I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App

jbadboy2007 said:
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
midNIGHT rom came with Quickboot.apk, so I assumed it's okay. I'll ditch it right away, though.

not meaning to hijack the thread butttt
is adb reboot acceptable to use on a non journal rom?

Is there a way to access Apps on a soft-bricked phone?

I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!

Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.

mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.

Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.

mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.

Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.

mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.

Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.

I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App

Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.

Cool glad you got her going.
Kaaameeehameeehaaaaaa!

Services crashing 2.3.5

So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?

reboot your phone every no and again, never hurts, also, Q&A.
This has happened to me every now and then, and reboot your phone every couple of days is good for it. Could also be you have flashed a different kernel over kernel and not cleaned stuff out.

LoL Yeah this probably belongs in Q&A but what was there at the time didn't seem to Developer-ish looking haha.
Anyways, yeah I've tried rebooting about 5times already. After every flash I reboot twice before really settling down to put stuff back in. That might have been the case when I was doing the MIUI ROMs but the NoFrills-AOSP ROM I have now was fresh from Stock Odin flash. Should I just try a new Kernel maybe?

also happening to me. i reboot once a day but still it occurs. btw im on MIUI

Over time I've noticed the same thing. Similar to a Linux memory leak... No matter what rom, radio or kernel I use the available ram dwindles to almost inoperable speed. A reboot on my Vibrant is almost daily depending on what I do with my phone. Even with CWM, Overstock and Zendroid all together I still have the same issue's, any viable fixes for this?
Sent from my SGH-T959 using XDA App

i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol

CharlieBoy808 said:
So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?
Click to expand...
Click to collapse
Stop restoring from titanium backup, and just reinstall your apps from scratch.
I had this same issue, found out it was my titanium backup app restores that were at fault.

Ya alot of people don't realize.. you can't use titanium with miui.. use the miui backup app.. if u come from a a different rom, Use titanium to restore, backup with the miui backup app, then reflash miui after wiping system, then restore using miui restore app.. everything should b alot better
Sent from my T959 using XDA Premium App

CharlieBoy808 said:
i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol
Click to expand...
Click to collapse
Stock is 2.2
Sent from my T959 using XDA Premium App

i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps

ceoesquad said:
i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps
Click to expand...
Click to collapse
Well you've just gotten lucky
Sent from my T959 using XDA Premium App

TI backup is not necessarily the issue with this. I've had the same problem for the last few week, and I've been using the MIUI backup exclusively. I might've used TI the first time I restored, but every other time it's been MIUI, mostly because it's WAY better.

Hmm ok well maybe the stock Odin I have is 2.1 because that's what it said in the about phone section. Anyways, TI causing a problem? or not causing a problem.. hmm LoL Oh how I love technology conflicts. Well right now I'm sitting on Simply Honey RC1 and so far no crashes yet. I went from Stock to Light then to Simply Honey as instructed. I did restore using TI, but I might flash back to MIUI from Stock and give it another try.

check your datadata partition and see if it's full. since miui is based off cm7, i'm assuming it uses the same partition scheme. if datadata is full, that may be your problem.

No CM9 Roms work for me

Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks

Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Make sure the kernel you using supports cm

Dasanko said:
Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)
Click to expand...
Click to collapse
Alright downloading now, hopefully this will work.
Edit:
Didn't work for me, I never saw a boot logo/animation.
fanaticprakash said:
Make sure the kernel you using supports cm
Click to expand...
Click to collapse
What kernel do you recommend?

I actually have the same problem. This CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"

I've been having the same problem for two weeks now, if anyone can solve this I would really appreciate it
Sent from my Kindle Fire using XDA

kwheel596 said:
I actually have the same problem. That unofficial CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"
Click to expand...
Click to collapse
I actually had it load completely after verifying apps, but once I rebooted it always froze at the boot animation.

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk

Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.

erikikaz said:
Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.
Click to expand...
Click to collapse
This doesn't work either :/
Sent from my PC36100 using xda premium

I have the same problem too, all the ics roms do not work except for the one stated in this thread previously and the Hellfire ics rom.
It gets stuck at the boot screen.. I have tried wiping everything including sdcard..
And also, my kindle hangs frequently when running 3d games and I have to hold the power button to force shutdown it..
Is it a problem with the kernel?
The notifications button at the bottom right corner is also very unresponsive, I have to press it several times to open the menu..

ammubarak said:
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.

how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.

Raiden619 said:
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.
Click to expand...
Click to collapse
man thats so strange... cwm or twrp? when you flash it dose it flash really fast

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
Its not that I'm not waiting long enough for the boot animation or anything. For example it will load up some the first time and get all the way past the spinning circle on the CM9 boot animation and get stuck on the "verifying apps" screen. Other times that i try to boot it it will get stuck with just the little android and the circle around him, not even 2 full seconds into the boot animation.

The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk

sej11 said:
The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Nice first post!
All signs are pointing to a ****ty wipe. The recovery's fault, so long as you didn't forget to wipe everything under mounts.

erikikaz said:
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.
Click to expand...
Click to collapse
i have switched over from twrp to cwm.. waited for at least 15 mins, but its still stuck at the bootscreen..

Pretty sure this would help alot of people, can someone try and solve this?
Sent from my Amazon Kindle Fire using xda premium

Got rooted, installed custom recovery, lost root, now i'm confused...

So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks

Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent

ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.

Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent

Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.

iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent

ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.

Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta

daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.

iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.

iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?

ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?

iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.

ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.