(searched the forums here, but there is apparently noone with a similar problem)
I have a larger problem with a former S5839i (French model - Bouygues branding). The phone belongs to a colleague of mine. She called me a few days ago claiming that her phone "is broken". It was stuck at the bootscreen. The software she used before the phone failed was the initial Bouygues release. Apparently there was an update pushed to her phone (the newer Bouygues-release) and it softbricked the device.
No big deal. I flashed the phone to a 5830i - using the emergency recovery files for Odin that someone posted here on the forum (the 5-part set including the pit-file). Afterwards flashed to the latest European build (Netherlands). Worked like a charm, the phone is working smoothly.
At least I thought so. But when I started it with her SIM, it would not recognize her Network (Pelephone - Israel). The same is true for other bands/providers. Other phones show a full signal with that SIM, the problematic device will barely recognize a network at all (sometimes gives one shaky bar). Prior to the softbrick, the phone would have a full signal as well.
Here is what I tried so far:
- Tried flashing several different basebands as well as changing the entire system (to Czech, French, etc version) - Problem remains
- Checked for possible SIM-locks - Phone is not locked
- Used shortcut *#197328640# and forced the phone to use only the 850Mhz or 2100Mhz band (these are the ones Pelephone operates on) - Problem remains
I have officially run out of ideas. So: Is there a white cellphone wizard that can come to my rescue...?
EDIT: Before someone asks: I checked if the IMEI is still there. Everything normal on that front...
Related
Hi,
I'm new to both this forum and android, just switched from iphone and already running into the same dead end that I was trying to avoid. Hope to get some suggestions on solutions before trying sell it off again...
I bought a second hand SGSII which is from the UK (T-mobile), and with the help of my brother who has a SGSII and have been on android for a while, I debranded/rooted changed ROM, Kernel and Modem firmware. Before doing this I noted that it did not work with the network I am on but it did with another (both Swedish). After rooting etc I tried again, still does not work (I've tried several sims from my provider, none of them work, still only the other provider). I tried using the Sim Unlock app on Market but it is of no use: It DOES NOT ASK for a sim unlock code on start up. In fact, the unlock app worked and gave me such a code but I cannot use it. Also, I tried plugging in the code using a few of the call codes but it was of no use. And when I put *#SIMLOCK# into the phone dialer everything says 'off'.
Does anyone have any idea of what to do? I cannot go back to Samsung as I do not have a receipt. I hate to think that I have to end my use of Android before it ever started but I have searched my problem for days on end and neither me nor my brother can think of anything.
Any help most appreciated!
Cheers Matt
Android version: 2.3.4
Baseband: I9100NEKF2
Kernel: 2.6.35.11-ninphetamine-2.0.5+ ninpo at titan #20
Build no: GINGERBREAD.XXKH3
Network not working: Telia (Sweden)
Network working: Comviq (Sweden)
I am confused did you buy an unlocked phone . If not did you get it unlocked .
jje
JJEgan - sorry if I was unclear. I do not actually know for sure, but as I have never seen the screen on startup where it asks for the unlock code I suspect that it must have been. It now - same as it has been for as long as I have had it - works only with one network which has nothing to do with T-mobile (on which is was originally).
I only know of one way of unlocking, i.e. the unlock app on Market. If there are others I would be very interested!
Phone may require you to enter the networks APN settings manually .
You may not have the correct CSC file for your network for automatic connection ,
jje
Hi - been busy the last few days and unable to try getting the phone to work. I cannot enter the APN settings (which should only have to do with internet?) as I cannot connect to any network in the list - I get "unable to select network". I've tried multiple official firmwares with both only NEE (Nordic) CSC and multi-CSC (where I chose NEE) and none work. Any other ideas?
Cheers
Hi,
TL;DR version below.
Note: This is just a traceback that may help diagnose the problem.
I "own" an Ace (S5830M, everything from i/C works fine). I was playing around with some custom ROMs and evertything was going pretty fine. I installed Jelly Blast (OTA 3) and flashed back to stock a few times, everything was fine and working. Used the recovery/backup functionality from CWM (5.0) to switch between the mentioned installations and it was all good.
Here start the real problem:
During one of the instalation of the custom ROM i went to Advanced -> Format /system (Because probably I miss read the instructions). After this the phone booted and didn't bootlooped, instead it just showed the initial logo (white letters, phone model. Not Samsung animation). As I noted it was stuck I flashed stock from Odin and got it working back.
Everything is fine, the phone works as intended, exept that it "can't" use the baseband I was using before (850 MHz frequency, 3G). I say "can't" because after n tries I was able to send 1 SMS, and only one. All the others failed. And on really unusual occasions I get signal and the phone tells me the provider (Kolbi/ICE) but after a few seconds it loses the connection/signal.
What I've tried so far:
Go to Settings->Wireless Connections->Movile Networks:
There I tried to choose my carrier, but isn't listed 99% the time. The other two are(Claro/movistar). So I set it to automatic.
Check IMEI:
It is the right one
Try to restore from a previous working state with CWM:
I can't it says that there's a MD5 missmatch. (Can I force it?)
Flash a Modem file that is known to work (With another, same model, phone and carrier)
Same sympthoms: does not work.
Dial *#197328640# and play with the settings:
Here I setted to: Type: DUAL_MODE_UMTS_PREF
Band: AUTO
These are the same settings that the working phone.
Flash the stock carrier-branded firmware.
Without luck so far.
====================================================
TL;DR
I have two phones, same model and same carrier. One does not detect the 850MHz band (3G to GMS) so I get no service 99.99% the time, but I was able to send a single SMS. All this after formating /system via CWM.
I've tried to use the same setup and setting from the working phone without success.
Any help or hint would be greatly appreciated.
Footnote: English is not my native language, please understand if I confused some of the tech terms even if IT is my field.
niant said:
Hi,
TL;DR version below.
Note: This is just a traceback that may help diagnose the problem.
I "own" an Ace (S5830M, everything from i/C works fine). I was playing around with some custom ROMs and evertything was going pretty fine. I installed Jelly Blast (OTA 3) and flashed back to stock a few times, everything was fine and working. Used the recovery/backup functionality from CWM (5.0) to switch between the mentioned installations and it was all good.
Here start the real problem:
During one of the instalation of the custom ROM i went to Advanced -> Format /system (Because probably I miss read the instructions). After this the phone booted and didn't bootlooped, instead it just showed the initial logo (white letters, phone model. Not Samsung animation). As I noted it was stuck I flashed stock from Odin and got it working back.
Everything is fine, the phone works as intended, exept that it "can't" use the baseband I was using before (850 MHz frequency, 3G). I say "can't" because after n tries I was able to send 1 SMS, and only one. All the others failed. And on really unusual occasions I get signal and the phone tells me the provider (Kolbi/ICE) but after a few seconds it loses the connection/signal.
What I've tried so far:
Go to Settings->Wireless Connections->Movile Networks:
There I tried to choose my carrier, but isn't listed 99% the time. The other two are(Claro/movistar). So I set it to automatic.
Check IMEI:
It is the right one
Try to restore from a previous working state with CWM:
I can't it says that there's a MD5 missmatch. (Can I force it?)
Flash a Modem file that is known to work (With another, same model, phone and carrier)
Same sympthoms: does not work.
Dial *#197328640# and play with the settings:
Here I setted to: Type: DUAL_MODE_UMTS_PREF
Band: AUTO
These are the same settings that the working phone.
Flash the stock carrier-branded firmware.
Without luck so far.
====================================================
TL;DR
I have two phones, same model and same carrier. One does not detect the 850MHz band (3G to GMS) so I get no service 99.99% the time, but I was able to send a single SMS. All this after formating /system via CWM.
I've tried to use the same setup and setting from the working phone without success.
Any help or hint would be greatly appreciated.
Footnote: English is not my native language, please understand if I confused some of the tech terms even if IT is my field.
Click to expand...
Click to collapse
Flash a new rom and kernel
Rahul4Ace said:
Flash a new rom and kernel
Click to expand...
Click to collapse
Yeah, that could fix it. BTW, was there any need to quote the whole OP?
Hi all!
I bought an S6 Edge second hand and after flashing a stock ROM, I had the "emergency only" calls issue, I tried everything I could find in the forums to no avail and I ended up taking it to a repair service. I did not think they could fix it but they did and I would like to know what they did to it in order to prevent it from happening again and to know if I can leave it as default (not custom OS) so that it can upgrade.
State of phone when bought:
So, the phone was working well with all carriers (from Colombia). The only thing I was able to notice after I bought it was that it was still on Marshmallow (6.0.1) with carrier branded stuff. It was in perfect shape otherwise.
So I downloaded a stock ROM and installed it using Odin. After this the phone would not let me make calls as it was not registering on the network. It did not even let me make emergency calls despite getting full bars of signal and being able to recognise the list of carriers when attempting to manually connect to them.
Important: The ROM downloaded was for the right version of the phone which was the G925i and the IMEI, serial number and baseband were not altered from the original. Also, I checked the phone to see if it was reported as lost/stolen and it was not (of this I'm sure because in Colombia you can consult a centralised database on any carrier's webpage). Also.. Here in Colombia it is illegal for carriers to lock phones.
Steps I took to fix it:
Downloaded ROMs for all carriers, branded and unbranded, I even installed one from Trinidad and Tobago and a LATAM one.
I performed all the tricks to disable and enable flight mode, location services, try con connect manually to the networks, changing to GSM only, GMS/CDMA, international roaming, etc.
I also extracted modem.bin from an earlier version and flashed the modem.bin with Odin (6.0.1 moden on 7.0, 5.1.1 moden on 6.0.1 and 5.1.1 moden on 7.0). All modems flashed correctly and the issue remained exactly the same.
So I finally gave up.. I installed the latest stock ROM which was an unbranded Nougat (7.0) version and took it to a repair service and they fixed it in a couple hours.
What I noticed after the phone was "repaired":
- The phone was rooted, SuperSu was installed, no other root app was installed.
- On SuperSu, there are entries for ADB shell (they all say Superuser command contents have not been logged for this entry) in a two minute timespan.
- The android version was downgraded to 6.0.1, I was told not to try to update it.
- Developer options was enabled with USB debugging turned on.
- The boot option (the one where you can wipe data and cache partition) was left as original (not the TWRP one).
- The ROM used to downgrade was the same I had before but only downgraded the version.
I suspect this same procedure was performed before on the phone but it had the original ROM carrier branded so it seems as if they installed a custom ROM, rooted it, connected with pc and performed some command line stuff to fix it, then cleaned the bootloader to a stock one.
The questions:
Any ideas what did the repairman do to fix the phone? Also, would it be safe to make a full backup with TWRP and flash again a stock ROM upgraded to 7.0 and then flash the backed up modem to get it working? Or would that possibly screw up the repair?
Thank you all in advance for any help. I'm sure there are lots of people out there experiencing the same "emergency only" issue I had but there does not seem to be a fix around, but clearly there is one! So I hope this sheds some light into what could possibly happen.
I purchased a 2nd hand Galaxy S7 Edge from someone on Facebook Marketplace. It's a dual sim model (which is not directly available in South Africa) - When I collected the phone the old owner manually removed apps which I found to be strange as I was planning on doing a factory reset anyways, but he said I first had to update the phone before I can do a reset. Once I got back home and put the phone of WIFI > Software update I got a message saying that the software was not verified (leaning towards the phone being rooted). I also saw that he had multiple copies of Whatsapp which I knew was not possible with a normal ROM.
Not wanting to constantly see his personal info, I decided to reinstall the base S7 Edge software I found sammobile.com - Using odin this worked and I was able to reset the phone, but now there is no network coverage at all. I have tried everything, even downloaded a different version (both XDA and XDE) but no luck. I took it to a cellphone shop and they say they think the moterhboard is faulty which I doubt, when I got the phone and put in my simcard the first time around there was no network issue at all, this only started once I reinstalled the original rom from Samsung.
My understanding now is that the phone was likely purchased in UAE or Dubai and the network was unlocked (not sure how this works) - When I reinstalled the default samsung rom the network lock is back and I can now not use the mobile device with my local provider.
What options do I have? Is there another rom (even if it's not samsung, happy with anything) I can use on the device? I presume they had a different rom installed anyways to get it working in the first place, but I was stupid and never made a backup of the rom so now the phone is nothing more than a wifi device.
Any assistane would greatly be appreciated!
I have been at this issue since Saturday and gone through a lot of possible solutions but to no avail. So first of all i am in Ghana. A friend came to me with his s6 edge that he had some issues with his phone going off when he unplugs the charger and getting stuck in a bootloop when turning it on unless he plugs a charger in before it boots up fully(even with full charge)
So first of all he wanted to do a factory reset(phone was not rooted). Factory reset completed successfully but issue still persisted.
Specs of the phone was:
android 5.0.2
model number = SM-G925F
original csc (i wasnt able to note that down because downloading stock firmware was going to be the last ultimate weapon. first i was going to try some custom roms to see if it fixed the issue. Besides it was working fine here in Ghana.)
So that's when i flashed a twrp and i dont exactly remember but i think i might have tried to flash a lineage OS or something. But long story short, when u try booting up, the samsung galaxy edge screen with powered by android came on and stayed there. and it did not go on to boot up.
After trying through the night i then decided to use the ultimate tool and flash a stock firmware. Try as i might none of them got past the "Repartition Operation Failed" portion of flashing it. The Pit File was becoming an issue. Tried firmwares for my country, countries nearer to us, contries in africa and finally even european firmwares. And since from reading from here and other forums that the F variant was an international version the international pit files should work but they werent.
All this while whenever i go to Odin Download mode on the phone, the product name there was SM-G925D. This started the confusion because at that point i had looked through alot of firmware and that was not an option. When i searched google for that, the search results mostly correlated it to SC-04G, which looking at it was a Japanese firmware. I didnt want to use a japanese Firmware for obvious reasons. At least i wanted a firmware that was by default in English. But after about 2 days and seeing a lot of answers saying stuff about going to settings and checking stuff there plus me wanting to see an interface and work my way from there i succumbed.
And lo and behold, it flashed on the first try(i used the 4-part files firmware. It was android 7.0). But when it came to booting up, the splash screen had changed from samsung bla bla bla powered by android to NTT DOCOMO powered by android. But it booted up and i skipped through the setup. i had to change the language to english but there were a lot of japanese bloatware that came with it. But as i expected when i popped a sim card into it, and restarted the phone, there was the not available symbol(circle with a bar across) where the network bars were supposed to be.
Seeing that this was not going to do, i went to the settings this time to check on any important details and this were the new details
android version 7.0(January, 2018)
model number=SC-04G
build number was now SC0.....(cant write the full code as im currently in odin mode)
But obviously it was the japanese network. After this i have downloaded more firmwares and they all fail at "Setting PIT...Re-Partition failed". Somtimes i try to mix the 4 files up using maybe the CSC portion of the Japanese firmware but BL, CP, and AP of firmware from my region. This time the error is "sboot.bin failed".
And that has been my grind till now. Downloading likely firmwares and all failing to doing extremes like the mix and match. When the mix and match with BL, CP, and CSC of Japanese with AP of my region works and eventually boots up, there is no touch input. The touch does not work. When that happens i just have to start all over with the SC-04G, which never fails to work.
I have even seen some things about changing csc files in the file explorer with root so i flashed the Japanese FW and rooted it. Went through the processes but to no avail.
PS:
The first part of the Odin screen where you choose to continue or reboot is now completely in Japanese whiles it was formerly in English.
And there is no indication on the phone itself that it was from Japan. The back says Samsung and below it says Galaxy s6 edge. Friend bought it from a shop in Ghana here brand new.(not from a carrier)
****So here lies my confusion. How come a phone with an original model number of SM-G925F have a Product name of SM-G925D in Odin and hence only Flash Japanese Firmware SC-04G(CSC code = DCM) but would not flash any of the international variants. Even if i can eventually get the Japanese firmware to read the sim card we can manage it that way. But thats for when there are no options left.
So please i would like to know your ideas as to how this is happening and any possible solutions that might be different from what my batallion of open tabs are telling me. You can also let me know if you want any more details i might not have included. Looking forward to hearing from you guys.
Update On Issue
I ended up using the japanese firmware in the end because it wasnt picking anything else.
This time after the setup process, it picked up the sim card and the imei is available. So since network is now available i just rooted it with cf autoroot and removed the japanese bloatware and everything looks normal now.
Except the original issue of going off randomly whn power cable is pulled out even when having full charge.
:good: