Hi everyone,
I finally might have figured out how to fix the ghost call issues and the reorginizing internal process problem... it has been 10 days that I have had no ghost calls and no RIP.
After many hours arguing with LG (who after all 12 calls still said they never heard of this problem before). The only advice they could offer me was to send my phone to repairs.
I decided to do a final attempt and if it didn't work I would have sent my phone in 3 times to get a different phone and end this nightmare.
So I did a factory reset on my phone.
The problem was still there.
I heard about keeping the CPU above 600mhz all the time and while that temporarily worked it came back.
I loaded the recovery mode and factory reset from there and I also cleared the cache. that didn't work.
After more research I found that putting the phone in 2g will help. While this was true it was still happening but a lot less.
I decided to explore the world of Roms and that's where the fix came in.
My phone is rooted. Big thank you to Dan 
I am running V20c 2.3.5
I Formatted my internal SD and my external.
I installed clockwork mod and backed up my stock rom... I then booted into recovery mode and cleared every cache option (2 on first screen and dalvik in advanced. The only exception was battery stats with CWM.
After doing all that, I had to leave so I figured I would look for a new rom another time. That was 15 days ago. After a week I realized that I haven't been getting the RIP or the GC problem... seeing as how it was hard to check I forwarded all my calls from my home office line to my cell phone so that if the call was not answered it would go to my cell after the 2nd ring. To this day (10 days later)... every call on that phone has been registered on my cell... therefore I believe that CWM IS THE KEY TO OUR PROBLEMS
*JUST NOTE THAT I SAVED MY SD CARD TO MY PC SO I HAD A EXTRA BACKUP SHOULD NEED BE.*
**WHEN I DID IT, I FORMATTED WITH CWM**
so after all that here's the process...
*WORKS ON V20C 2.3.5 ROGERS*
1. ROOT
2. FORMAT EVERYTHING (SETTINGS/STORAGE...)
3. VERIFY THAT YOU STILL HAVE ROOT (YOU SHOULD)
4. INSTALL CWM
5. BACKUP YOUR DEFAULT ROM (NEVER KNOW)
6. ENTER CLOCKWORK RECOVERY
7. CLEAR ALL CACHE EXCEPT BATTERY STATS (I DID NOT TOUCH ANY PARTITIONS OPTIONS)
8. GO BACK IN YOUR PHONE
9. DO NOT PUT BACK YOUR BACKUP ROM
***Remember this is working for me on Rogers V20c 2.3.5***
I made a titanium backup of all my Apps but I am not restoring them I am redownloading from scratch. I do not know if it will cause issues with the GC/RIP issues.
Good luck to all of you and I hope that you finally get to enjoy our cursed phones. I had RIP messages easily every 2 hours and for 15 days I haven't seen a single one and all my calls are working.
Thank you to Dan for Root and the Creator of CWM for saving us.
Sent from my LG-P925g using XDA
Nitedriver said:
Hi everyone,
I finally might have figured out how to fix the ghost call issues and the reorginizing internal process problem... it has been 10 days that I have had no ghost calls and no RIP.
After many hours arguing with LG (who after all 12 calls still said they never heard of this problem before). The only advice they could offer me was to send my phone to repairs.
I decided to do a final attempt and if it didn't work I would have sent my phone in 3 times to get a different phone and end this nightmare.
So I did a factory reset on my phone.
The problem was still there.
I heard about keeping the CPU above 600mhz all the time and while that temporarily worked it came back.
I loaded the recovery mode and factory restored from there and I also cleared the cache. that didn't work.
After more research I found that putting the phone in 2g will help. While this was true it was still happening but a lot less.
I decided to explore the world of Roms and that's where the fix came in.
My phone is rooted. Big thank you to Dan 
I am running V20c 2.3.5
I installed clockwork mod and backed up my stock rom... I then booted into recovery mode and cleared every cache option with CWM. Formatted my internal SD and my external.
After doing all that, I had to leave so I figured I would look for a new rom another time. That was 15 days ago. After a week I realized that I haven't been getting the RIP or the GC problem... seeing as how it was hard to check I forwarded all my calls from my home office line to my cell phone so that if the call was not answered it would go to my cell after the 2nd ring. To this day 10 days later... every call on that phone has been registered on my cell... therefore I believe that CWM IS THE KEY TO OUR PROBLEMS
so after all that here's the process...
1. ROOT
2. FORMAT EVERYTHING (SETTINGS/STORAGE...)
3. VERIFY THAT YOU STILL HAVE ROOT (YOU SHOULD)
4. INSTALL CWM
5. BACKUP YOUR DEFAULT ROM (NEVER KNOW)
6. ENTER CLOCKWORK RECOVERY
7. CLEAR ALL CACHE AND FORMAT (I DID NOT TOUCH ANY PARTITIONS OPTIONS)
8. GO BACK IN YOUR PHONE
9. DO NOT PUT BACK YOUR BACKUP ROM
***Remember this is working for me on Rogers V20c 2.3.5***
I made a titanium backup of all my Apps but I am not restoring them I am redownloading from scratch. I do not know if it will cause issues with the GC/RIP issues.
Good luck to all of you and I hope that you finally get to enjoy our cursed phones. I had RIP messages easily every 2 hours and for 15 days I haven't seen a single one and all my calls are working.
Thank you to Dan for Root and the Creator of CWM for saving us.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
CWM isn't the issue. It's the baseband.
CWM is on a different partition than the baseband and is not active until it is called. Ghost calls still exist because 2.3.5 in general has this issue. 2.3.6 fixed ghost calls.
Sent from my Samsung Galaxy S II w/ CM9
Never said that CWM was a problem I said CWM helped fix this issue
I posted this to help others who were looking for a solution it is still working for me so I'm happy and I figured id share my findings in hopes of helping others who got nothing to lose and everything to gain with this phone.
Have a good one.
I believe that CWM FIXED my phone
Sent from my LG-P925g using XDA
[Removed comment after being confirmed safe to format SDCARD in CWM]
johnw230873 said:
Hi Guys, be aware that people have fully bricked their phone formating there sdcard using CWM.
Click to expand...
Click to collapse
Ooo I wasn't aware... well guess I was lucky.... I think just formatting the SD card regularly (not with CWM) and then using CWM to clear caches would be enough...going to modify original post thanks John
Sent from my LG-P925g using XDA
146 views and no confirmations or experiences... there is a 0% chance of bricking your phone.... come on guys try it and post... if it doesn't work for everyone else then at least people know. Help eachother out you got nothing to lose (if u back up) if ur scared for ur backups remove the external SD during testing or backup to ur PC.
Sent from my LG-P925g using XDA
Wait. You should remove the notices for BRICKING.
Reason being as it is only applicable to CyanogenMod. It has an option to use the sdcard for data instead. Stock doesn't.
Formatting sdcard and emmc in ClockworkMod will not and can not brick your device on a LG Firmware.
This, again, does not include CyanogenMod.
Now. As for fixing the problem, I've done this method and still have ghost calls.
You will ALMOST always get ghost calls with 2.3.5.
Sent from my Samsung Galaxy S II w/ CM9
Hi Guys I was going off other information in other posts for example http://forum.xda-developers.com/showthread.php?t=1529836&page=2 talking about CWM and CyanogenMod.
I'm not an expert in this area and after reading this didn't want a lot of bricked phone so thought I'll better say something, have edited my post and removed the comment.
I have also tried this, worked for 3 days then a GC
The Dark Lestat said:
Wait. You should remove the notices for BRICKING.
Reason being as it is only applicable to CyanogenMod. It has an option to use the sdcard for data instead. Stock doesn't.
Formatting sdcard and emmc in ClockworkMod will not and can not brick your device on a LG Firmware.
This, again, does not include CyanogenMod.
Now. As for fixing the problem, I've done this method and still have ghost calls.
You will ALMOST always get ghost calls with 2.3.5.
Sent from my Samsung Galaxy S II w/ CM9
Click to expand...
Click to collapse
Done thanks
Sent from my LG-P925g using XDA
Its been mentioned that 2.3.6 fixes the ghost call issue, however i am having dificulties finding this. Can someone post a direct link to the thread or download spot gor it?
Sent from my LG-P925 using XDA
cmeducknow702 said:
Its been mentioned that 2.3.6 fixes the ghost call issue, however i am having dificulties finding this. Can someone post a direct link to the thread or download spot gor it?
Sent from my LG-P925 using XDA
Click to expand...
Click to collapse
I assume this because all devices friends have ranging from Nexus to Samsung to HTC with 2.3.5 had ghost calls and when they updated to 2.3.6, ghost calls disappeared. They were on stock as well.
Sent from my Samsung Galaxy S II w/ CM9
Ok, i've only been worried about my thrill... never paid attention any others. Thanks
Sent from my LG-P925 using XDA
NOOOOOOOOOOOOO!!! Scrap this thread guys....I just got my first. R.I.P I HATE THIS PHONE!
it was going so well....
Does anyone know any stable 3D working roms that fix this issue??? Let me know thanks...
Sent from my Rooted ANTI GC/RIP LG-P925g using XDA
Related
What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App
Anyone?
-------------------------------------
Sent via the XDA Tapatalk App
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?
Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.
Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App
I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App
SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.
Hey,
this problem started only today and has never happened before. The only things changing were some app updates and a few new installs. I already uninstalled all of the apps installed in the last few days in hopes of reverting the situation but it didn't help. And after I made the first reboot when the apps began to force close randomly it looked like a semi factory reset was made. All my contacts are gone, there are no SMS/call logs, but all SMSes, pictures and videos are still there. If I try to open the Market app it asks me if I accept TOS, Gmail is not set, mobile internet is not working (due to reset settings), Wi-Fi and bluetooth settings are still there. In short, everything is half-fuc*ed.
What do you thing happened? And is there any possibility I can go back to a normal state without starting from fresh?
Pegart said:
Hey,
this problem started only today and has never happened before. The only things changing were some app updates and a few new installs. I already uninstalled all of the apps installed in the last few days in hopes of reverting the situation but it didn't help. And after I made the first reboot when the apps began to force close randomly it looked like a semi factory reset was made. All my contacts are gone, there are no SMS/call logs, but all SMSes, pictures and videos are still there. If I try to open the Market app it asks me if I accept TOS, Gmail is not set, mobile internet is not working (due to reset settings), Wi-Fi and bluetooth settings are still there. In short, everything is half-fuc*ed.
What do you thing happened? And is there any possibility I can go back to a normal state without starting from fresh?
Click to expand...
Click to collapse
Go into Recovery and Fix Permissions, then reboot and see if that has fixed the problem.
Flash a new stock rom to solve this issue..
Sent from my GT-I9000 using XDA Premium App
doomsdaycs said:
Flash a new stock rom to solve this issue..
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
But try a wipe (factory reset) before, should solve thus issue.
Sent from my GT-I9000 using XDA Premium App
Oh yeah, and another thing. Market, Youtube and Maps apps where all a few version lower than before and started updating immediately after opening the Market app. Market still is (even the old design and everything). How can this be?
rschenck said:
Go into Recovery and Fix Permissions, then reboot and see if that has fixed the problem.
Click to expand...
Click to collapse
I don't have a Fix Permissions option in recovery (3e)???
doomsdaycs said:
Flash a new stock rom to solve this issue..
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I'm trying to avoid that at the moment. Just for the time being so I can make a complete backup of all my stuff.
Lunchbox115 said:
But try a wipe (factory reset) before, should solve thus issue.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same as above. For now.
i9000 random loss of data
Yes, this is a rather old thread I'm trying to revive here, but as it is adviced to continue those instread of duplicating them, here are my issues:
I gave my i9000 to a relative ~a year ago and recently it started acting strange. About 1-2 times a month I get a call from that relative saying: "I get a lot of force closes, phone is unusable, nothing works". I then walk over, take a look and yes, unusable. It appears that all information in the /system partition gets lost for no reason. The relative told me that this usually happens when some google apps are updating, but it might still be random.
Currently MackayRom (latest) is installed.
Usually when I got the call, I hopped over to my relative, did a factory reset (wipe of /system and /data + Cache and Dalvik Cache) then reflashed the ROM and Gapps and everything looked good again. Sadly the issue continues to return.
What I tried so far is a complete wipe of anything, reverting to a stock TW Rom, and going back to an AOSP Rom from there (first CM 11, then Mackay). The issue appeard to be gone afterwards, I didn't hear from that relative for an unusual amount of time, but after a month or 1 1/2, it returned.
My guess is, that one of the chips that are containing the /system partition is broken or at least close to die (I'm not sure if it is just one or multiple chips, since the CM Team or Pawit himself changed something in the partition structure somewhere between cm10, cm10.1 and cm11 to ensure the compatibility of that old device with KitKat). Anyways, I'd love to hear any ideas or suggestions on how to solve this issue (although I reached a point where I think that solving this isn't possible anymore, unless I wanna swap the Mainboard, which would mean paying an amount of money that I could get a new phone for as well.) Soon as I have the time, I'll Odin-flash the latest TW Rom to the device and have my relative use that for a while, just to see if the different/older partition structure helps in any way.
Thanks in advance for any replies .
I would be ok with this if it wasn't almost every time the phone is left alone.
i thought maybe installing CM would help but it still does it, went back to stock firmware (S5830DTLKI4) with no resolution.
It appeared to only be doing it when it is put to sleep, but after i unlocked it and tried to send a text with my Bell Canada sim card the phone restarted again.
It certainly isnt a SoD, because it is turning itself back on.
wifi is off, GPS is off, Bluetooth is off, and it is doing this on a 100% stock install; no market apps installed, no google account even linked.
so it appears to be restarting when i let it go to sleep, and when i try and send a text using a non-Koodo sim card. (although i dont know the effects with a Koodo sim; never had one)
I went to samfirmware and downloaded a md5 for the UK network Orange, but it didnt fix anything as far as i know, i didnt unlock it but it was still restarting itself.
Im wondering is this a software issue (if so, what is happening and is there a way to fix it?), or is this a hardware issue (perhaps there is a faulty capacitor somewhere on the board that isnt filtering voltage spikes and causing the device to reboot because of that)?
i couldn't find any references to this problem ever really being addressed.
help would be greatly appreciated.
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Narwhal73 said:
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Click to expand...
Click to collapse
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
blueblitzpup said:
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
Click to expand...
Click to collapse
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Narwhal73 said:
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Click to expand...
Click to collapse
its not a bootloop though, it's booting into CM and then once the screen goes to sleep the phone restarts itself, just like it did on the stock rom.
i already tried mounting data, system and sdcard, but it didnt help any.
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
racer_25 said:
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
Click to expand...
Click to collapse
Since you don't have the warranty, you'll have to pay for the service anyway. Just be sure that the phone serial no. that's on the label after taking out the battery is intact & you are all fine to get a clean service. There's nothing much you can do by yourself as it doesn't appear to be a software problem. But it might quite happen b'coz of a faulty battery. My friend's galaxy y had the issue & a replacement killed it. So may be it with you. Anyways, before buying you can try it out with your friend's battery & hope to see if the issue is solved & then go buy one. If this doesn't help, head for service as said earlier.
Sent from my GT-S5830 using xda premium
Let me tell you a story. I once brought a Galaxy Note form Flipkart.com . When it arrived, it had features rivalling that of the iPhone 5, but had half the price and a larger screen size at that. I was over the moon. It seemed like nothing could go wrong.
I rooted it the day after it came. Almost miraculously, you had features like dual-boot animation. I, of course, in my inimitable stupidity, forgot to make a Nandroid backup. But who cared ? The device was up and running.
That's when the nightmare started. It just started out as minor blips - Google Play saying that authentication required or sevrver error or offline mode ( whatever the hell that means ) ; Google Talk forever on offline mode ; Gmail not being able to sync. These and more warning signs appeared, but I brushed them aside, thinking that they would be fixed with the passage of time. In retrospect, this was a very stupid thought.
Then the hell started. Galaxy offered a Jelly Bean Update. In my steadfast optimism, I downloaded it and installed it. Nothing changed. Absolutely ****ing NOTHING. My mother's sister, who was Android Development Head, informed me that it was due to some conflict between TouchWiz not being compatible with Android Jelly Bean. Then apparently, since the update was downloaded and not installed, it kept informing me that your update is due, and kept asking me whether I would install it. I, obviously kept saying NO. Some stupid person on androidforums told me to freeze Samsung Updater using Titanium Backup. But, my friends, the worse was yet to start.
As soon as I froze Updater it crashed. I had to force start using Recovery. Then the device wouldn't give any signal and even WiFi stopped working.
I then unfroze Updater, since that was the natural action one would take. It crashed again and on force start it said - " Android Updating, Start Applications... ". There was no signal whatsoever.
Then it seemed like Satan had reserved a special place in the depths of Hell for the Note. Every thirty seconds the Note would crash and give the same message which I listed above. Some person on some random forum suggested moving all the apps from the SD Card to Internal Memory. Well, great suggestion, because whenever I tried to open settings, Note would, very conveniently, crash again.
I tried backing up using ADB. Crash. Factory Reset attempt. Crash. Crossing my fingers. Crash. Just isolating it and keeping it on a bookcase. Crash.Crash all the way.
I've run out of ideas, so from my long post, if you have figured anything that might be of use, don't hesitate to reply
Regards And Thanks
Sid
Just download ROM of your choice, stock or custom. Use pc odin to flash stock rom or cwm to flash custom rom.. Head over to dr ketans thread for list of stock roms be it jb, ics or gb. If you still can access custom recovery (dont wipe on stock recovery) do all the wipes like /system /preload /data /cache(ofcourse if u dont want to backup anything important ) and the flash the stock or custom rom
Sent from my GT-N7000 using xda app-developers app
try Cursed4eva on youtube...this guy's videos would definately help u....btw u did tried flashing an official rom right?
Usually a factory reset and stock rom solves evrything
Sent from my GT-N7000 [better than gtn2] using xda app-developers app
i have a note 4 on t mobile. i just rooted my phone (first root ever) using the method described on here no issues. my phone worked normal for a day and now today when i try to send a text message it shows that it is sending and will be like that for an extended period of time 30 mins plus and when someone text messages me it takes 30 plus minutes to reviece it. i have reset the phone pulled the battery restarted the phone i dont know what else to do on why it would be causing this issue is it because of the root?? or something else or is there a fix for it......thanks guys
jasonjp82 said:
i have a note 4 on t mobile. i just rooted my phone (first root ever) using the method described on here no issues. my phone worked normal for a day and now today when i try to send a text message it shows that it is sending and will be like that for an extended period of time 30 mins plus and when someone text messages me it takes 30 plus minutes to reviece it. i have reset the phone pulled the battery restarted the phone i dont know what else to do on why it would be causing this issue is it because of the root?? or something else or is there a fix for it......thanks guys
Click to expand...
Click to collapse
Do you have a recovery in place? Try wiping your dalvik and cache.
Also, try wiping the cache on the messaging app. IS there a different messaging app you are using? What you are describing only happens with me on the google messaging app. Safe to assume no special rom in place, baby steps?
P.S I'm 99.9% sure rooting is not the issue, so you can calm down if you think rooting broke your messaging
ok you are speaking greek to me lol. i am very very new to this. i just rooted using the method listed in the t moble note 4 root. not the custom one just the first step with the root file. phone is stock besides that no special messaging apps just what came with the phone. i have had the phone for 3 months never had a issue. i rooted yesterday and now today im having this issue. everything else on the phone works just sending and recieving texts is messed up
jasonjp82 said:
i have a note 4 on t mobile. i just rooted my phone (first root ever) using the method described on here no issues. my phone worked normal for a day and now today when i try to send a text message it shows that it is sending and will be like that for an extended period of time 30 mins plus and when someone text messages me it takes 30 plus minutes to reviece it. i have reset the phone pulled the battery restarted the phone i dont know what else to do on why it would be causing this issue is it because of the root?? or something else or is there a fix for it......thanks guys
Click to expand...
Click to collapse
Relax... Take a deep breath... there is one important thing to realize now that you have rooted your phone. You can fix just about any software problem you could have.
Root should not effect the sms or the mms though. So my guess is it is an apn issue. Do you have the correct apn set up? [Google search: Tmobile APN]
If the above doesnt work,Then next thing I would try is to go into TWRP recovery and fix your permissions. [Google search: How to fix permissions in TWRP]
If neither of those work I would try using TWRP to clear your cache and your davlink cache. [Google search: How to wipe cache in TWRP]
Finally If none of those work then my next idea would be to use ODIN to flash the NK4 stock ROM and then reroot using cf auto root. Then use Odin to flash TWRP again. http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4/
Sent from my SM-N910T using XDA Free mobile app
I used the auto root file from there. This is my first attempt at this and it's very confusing lol. Whole reason I rooted is because of unlimited wifi Hotspot which works perfectly
ShrekOpher said:
Relax... Take a deep breath... there is one important thing to realize now that you have rooted your phone. You can fix just about any software problem you could have.
Root should not effect the sms or the mms though. So my guess is it is an apn issue. Do you have the correct apn set up? [Google search: Tmobile APN]
If the above doesnt work,Then next thing I would try is to go into TWRP recovery and fix your permissions. [Google search: How to fix permissions in TWRP]
If neither of those work I would try using TWRP to clear your cache and your davlink cache. [Google search: How to wipe cache in TWRP]
Finally If none of those work then my next idea would be to use ODIN to flash the NK4 stock ROM and then reroot using cf auto root. Then use Odin to flash TWRP again. http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4/
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I think he just rooted and has not installed twrp or any recovery. I would say most likely apn issue .
BAD ASS NOTE 4
I see,
I will suggest you do some readings my friend...it comes with rooting. Do what @ShrekOpher suggested and do the google search he placed. If you do not have a crash course in what comes with rooting and how to get out of jam...especially what TWRP can do, how to install it, the benefit of it...it will be hard for anyone to help you. Ultimately, we will all be talking greek to you lol
Do not panic, for now download a third party messenger and read around than get back to fixing your stock messenger. Good luck! Google is your best friend!
P.S You can also search the terms he suggested with in XDA as well, a lot of good guides and questions for beginners. You have to be able to search and read read read, its a nice way to get rooting knowledge
Are you on WiFi when sending?
Android_Monsters said:
Are you on WiFi when sending?
Click to expand...
Click to collapse
This is usually the issue, try turning off wifi and see if that helps.
btort1 said:
This is usually the issue, try turnging off wifi and see if that helps.
Click to expand...
Click to collapse
Should not be an issue I am on WiFi and send no issue.
BAD ASS NOTE 4
BACARDILIMON said:
Should not be an issue I am on WiFi and send no issue.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Ooops I should have said, if he didn't want to factory reset his phone and find a temporary fix he should try turning off wifi.
I remember a thread during the first week about this, updating to nj7 and making sure my apn was set to TMobile US LTE fixed my issue.
how do i go about un rooting my note 4 for t mobile until i can have the time to read all this stuff and do it right next time.
jasonjp82 said:
how do i go about un rooting my note 4 for t mobile until i can have the time to read all this stuff and do it right next time.
Click to expand...
Click to collapse
Odin back to stock
BAD ASS NOTE 4
where do i get the stock file from
http://www.sammobile.com/
This guy has 'em, too:
http://forum.xda-developers.com/showthread.php?t=2957156