Help Lost IMEI after P605T 5.1.1 update
Hi,
I recently purchased a Samsung Galaxy Note 10.1 2014 edition TMobile variant. It came installed with 4.4.2. I wanted to have a rooted 5.1.1
* Applied CF-autoroot from here: primehowto com root-galaxy-note-10-1-lte-sm-p607t-t-mobile
(I didn't check but I think at this stage it didn't wipe the IMEI)
* I used Kies to upgrade from 4.4.2 to 5.1.1.
Now when the IMEI appears to be unknown (not registering with tmobile sim card)
Although the WIFI works whenever the table is rebooted the SSID profiles/passwords are forgotten.
I've been seeing folks suggest the EFS is corrupt.
What is the best way of recovery?
1) Downgrade back to 4.4.2? Maybe the Autoroot isn't compatible with 5.1.1? Is there a safe way to do this?
2) Try to recover EFS? Is there a way to confirm the state of EFS? What would be the best way to do this?
Thanks for your help!
Resolved
I've resolved the issue. It appears CF autoroot didn't cause the problem, but rather using Kies to update to the latest 5.1.1. TMO caused the problem. I was able to get back the IMEI # flashing with .tar.md5 using Odin .
Related
Two days ago i bought Samsung Galaxy Note 2 N7100 (international). It had android 4.1.2 but i saw there is available update. After update to official android 4.3 my phone lost signal and started showing me "Not registered on network". 1 day passed since i am searching how to fix this thing. Tried custom rom (4.4.2) and still the same. I went back to official 4.3 for UK O2 , successfully rooted it, passed knox, installed busybox, installed ARIZA Patch. Still the same. Tried to flash MJ5 bootloader via ODIN but it shows me FAIL. And after every FAIL my phone is bricked so i am flashing all over again official ROM. I have NO backups of my EFS (in my search i saw that i need some EFS to repair this thing). I got no issue with WI-FI but only with network. If i revert back to stock android 4.1.2 will i be able to call somebody? If the answer is "YES", would somebody tell me how? I saw in some threads that with new 4.3 ROM note 2 got knox locked bootloader which is impossible to be downgraded. Please, give me guide step by step what to do to repair my phone by myself. Thank you in advance.
I would suggest you to take an efs backup on 4.1. Then flash 4.3 and if you aren't getting network try restoring your efs backup. That might solve your problem.
Hello
Back in March, I rooted my T-Mobile (USA) Note 3 'after' upgrading OTA to KitKat 4.4.2 - everything has worked great. Today, when I connected my phone to Kies3, I see that there is an available firmware update from:
PDA:NB4 / PHONE:NB4 / CSC:NB4 (TMB)
to
CSC:NF9 (TMB)
It is asking me if I want to upgrade in Kies 3. My question is, what happens if I say 'yes'? Also, I believe the Knox flag is tripped as I used the following procedure back in March:
http://forum.xda-developers.com/showthread.php?t=2672393
What is the correct way to upgrade my phone?
Thanks in advance!
Update: So I went ahead and performed the upgrade to CSC:NF9 (TMB) using Kies3 via USB cable. It looks like the upgrade was successful and my phone did not brick during the process - however, it appears my phone is 'not' rooted now.
My question is, what is the correct procedure to root my phone which is on Android 4.4.2, build number KOT49H.N900TUVUDNF9?
Thanks!
Hi All,
My wife's old AT&T Galaxy Note 2 - never been rooted - is still on 4.3.
So I went to Software update and it is saying that the update has been interrupted and I have to wait 24 hours. So I keep on restoring to factory defaults / changing the time trick -- and It still fails. I have clue why it can't pick up the updates from the AT&T Servers.
Is there a way to update it forcefully - Like using ODIN or something? The last time I tried this (even with the official AT&T ROM - it tripped the counter of my Galaxy Note 1). -- is it the same case with ODIN and Note 2?
Also, the more important question is - will I lose my SIM unlock if I update to 4.4.2 via ODIN or other methods?
Long time ago, I have used the trick *#197328640# and it worked wonders. Will I lose it in 4.4.2 ?
As much as possible, I don't want to root it because I will sell it and he doesn't want rooted phones.
Thank you.
keplenk said:
Hi All,
My wife's old AT&T Galaxy Note 2 - never been rooted - is still on 4.3.
So I went to Software update and it is saying that the update has been interrupted and I have to wait 24 hours. So I keep on restoring to factory defaults / changing the time trick -- and It still fails. I have clue why it can't pick up the updates from the AT&T Servers.
Is there a way to update it forcefully - Like using ODIN or something? The last time I tried this (even with the official AT&T ROM - it tripped the counter of my Galaxy Note 1). -- is it the same case with ODIN and Note 2?
Also, the more important question is - will I lose my SIM unlock if I update to 4.4.2 via ODIN or other methods?
Long time ago, I have used the trick *#197328640# and it worked wonders. Will I lose it in 4.4.2 ?
As much as possible, I don't want to root it because I will sell it and he doesn't want rooted phones.
Thank you.
Click to expand...
Click to collapse
Here if you haven't figured it out yet try this
http://forum.xda-developers.com/showthread.php?t=2618447
This will downgrade to 4.1.1 then ota to 4.3 but it wont root it and thats what your problem
Fam...
I bought a LTE Samsung 10.1 P605 from Verizon some months ago. It came with 4.3 already on it factory. I have been able to root it but that is all. I would love to get to a custom rom but with the Verizon boot loader issue not sure if totally possible get around the lock with 4.3.
I have read P605XXUCNE2 has been made available for the P605 LTE 10.1 models but my device does not show from it for update. I have gone to Sammobile and downloaded the P605XXUCNE2 (Nomadic) download listed for it.
Issue:
- Kies does not show for an update nor I see no way to push this rom NE2 manually
- Odin fails each time I try to push P605XXUCNE2 I assume due to boot loader
- Odin will not let me install TWRP (openrecovery-twrp-2.7.0.1-lt03ltexx.img) posted for the LTE model
So I cannot install a OEM firmware like NE2... How can I force or push a firmware to this darn device if ODIN fails? Am I locked in no mans land since I pushed a model that has 4.3 already on it? Am I stuck since it is a Verizon LTE model...?
Anyone can provide any steps who know a little about this model how I can get NE2 on it or TWRP even though OBIN says fails each time I try??
Model came as 4.3 with firmware P605VVRUCNC2
I'd guess the issue is that your device is not an SM-P605. Your device is an SM-P605V. The latest firmware SamMobile is showing for the 605V is NC2 (which should be 4.4.2, not 4.3).
blindmanpb said:
I'd guess the issue is that your device is not an SM-P605. Your device is an SM-P605V. The latest firmware SamMobile is showing for the 605V is NC2 (which should be 4.4.2, not 4.3).
Click to expand...
Click to collapse
Thx...I read it work...
With this info is there a way to get TWRP to install on the 605V?
I am pretty sure you are screwed if you want to flash Roms. Probably best bet is to sell it pay off what ever you owe or break contract and go to T-Mobile or buy WiFi (better for flashing Roms if you can handle not having LTE)
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Flash a firmware version that contains S6 or U6 in the middle, it won't work with U5/S5! Not the Samsung phone S5 or S6, but rather, the firmware version.
For cellular, change the modem firmware, or backup and wipe /data/. /data/data/?.
Unless the efs was wiped (probably not if the baseband version isn't there, load a backup then, only if the efs was wiped don't restore it otherwise, and it must not be a backup created with an older twrp, view the recovery log in the backup folder)
julianmunozvaras said:
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Click to expand...
Click to collapse
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
iloveoreos said:
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
Click to expand...
Click to collapse
I tried installing the latest version available and I had the same error.
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Well, I don't know what else could be wrong.
Sent from my Samsung SM-A520W using XDA Labs
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Listen to me, it happened to me 2 days ago, and I came to the conclusion that I was not flash the latest firmware. You need to flash the same firmware with the same bootloader or more recent, the error you receive is because you are flashing an older version of bootloader. Do one thing, type the code *#1234# on the phone keypad
mark the code that gives you on 'AP and look it on Sammobile at https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ITV/ select your language and look for the firmware with your own code . You will see that odin flash it.
Samsung A520F Custom Binary Error
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
koolblowkid said:
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
Click to expand...
Click to collapse
Obviously you are frp locked. But I didn't think that blocked from flashing official.