I did this via Magisk, and network/IMEI/baseband were permanently gone after receiving a call. Unrooting and reflashing stock via Odin does NOT fix it.
Same issue(and a partial solution) has been discussed for A32 4G in thread https://forum.xda-developers.com/t/fixed-rooted-a325m-suddenly-no-imei-no-sim.4386753 and also in Russian 4pda forums.
(Details: As soon as a call ends in a rooted device, a file named IP21_000 is written by system in NVD_IMEI folder, resulting permanent signal loss. So, idea is to remove this file and then write-protect NVD_IMEI folder by using 'chmod 550 NVD_IMEI' command in adb as superuser. 4pda forum suggests a less drastic measure of overwriting IP21_000 with an empty file and then applying write-protect permission only on that file, instead of the whole NVD_IMEI folder. If either of these doesn't solve the issue, remove entire NVRAM folder, reboot and then again apply write protection command before making/receiving any call. Even after making these dirty fixes, temporary signal loss of 10-20 secs occurs after each call ends, as possibly the modem crashes and restarts. Unrooting and reflashing stock via Odin afterwards has no effect on this.)
Some other common problems encountered during dirty fix above:
1. NVRAM is inaccessible for some time after deletion. (It is always regenerated after a reboot)
2. IMEI/Baseband appears but call cannot be initiated.
3. In SIM manager, both SIMs appear active when only one SIM is present.
4. When empty SIM2 is turned off, you sometimes get funny messages like no SIM card active, even when a signal is present from SIM1.
Other solutions might be expensive: Using paid apps like Chimera/Z3X tools to repair NVRAM/EFS/GodKnowsWhat , or approaching samsung service center to reprogram/replace the motherboard.
Samsung galaxy m32 prime bootloader unlock failed fix issue rooted firmware please uploaded M325FXXU4AVB1 bootloader unlock failed this issue fixed twrp
Related
Hi Everyone,
I have a phone, the Huawei Ascend P7 -L10.
Some weeks earlier I tried to install Spotify in my phone, but I didn't manage to install it. After several attempts I end up crocking my phone.
It happened when I found some app that had apparent solution to solve Spotify installation problem. I don't remember the name of the app. Anyway, I found it effective so I tried to follow the instructions given. I made it, then the changes were effective. What the app does is to change the phone model and respective carrier.
All the dilemmas started when I decided to restart the phone.
Here goes what I've done so far after the incident.
1. I tried by myself to restore/upgrade the system. I've experience doing this.
2. I took the phone to the 1st Repair Agency - they did not fix it
3. I took to the 2nd Repair Agency - the same thing, they fail to fix it
Note: When you try to restore the phone it gives the following information “update failed!"
and when you normally try to switch the phone on it stop on black screen and nothing else, I've also tried wipe cache, wipe data everything but nothing. Please help!!
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
es0tericcha0s said:
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
Click to expand...
Click to collapse
Thanks for your replay. My device is rooted one, but the problem is, I can't login not even connect it via cable (using e.g. HiSuite). So, how can I pick up the file from phone?
Hello,
My LGE Nexus 5 (16GB) recently got stuck during booting. I had to flash the factory image (6.0.1). I want to recover data.
In order to do so I downloaded a data recovery program: "Dr.fone for Android". This told me to root my phone. Which I did using https://autoroot.chainfire.eu/. I have SuperSU Free v2.74.
The data recovery program confirms my phone as rooted: http://imgur.com/a/C7gF7.
However when I attempt data recovery, it doesn't prompt me with a message (when it should): http://imgur.com/a/1rMRg. I can continue to start the data analysing process anyways, during which it will prompt me for SU access, but the data recovery always turn up empty.
I downloaded another data recovery program, EaseUS, to pinpoint the issue. EaseUS simply says my phone isn't rooted: http://imgur.com/a/nfXVh. Which is quite a contradiction.
So.. I looked for another way. I came accross this thread: https://forum.xda-developers.com/showthread.php?t=2450045. However my Nexus 5 DOES NOT HAVE AN SD CARD. I looked further and found: http://www.nburles.co.uk/android/recovering-data-from-an-android-device-using-dd. I installed cygwin+nc and on the phone Busybox v1.26.2-meefik (which contains nc for phone).
So I tried to follow the second guide again, but I kept running into the issue where no actual data was being sent. In my attempt to pinpoint the issue I found that the tcp connection between the phone is not being established properly: http://imgur.com/a/ooe1J.
- If I type anything from my laptop-shell it instatly shows up on the phone-shell. (expected behavior)
- If I type anything from my phone-shell it will instantly echo back. (as if it is connected to itself?)
- If I type anything from my phone-shell it won't show up on the laptop-shell. UNLESS I send 2 messages from the LAPTOP-shell, as if it needs encouragement (1yes I hear you, 2you may talk?).
Using this knowledge I was able to start dd'ing some data to my laptop, however I need to send 2 messages from the laptop shell for each 16Kb chunk of data. http://imgur.com/a/WvrIH. If I want to make a dump of my 12-16GB data I would need to send roughly 2 million messages. As close as I am, this is no solution.
I have searched the internet, but my the guides and tutorials don't venture this deep. Dear XDA, please help me with this issue.
Dear xda-community,
My phone: Honor 9 lite, non-branded, android 8, magisk installed. Running unofficial lineage-os 15.1.
Since 2 days now, after I enter the SIM-card's PIN, it says "SIM network unlock NCK" unlock/dismiss like in the attached picture.
How I tried to fix it:
* factory reset
* using different sim card
* flashing another ROM
* restoring a FULL TWRP backup of stock ROM (bck includes: kernel, ramdisk, cust, oeminfo, product, system, system image, vendor, vendor image, version, odm)
* TWRP -> advances -> fix contexts
* I also changed the permission of the sd-card with chmod +rw. I don't think I accidentally did that recursively on the / directory. But to be sure, I also ran the fix_permissions script following this guide: https://www.drewgreen.net/2012/03/15/manually-run-fix-permissions-from-recovery/
How it probably happened:
I was trying to delete content of a microsd-card in my phone. I used adb shell su went into the sd-card directory and executed rm -rf ./
However, I accidentally forgot the "." before the "/" :crying:
The terminal got flooded with "... read only file-system", since most is mounted as read only. But maybe somefiles were deleted, that I couldn't see in the terminal (scrollback buffer was full) .
Does anyone have an idea
1. why the error still exists after a factory reset (both with twrp and stock recovery) and even after restoring a full twrp backup?
2. how to fix this? Or is the problem unrelated to the stupid thing I did and just coincidental?
I am very thankful for any help and appreciate whoever takes his time to help me.
*UPDATE*
I used my warranty and my phone got sent to honor. Before, I relocked the bootloader and flashed an updated stockrom, so 1. they didn't see I immediately (at boot time) that I tampered with the phone and 2. I could tell the shop that it happened while installing system update.
they didn't charge me anything and it works again.
were you ever able to resolve this? i have the same imei and nck issue.
MateUserHHTT said:
Dear xda-community,
My phone: Honor 9 lite, non-branded, android 8, magisk installed. Running unofficial lineage-os 15.1.
Since 2 days now, after I enter the SIM-card's PIN, it says "SIM network unlock NCK" unlock/dismiss like in the attached picture.
How I tried to fix it:
* factory reset
* using different sim card
* flashing another ROM
* restoring a FULL TWRP backup of stock ROM (bck includes: kernel, ramdisk, cust, oeminfo, product, system, system image, vendor, vendor image, version, odm)
* TWRP -> advances -> fix contexts
* I also changed the permission of the sd-card with chmod +rw. I don't think I accidentally did that recursively on the / directory. But to be sure, I also ran the fix_permissions script following this guide: https://www.drewgreen.net/2012/03/15/manually-run-fix-permissions-from-recovery/
How it probably happened:
I was trying to delete content of a microsd-card in my phone. I used adb shell su went into the sd-card directory and executed rm -rf ./
However, I accidentally forgot the "." before the "/" :crying:
The terminal got flooded with "... read only file-system", since most is mounted as read only. But maybe somefiles were deleted, that I couldn't see in the terminal (scrollback buffer was full) .
Does anyone have an idea
1. why the error still exists after a factory reset (both with twrp and stock recovery) and even after restoring a full twrp backup?
2. how to fix this? Or is the problem unrelated to the stupid thing I did and just coincidental?
I am very thankful for any help and appreciate whoever takes his time to help me.
Click to expand...
Click to collapse
@AShah85
Unfortunately not.
I brought it to the shop were I bought the phone and they then sent it to honor. They fixed it free of charge but never told me what they did.
I bought this phone in Germany, where simlocking is illegal. They buy them elsewhere and unlock them for the german market. Apperantly I (somehow) undid this unlocking.
I'm not familiar enough with this topic, but I don't think you can change that with regular tools and probably need a key which hash is stored on the phone.
In short:
I used warrenty to fix it. I relocked the bootloader (to get rid of that "phone cant be trusted" screen at boot time) and reflashed stock rom (some newer one) and told them this error occured when I was trying to upgrade (cuz this apperantly indeed happens sometimes, search the internet...).
Hmm thanks for the reply. I guess I'll have to take it into the shop and see if they can figure it out.
I have a Razer Phone 2 rooted with magisk. I use GPS Joystick. I decided to select the "disable system GPS" setting in its options. I rebooted as the app requested and now my phone loads to the point where it wants me to enter my pin and I see my wallpaper for a split second then the screen goes black and it loads up the status bar about ever 10 seconds for a split second then it repeats. Like it is stuck in a loop. After a couple minutes phone reboots and I get this message...
Android Recovery
razer/chery12/aura
9/P-MR1-RC003-RZR-190305/3110
user/release-keys
Use volume up/down and power
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Click to expand...
Click to collapse
So I reached out to the dev of GPS Joystick and he explains that the option disables the location services called "fused location provider" and I have to re-enable it to fix the problem. He sent me a post here explaining that I need to pull an .xml file from the phone, change the code, and push it back. Simple right? Well maybe if I have TWRP, but I don't. I can however boot into the phones recovery options and there is an option there to "apply update from adb" but I cannot seem to pull anything using that interface. My Windows computer recognizes the device using Minimal ADB and Fastboot but it shows it as a whole bunch of numbers then the word "sideload" which I guess is a limited form of adb just for side loading? Maybe someone could make me a script that I can sideload that changes the file back to normal? Here is the code from the dev of GPS Jostick that is used to disable and enable the fused lcoation provider.
It calls this code to disable:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 0);
And similar code to re-enable it:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 0);
Click to expand...
Click to collapse
So my question is, can I pull this /data/system/users/0/package-restrictions.xml file from my phone and push it back without using TWRP? But instead using the phones recovery option and its various selections? I'd prefer to exhaust the resources to recover the phone since I have spent weeks personalizing it. I am not fluent in adb but I am hoping someone can throw some ideas or even a solution at me that I am missing. All I got to do is pull a file, change a word, push it back and reboot. I can't imagine there isn't a way to do this by just using what the phone has to offer. Any help would be greatly appreciated.
Another idea that came to mind is in its current condition could I install TWRP? Is fastboot an option at this point? Maybe if I can flash TWRP in its current state I can then make the appropriate modifications.
I ended up fixing the problem. I installed arter97's kernel that had TWRP baked into it. I then used TWRP to copy over the .xml file, change the code as mentioned above, and then copied it back to the phone. Problem solved. It is amazing how one simple word in a .xml file can prevent a phone from functioning properly. It simply amazes me.
Hello guys, first of all: thank you very much for your Forum; I'm learning a lot even if I remain a complete noob!
I'm trying to use LineageOS 17.1 (lineage-17.1-20210118-UNOFFICIAL-a3y17lte, recovery OrangeFox 11.01) on Galaxy A3 2017 (SM-A320FL), and I did something really stupid trying to make Link2App work.
I had problems to format properly the miniSD using Android's apps, and I could not remove the card from the phone (the slot's opening is damaged). So then I tried to format the card using ADB + BusyBox + fdisk, BUT I did it while I was distracted by other job's issues, and I didn't realize I was working on the internal SD instead of on the removable card (yes, complete idiot...).
Result: a brand new empty partition table in my phone, permanently stuck in Download mode (impossible even to power off it).
I tried to restore the phone using this procedure, but it failed midway. By the way, I could Odin-flash TWRP and then restore the partitions using the repartion script. Eventually, I fleshed my OrangeFox and LineageOS: the system is now perfectly working, but the phone doesn't recognize any more my SIM and IMEI (dialing: *#06#) is blank.
I had a Fox's "light" backup, but it didn't solve anything.
I'm still having the original box with the IMEI number on the label, but I didn't find a suitable procedure to use it.
Kies3: the SM-A320 phone seems too old to allow the Initialization procedure described here (yes, the phone was unplugged)
There are many apps promising miracles (for instance: ToolHero, MTK Engineering Mode, IMEI Generator Pro, EFT Dongle...); however, I tried some, and they seem to me just ****ty pieces of software, requiring the original system or dubious paid services.
Dialing codes* procedure (like Method 1 here). I cannot remove SIM or battery to complete the procedure. Besides, my phone doesn't react to the code; probably they are country or SIM specific...
Line command (terminal emulator or ADB): this seems to be the most promising method; however, the line
Code:
echo 'AT +EGMR=1,7,"MY_IMEI_NUMBER"'>/dev/pttycmd1
doesn't do anything on my device
IMEI generator: I tried to generate a new MP0B_001 file using this guide. The download link is broken, then I downloaded the files from another source, and I prefer to add to my system just the MPB_001, without flashing the "repair" tool. Besides, I don't have any /nvram folder in my $root/data/ directory... (the only IMEI related folder is in $root/eps/).
Any suggestion to solve this mess? Thank you very much!
Daniele
* EDIT: after typing *#*#197328640#*#* the phone window closes.
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
jwoegerbauer said:
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
Click to expand...
Click to collapse
Thank you very much for your answer! The 2-3 methods seem promising; however, I isolated the problem and solved it before receiving your message.
The problem: after messing with the partitions, I tried to restore my system, downloading the files via Freja. However, I select the wrong CSC, using my SIM provider code (TIM) instead of the generic code for Italy (ITV).
I noticed it exploring the light backup I had done in TWRP (only System partition): a CSC_version.txt was there, pointing to A320FLOXA9CTK1 (ITV version, while I restored using A320FLTIM8CTH1, TIM carrier version). ITV was also mentioned in the file $ROOT/eps/imei/mps_code.dat (dunno if this is relevant)
Solution: Odin + the right firmware did the trick. I had my IMEI back and the phone working, then I came back flashing TWRP, Orangefox and, eventually, LineageOS.
Everything is working now, and, of course, I backed up EPS partition (now).
Many thanks!
daniele