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?

Issue formatting data under clockwork mod

Folks,
I've been running the ICS Kang project build without any issues (2.3) for the past while. Last night the tablet locked up on me and I powered it off by holding down the on/off button. When I went to turn it back on it now permanently hangs during boot. I can still get into CWM but attempting to wipe either the D. Cache or data hangs. Anyone got any ideas?

Can you restore a backup?
If you can't do anything in CWM then you might have to Odin back to stock....

I can flash a new rom but there appears to be something wrong with the data partition - can't wipe it and tablet wont boot.
You don't happen to have a link to restoring tab via ODIN? I was just browsing for that...

powercrazy said:
I can flash a new rom but there appears to be something wrong with the data partition - can't wipe it and tablet wont boot.
You don't happen to have a link to restoring tab via ODIN? I was just browsing for that...
Click to expand...
Click to collapse
http://www.teamovercome.net/p7500/?page_id=5
Scroll down to where is says Re-Stocking Yer System and follow the instructions.. Make sure you choose the correct download (7500 or 7510)

Thanks - I'll let you know what happens.
Its bizarre, flashed roms lots of times, never had an issue even close to this...

powercrazy said:
Thanks - I'll let you know what happens.
Its bizarre, flashed roms lots of times, never had an issue even close to this...
Click to expand...
Click to collapse
No problem... It should go nice and smooth and once it boots back up check in settings for system updates..

Well, thanks! That did the trick! I am back to the stock Samsung firmware and have already reflashed clockwork. I really don't know what went wrong in the first place, but I suppose that's what you get for living on the 'alpha' edge...
Thanks again! (BTW I did click the 'thanks' button ;-) )

BTW - for anyone interested or suffering a similar problem, in the end this required a full reset - all data was lost which sucked for me as I had all my backups on the device too (don't bother calling me stupid, I've already done it)....
I'm guessing some bug in the ICS KANG alpha screwed the partitions up which nothing short of a full reset could fix...

Sweet! Glad you are back up and rockin'...

