Phone not sending or receiving texts - Fascinate General

So I attempted to manually push my wife's phone to dl09. It failed, I tried again a day later, failed again. Now when I turn her phone on it force closes on media sync and isn't sending or receiving text messages. Any ideas?
so fresh and so superclean.

Anyone
so fresh and so superclean.

could you be a bit more specific about what you mean by manually push? What do you mean by failed?
You could mean you flashed with Odin et al.
You could mean you did 'adb push modem.bin ...'
You could mean you tried to do the update from the settings menu, with or without going back to stock first.
Did the kernel update take? What version shows for baseband in settings/phone information?
Not knowing any specifics, the safest and most general solution is to [make sure lagfix is disabled if voodoo is installed and] run adrynalyne's all-in-one odin restore back to Di01. If you expect any answer beyond that, you need to give more information.

It simple. Stock di01. No root. Nothing. I did the manual update through the phone setting menu. After it turns back on, the basrbabd version says s:i500.04 v.dl09. And the build number still says its di01. If I Odin push the official update, will she loose all of her information
so fresh and so superclean.

did u flash modem threw odin?
cwm rom ?
cwm kernel?

I'm using Odin as a last resort. She doesn't want to loose all of her data.
so fresh and so superclean.

Just I just went ahead and used Odin to flash the official dl09. Wiped everything but her phone is working again
so fresh and so superclean.

Related

[Q] will this work to get back to 2.1

One more question, im not to sure of this program ODIN, but i remember i did a factory reset to get my GPS working a few weeks ago. I followed this post
""Fixing the GPS no fix issue on the Samsung Epic 4g requires you to do a manufacturer's reset by obtaining the MSL code from Sprint. Once you get the MSL Code, remove the SD Card and Enter ##786# on the dialer keypad. You will see two options: View and Reset. Tap on the Reset option and you will get a prompt to enter the MSL code. At this point you will be asked if you want to do a manufacter's reset, enter yes. The phone will shut down and reset itself after a few seconds. Once the process is complete, the phone will go through a hands free activation. After the activation process, updates may be downloaded and installed. Now that all updates have been performed, you may check to see if your GPS is working by going to Google Maps. You should be able to lock in GPS signal in under 10 seconds. Thats it. Your GPS woes are over."
After i did that and got a GPS lock, i went to CWM and did a ADVANCED data restore, and i back on DK28 and had GPS lock when i went into maps. COuldnt i jsut do the same factory reset, then open up CWM, flash the DEOXED eb13, and then do a advanced data restore??
Major question would be if i did ADVANCE, would it bring me back to DK28, or would i just do a DATA restore.
I really was hoping there would be a easier way to go from Dk28 to EB13, but this way seems alittle easier then ODIN.
Flashing the DK28 rom will NOT update the modem to EB13. Use Odin or samsung updater program. Both are very easy, just follow instructions.
Well to answer my own question, it says it does a MASTER RESET, but it DOES NOT!!! I ended up resetting my phone without my data but still am on DK28 with the ROM i flashed. And to make matters worse, somehow i ended up wiping all the data off my SD Card in the process, not sure how, Good thing i copied all my info to my laptop earlier today. I am now putting everythign back aswell as the DEOXED EB13 rom which im going to try and FLAsh the zip via CWM. worse case scenario i just advance rstore back to my CW backup from today and its like i didnt do any of this. ugg
If you are trying to get back to Stock (not rooted) just use the Samsung tool for EB13.
As far as going back to DI18 2.1, you will be better off with EB13 flashed, not the update.
im trying to go back to DK18 and stay rooted, to update to EB13.
urirx98 said:
im trying to go back to DK18 and stay rooted, to update to EB13.
Click to expand...
Click to collapse
Why not just use the samsung update tool, then use CWM 2.5.5
http://forum.xda-developers.com/showthread.php?t=770388
to root it. You will get a clean install (recommended) and root.
ok, so i actually was able to FLASH the DEOXED version of FROYO EB13 ontop of my DK28 , dont ask me how, it told me it didnt work, but it did. Now i tried to CWM my data and its saying its a non match. THis is not making me happy. I heard people had probs with this, any way to fix it??
Edit, i actually accidently swapped SD cards when i was copying and pasting and when i replace it with the correct card, i had no problems doing a FULL DATA restore.
I KNOW HAVE SUPERNOVA 2.2.2 EB13 Kernal version 2.6.32.9 running Firmware GENOCIDE 0.3a EB13 OC/UV kernal
Its KICKASS!!
I would odin to stock eb13 and if you really want everything to work try ACS FROZEN rom. Ive never been so happy with my device it ALL works

