Related
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
Where did you find the fastboot file?
________
v7
XDA Assist
v7 said:
Where did you find the fastboot file?
________
v7
XDA Assist
Click to expand...
Click to collapse
I forgot where I found it from... do you know where he correct one is?
ethanscooter said:
I forgot where I found it from... do you know where he correct one is?
Click to expand...
Click to collapse
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist
v7 said:
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist
Click to expand...
Click to collapse
I forgot, honestly this happened a few weeks ago I tried looking through my history but I couldn't find it. How can I fix it?
EDIT: It wasn't from XDA for sure.
ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
_MetalHead_ said:
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
Click to expand...
Click to collapse
I tried it and still nothing...
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.
krishna442 said:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.
Click to expand...
Click to collapse
I cannot use that because my device is not hard bricked and it will not install the driver since I can enter the bootloader normally.
Not sure if you've seen this post its based on the post above but I think it just uses fastboot. Don't know if it will work for you, but figured it would be worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
I tried using the tool and it did not work, I purposely hard bricked the device to try it and still no signal or imei. Another problem is WiFi takes about 4 minutes just to turn on but I can live with that I just want service.
Basically flashing back the stock should bring back the efs. Let's see if someone has a solution. Sorry!
EFS files are unique to each phone. If the EFS is corrupt or damaged, and there is no backup, I don't know of any way to fix it ;_; You can try OnePlus support but they aren't as dumb as carrier warranty or other phone manufacturers. They'll be more likely to know what you did.
It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!
EddyH1993 said:
It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!
Click to expand...
Click to collapse
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?
ethanscooter said:
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?
Click to expand...
Click to collapse
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/
EddyH1993 said:
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/
Click to expand...
Click to collapse
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?
ethanscooter said:
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?
Click to expand...
Click to collapse
Have a look at this link http://droidmodderx.com/galaxys3/?page_id=79 I really can't remember how I did it and without researching again I won't know. It's a rough idea to maybe help you, I think the device just needs to be in USB debugging mode. I can't help anymore sorry and good luck.
any fix for this yet?
Same problem also with my op2 . No imei no baseband
I tried out Marshmallow but didn't like it so used a nandroid backup to completely restore the phone.
After a few errors trying to restore (think it was a 255 error?) in recovery it finally worked however now I have no service, and the IMEI just says 0.
Can this be fixed or have I now got a small tablet?
Note: I am not trying to change my IMEI which I know is illegal, just trying to get back my one.
restore a 6.0 twrp backup..changing IMEI in a snapdragon device is a pain in the ass. MTK devices are easy.
bablu048 said:
restore a 6.0 twrp backup..changing IMEI in a snapdragon device is a pain in the ass. MTK devices are easy.
Click to expand...
Click to collapse
I don't have any TWRP backups from marshmallow, just one from lollipop. I read that QPST is the tool that sorts this however Windows cannot find the correct drivers (despite having Motorola Device Manager installed) for my device so I cannot input a port into the software to find the phone.
I read somewhere that flashing stock firmware solves the problem, you should try that
nimcitor said:
I don't have any TWRP backups from marshmallow, just one from lollipop. I read that QPST is the tool that sorts this however Windows cannot find the correct drivers (despite having Motorola Device Manager installed) for my device so I cannot input a port into the software to find the phone.
Click to expand...
Click to collapse
here are the twrp backups forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
bablu048 said:
here are the twrp backups forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
Click to expand...
Click to collapse
Will that be alright to flash onto a XT1562?
What do I need to do after Marshmallow is back on the device?
nimcitor said:
Will that be alright to flash onto a XT1562?
What do I need to do after Marshmallow is back on the device?
Click to expand...
Click to collapse
yes the backups work on xt1562
nothing first see if you have network is back.
bablu048 said:
yes the backups work on xt1562
nothing first see if you have network is back.
Click to expand...
Click to collapse
Flashed the file you said but still IMEI is 0.
What now?
If no one else has any other software ideas then two things come to mind:
1. If you have the box that the Moto X Play came in then the IMEI is on the outside of the box. The information on how to restore it is on the Internet. Just google it. Not going to discuss it due to legality issues.
2. Return the phone to warranty depot for repairs if possible. Not sure on your circumstances.
Sent from my XT1563 using Tapatalk
Mod Edit
Thread Closed - OP request
ronnie498
Senior Moderator
Hi!
Really need your help
I flashed my phone and sold it.
Now customer claimed no network connection and sent it back.
Today I checked the phone and saw, that no IMEI were present.
I restored the IMEI, but there is no network connection.
I flashed the OEM ZTE image and have no clue what else could help.
Any idea?
Is this maybe MODEM related?
Sui77 said:
Is this maybe MODEM related?
Click to expand...
Click to collapse
Yeah, just flash the corresponding modem file
Choose an username... said:
Yeah, just flash the corresponding modem file
Click to expand...
Click to collapse
Flashed the A2017G-N-Modem ---> No success
Sui77 said:
Flashed the A2017G-N-Modem ---> No success
Click to expand...
Click to collapse
I don't know. Maybe a screenshot or two of *#*#4636#*#* would be helpful. This is a shot in the dark though
Are you 100% sure it is a a2017g?
joaste said:
Are you 100% sure it is a a2017g?
Click to expand...
Click to collapse
Was bevore flashing and was brandnew, sticker states also A2017G
joaste said:
Are you 100% sure it is a a2017g?
Click to expand...
Click to collapse
well that's also something worth looking, just see on the back of the phone if it says a2017g. i just assumed you would be sure
Sui77 said:
Was bevore flashing and was brandnew, sticker states also A2017G
Click to expand...
Click to collapse
I would try reflashing the modem, making sure you're using the latest twrp 3.1.1 and that system is mounted before flashing.
joaste said:
I would try reflashing the modem, making sure you're using the latest twrp 3.1.1 and that system is mounted before flashing.
Click to expand...
Click to collapse
No success
I think there is an issue with the IMEI.
I have restored them, but maybe still broken
Sui77 said:
No success
I think there is an issue with the IMEI.
I have restored them, but maybe still broken
Click to expand...
Click to collapse
Sorry. Can't help you there. I have no experience with restoring IMEIs and resulting issues.
Good luck.
my baseband is another
i use an A2017G stock
https://www.pic-upload.de/view-34346603/Screenshot_2017-11-22-11-27-05.jpg.html
I sometimes get problems just after flashing, and GSM/Wifi 5Ghz take up to 5 minutes to initialize. Deactivating and reactivating the sim card helps. Did u try that?
- Else, I'd get a 7.1.1 factory image and start over, that baseband is *exactly* the same as mine and I only have that "5-minutes-without-wifi-and-network" bug.
- Try looking for wifi just after booting the phone : if you only see 2.4Ghz networks and no 5Ghz network, just turn the sim car off and on, and it's ok, just that bug.
reflash a full stock firmware, if you have imei, you must have then, then if you want, do the process again to get twrp
Hi Folks,
i've done some reading and my problem is a broken EFS sector due to TWRP recovery.
Even after manual IMEI restore, the EFS is broken and causes the no service issue:
https://forum.xda-developers.com/axon-7/how-to/investigation-recovering-efs-twrp-t3522171
Only option is to get a EFS copy from another device, push it on my one and change the IMEI to my own manually.
If efs was ’restored’ using the signed twrp used for unlocking then there is no fix for that.
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Wifi works, but sim = 0
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Thank you soo very much. you are the best, I followed your instructions step by step and my phone wifi is working as charm. my phone is alive now. Thanks a ton again.
-Bimlesh
colegui said:
Wifi works, but sim = 0
Click to expand...
Click to collapse
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
I'm trying some methods but I have not luck yet.
colegui said:
I'm trying some methods but I have not luck yet.
Click to expand...
Click to collapse
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
dmbardal said:
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
Click to expand...
Click to collapse
I'm fixing imei downgrade to 7.8.23 and repair imei with rbsoft tool, but when I upgrade to oreo with OTA, imeo=0 again....
I'm trying again other method....https://forum.xda-developers.com/mi-a1/help/efs-partition-eraised-boot-t3753619
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
Here is solution: : How to restore IMEI permanently after using factory flash
I have the same problem with IMEI, the fix is permanent.
After the repair can be uploaded any rom, including Oreo .
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
coda00 said:
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
Click to expand...
Click to collapse
Sorry I cant posting outside links,
You can try EDL mode:
solution how boot EDL mode via ADB or fastboot: link>> 99mediasector.com/edl-mode-boot-edl-mode-xiaomi-devicesI think this will not work for youBut you can try EDL:via Deep Flash Cable (how quickly make Deep Flash Cable): link>> en.miui.com/thread-310325-1-1.htmlorvia disassembly Mi A1 (Guide to Flash Bricked Mi A1): link>> en.miui.com/thread-1680467-1-1.html
Excellent
Ecoda00
Click to expand...
Click to collapse
amazing bro Thanks, i work fine for me...
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Now that my wifi issue is solved, can I delete the persist.img from my device? Please advice.
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
amithiel said:
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
Click to expand...
Click to collapse
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Bimlesh1681 said:
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
Edit: But you need to have you original persist file
Thank you so much, Bro. You saved my day. I am getting the similar problem. And ended up flashing multiple ROMs. but nothing worked out until I found your post.
i used this tool to solve wifi issue.
while using this tool make sure you enable USB debugging or it won't work.
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
infuerano said:
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
Click to expand...
Click to collapse
try flashing the latest void kernel.
I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?
mouth said:
I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?
Click to expand...
Click to collapse
Did you by chance did a backup of the full phone from twrp? If yes try to flash back in everything including the rom.
I always make a full backup on twrp after flashing a new custom rom and finish setting everything up. Just in case I did something wrong down the road I can just wipe everything and restore everything from the full backup. And I won't need to go through the hassle of setting the phone up.
Sent from my SM-G985F using Tapatalk
mouth said:
I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?
Click to expand...
Click to collapse
Nope, you need odin and combination rom and ofcourse pc - per my best knowledge..
But if you have pc, but can't get odin/combination due to whatever reason.. follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911/post79889098
Sent from my S7 Edge using XDA Labs
vash_h said:
Did you by chance did a backup of the full phone from twrp? If yes try to flash back in everything including the rom.
Click to expand...
Click to collapse
No, just Boot, Recovery, Baseband, and EFS. That's what I thought is all I'd need for any low-level recovery, since I was wiping and flashing anyway (a process I've done many times over the years). I thought the IMEI came from EFS anyway.
Thanks for thought.
shah22 said:
Nope, you need odin and combination rom and ofcourse pc - per my best knowledge..
But if you have pc, but can't get odin/combination due to whatever reason.. follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911/post79889098
Click to expand...
Click to collapse
Thanks, unfortunately it appears that thread needs working USB though, which I don't have.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965 looks interesting. Could that work for an S7e?
mouth said:
Thanks, unfortunately it appears that thread needs working USB though, which I don't have.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965 looks interesting. Could that work for an S7e?
Click to expand...
Click to collapse
Yes follow this thread for imei repair using twrp. Should work
But be careful about the file paths..
S7 edge on oreo fimware path maybe different..
Also your phone must be in working condition..
https://forum.xda-developers.com/no...rity-factory-csc-serial-t3422965/post67840769
Sent from my S7 Edge using XDA Labs
shah22 said:
Yes follow this thread for imei repair using twrp. Should work
Click to expand...
Click to collapse
Hasn't worked
Also found /efs/.nv_backup.bin[.md5] but using these didn't't help either.
Any other steps available?
mouth said:
Hasn't worked
Also found /efs/.nv_backup.bin[.md5] but using these didn't't help either.
Any other steps available?
Click to expand...
Click to collapse
Follow steps to letter, should fix your issue.. make sure you have su access in adb and you use the right file paths, don't know why a solution won't apply to your situation, it should as i think ..
Sent from my S7 Edge using XDA Labs