phew!
I had exactly the same problem yesterday, and I thought my tab was completely fubar until I came across this post.
I was running the "official unofficial" CM9 snapshot for p4wifi, and before that I ran AOPK build 27, I think. I did not perform a full wipe before going to CM9.
I change roms on my tab very often to try to find the best, so something must have gotten messed up, but it's somewhat odd since it worked in the morning, and then when I came to work it had totally b0rked up on me.
Anyway, this post was a life saver although I lost all my data (didn't keep a titanium backup or a CWM backup on another storage than the internal storage. shame on me).
So - thanks alot raqball!
Br,
primpa

primpa said:
I had exactly the same problem yesterday, and I thought my tab was completely fubar until I came across this post.
I was running the "official unofficial" CM9 snapshot for p4wifi, and before that I ran AOPK build 27, I think. I did not perform a full wipe before going to CM9.
I change roms on my tab very often to try to find the best, so something must have gotten messed up, but it's somewhat odd since it worked in the morning, and then when I came to work it had totally b0rked up on me.
Anyway, this post was a life saver although I lost all my data (didn't keep a titanium backup or a CWM backup on another storage than the internal storage. shame on me).
So - thanks alot raqball!
Br,
primpa
Click to expand...
Click to collapse
Never understood why people don't do a full wipe and expect nothing to go wrong.
Sent from my GT-P7510 using XDA Premium HD app

Hehe, well, I usually do a wipe but this time I read somewhere that you probably didn't need to when going from aokp to cm9, since they are pretty much the same.
But..... Lesson learned
/primpa

primpa said:
Hehe, well, I usually do a wipe but this time I read somewhere that you probably didn't need to when going from aokp to cm9, since they are pretty much the same.
But..... Lesson learned
/primpa
Click to expand...
Click to collapse
Understandable... but unless the Dev. says no wipe needed, I would always suggest it, even when it's virtually the same ROM, thread, Dev., etc...
At least it wasn't too hard of a lesson.
Sent from my GT-P7510 using XDA Premium HD app

Weird issues after kitkat upgrade

Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?

y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.

Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.

y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?

If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk

Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.

Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?

After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???

Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.

Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.

radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?

Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse

crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it

GPS fix for Cyanogenmod & other custom roms

I know that I faced problems with the gps functionality when I flashed cyanogen11 for the first time. The GPS would not work, at all. No satellite lock, no google maps, nothing! Here are some steps I took to get my gps working again. And now it's at 100%
1. Try gps fixing apps from the play store. GPSfix, etc. These will load your phone with data, and erase the gps data your phone already has.
If this doesn't work, (which it did NOT for me, try this)
2. This part really sucks, you have to reflash stock kitkat 4.4.2 to your razr, and then from there, enable high accuracy mode in the gps. MAKE SURE IT IS ENABLED. Then from here, use fastboot to load it back into bootloader mode, and then reflash your recovery, and your mod of choice. This should fix the gps. Mine works great now. Hope this helped!:laugh:

Will my bootloader still be unlocked if I reflash stock kitkat? And I have to use RSD Lite correct?

brando9 said:
Will my bootloader still be unlocked if I reflash stock kitkat? And I have to use RSD Lite correct?
Click to expand...
Click to collapse
You're bootloader will never re-lock. Once unlocked you can not go back. And yes, use RSD Lite to restore the factory firmware.

PrankCallPimp said:
2. This part really sucks, you have to reflash stock kitkat 4.4.2 to your razr, and then from there, enable high accuracy mode in the gps. MAKE SURE IT IS ENABLED. Then from here, use fastboot to load it back into bootloader mode, and then reflash your recovery, and your mod of choice. This should fix the gps. Mine works great now. Hope this helped!:laugh:
Click to expand...
Click to collapse
This worked for me. Thank you.

I've been searching for a couple hours for a fix to this problem on my Razr HD (xt926). I figure this will work for me, but I have one question. Would I have to do a fresh installation of my custom ROM, or could I restore a nandroid?

pieareround said:
I've been searching for a couple hours for a fix to this problem on my Razr HD (xt926). I figure this will work for me, but I have one question. Would I have to do a fresh installation of my custom ROM, or could I restore a nandroid?
Click to expand...
Click to collapse
I would think you could restore from a nandroid just save it to an sd ( if your phone supports them ).

wendorf12213 said:
I would think you could restore from a nandroid just save it to an sd ( if your phone supports them ).
Click to expand...
Click to collapse
Thanks. My phone does have an external SD, so I'm going to try it and find out. Can't hurt, right?
EDIT: I tried it and everything worked out just fine. The only slight hitch was that I lost all my photos, because I forgot to move them to my external SD. That was easily fixed thanks to Google+ auto backup, though. Definitely worth it to be able to use navigation again.

pieareround said:
Thanks. My phone does have an external SD, so I'm going to try it and find out. Can't hurt, right?
Click to expand...
Click to collapse
let me know if i works ive slipped out of the habit of making backups due to having very little storage built in.

wendorf12213 said:
let me know if i works ive slipped out of the habit of making backups due to having very little storage built in.
Click to expand...
Click to collapse
You must've posted right before I finished my edit. This worked for me. I saved a backup to my external SD card, then followed option 2 in the op, then restored my backup. I now have working GPS.
From your post, it sounds like you may not have an external SD card, so you'd want to transfer your backup to your computer before reflashing the stock ROM, otherwise you would wipe your backup. I'd also recommend transferring your pictures and other media you want to hold onto, just to save some headache on that front.

pieareround said:
You must've posted right before I finished my edit. This worked for me. I saved a backup to my external SD card, then followed option 2 in the op, then restored my backup. I now have working GPS.
From your post, it sounds like you may not have an external SD card, so you'd want to transfer your backup to your computer before reflashing the stock ROM, otherwise you would wipe your backup. I'd also recommend transferring your pictures and other media you want to hold onto, just to save some headache on that front.
Click to expand...
Click to collapse
i do have an external sd card but i didnt know i could do backups straight to it until earlier today but im glad everything worked out for you.

PrankCallPimp said:
2. This part really sucks, you have to reflash stock kitkat 4.4.2 to your razr, and then from there, enable high accuracy mode in the gps. MAKE SURE IT IS ENABLED. Then from here, use fastboot to load it back into bootloader mode, and then reflash your recovery, and your mod of choice. This should fix the gps. Mine works great now. Hope this helped!:laugh:
Click to expand...
Click to collapse
From what I gather, this is probably the only fix for most people. KKBL roms cannot 'unlock' the GPS, and a fresh RSD load of KK locks it by default when you boot up for the first time. Apparently, the very same issue was resolved for JB a very long time ago. Currently, the best workaround is to use the GPS from within the stock ROM before flashing a custom recovery/ROM image. This unlocks the GPS, and the unlocked status will persist through subsequent flashes and reboots.

radiopayola said:
From what I gather, this is probably the only fix for most people. KKBL roms cannot 'unlock' the GPS, and a fresh RSD load of KK locks it by default when you boot up for the first time. Apparently, the very same issue was resolved for JB a very long time ago. Currently, the best workaround is to use the GPS from within the stock ROM before flashing a custom recovery/ROM image. This unlocks the GPS, and the unlocked status will persist through subsequent flashes and reboots.
Click to expand...
Click to collapse
Same here: GPS was broken since I've installed CM11 over the stock KitKat. I've tried to wipe everything and reflash the ROM, updated to the latest CM11 nighties, used GPS fix apps from the play store: nothing worked. Today I made a backup whit TWRP and I rolled back to stock KK using RSD: as stated early in this thread the GPS is OFF by default. I activated it, setted it in high precision mode, waited for it to lock my position and spent 10 minutes driving around to be sure that it worked fine. After this I reflashed the recovery and restored the CM11 backup: everything works fine now!

j27h said:
I activated it, setted it in high precision mode, waited for it to lock my position and spent 10 minutes driving around to be sure that it worked fine.
Click to expand...
Click to collapse
I have no doubt this would get it done, but the safest bet is to put it in "device only" mode before loading up maps. The split second you get a location lock in 'device only' mode, you' know your gps radio is working and are ready to reboot and flash whatever you want. High Accuracy mode mixes in wifi positioning, so it's more difficult to know that you have a gps signal without driving around..

radiopayola said:
I have no doubt this would get it done, but the safest bet is to put it in "device only" mode before loading up maps. The split second you get a location lock in 'device only' mode, you' know your gps radio is working and are ready to reboot and flash whatever you want. High Accuracy mode mixes in wifi positioning, so it's more difficult to know that you have a gps signal without driving around..
Click to expand...
Click to collapse
You're right, it's much better to put it in "device only" mode! Thanks for pointing it out!

Weird STRIPES in CAMERA view

Hi there.
Just check the video, everything's in there.
Forgot to mention that I'm rooted and with TWRP recovery flashed.
Not sure how long I have those stripes, if you guys have no idea what is causing them, I think the best way to go will be returning to absolutely stock, and step by step install every mod I had and need (root, recovery, XCam adv. drivers etc.) with tests inbetween them. What do you think?

up, I guess...

Stripe caught on photo! https://dl.dropboxusercontent.com/u/18111725/20150702_095914.jpg
Any idea? Visible in different camera apps too (lgCamera etc.)

No one?

Anyone?

I'll give you a free bump.
I had this problem before, asked for help on it and never got any help.
Unfortunately this is how things are in these G2 forums, just be happy no one has said "try searching".
I hate it here.
Mine went away on its own I guess since it's not happening anymore.
My videos would also freeze frame for minutes.
Try the xcam flashable mod or try CM with Google camera app(included in stock flashable gapps)?
Maybe when I ToT/KDZ restored it might have done something to fix it but it wipes your internal storage too.
Sent from my Android using Tapatalk.