Hey Guys,
I've come across my limit of knowledge during the past days.
I purchased this new phone, "Samsung Galaxy S 7".
When I look up the "About phone" option in "Settings", it says, that it's a SM-G930F with android verison 6.0.1.
I couldnt find ANYTHING according to my Build number, which says: MMB29M.G930FXXU1BPIA or that my Smart Switch says, that the software version would be PIA(VZW).
But when I go into Download/Odin-Mode there are the following text lines:
ODIN MODE (HIGH-SPEED)
PRODUCT NAME: SM-G930V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
FAP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
So, both informations are dividing from each other, because the first says it's a SM-G930F and the second says it's a SM-G930V, except that both have in common, that they say system status is official.
But, my problem is, as you can see, it's still marshmallow that is installed on my Galaxy S 7 and in my settings there is absolutely no possibility to update my phone to nougat.
I've tried several things via Odin like installing: Stock firmware for ADB, Nougat firmware for ADB, Stock firmware for VZW, Nougat firmware for VZW
But just nothing worked out.
Most common issues I had with Odin were: "sboot.bin FAIL!, recovery.img FAIL!, Complete(Write) operation failed.", depending on what kind of files I tried to apply, like pit file, AP-File, Home_CSC-File, etc...
Even if i tried to solve it with the most common troubleshoting methods i could find on google, there would be another issue, like a never ending story.
I also tried applying a firmware with recovery mode but there it says: E: "footer is wrong” ,followed by “E: signature verification failed", even if my SD-Card has never been encrypted.
I dont have any idea what to do anymore,
so i would extremely appreciate some help of a pro, who can tell me, what to do exactly.
Thank you!
*EDIT*
I managed to unroot the phone with the verzon nougat firmware but now it won't let me use the phone with a diferent SIM-card than a Verizon's and I'm going to return the phone.
Hi,
I'm facing the exact same problem.
Which Verizon firmware did you use to unroot your phone?
Thanks!
b0rgsen said:
Hi,
I'm facing the exact same problem.
Which Verizon firmware did you use to unroot your phone?
Thanks!
Click to expand...
Click to collapse
I managed to flash the latest Verizon ROM (SM-G930V_1_20170330100826_87cd9631jd_fac). Now it is obviously branded and I always get a message (after reboot/after ending airplane mode, so everytime the phone connects to a cellular network) that I'm using a non-verizon sim card. Nevertheless, after manually adding the APN, everything works fine, no SIM lock.
Edit: it works even better with this stock ROM w/o branding: updato.com/firmware-archive-select-model?record=EF06A1ED34EB11E7963AFA163EE8F90B
Same Problem
Its showing 930f in my phone information
but when i go into download mode it shows 930v
cant update my phone it's still stuck in ****ty marshmallow
i would highly appreciate any sort of help.. TIA
b0rgsen said:
I managed to flash the latest Verizon ROM (SM-G930V_1_20170330100826_87cd9631jd_fac). Now it is obviously branded and I always get a message (after reboot/after ending airplane mode, so everytime the phone connects to a cellular network) that I'm using a non-verizon sim card. Nevertheless, after manually adding the APN, everything works fine, no SIM lock.
Edit: it works even better with this stock ROM w/o branding: updato.com/firmware-archive-select-model?record=EF06A1ED34EB11E7963AFA163EE8F90B
Click to expand...
Click to collapse
yes I get that error too, and I added the APN. it started to work but sooner or later the network drops.
---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------
androidarif said:
Its showing 930f in my phone information
but when i go into download mode it shows 930v
cant update my phone it's still stuck in ****ty marshmallow
i would highly appreciate any sort of help.. TIA
Click to expand...
Click to collapse
you have the exact same issue as me. I suggest you review this thread, it would be helpful.
In summation, you have a converted phone. you can flash Verizon's rom if you want nougat. But that didn't help with my network issues.
Same problem
is this phone is not official what's the matter please explain
I'm also having the OP's exact same problem? I thought the phone I had just bought off gumtree was fake. I'm in Australia and noted that the model one the sticker on the back on my device is SM-G930F, the "about" page lists it as SM-G930F running 6.0.1, odin lists the as model SM-G930V, smart switch as PIA(VZW), CPU-Z as having it having a Snapdragon processor and finally the paper instruction manual is for a SM-9300 (China) - WTH!?
I cant seem to figure out which device it was or is ha! I believe it may be a chinese device that has been flashed to american standard. Is the the core point here, are these perhaps all flashed/refurbed chinese models?
Long story short, i'm not having any problems but i want a newer OS like oreo or nougat - if I flash to say SM-G930U standard with XAA (generic, samsung branding), will i begin having network issues in Australia?
Related
Hi Guys,
2 months ago I bought a Samsung s5 in Hong Kong.
While travelling through South East Asia this device worked fine.
While traveling through New Zealand (Old home) this phone worked fine.
While traveling through America (New Home) this phone worked fine for the first 2 weeks (on the metroPCS network).
The problem:
Randomly after 2 weeks the s5 stopped connecting to the metroPCS mobile network even though the network was available (btw metroPCS uses the T-Mobile network). It gives errors such as network not available or cannot register with network.
Things I have tried:
-Im sure the APN settings of the phone have not changed and I have double checked to see if they are correct.
-replacing the sim card with another does not fix the issue
-soft and hard reset of the phone does not fix the issue
-Getting metroPCS to refresh the service on this number does not fix the issue
Other important info:
-This phone was purchased in hong kong but it is from the Philippians according to Kies's firmware information (XTC is the country code)
-It is running a custom allianceROM that must have been installed by someone in hongkong
-The device is rooted (superuser app installed)
-the model number as shown in settings is g900f BUT when attempting to flash with odin the phone displays g900t and fails to flash the latest Philippians verison of kit-kat
I have 2 questions:
1. Any ideas why my network connection has suddenly self destructed (and how to fix)?
2. Would flashing a stock ROM to my s5 help? and if so why is there conflicting information on which model I own (g900t/g900f)?
Please help. I do have some know how on flashing android devices but i've really hit the wall on this one guys!
Cheers,
Yetti.:cyclops:
It's not uncommon for the model # to be different with a custom rom as that is a very easy thing to edit in the build.prop. It should tell you under the battery which one it is. As far as the network issues, check to see if the baseband and IMEI are still there and not listed as unknown or incorrectly. It's possible you could get away with flashing the appropriate modem that matches with your update and that might work better in this region vs the previous one.
Please list the Alliance rom version and baseband version here in case it's relevant to your issue.
More info
Im not sure if this helps but looking through the build.prop file in the system folder my ro.product.local.region=GB
When in recovery mode the region is set to XTC (Philippians) using mutli-csc.
Also my IMEI number seems ok and is NOT blocked.
Cheers. Yetti :cyclops:
Baseband and rom etc
Thankls for your reply!
Sorry when you say "under the battery symbol" do you mean in /odins boot script on the device/ or /in settings on the phone/?
Baseband is g900TUVU1ANCH
Build Num: AllianceROM_G900F_XXU1ANCF
If the "no network" issue can be solved with the current firmware that would be the most desirable solution but going through the flashing process may be a good idea for my learning process, and will help with future updates.
Do you think getting back to a stock rom would help me?
tHANKS AGAIN!:cyclops:
Model confirmed to be g900t
Sorry i didn't understand the "under the battery" thing. I was lost in software world. The sticker under the physical battery says SM-900T so i guess that confirms that it is a t-moble verison (and the baseband is therefore correct).
I will try to flash the T-Mobile stock image to the phone and see if that works.
Also i will try to flash a modem (after i work out which one i need).
Cheers, Yetti :cyclops:
Current status.
Flashed the stock T-Mobile firmware to the phone. No success.
Flashed new modem to the phone. No success.
Will go to the T-Mobile store tomorrow to see if they can help (I doubt it but i have to exhaust all the options).
Any more help would be appreciated...
cheers, yetti:cyclops:
By under the battery I mean like to take off the battery cover of the phone and pull the battery out and look at the sticker found there.
G900t.
es0tericcha0s said:
By under the battery I mean like to take off the battery cover of the phone and pull the battery out and look at the sticker found there.
Click to expand...
Click to collapse
Yep it says g900t (see above)
As per flashing a modem. I have heard that it is possible to flash any modem for any version of the s5 to the phone. Some work well and others not so much. I have tried 2 T-Mobile modems (baseband) the G900TU1ANCH and the G900TUVU1BNG3 with no success. Do you have any recommendations for a modem to try (or even a custom ROM that might help?)
Cheers,
Yetti :cyclops:
I know that you mentioned they refreshed the service for your number, but do they have the correct IMEI in the system for your account? Metro makes a big deal about that now and you can't just take your SIM from another phone and pop it in a new one and go like you can with pretty much every other service (Cricket is like this too now).
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.
Hi all.
This is my first post and will try and make it really quick.
I recently got a Galaxy Note 5 (because their just amazing) It came with Android 6.0.1 installed and the "Software Update" section of the settings menu does nothing. I mean literally nothing. I tap "About Device" then "Software Update" and nothing happens no new screen loads or anything.
so I was looking for the OEM ROM's and this is where I ran into so much confusion. The current details the phone gives me is.
Galaxy Note 5 SM-N920F (There are no F rom's)
Build Number MMB29K.N920FTMB4DPH2
Bootloader N920TUVS6ERH1
Which lead me to believe even though their is no "F" variant, That its a T-Mobile model (No Rom's really give 100% functionality to these except the standard 7.1 from T-Mobile)
So I went to Sammobile.com to download the latest official firmware released, But the the CSC numbers don't match my device. they are all starting N920TT***** and mine starts N920FT*****. However the PDA numbers match my bootloader. So will any Note 5 T-Mobile ROM work even if the CSC numbers are different? as long as the PDA numbers are the same?
I get more confusing info from Samsung as well. The "Samsung Members" app shows my Model number as : SM-N920TZKATMB (Which again has no "F" in it, The sticker on the back of the device with the IMEI even states it as SM-N920F)
Am I making this weirdly complicated for myself? Will the US T-Mobile ROM's for android 7.1 work find I flash them with this device? (I live in the UK and the device has 100% compatibility with my network)
Also will flashing the stock 7.1 US ROM from T-Mobile re-lock the SIM ? I'm pretty sure it doesn't/Cant relock SIM to T-Mobile only, But nothings better than a professional confirming.
There is also another issue. according to "Root Checker" I have a Rooted device. But their is no Super User apps on it at all (Cant seem to even find Binaries for SuperSU when using Root File Manager), Pokémon GO fails to load which I have read could be because of the "Root Check" throwing up a positive. But no other apps fail to work at all. their all perfect even banking never even so much as an error. it is just Pokémon GO. Or has someone previously messed up rooting so it looks like it is but the files are missing and isn't really? I tried using Magisk Manager but it did nothing and I don't get any prompts for Root access when installing apps.
So Please Help Me! Thank You.
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
SOLVED
cw9002 said:
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
Click to expand...
Click to collapse
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
cw9002 said:
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
Click to expand...
Click to collapse
I am now at the same baseband version as my mom. Everything worked perfectly. I suggest you go with the least change possible to get to the point that you are able to do OTA updates. For me this was going to the latest Android 9 that they had at sammobile since I was on Android 9 and going with the Tmobile version. I hear the carrier doesn't even matter these days, but I decided I wanted to make sure it was Tmobile compatible so I chose the Tmobile version from sammobile. Happy trails to you in your endeavors. Hopefully you can learn something from mine.
Hey, I really want to thank you for this! I had the same issue and was exploring similar solutions. After several days of researching alternate plans, I was about to give it up as too risky until I found your post - by googling for hints: "SW ver. TMB/TMB/ATT"! You helped me take the dive, and I'm now happily past having a second-hand S9 (sm-g960u) that wouldn't do an OTA update. After a flawless flash, my first OTA request got me to Android 10, (UI 2). now I have a follow-up update scheduled for the wee hours. (And, yes, I'm still at "TMB/TMB/ATT".)
Perhaps like you, I started by investigating the possibility of flashing the UNLOCKED ("U1") firmware. After learning it was possible with the _patchedD Odin, it still scared me enough that I decided on a more conservative approach and followed your exact advice. I especially appreciated your plan to flash NOT the latest update, but the last Android 9 TMB update. That turned out to correspond to the ATT version on my phone, making TMobile either unable or unwilling to offer an OTA update.
History: This is my third used S9. While all were sold as UNLOCKED, only the first had the "U1" model suffix (SM-g960u1). When the second one booted up as a TMobile phone, I felt tricked - but also lucky that I got the right carrier. That's when I learned about the difference in model numbers. As you noted the U1 firmware is factory unlocked - attached to no carrier. When my third phone booted up with a Verizon greeting I figured I could be facing trouble - even though it accepted my TMB sim card.
The seller explained to me that my phone was part of a batch of ATT phones, all "SIM unlocked" using a Verizon sim card. I think sellers of phones with claims to be unlocked should be required to specify whether FACTORY or SIM unlocked.
Hope this great contribution of yours will continue to help others.
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: