[Q] Cyanogenmod issue please help - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

Couple days ago I flashed my first rom, a nightly kltespr Cyanogenmod 12 through Clockworkmod custom recovery. When it booted up the cell network kept turning on and off but everything else was working (not due to bills or location, it did not acknowledge my SIM). I attempted a clean install several times, but to no avail. Went to boost mobile (my provider) and asked if I could get some help with my phone. I told them I installed a custom OS and they thought it was a virus when they saw the booting animation, lmao. He did a full ****ing system wipe.. So it booted up with CMOD 12 again because I didnt have a backup and didnt install another rom. He asked me if I could connect to their wifi. Then this dumbass wouldnt give me the password to it because he thought I can hack into his PC and **** and threatened to call the cops.. He didnt even give me a new SIM to try. Then I went home and tried downloading the latest version in klte and installing it (still CMOD 12).. Unfortunately, I confused it with kltespr, the correct rom for my SM-G9OOP (keep in mind, before this I installed the correct version, but i had cell service issues). Before I noticed, everything was working fine, then my cell network turned off. I noticed the problem when I went to settings and checked my model number and it was changed to SM-G9OOF, so I downloaded the kltespr version and appropriate gapps package, and prior to installing in Clockworkmod I wiped davlik cache, system, and everything. It boots up fine, but cell network is still not working, and more recently the phone turned off, then got stuck in bootloop. I took out the battery and reinstalled everything in CWM, after wiping again. Booted up fine again, but I still dont have cell service and the phone uncontrollably restarts over and over, forcing me to take the battery out. Is there anything I can do?
Btw this is my first post excuse the length.
Also, **** you Boost, get some competent employees. I highly suggest anyone considering them to stay away.
If I cant fix this im going to get a new iPhone6+ or Note 4 from Verizon.

Try this fix posted in this thread. Has nothing to do with Boost Mobile.
http://forum.xda-developers.com/sprint-galaxy-s5/help/help-t3006806

Related

[Q] Nexus S no network service! What do I do?

Hi guys I have a 2 month old Nexus S and for no apparent reason all of a sudden today I noticed I am not getting any network service (australia vodafone).
I've tried removing and trying other sim cards which are known to work. My sim card works in other phones so it's nothing wrong with the sim card. Wifi still works perfectly. I've tried going in and out of airplane mode to restart the antenna and I've tried to turn it off and on again. I've also done a factory reset and erased all data through the android menu as well as the bootloader separately to no avail.
However what I also noticed is even though I did factory resets it doesn't seem to completely reset it as the android version still shows 2.3.3 which I applied using a manual update. The phone had 2.3.1 when I bought it. How do I do a full reset to send it back to 2.3.1?
The phone is still under warranty however if it is a software issue I would rather fix it myself then send it away.
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Additionnal bit of info.
Someone on Cyanogen forums asked me to try to flash the radio through fastboot instead of clockwork recovery..
If I do that, it is able to send the file but it seems unable to write. It gets stuck here:
fastboot flash radio XXKB1-GRI40-radio-nexuss-unsigned.zip
sending 'radio' (4126 KB)... OKAY
writing 'radio'...
(I've tried flashing both KB1 and KB3 through flashboot, same results)
Hello everyone,
I have the same issue. I turned my phone on this morning and it said "no service, emergency call only".
I used wifi to apply the OTA 2.3.4 with hope that it'd fix the issue as I read from my google searches. But it does not.
I tried flashing back to KB3 to run with 2.3.4 as well but that doesn't help.
If the phone can still do emergency call, it means the hardware is OK, right?
any suggestion? Thank you very much.
Opteron.
Did anyone ever find a solution?
you could try dialing *#*#4636#*#*, going to phone information, and looking at your preferred network type (might be the wrong one). you could also go to phone information, push menu, go to select radio band, and try a few different ones. hopefully that solves it, or you might have to flash a different radio/rom
edit: make sure you write down the original preferred network type before you change it. it could screw with what kind of service you get if you set it to the wrong one
Hi,
I am having the similar problem with my Nexus S
Tried the *#*#4636#*#* settings to EURO and GSM only but with no success.
Did anyone ever find a solution?
hi, im just wondering what type of root did you use for the AU nexus s. im not sure what root method to use for the SCLCD :S
thanks
fooraide said:
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Click to expand...
Click to collapse
Hello! did you find any solution or you repaired your nexus s? Im having the same problem. when i try to back to stock from Cyanogen..Any suggestion? Regards
found a solution
hi guys ! I recently had the same trouble that no signals were being received after updating to 4.1.2 but then i dialed *#*#4636#*#* and turned off the radio and turned it on again and now its all fine

[Q] Service issues on MIUI

I flashed MIUI V8 for the mesmerize about a week ago and everything was going great until today when my phone randomly lost all data service. every now and then it goes into roaming but i still cant do anything. i wiped data and reflashed the ROM and still nothing. any suggestions or help. im pretty new to the forums
did u wipe the data in android or in cwm recovery??
yea i did that but still nothing

Problems after getting back to stock ROM from CM7

Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy

Lost all Mobile Data connectivity

So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Ron Overdrive said:
So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Click to expand...
Click to collapse
Maybe you need to contact your carrier?
You're not alone, I'm having the same problem since going to 5.0. I use Red Pocket on AT&T's network. Can't get mobile data working at all. Contacted Red Pocket and they reset my data on their end but still a no-go. Wi-Fi fine, calls and SMS fine. MMS, like data, doesn't work.
I guess I'll pick up another MVNO card to make sure it isn't still Red Pocket's issue. I have another SIM, but unfortunately my T-Mobile card, which is usually in a Lumia 1520, doesn't work for data on the Nexus 5 because that is on their blocked list of phones (stupid carriers).

Help, out of ideas. Possible mother/logic board going bad?

I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL

Categories

Resources