i spent several hours trying to unlock my sim today and fubar'ed my vibrant.
i first lost my baseband. it said 'baseband unknown', so i odin'ed back to JFD from AOSPish...after several trys i got my modem back. now it's stuck in airplane mode.
will someone enlighten me...i've searched everywhere
Damn...55 views and not a single responce. WTF? Anyway, it's fixed. Screw it.
Care to say how you fixed it? I don't know if I am having the same problem but I have a problem where my phone goes into flight mode by itself about 10 times a day... Pretty frustrating.
My friend Steve B. rescued it for me once again. I'm certain he used odin and repeatedly flashed, wiped and reflashed untill all worked. Persistance seems to be cure for most Vibrant bricks.
I use True Stock 2.1 for all my brick rescues.
Hi all,
I am having same (or similar) problem, here is how it happened:
- Previous ROM: CM7.1 nightly (based on v2.3.7)
- Flashed to MIUI from neoBuddy89 (but without odin) (http://forum.xda-developers.com/showthread.php?t=1326764)
- The phone was successfully upgraded, everything was working fine, even the GPS start working which wasn't when I used CM ... for the first day
- The next day, I lost signal connection (week signal) and I couldn't connect to the network anymore. I rebooted, and the phone worked for 1 hours and then lost signal again but this time it wasn't due to week signal
- I rebooted again, when it started I found that baseband/IMEI shows Unknown (I have an efs buckup)
- I read somewhere at xda to turn on/off flight mode which sometime fixes the problem.
- I did turned on flight mode, but when I tried to turn it off it freeze and doesn't exit air plane mode
- tried to reboot, and for no reason, the top panel shows an aircraft but options indicates flight mode as OFF
- I ODIN back to stock but this did not fixed the problem; when it starts baseband/imei both shows unknown and if I turn flight mode ON I cannot exit anymore.
any recommendation on how to fix the problem or the only solution is to buy new phone ?
Related
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
Hello everyone,
I'm new here and I need your help about an issue that I'm facing at the moment.
I got a Samsung Galaxy Alpha G850F that it is in 100% official state. I haven't touched its rom, bootloader, kernel, root access or anything. It is completely stock.
A few days ago I received the OTA Update for Android 5.0.2 Lollipop. I downloaded it and installed it. Then I did a hard reset and started to reinstall my apps and stuff from zero. But I noticed an issue.
I did this. I enabled flight mode and turned off the phone completely. Then, on the next startup if you turn flight mode off it will NOT ask for SIM PIN (while it should) , it will find signal but it will be unregistered to the mobile network! So you can turn flight mode off but the phone will be in "Emergency Calls Only" state and you will not be able to make phone calls, use mobile internet or anything. The only way to fix this is restart the phone BUT with flight mode disabled.
I never had this issue with the previous KitKat firmware (I could do this easily with KitKat, when I turned the phone on and disabled flight mode it would ask me for SIM PIN and then it would be ok). So it seems like you can't start the phone on flight mode anymore. Flight mode works good in general, u can turn it on and off while the phone is on BUT if you enable flight mode and then power it off then you will have no network on next power on.
Anyone else with stock Galaxy Alpha and official 5.0.2 experiencing this ??
Any ideas?
Thanks in advance.
SOLVED!
So problem got solved by itself! I tried to do this today and it worked fine as it should. I haven't changed anything. I don't have a clue what caused it. Maybe it was network related?
Thanks anyway!
Please help me, I have a galaxy alpha g850f fingerprint sensor does not work Is there a solution to this problem
I've been having many software issues with my M4 E2303, ll try make this as short as possible:
I keep on having issues with every firmware I flash. A problem will go away after flashing, but a different one will pop up.
Please note all these firmwares are STOCK.
Issues include:
- Very poor wifi signal (Marshmallow ONLY)
- Wifi "freezing" (Seems like a wifi driver crash) (Lollipop only, fixed after reflash)
- OS Crash with soft reboot (lollipop, happened alongside previous wifi freeze, is still occurring on new firmware)
- Bluetooth not function (seemingly fixed)
The issue im currently experiencing is the OS crash, which occurs randomly with no discernible cause.
From what I can see, flashing with flashtool may well install a new OS, but it seems like it doesnt completely remove elements of the previous firmware. Is there any way I can flash and make sure all my system files are completely replaced by the new firmware?
UPDATE:
I installed stock android 5.0 and booted successfully, WiFi had an issue. I turned off the phone to let it charge and.... it won't turn on. Gets stuck in a infinite bootloop from which I cant recover. I've flashed it twice with different firmwares on the Xperia Flashtool and used the PC companion to do a software repair twice. Still dead... Left it overnight turned off and booted it in the morning, reached the purple waves and froze. Thats the furthest its ever got into a boot.
Don't soft reboot the phone, it's not recommended
Well my phone is actually Rebooting it self for no reason RANDOMLY i don't know why but it happened to me more than 5 times
This correlates with the fact the battery drains very quickly as opposed to months ago where I could leave it in airplane mode for 4+ days for sure. Now it can't last 12 hours in standby (no airplane mode but no connections either - I believe the phone broadcasts something from time to time consuming battery, or simply keeps the hardware lit which he wouldn't in airplane mode). The fact I flashed original firmwares didn't change the fact I can't enter airplane mode again. Also have no IMEI or the efs directory for the files, no network and probably other problems
How can I fix? Flashing gingerbread and its baseband didn't help at all. Should I go back to Froyo? I can't even flash back the restore point I made in CWM...
I've flashed what seemed to be the original firmware (v10L), and all my functionality seems to be back (airplane mode included)