[Q] Is it possible to go 100% stock with update

Here is my problem. I would like 100% stock with update.When I first got the phone I rooted with motochopper and installed SPH-L720 OUDHS Recovery. I tried ForceRom 1.0, but went back to my original Nand. Everything worked fine. I used odin to go stock and factory reset data and cache, im good to this point. When I install the sprint update I get the error "Prevention information: This device has detected an application attemping" blah blah blah. Also when i try turning on WiFi the error message pops back up. I checked and the phone is not rooted. I have tried every back to stock thread in these forums. One thing I found in settings: about phone: Status: device status: This still say's custom, even after all the attempts to go stock. Thanks for you help in advance.
How to unroot Galaxy S4, restore to stock and reset the flash counter
Or you can go to the Developer's section and find some threads about restoring. The security thing sounds like you still have Shabby's custom kernel installed. (I could be wrong.)
But the official stock MDC rom from Samsung includes the official kernel. I've restored a couple of times with the official ROM, and I was always back to the original stuff, including kernel. To completely restore, you can always also do a factory reset from the stock recovery (after you flash back the original rom). It will wipe all your data and settings, of course, so be warned.
Edit: A Local Thread: http://forum.xda-developers.com/showpost.php?p=40947712&postcount=6
Also, I forgot to mention, but after this, you'll either just have to wait for Sprint to push the MDL update to you (since you say you want to be updated), or go find the thread (in dev section) from crawrj (I think him) about how to install it manually; but I think that will require a custom recovery, and you are trying to avoid customizations, so...
I have done exactly what the video posted said, even wiped data factory reset. The problem is after i install the OTA update I get the error message and my WiFi does not work. When I try and turn on WiFi it keeps popping up the error. Unrooted I should not get the error and WiFi should definitely work either way.
(At this point, then, this is somewhat like the blind leading the blind, so hopefully a more seasoned ROM manipulator will respond soon to help fix ya up, but until then...)
Maybe you can try crawrj's "Wipe All" script first before flashing the stock ROM? *shrug* (Link: [SCRIPT]Wipe All Zip)
I mean, if you wipe everything and then flash the stock ROM, I would be puzzled as to why something you installed before the wipe would still be lingering around to mess up your system. Again, though, I make no claims this will fix you up--it probably won't. Just throwing out ideas until someone more knowledgeable comes along to help you.
vertualrod said:
I have done exactly what the video posted said, even wiped data factory reset. The problem is after i install the OTA update I get the error message and my WiFi does not work. When I try and turn on WiFi it keeps popping up the error. Unrooted I should not get the error and WiFi should definitely work either way.
Click to expand...
Click to collapse
I had same problem when following the steps to return to stock after flashing custom kernel, Wifi wasn't working and was getting nagging Update and Information notifications. However I did notice after flashing Stock rom via Odin when checking 'about phone' that the Broadband Version was still MDL while Software Version did revert back to MDC. I was also under the impression that flashing the stock rom would restore stock everything, including Broadband Version back to MDC. However wasn't a big deal, I went ahead accepted the OTA update, which downloaded and went through the install process. Afterwards I went ahead and flashed ForceRom 1.0 and the 1.1 update, followed by flashing shabby's custom kernel to get Wifi working. I'm now completely happy with my setup, no nagging notifications and showing Software and Broadband Versions running MDL with shabby's custom kernel. Been running smooth for a couple of days now without any issues..
Figured it out! Had to reset the Flash counter with triangle away in order for the Device status to become official. Then i did data factory reset then flashed the stock .tar with odin. I installed the update on the phone and Viola! device official and everything is stock and working. Thanks for the help.
Good info, there, about Triangle Away. Glad you sorted it out!
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

No wifi, and prevention info notification.

