Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
Have you updated your vendor firmware?
sotosgolf said:
Have you updated your vendor firmware?
Click to expand...
Click to collapse
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
[email protected] said:
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
Click to expand...
Click to collapse
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
One can't really know, until they open the phone. If you're still on warranty, get it to your repair center.
sotosgolf said:
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
Click to expand...
Click to collapse
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Olystem said:
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Click to expand...
Click to collapse
I didn't realize it looked like an urge for someone to open their phone without knowing what to do.
I'll edit.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Based on your reply, Question(s) If the phone is "working/functioning" in my case "without wifi & sim" can I assume that my efforts to "bring back to stock" were successful? This is really what I've been wrestling with, Firmware, Stock rom, etc. Bootloader is still unlocked, Stock Recovery in place, I hope all that leaves is securing part(s) in this case a MotherBoard (modular?) to get "wifi & simcard" working again? Thank's XDA
The_wolf88 said:
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Click to expand...
Click to collapse
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
[email protected] said:
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
Click to expand...
Click to collapse
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Taking a break, tired... I have to re-install TWRP, then I'll check the SDcard tomorrow, and Post a GOOD conclusion... I hope! while i have your attention, as far as "service" any reccomendations? I split my time in Philadelphia/Maryland or I could ship if needed. Thank-you!
This happened to my girls poco, she has PE on it. All of a sudden thebphone dint read sim or sd (wifi was good). I switched the slots for each, had no effect, then i took her whole tray and inserted it into my poco where they worked. My sim and sd dint work in hers.
I updated vendor/firmware(no effect), clean flashed rom etc did everything, made a google backup and a twrp backup of data partition.
I ended up using mi flash to put miui fully back and it still dint work. I spent the night trying all this stuff and went to bed frustrated.
I woke up and decided ill just bring it to the phone repair shop downstairs and see (he has a poco). I have no idea how but we put her sim in and it worked, just like that, sd card also. I went back up installed twrp, flashed pe, restored data and she was right back to where she was after moving backup files.
I dont know if all this helps but its my short anecdote.
The_wolf88 said:
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Click to expand...
Click to collapse
I knew there was a "fix" I couldn't believe it was a "hardware" problem either... 2 good articles on "EFS Partitions" one here on XDA Read Up all!!! I'll post a "conclusion" when I
attempt tomorrow, need a break! Thanks too all that replied. Phillip
Poco is BACK!!! It was the EFS partition!, not a hardware issue at all, recovered from a backup after re-installing TWRP. Thanks to all... and especially Wolf88!
Sorry for the delay, out enjoying the day, ... https://dl.twrp.me/beryllium/ ... I used "3.2.3.2- Beryllium" if you have a "backup" just de-select everything but the "EFS" partition, thats what I did and it recovered successfully! Good luck!
poco wfi
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
berty321 said:
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
Click to expand...
Click to collapse
ROM doesn't matter. So long as you have the EFS partition backed up, it is good.
Some time ago it happened to me as well - no cellular and wifi. I fixed it by restoring from a full backup. I keep it on the SD so I can torture my phone any way I see fit and get away with it when I sc*ew things up.
Good to know the specific reason for losing the comms tho. Thanks for specifying. Next time I get there I'll start with efs restoration, instead of full system restore.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
i happen to suffer from the same problem and I dont have a backup of efs or anything what solution can you give me?
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
You wipe the vendor and esf partition. You lost imei ,and wifi . Try hardware test ,because you lost gyroscope and etc working .flash a with fastboot stock miui and fő service .
My friend get same in note 7
Related
Update:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
AUAnonymous said:
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
Click to expand...
Click to collapse
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
ctomgee said:
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
Click to expand...
Click to collapse
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
AUAnonymous said:
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
Click to expand...
Click to collapse
Did you read the whole thread? Specifically, check out pages 5 & 6.
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
AUAnonymous said:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
ctomgee said:
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
Click to expand...
Click to collapse
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
AUAnonymous said:
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
Click to expand...
Click to collapse
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
ctomgee said:
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
Click to expand...
Click to collapse
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
If it keeps failing at NAND write, NAND is stuffed. Service centre job. JTAG repair won't fix it & a person who normally does JTAGs won't be able to fix it at all unless they're able to swap out the NAND.
Well thanks for the confirmation at least :/ looks like I might be getting the GSIII seeing as I can get it on contract at the discounted price. The only downside being that I'll have to get a limited data plan and that the $700 I spent on this one go down the drain unless I can repair it...
AUAnonymous said:
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
Click to expand...
Click to collapse
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
centuriondan said:
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
Click to expand...
Click to collapse
Thanks for the advice but unfortunately I can't boot into recovery, only download mode., and I wasn't using CWM touch beforehand. It didn't even break when I was flashing a ROM, just when I was using the phone normally. I'm going to be in Europe in a couple weeks and I'll be able to take it in to a repair center where it's still under warranty. All I need to do is to use a USB Jig to reset the counter back to 0 so they'll work on it.
Have you tried Heimdall:
And I'd suggest reinstalling CM9. I found that when I had issues re-installing the kernel that I had to go back to the last working rom (ICS based) b4 I could downgrade.
The fact that you can't get into recovery indicates that either the primary or secondary bootloader is corrupted. Try flashing them again with the CM9 versions. Use the USB jig to get into download mode everytime you do flashing so that if you trash it further the counter is always zero. Also use the original USB cable with no hubs in between the phone and computer, and remove any other usb devices plugged in too.
BTW What was the result of *#1234* HW version?
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
aznboix said:
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17587351, but I see you claim to have tried this already. If it didn't work, you'll need to take it to service.
BTW, the efs folder from another phone won't help you. IMEI is unique to each phone.
i dont have any files in EFS excepte the two folders that i mentioned above. Can't even start the procedures.
Service centre job, or contact Odia via PM & he might be able to recover it for you (for the cost of a case of beer).
Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Shasinda said:
Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Click to expand...
Click to collapse
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
fr3nlysmil3 said:
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
Click to expand...
Click to collapse
I tried this also, but it didnt solve my issue :crying:
...
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
MistahBungle said:
If you have a backup, then you should be able to recover it. There are tons of threads on here with instructions on how to restore an EFS backup. Search (if you want it fixed, that is. If you don't want it fixed, keep posting to this thread in the hope someone spoonfeeds you. Might be waiting a while tho).
Click to expand...
Click to collapse
I tried almost every thread here in xda about restoring, tried GSII_repair, kTool to restore it but none of them recovered the IMEI. I did not made a backup of efs but when I installed the Hydra H2O ICS Rom for GS2 it made the backup i guess, because a file called "efs-backup.tar.gz" was in a folder called .hydra inside the sd card.
does the drop of the device has anything to do with the erased IMEI?
robdpi said:
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
Click to expand...
Click to collapse
I have installed stock roms from samsung using Odin, but then I discovered that efs folder get unmounted everytime I install the stock rom, phone just starts after flashing without android setup wizard, also when I long press power button, menu wont appear, device just shut down, after I restore the efs from the backup i have, and mount the efs using the CWM recovery would bring back the power button long press menu. everything else working except for Mobile Networks. and imei/baseband shows unknown
Drop Caused this problem
Hi all,
Thank you for replying on this thread and helped me figured out my problem, I have contacted Odia and he thinks that dropping the phone damaged the baseband chip inside the main board, not a flashing of the roms or efs folder issue. i have only 2 options either replace the whole board paying LKR 35,000 (New s2 costs only LKR 65,000) or use it as a MP3 player :crying:
Hey guys,
So I got a real doozy here...
I flashed my Verizon Note 2 (SCH-I605) to the SOKP Rom from a Jedi X Rom (v13 I believe). After the flash, I noticed my network was not working. Eventually I found out that the device was registering as a GT-7105. Not sure what went wrong, as the rom was flashed with no errors. I also ensured that my recovery was on the appropriate version (TWRP 2.6.3.3 in this case) and I also did a factory reset. To try and rectify the issue I wiped the phone and tried various other roms. In every one of those cases I found that the phone was constantly roaming. I had checked my network mode and tried switching between Global and LTE/CDMA which did nothing. Being completely out of options, I just installed to a stock rom through Odin (VRAMC3 4.1.2) and let it update via Wifi to 4.3 and still nothing. (I am well aware of the Knox security feature and will address this in a moment)
Here are the different ways I tried to diagnose the issue after this that led nowhere:
1. Made contact with a Tier-2 specialist from Verizon that tried various diagnostic methods and found that my phone was simply not registering on the Verizon network, or ANY other network for that matter.
2. I went to a Verizon store and got my SIM card replaced.
3. I even went to a repair shop to see if the phone possibly had a faulty connection.
I have already verified that the IMEI is correct based on the sticker behind the battery. The PRL is on 15310. The very last thing I tried was entering "getprop" inside a terminal. I'm taking a guess here, but I noticed my ril.serialnumber was all 0s. Could this be the problem? If there's anymore information someone needs, I'll be happy to post it up. Just hoping I can get a little direction here. If I need to root my phone again to try something, I am more than willing to. My phone is out of warranty and not insured, I'm not really concerned about the Knox warranty trigger unless it will render my phone completely unusable.
jvar105 said:
Hey guys,
So I got a real doozy here...
I flashed my Verizon Note 2 (SCH-I605) to the SOKP Rom from a Jedi X Rom (v13 I believe). After the flash, I noticed my network was not working. Eventually I found out that the device was registering as a GT-7105. Not sure what went wrong, as the rom was flashed with no errors. I also ensured that my recovery was on the appropriate version (TWRP 2.6.3.3 in this case) and I also did a factory reset. To try and rectify the issue I wiped the phone and tried various other roms. In every one of those cases I found that the phone was constantly roaming. I had checked my network mode and tried switching between Global and LTE/CDMA which did nothing. Being completely out of options, I just installed to a stock rom through Odin (VRAMC3 4.1.2) and let it update via Wifi to 4.3 and still nothing. (I am well aware of the Knox security feature and will address this in a moment)
Here are the different ways I tried to diagnose the issue after this that led nowhere:
1. Made contact with a Tier-2 specialist from Verizon that tried various diagnostic methods and found that my phone was simply not registering on the Verizon network, or ANY other network for that matter.
2. I went to a Verizon store and got my SIM card replaced.
3. I even went to a repair shop to see if the phone possibly had a faulty connection.
I have already verified that the IMEI is correct based on the sticker behind the battery. The PRL is on 15310. The very last thing I tried was entering "getprop" inside a terminal. I'm taking a guess here, but I noticed my ril.serialnumber was all 0s. Could this be the problem? If there's anymore information someone needs, I'll be happy to post it up. Just hoping I can get a little direction here. If I need to root my phone again to try something, I am more than willing to. My phone is out of warranty and not insured, I'm not really concerned about the Knox warranty trigger unless it will render my phone completely unusable.
Click to expand...
Click to collapse
If updating the Profile and PRL on a stock based rom doesn't get it back, then you might have corrupted your EFS partition. I don't suppose you used TWRP to back up the EFS partition when you did a nandroid?
FYI: Doesn't matter what the phone is listed as (n7105) for connecting to the network. It's just a build.prop edit away from saying whatever you want it to.
es0tericcha0s said:
If updating the Profile and PRL on a stock based rom doesn't get it back, then you might have corrupted your EFS partition. I don't suppose you used TWRP to back up the EFS partition when you did a nandroid?
FYI: Doesn't matter what the phone is listed as (n7105) for connecting to the network. It's just a build.prop edit away from saying whatever you want it to.
Click to expand...
Click to collapse
Unfortunately, I did not back up the EFS partition. I'm guessing I should try and restore this somehow?
jvar105 said:
Unfortunately, I did not back up the EFS partition. I'm guessing I should try and restore this somehow?
Click to expand...
Click to collapse
Can't restore what wasn't backed up. The efs is unique to your phone. In some cases you can use another part of another phone's efs partition, but not always and is gonna be a huge hassle either way. But yea, I think you're in a pretty tricky situation. I was reading on another forum that the serial number being 0 shouldn't cause this issue though, so not really sure what to think. Usually when this sort of thing happens, the IMEI gets messed up too. Updating Profile and PRL didn't help?
es0tericcha0s said:
Can't restore what wasn't backed up. The efs is unique to your phone. In some cases you can use another part of another phone's efs partition, but not always and is gonna be a huge hassle either way. But yea, I think you're in a pretty tricky situation. I was reading on another forum that the serial number being 0 shouldn't cause this issue though, so not really sure what to think. Usually when this sort of thing happens, the IMEI gets messed up too. Updating Profile and PRL didn't help?
Click to expand...
Click to collapse
I guess that'll be the next step for me. I didn't want to go through the hassle without making sure. Please send me the links on how to do this if they are available.
jvar105 said:
I guess that'll be the next step for me. I didn't want to go through the hassle without making sure. Please send me the links on how to do this if they are available.
Click to expand...
Click to collapse
I don't have a Note 2 in front of me, but generally it should be in Settings / About Phone / Update or Software Update and for most Samsung CDMA phones, the Profile and PRL options are in or around there.
es0tericcha0s said:
I don't have a Note 2 in front of me, but generally it should be in Settings / About Phone / Update or Software Update and for most Samsung CDMA phones, the Profile and PRL options are in or around there.
Click to expand...
Click to collapse
Yeah, it's actually in the Status section. It does not allow me to edit anything in this area. I don't see anything that says Profile.
Hmm I guess VZW decided you don't need to have access to those functions. Weird. Sorry man, I dunno what to tell you at this stage.
Edit: Found this -
"The only acceptable way to update it on LTE phones is to take the SIM out, boot the phone back up, let it sit for 5 or 10 minutes, power off, reinsert SIM, reboot phone. That's the only one I know of, there may be other ways to do it but that is the easiest."
Not sure if it will help, but certainly isn't going to make it any worse. What baseband version do you have installed?
First thing you need to do is write down your IMEI number. You do NOT want to lose that. Seriously, write it down with a pen. Also your serial number and anything else you find in the EFS partition you might need that's specific to your phone. THEN: at this point it sounds like you'll have to find someone's EFS partition. I've seen it around on XDA multiple times as I've gone through threads similar to this one. Once you find an SCH-i605 efs you'll have to flash/replace/edit yours somehow, try editing your own first to match the same values as your peer's. Don't replace personal information tho. If you end up replacing it you'll have to go in and re-enter your own IMEI number somehow. I am not an expert on how you can do this, but stated here is/would be the process.
--
Say thanks if I was of help,
Sent from my SCH-I605 using XDA Free mobile app
es0tericcha0s said:
Hmm I guess VZW decided you don't need to have access to those functions. Weird. Sorry man, I dunno what to tell you at this stage.
Edit: Found this -
"The only acceptable way to update it on LTE phones is to take the SIM out, boot the phone back up, let it sit for 5 or 10 minutes, power off, reinsert SIM, reboot phone. That's the only one I know of, there may be other ways to do it but that is the easiest."
Not sure if it will help, but certainly isn't going to make it any worse. What baseband version do you have installed?
Click to expand...
Click to collapse
I tried this and still no luck. My baseband is I605VRUAND3.
aarongillion63 said:
First thing you need to do is write down your IMEI number. You do NOT want to lose that. Seriously, write it down with a pen. Also your serial number and anything else you find in the EFS partition you might need that's specific to your phone. THEN: at this point it sounds like you'll have to find someone's EFS partition. I've seen it around on XDA multiple times as I've gone through threads similar to this one. Once you find an SCH-i605 efs you'll have to flash/replace/edit yours somehow, try editing your own first to match the same values as your peer's. Don't replace personal information tho. If you end up replacing it you'll have to go in and re-enter your own IMEI number somehow. I am not an expert on how you can do this, but stated here is/would be the process.
--
Say thanks if I was of help,
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'll see if I can hunt down an EFS partition that fits my phone. Considering I haven't had any luck yet...I'm not too hopeful in finding one.
jvar105 said:
I tried this and still no luck. My baseband is I605VRUAND3.
Thanks, I'll see if I can hunt down an EFS partition that fits my phone. Considering I haven't had any luck yet...I'm not too hopeful in finding one.
Click to expand...
Click to collapse
Hey guys, I just gave up and traded it in for an S5. I knew a guy so it was a good deal. I appreciate all the help!
Ok, so looks like my phone decided to take some time off...
What happened was that yesterday I was playing a game on it and the battery had just about 3% left, so I put it to charge (wall charger) and the game froze.. Din't pay too much attention to it when I came back a couple of hours later, the phone was off. Turned it on and didn't go past the Samsung logo.... And it's been like this since then.
I was running a 4.4.4 ROM Eclipse V5 By AC, which was working fine and I have access to TRWP Recovery and also to Download Mode.
I have tried to restore a different nandroid backups and install other ROMS, inclusively an original stock ROM.. I tried to restore EFS, but only managed to restore and old one that was stored in the phone's memory.
I also have an emergency firmware and a stock one and I believe I have everything else to be able to do it by Odin, but I don't have USB debug!!!
Please tell me there is a "magical way" to enable USB debugging without having access to the phone!! Even on Download Mode, Odin doesn't recognize the phone. I also have Samsung and ADB drivers installed.
I'm getting desperate and don't know what else can I do to sort this out..
My phone is GT-I9300 International, running a 4.4.4 ROM (when it bricked) and have PhilZ Touch 6.48.4
Any ideas or suggestions, please???? Thanks guys!
Deinstall all Samsungdrivers, KIES and Odin on PC. Install actual software from sammobile.com. Try another USB-port, if possible at mainboard. Run Odin as Admin. If phone isn't shown in Odin, it's gone.
Hey rp158, thanks for your reply! I'll try and do that! Hope I don't have to bury it ......
migasbr said:
Hey rp158, thanks for your reply! I'll try and do that! Hope I don't have to bury it ......
Click to expand...
Click to collapse
*EDIT*
Thanks again for your advice rp158! I decided to borrow a laptop running Windows 7 (I have Windows 10 on my PC), installed fresh version of Kies and finally I got it to work with Odin!! Flashed a couple of emergency firmware and finally an original 4.3 ROM. The problem continued and finally I flashed an efs fix. I guess that did the trick and my phone came back from the dead! Rooted my phone again, installed PhilZ and restored a previous backup I had.
Now I still have one problem to solve! I still didn't managed to have network service... I already managed to fix my IMEI, or at least when I press*#06#, shows the right IMEI, but no network service....
I read about a few "fixes" for this but I haven't fully tried any of them.. Any suggestions?...
Thanks again for your help!
Maybe, you imported wrong settings by restoring backup. So go back to firmware again without any patches and check, whether IMEI and net access are ok. If not, try KIES-emergency-repair. If you succeed, don't use your backup (and continue with TWRP ).
rp158 said:
Maybe, you imported wrong settings by restoring backup. So go back to firmware again without any patches and check, whether IMEI and net access are ok. If not, try KIES-emergency-repair. If you succeed, don't use your backup (and continue with TWRP ).
Click to expand...
Click to collapse
Hi rp158, I've reinstalled the original firmare and ROM by Kies and everything went well but I was still getting a "0049" IMEI... I was burning my eyes so much because of it that I decided to take the phone to a store. They have been trying to re-register the IMEI for the last couple of days and just got a message saying that they have managed to do it. I'l pick it up tomorrow. If they really managed, it will cost me about 25 Euros, but will sabe a lot eye burning! :silly:
First I'll do is a Nandroid job and about 100 EFS backups! lol
It shouldn't be problem to restore a previous backup that I know it's working well, right?...
Maybe. Or a goed moment to try something fresh...
rp158 said:
Maybe. Or a goed moment to try something fresh...
Click to expand...
Click to collapse
Hello rp158, they actually did it!! Phone works great and it's totally functional. Tried to find out what kind of software they used but they wouldn't tell me as expected..
Made a nandroid and efs backup straight away and restored my previous ROM, just to do a Titanium backup of everything and now I', using a 5.1 ROM.
Thanks again for your help!
@migasbr: fine.
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.