So, Here is what happened.
I had January 2018 security patch, but I wanted the latest version. And I have hard bricked my device once, so the only way I can update my software version is 'TWRP FLASHABLE ROMS' So I used Indian variant one and I lost my IEMI number, there are no signals and I don't have EFS BACKUP.
PLEASE IF ANYONE CAN HELP.
Related
Sold my galaxy s via ebay last week, had the phone over 9 months no problems.
phone was unlocked and rooted and advertised that way, also had oclf installed. Buyer emailed me asking if he could reset the phone. I advised him that it had to have oclf removed etc. before he did this.
He returned the phone yesterday to me as faulty. It now says emergency calls only and the update that was available on kies, is no longer available and it only had 2.2 froyo installed previously.
How do I get it back to stock uk orange firmware and is the emergency calls the problem of the csc file as most people suggest.
Cheers
Sean
Sent from my GT-I9100 using XDA Premium App
Got a copy of original Orange firmware or find one .
Or try post 44
http://forum.xda-developers.com/showthread.php?t=1032437&page=5
Wrong CSC only means network manual entry of details .
jje
still not workinginggggg
still not working no product code showing. on spooffw, an error shows "the folder/efs could not be found. so wont update. how do i update
the product code xee(nordic) shows when using 272 imei on phone, but i need/want uk orange and the fimware installed is i9000xwjp6
i stll have the emergency calls only fault....phone worked faultless for months
sean
If I remember correctly, /efs contains IMEI and radio adjustment data. This is essential for phone operation, is individual for each phone, and is signed.
I wonder if a /efs from another phone would work, but first check if /efs is an existing directory on your phone. There is a trick for recreating the MD5 signature there is that is missing, I think.
Sorry for the vague pointer, but I've never had this problem (nor rooted my phone nor backed up /efs) myself.
I hope you have a back up of the EFS folder because as has been mentioned that contains IMEI details and stuff which is unique to your phone. Assuming replacing your efs with someone else's actually works, it's still illegal to do.
I'd say OCLF is the most likely candidate for removing it since it is outdated and dangerous and known to corrupt stuff. It has been superseded by newer, safer and more effective methods long ago which is why it has not been advocated or even supported by the dev in a long time. Probably was not removed properly before flashing or something.
The CSC has literally nothing to do with this.
i dont have a back up of my efs file
I believe (but can't swear to it) that I've managed to change my build number with flashing various roms. My number now is NXT-C900xxxx where xxx= software version. Before it had a more random set of numbers. I'm beginning to think this change has stopped my ability to apply standard ota updates.
I've downloaded the full B133 Rom, flashed the four partitions as stated on the unlock / unbrick tool. I also flashed the userdata.img file so I'd have my themes.
I then re-locked the boot loader using the method where your phone stated its locked, not relocked.
I thought as this point I should be able to apply the full b133 update.app file yet I get an error saying incompatible device. I've tried other update.app versions and I get the same issues. Also tried the ota update check and that states no updates available.
Does anyone have any ideas to get me back to a valid build number?
Thank you.
for that, ull first have to check which regional firmware u had in the first place unfortunately, we are not at a stage yet, where we can fully convert a phone as to be able to receive OTA updates, thus fool the update servers that this is the actual phone. were only capable of crossflashing firmwares, but this still makes it a modified phone, more or less...
this is why were tinkering with oeminfo backup and flash in others thread atm, this is a step towards enabling a user to fully change a phone model!
Is there any way (it's not printed on the box or anywhere else that I can see) I can find out my original region?
This may be help.
hw/eu for Europe and...
Hello guys I'm new and partially retarded. I can compute quite well but modding phones on this level is very new to me. I severely need help..
I SDcard loaded the Oreo fw from the ZTE English site and the support area mentioned nothing about "don't upload this Oreo fw to your Chinese a2017 b15 on 7.1.1 or you'll lose all modem function" and so I loaded it no problem and now the phone reports I don't have a sim card installed. When I downgraded to 7.1.1 again using another u fw I noticed it found the sim card but it can't get service still. Also now, when I tried to sdcard load the b15 nougat firmware from the Chinese zte site in recovery mode, I get footer error 21 and I can't upload the Chinese firmware now either. I'm seemingly stuck as an a2017u on a Chinese a2017 hardware chassis. I can only use the Wi-Fi and everything else on the phone. I get no cell service.
Apparently it's not bricked but I severely need guidance on returning this to its former a2017 b15 firmware so I can go back to using it with only 3g on my 4g LTE plan.
That's actually why I updated. I've had this phone second hand from a friend who claimed he had the 4G and LTE service when he was still with Cricket last year. I am starting to doubt that being truthful as Cricket reps could not get me 4g service no matter what.
Please help thank you.
@jdk309: You say Cricket (owned by AT&T) is your carrier, so I'm assuming you live in the US. But you have a Chinese A2017. As I see it, you have 2 viable choices:
1. Flash A2017 pure stock firmware. But then you will not have the Google apps, like Play Store. The A2017 doesn't support most of the 4G LTE radio bands that most US carriers use. I have heard talk elsewhere of adding new bands with QPST/QFIL, but never heard of anyone being successful with an A7. Mostly for other phones that use a Qualcomm chipset, of which the A7 is one of many. So you will still be limited to 3G.
2. Flash A2017U stock firmware, then you will have native English support and the Google apps. As I understand it, you will then need to flash a Chinese modem to get your SIM card and cell service working on the U ROM. Which modem you need depends on the firmware (Marshmallow modem for MM, Nougat for Nougat, Oreo for Oreo). But you will still be limited to 3G. Easiest way to flash a modem file is to use Axon 7 EDL tool. Or you can unlock bootloader, flash TWRP, then install the proper modem zip file.
I recommend using EDL and A7 EDL Tool or MiFlash to flash the firmware.
Other options are to flash a non-stock custom ROM, like LineageOS. Then you will have much more customization capabilities. But you will still need to use the proper Chinese modem. You call also sell your A2017 and use the money to buy an A2017U. Then you will have full 4G support.
I myself own an A2017U, live in the US, and have T-Mobile as my carrier. I have full 4G LTE service, no issues at all. But I have never tried to use the Chinese/Global A7 variants on a US carrier. I am mostly just repeating what others have said, so take it with a grain of salt.
Hope this helps!
AnonVendetta said:
@jdk309: Hope this helps!
Click to expand...
Click to collapse
More than you know! Thanks!!
@jdk309: A modem file will usually be named as NON-HLOS.bin. Install/unzip A7 EDL Tool, put the file in the right folder, boot to EDL, then flash. I'm not sure if flashing EDL zips requires an unlocked bootloader, I have read that you can brick the phone if it is BL-locked. Not sure, be careful. My BL is always unlocked, so I never have to worry about/consider it.
AnonVendetta said:
@jdk309: A modem file will usually be named as NON-HLOS.bin. Install/unzip A7 EDL Tool, put the file in the right folder, boot to EDL, then flash. I'm not sure if flashing EDL zips requires an unlocked bootloader, I have read that you can brick the phone if it is BL-locked. Not sure, be careful. My BL is always unlocked, so I never have to worry about/consider it.
Click to expand...
Click to collapse
Thank you I will keep that in mind. Yes Im in the states just as you are. I just remembered and located two screenshots I took of my old phone's firmware info page and I was wandering if you could glean any information from it that might help locate the original firmware that I was running. The two photos are in my username's page under a new photo album I created.
A2017v1.1.0B15 was the build info. Have you ever seen that anywhere on here where it has zero chinese bloatware or incomplete translation (chinese language remnants) and full 3G capabilities? Its so odd that I cant find anything like it online. Your help is greatly appreciated!!
@jdk309:
For B15 Oreo Firmware:
https://androidfilehost.com/?fid=1322778262903996734
I found another B15 file:
https://androidfilehost.com/?fid=745425885120758937
One file was published in 2017, the other in 2018. I would use the newer file, if you want Oreo. Both are Chinese firmware for the A2017, 100% original and untouched, you should even be able to install OTA updates when they are released.
You may also be able to get an A2017 Oreo SD Card zip from the ZTE China support site. I don't know Chinese so you'll have to find it yourself. Not sure if they released an SD Card update for the A2017 though. Just place on SD Card and install from stock recovery. Or you can install from TWRP with my steps (just substitute the A2017U file with the A2017 file, all other steps are the same, and remember to install Chinese modem afterwards):
https://forum.xda-developers.com/showpost.php?p=77890409&postcount=4
I had recently updated my moto g5 plus phone potter version xt1687 to oreo with the september OTA update( i downloaded the update with cellular data) and when i did the imei was set to zero i updated it again with wifi to october security update but nothing happened. After looking throughout the web and trying various methods such as : Downloading pixel experience to get imei, downloading stock rom to get IMEI, and using persist fix from online. None of these has worked. Could anyone here help me out with putting back my imei number, i do have it down on paper as i have the phone box still.
Hello everyone,
I explain you my problem:
I tried this morning to update my samsung galaxy A41 SM-A415F rooted with Magisk (firmware patched via magisk) to the latest version (A415FXXU1CUH2) that can be seen on sammobile :
Download Samsung Galaxy A41 SM-A415F XEF France A415FXXU1CUH2 firmware
So I tried to update the phone by setting the HOME_CSC to odin but what was the surprise when the phone rebooted? Some partitions were corrupted and I had no choice but to reset the phone.
I wanted to reset the phone with the last ROM and so I started the installation on odin BUT I checked the option "Nand Erase" and "Re-partition" and since then the IMEI number has been deleted and I can't put it back nor send messages / calls etc.
I have searched everywhere on the internet and even trying to put back the last ROM doesn't work and when I want to do *#06# the message: sm-a415f is not supported on showIMEI is displayed
After a while I found a tutorial on the internet that said I had to put the .pit file of my rom in the "PIT" tab on Odin in addition to my ROM because I had deleted all the partitions of the phone... I checked the Re-Partition option in addition to F. Reset Time & Auto Reboot to register the .pit but it didn't work, I always get 2 errors: One when I reset the phone before the menu with all the apps is displayed telling me: "IMEI or MEID is empty" and another one when I try to see the IMEI number when I press *#06# in the phone app telling me: sm-a415f is not supported on showIMEI
I thank you in advance for your help,
Sincerely.
Edit:
Oh yeah, and the phone doesn't detect the sim card even when I take it out and put it back in...
Hello,
i also have a similar problem.
I rooted the samsung A41 smartphone with magisk. After a while, I wanted to go back and put the original firmware back. Everything worked until I installed update A415FXXU1CUH2. Now the IMEI is empty and the sim card cannot be used. I went back to the A415FXXU1CUD4 version and now everything works fine. I initially blamed all these problems whit the root, but looking around on web I saw that the IMEI problem happens.
Can't read SIM cards after the latest update
Hello, I received and installed a firmware update two days ago. I noticed cell signal icon was replaced by a crossed circle; . Also, the options for 4G and 5G are nonresponsive, the menu options are not greyed out but they are unresponsive when pressed. So I can't connect to my cell service...
eu.community.samsung.com
Samsung A21s software update problem
After the last update.. I have lost my connection to 3g/4g ... my phone only connects to my home wifi... but doesn't connect anywhere else. Any advice?
eu.community.samsung.com
Problem: IMEI is null after updating to A415FXXU1CUH2. Cant call, message or use data.
Solution: Flash earlier firmware or restore from your full backup.
I confirm this IMEI problem and that the @Arazon´s solution works.
I tried to update the phone to the latest stock firmware Android 11 (A415FXXU1CUH2) from an earlier version. I got everything to work except the IMEI showed null. I tried flashing with both root and non-root. I tough I had broken the EFS-partition but luckily that was not the case. Somehow the IMEI could not be red with the newest firmware. I guess Samsung needs to fix it and we have to wait for a few months? Anyways I will try updating the A41 "the normal way" and then flashing my root after that. Maybe it will work.
I wonder when we get the unofficial LineageOS for the A41 SM-A415F. Hit me up if you are up to it, I might be able to help.
Judxx said:
Problem: IMEI is null after updating to A415FXXU1CUH2. Cant call, message or use data.
Solution: Flash earlier firmware or restore from your full backup.
I confirm this IMEI problem and that the @Arazon´s solution works.
I tried to update the phone to the latest stock firmware Android 11 (A415FXXU1CUH2) from an earlier version. I got everything to work except the IMEI showed null. I tried flashing with both root and non-root. I tough I had broken the EFS-partition but luckily that was not the case. Somehow the IMEI could not be red with the newest firmware. I guess Samsung needs to fix it and we have to wait for a few months? Anyways I will try updating the A41 "the normal way" and then flashing my root after that. Maybe it will work.
I wonder when we get the unofficial LineageOS for the A41 SM-A415F. Hit me up if you are up to it, I might be able to help.
Click to expand...
Click to collapse
I tried updating the A41 with bootloader locked but the results were the same. It seems that if you have tripped the Knox (voided warranty) the recent update A415FXXU1CUH2 will somehow break your imei and it will show up as null.
These firmware versions (root or non-root) do work and the imei problem does not exist even with tripped knox and unlocked bootloader:
A415FXXS1CUG1
A415FXXU1CUD4
A415FXXU1BUC3 and older