Ok, talk to me like I'm an idiot about this stuff, because apparently I am.
I decided to root using chainfire autoroot, and that was successful, aside from a couple weird things like my UCCW widgets suddenly not stretching fully across the desktop, and what seemed like some new lag. I then flashed slimbean. My contacts didn't restore from google or anywhere, and my sd card seemed to be having problems. I then decided to flash blue kaban or whatever, and that straight up wouldn't boot. However, at that point my sd card fully stopped working, and that is the place I had the slimbean zip. So I did not have a working rom on my phone.
So what I decided to do was unroot and start from scratch. I used the method in this video on youtube by qbking
The result is that my wifi is not working and I have a persistent notification that says Prevention information the device has detected an application attempting etc.
Also software version is MDL, Baseband version is MDL, and Build number is MDC. I was under the impression that they would all be MDC and it would automatically push the MDL but apparently I suck.
My ultimate goal is get back to pure out-of-the-box stock so I can start the rooting process over and try flashing something stable again. But abviously the most important thing right now is to get the wifi working and (I think) the Basbeband and build numbers to match. But I don't know. Please help me. Please. I beg of thee.
ok so after an hour or so it pushed the update to me and my wifi is now working, and everything is MDL. The SD card still says damaged and my contacts aren't there. Any ideas on why those two things would be casualties of rooting and flashing?
I've got the same problem after flashing back to stock from some rom. Would you mind telling me how you got the wifi to work and that notification to go away? I'm not getting an update.
Did the SD card problem happen afterwards? Did you do a factory reset and delete data before you reflashed it? Sometimes when you flash over a partial thing system apps get corrupted.
I have actually performed this and had this happen a few times. What I have found thay it does on some devices is will not properly install random MDL firmware(Saw MDL Firmwares In Settings Still Being Reported). So what I found to be the proper steps for me is before installing any ODIN tarballs thatcare firmware based besides rec9eries are to boot into Recovery and wipe "System, Data, Dalvik, Cache and Preload(Dont Know Why All Of Those) then immediately reboot into Download Mode, install tarball and then when it reboots I go ahead and let it go into recovery and do what it wanrs and when it reboots from stock recovery I hold vokume down to go into download mode and if it says Samsung Official/Official for both options then you are set but if not then I reinstall tarball while I am already in Download Mode again. It happens literally every time I ODIN back to bone stock. I have had to do it at the most 2 extra times after the initial ODIN install.
Sent from my SPH-L720 using Tapatalk 4 Beta
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Now, I also do go ahead and after initial install of tarball go into OS and if I dont have working wifi then I go ahead and do an FDR while I am in the OS just in case even though should helo whatsoever lol then start going to download mode to check Recovery and Software Status.
Sent from my SPH-L720 using Tapatalk 4 Beta
Brains, did you ever get it to work?
Sent from my SPH-L720 using Tapatalk 4 Beta

HELP NEEDED Can't update to Lollipop

Alright, I have a Virgin Mobile S4. I rooted it a year ago with towelroot and installed clockwork mod on it to install cyanogenmod. I tried it, didn't like it so I restored my backup of the stock rom using CWM.
Fast forward to now. I tried to update my S4 OTA for Lollipop, but it would give me an error. I figured it was because I had changed the recovery software. So I went and downloaded the virgin mobile lollipop stock rom from sammobile. ( I337MVLUGOC4_I337MOYAGOC4_VMC ).
I tried to flash it onto my S4 using Odin 3.09. To no avail, it always failed at the system4.img.ext or something. From there I tried to make it work by using 3.10. Still failed. I googled for a fix or workaround and found something about reinstalling clockwork mod. I also tried reinstalling the PIT file for I337M. It was still not working. So I tried to flash back to my stock backup.
1st time I flashed, I kept having program that didn't want to start errors. I wiped dalvik, I wiped cache, I factory reset. Still bugged. So as a last resort I restored the backup again after having done all this. It worked! But...
Well, I'm at a lost now, I can't update using OTA, I can't update with Odin, I can't update with Kies. Now what? Is there a way to go back to the stock recovery and let the OTA or Kies update go through unhindered?
BTW, I had a problem when trying to use EFS professional to backup my EFS before the procedure. No matter which port I used ( front port or back motherboard port ), I could never make the backup, it said something about the phone currently being offline or something.
Anyway, I'd prefer to be able to switch back to the stock recovery and let the OTA or Kies do its thing. Any clues?
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
See first post edit^^
Diabo|ik said:
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
Click to expand...
Click to collapse
Did you check the APN settings? Make sure you have the right one for your carrier.

ODIN Hangs on system.img.ext4 step when flashing SM-G900P

Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Update: I flashed a nandroid backup from right before I started all this. It installed fine. I'm back to my Android 5.0. However, WIFI has stopped working, and the phone stops responding a little bit after the screen turns off, requiring a battery pull and reboot. Additionally, making or accepting calls causes a reboot.
Another update: Tried KIES to install new Firmware through normal update method, it starts but then hangs at 3%.
So any help you might have would be really appreciated!
same problem
I have the same problem. Did you ever find a solution to the system hang on that file problem???
cjs678 said:
Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Click to expand...
Click to collapse
I don't know if I have ever gotten that error before. You can try to update your samsung drivers on your computer, and make sure you are using the cable your phone came with. It sounds silly, but I have had issues with ODIN if I am not using the original cable.

Categories

Resources