Hi, I updated my N920G from LP to MM yesterday, Stock Rom N920GUBS3BPI2_N920GZTO3BPI1_N920GUBU3BPI2, after the I update I get emergency calls only, If I go into settings, I cant seach for networks or see them.
My Imei is not corrupted or blocked, I tried flshing several Modems from other Roms and the result is the same.
Also tried Smart Switch(Emergency Mode) it downloads the firmware but fails to flash.
Problem solved
efs partition was corrupted, had to repair the imei
Related
Hello everyone i am new to rooting and flashing devices and kinda stuck with a problem. I have a Samsung Galaxy s with
Firmware 2.3.3 Gingerbread
with Build number DDjv9
I tried flashing the the rom using oden3 with CF-root....tar file and then installed superuser through recovery...At 1st the phone was stuck in a loop and it kept rebooting ..i tried another cf-root file and that fixed the looping and rebooting problem ...Now ths issue is it dosnt detect my sim card...and dosnt allow me to use wifi...i tried many other files ...tried factroy reset frm recovery and even tried to reset using the code...noting works the phone just resets and i can see superuser app in the menu...
Really wish i could get some help on how to get my simcard to work again and wifi..Or even get my phone back to stock rom.
Thanks in advance
Have you tried reflashing with another romhttp://forum.xda-developers.com/showthread.php?t=1136449)? Did you backup your efs folder (using for exemple nitrality), if you did, try restoring your efs folder.
My phone first was stuck on boot-loop and in recovery mode it was giving error "failed to mount /efs"
I tried flashing different roms but none seemed to work until I found N7000ZSLPF_N7000OZSLPF_OZS, it did install but now my phone doesn't detect sim card and its IMEI is also blank\undefined. My phone is an unlocked\international version so there is no question of any country\carrier lock.
I switched to recovery mode and it still gives that efs error.
Any help will be highly appreciated to solve this problem.
Hi,
I've got a hard bricked Galaxy S3 LTE (i9305). I got it with a message, that a software update failed and that I should connect to Kies, to fix this issue. I've tried that multiple times, but it never worked and Kies cancelled the repair every time. After that I tried to flash a stock image with Odin. The phone turned of to reboot, but never started again.
Now the phone isn't turning on at all and isn't recognized on my comouter via USB.
I've read that there is the possibility of restoring the bootloader from an sdcard on other models. Does this method work on LTE models too? If yes, where can I find a image for the sdcard?
witti
Hi. i am having a galaxy note (n7000). After flashing it with cyanogen 11, everything works perfectly alright except data and call services. Initial there will be data and call services. After sometime there will be no data and call services even when its showing full signal. it occurs when the network changes to H data mode. when it becomes H+ mode or E mode , i can use data as well as i can call. Sometimes it shows emergency calls only. Before flashing this custom rom, such an issue was not there. Anyway, i then flashed it with Slim-n7000-4.4.2.build.4-OFFICIAL-3657. Its a great rom but this problem still remained. Assuming that the custom roms might had some bug, i then decided to flash the stock rom(jelly bean 4.1.2) using odin. And to my horror, the problem still remains. i tried flashing with another firmware and still there was no change. now i cant install cwm recovery or tmrp recovery.
it shows status 7 error. i used the same file at the beginning. But now that too doesnt work.
I feel so exhausted :crying: . Please Help me to solve this problem.
Thanks in advance.
me too same problem
I made the mistake of flashing the wrong version of TWRP using Heimdall, causing the device to get caught in a boot loop. Initially, I couldn't enter recovery or download mode to re-flash the firmware, but after disconnecting the battery to shutdown I was able to get back into download mode and flash a stock ROM (downloaded from SamFirm).
After flashing the ROM (now using Odin) and auto rebooting, I get the installing software update screen with a loading symbol (for a few seconds), followed by a boot loop (Samsung screen -> Knox warning -> reboot -> repeat).
- Power cycling the device boots back into recovery mode.
- "Reboot device" option from recovery mode enters the boot loop.
- "Reboot to bootloader" option reboots into download mode (I'm not sure why)
- Wiping the cache / factory reset between reboots seems to have no result
The phone is an unlocked SM-A305G/DS from Amazon, so I'm not confident I have the carrier version correct. The only record of the CSC version I had before was the .pit file I extracted through Heimdall before flashing the wrong firmware. It contained the string "TPA", so that's my current best guess. I have tried firmwares for TPA, CHE, and CHO but with the same results.
Any ideas what might be wrong? I imagine the device isn't hard bricked, so I don't know what else could have went wrong. Kind of a newbie when it comes to android firmware, but I have some technical background, so let me know if there's some more things I can try or if more information might be needed to debug this issue.
Some more specific questions:
1. Does the carrier code matching the device matter? If so, is there a way to find the original CSC from IMEI on an unlocked/no warranty phone? The few websites I tried don't appear to be able to get that info.
2. Is there any way to access the logs from the last normal boot attempt? (Recovery mode only appears to keep logs for itself, not normal boot)
3. Could tripping Knox somehow be the problem? I didn't think it had any repercussions except voiding the warranty (which the device didn't come with)....
4. Can Samsung support somehow help me find my CSC/correct firmware even if I don't have a warranty?
Solved
Posting solution here just in case someone makes the same mistake,
I realized that I neglected to post the information displayed in download mode, most importantly:
`KG State: Prenormal`
Googling that, I found that this might be caused because of a mismatch between my SIM card region and the installed firmware region. So I removed my SIM card, re-flashed the latest stock firmware again, and it booted :laugh:
Also, download mode displayed the correct CSC code regardless of installed firmware (I installed CHE firmware and it still displayed TPA), though I'm not sure if that's consistent across devices.