Develop Bugs

big mistake! need help urgent please!

hey so guys, i just flashed cwm recovery latest .43 and i was going through my usual routine of wiping for a new rom.... well this new cwm has a new wipe called wipe factory (i pressed it by accident because i am so use to having wipe sd card there) and then a few minutes later i bump into this post concerning it
now my IMEI is a generic 00499 and have no call signal at all!
and i dont have a backup!
how can i fix this?
why was such a dangerous option in CWM recovery......?

anybody please, let any help you can!

BUMP, please does anybody know any solutions?
is my phone a paperweight forever?

BUMP, please does anybody know any solutions?
is my phone a paperweight forever?

Try to check here
http://www.droidviews.com/how-to-ba...imei-on-samsung-galaxy-devices-did-you-do-it/
Check here, grasnoff solution
http://forum.xda-developers.com/showthread.php?p=24175451
This could be useful
http://forum.xda-developers.com/showthread.php?t=1264021

enricocid said:
Try to check here
http://www.droidviews.com/how-to-ba...imei-on-samsung-galaxy-devices-did-you-do-it/
Check here, grasnoff solution
http://forum.xda-developers.com/showthread.php?p=24175451
This could be useful
http://forum.xda-developers.com/showthread.php?t=1264021
Click to expand...
Click to collapse
thanks but all those methods require backup of original EFS folder, which i do not have

i freaking hate CWM for all it stands for
what kind of dumb idea is to have format factory folder in there?

i freaking hate CWM for all it stands for
what kind of dumb idea is to have format factory folder in there?

jt.one said:
thanks but all those methods require backup of original EFS folder, which i do not have
Click to expand...
Click to collapse
In the last method i read
"If you didn't make a backup ... "

enricocid said:
In the last method i read
"If you didn't make a backup ... "
Click to expand...
Click to collapse
well he clearly cant read since he bumped his own thread like 6 times in a couple hours.

enricocid said:
In the last method i read
"If you didn't make a backup ... "
Click to expand...
Click to collapse
yeah the last method required untouched shipped EFS folder, mine has been "touched" already so yeah... RIP my phone i suppose

jt.one said:
yeah the last method required untouched shipped EFS folder, mine has been "touched" already so yeah... RIP my phone i suppose
Click to expand...
Click to collapse
not sure this will help but a tutorial like this is probably your best bet: http://galaxynexusspecs.com/how-to-unrootunbrick-the-samsung-galaxy-nexus-latest/

jt.one said:
yeah the last method required untouched shipped EFS folder, mine has been "touched" already so yeah...
Click to expand...
Click to collapse
did you check this post ? http://forum.xda-developers.com/showpost.php?p=46376962&postcount=1413

samersh72 said:
did you check this post ? http://forum.xda-developers.com/showpost.php?p=46376962&postcount=1413
Click to expand...
Click to collapse
yeah i actually tried that method but it was a no go. my /data/radio was "touched" already
thanks though

i wanted to bump this.
so heres what happened. i went to my tmobile store to buy a micro-SIM card for my new Moto G. The register guy thought I was gonna use it right away (but i didn't because the Moto G was still on its way via delivery) so he prematurely cut my old sim card and switched my phone number to the new micro-sim card. When I had realized this- i went back to the store and told him about the mistake.
Since you cannot reactivate a sim card that has been cut, he gave me a fresh regular sized sim card for free with my number back on it and so I went home.
Now for fun, i figured "hey what happens if i put this new fresh sim card inside my galaxy nexus with the nuked generic IMEI?"
............ to my SHOCK, my notification drawer said "T-MOBILE" and I had full bars of signal. I could call, I can text and everything! I went to my system information in settings menu and it still had the generic 00049 IMEI! So for those who had my same problem, try replacing the sim card!

[Q] Restore Z1 Compact to stock firmware before sending it for warranty repair.. help

Hello XDA!
I've ran into some hardware related issues with my Z1 compact (the earphone jack is glitchy) and i want to send my phone in for repairs.
The thing is i have a modded cyanogenmod firmware on it as i preferred it over the stock rom. I also have that clockword mod thing.
As you can tell i'm not very accostumed to doing these things and i was wondering if anyone would guide me on how to restore the phone to its original stock setting?
The phone is a swedish device so i would need the scandinavian versions i'm guessing, any ideas out there?
Thanks.

jeriksson said:
Hello XDA!
I've ran into some hardware related issues with my Z1 compact (the earphone jack is glitchy) and i want to send my phone in for repairs.
The thing is i have a modded cyanogenmod firmware on it as i preferred it over the stock rom. I also have that clockword mod thing.
As you can tell i'm not very accostumed to doing these things and i was wondering if anyone would guide me on how to restore the phone to its original stock setting?
The phone is a swedish device so i would need the scandinavian versions i'm guessing, any ideas out there?
Thanks.
Click to expand...
Click to collapse
You just need to find the right firmware for your region / provider.
I would recommend IaguCool's thread on Xperia Firmware Downloader & Checker, if you have flashtool installed you can make your own ftf that is exactly right for your phone. All the instructions are in the thread.
Hopefully you made a copy of your TA partition before you unlocked it and put CM on your phone? it may not matter if you have not, as long as it looks stock.

Didgesteve said:
You just need to find the right firmware for your region / provider.
I would recommend IaguCool's thread on Xperia Firmware Downloader & Checker, if you have flashtool installed you can make your own ftf that is exactly right for your phone. All the instructions are in the thread.
Hopefully you made a copy of your TA partition before you unlocked it and put CM on your phone? it may not matter if you have not, as long as it looks stock.
Click to expand...
Click to collapse
Hey digesteve,
Thanks, i'll check that tool out. I don't know if i made any backups of my TA partition, but probably no because i don't know about it.
Is there a way to see if i made a backup of the TA partition, could it be stored somewhere on the phone after installing clockwork mod?
Thanks for the help!

jeriksson said:
Hey digesteve,
Thanks, i'll check that tool out. I don't know if i made any backups of my TA partition, but probably no because i don't know about it.
Is there a way to see if i made a backup of the TA partition, could it be stored somewhere on the phone after installing clockwork mod?
Thanks for the help!
Click to expand...
Click to collapse
If you didn't do it, then it won't be saved anywhere on the phone. You have to physically copy it to the hard drive of your pc for safekeeping.
It doesn't matter, it won't stop you from restoring the stock rom and I don't think not having it voids the warranty. Maybe somebody could correct me on that?

Didgesteve said:
If you didn't do it, then it won't be saved anywhere on the phone. You have to physically copy it to the hard drive of your pc for safekeeping.
It doesn't matter, it won't stop you from restoring the stock rom and I don't think not having it voids the warranty. Maybe somebody could correct me on that?
Click to expand...
Click to collapse
Definitely didn't do it then. Hopefully they won't give me any trouble for rooting it, it's worth a shot anyway.
I've downloaded the firmware but it doesn't come in the same sort of package as cyanogenmod, are there any guides you can recommend on how to apply this firmware to the phone?

and don´t forget to relock the bootloader with flashtool!

jeriksson said:
are there any guides you can recommend on how to apply this firmware to the phone?
Click to expand...
Click to collapse
You'll need a copy of flashtool and the adb drivers.
Flashtool will turn the downloaded files into a tft file, but all the instructions are in the thread.
If you get lost then XperienceD's AIO thread will guide you in the right direction

I downloaded flashtool from sonys website and it actually listed stock firmwares in a list which i could apply to my phone so i did.
Now the phone boots into what seems to the be stock firmware, however i was going to go into recovery just to check that was restored too and not the clockworkmod i had previously installed but it seems i cannot boot to recovery anymore, what can i do? Where can i find the "stock recovery" that these phones comes with? I want the phone to seem as it was never rooted/changed on the software level

jeriksson said:
I downloaded flashtool from sonys website and it actually listed stock firmwares in a list which i could apply to my phone so i did.
Now the phone boots into what seems to the be stock firmware, however i was going to go into recovery just to check that was restored too and not the clockworkmod i had previously installed but it seems i cannot boot to recovery anymore, what can i do? Where can i find the "stock recovery" that these phones comes with? I want the phone to seem as it was never rooted/changed on the software level
Click to expand...
Click to collapse
You have flashed the Sony rom, so now it is stock, with no root or recovery. There isn't a stock recovery. Your work is done.

Isn't there a menu you can boot to that gives you the option to wipe cache partition and do some various other stuff? Perhaps this is only for samsung devices, sorry for the confusion and thanks for the help!
Hopefully the service goes as planned!

Is still the way to do it or is there any new ways ?? I have bought a Z1 Compact for my son who is 8 and he wants it back to stock. It has CyanogenMod now.....cant recall what version though since i dont have the phone with me.

[INFO] Xperia ACRO S Re-listed for Unlocking Bootloader

Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda

As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand

Wow, Thanks for the surprise! U make my days!

sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good

Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(

sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.

hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.

sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.

hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.

sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.

sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.

hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161

sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.

This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.

sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?

hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse

sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.

hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.

sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago

hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.

IMEI lost, questions about backing up another MOTO Z Play "EFS".

Hi, I've been trying to find a solution for the problem of null IMEI I'm having after wiping EFS partition on the Chinese TWRP, maybe it's not that and it is because I've erased modemst1, modemst2 and flashed modem+fsg.
I'm pretty sure it had to do with one of those procedures, when I wiped the EFS I've got some error saying it couldn't be done but something went missing.
I've got a more direct question now, my brother just bought a Moto Z Play yesterday, if I backup his EFS on my phone (he already asked if I want to do that) will both of us would be able to use our phone normally?

can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs

kkarora said:
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
Click to expand...
Click to collapse
No way, like you already now, each phone has an individual IMEI. Your phone is unfortunately unusable.
What did you attempt to do? Flash another firmware package ?
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
No way, like you already now, each phone has an individual IMEI. Your phone is unfortunately unusable.
What did you attempt to do? Flash another firmware package ?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
isn't there ANY way of rewriting this thing back?

mcaxtr said:
isn't there ANY way of rewriting this thing back?
Click to expand...
Click to collapse
Unfortunately no

mcaxtr said:
isn't there ANY way of rewriting this thing back?
Click to expand...
Click to collapse
Lenovo could generate it. But they probably instead replace the main board. You may ask them how much the repair is.

I think I'll just take it there and see if they can do anything about.
well, lesson learnt hard way

mcaxtr said:
I think I'll just take it there and see if they can do anything about.
well, lesson learnt hard way
Click to expand...
Click to collapse
New motherboard unfortunately

Now you know not to use fishy Chinese recoveries.

efs
Hey you can use sigma box to restore imei which will cost you around 800 rs,same thing happened for me but still not fixed just using with wifi

If partition can be wiped, then is not read only. If is not read only, should be possible to write backup back. Otherwise, what's the point of the backup?!
Each phone should/must have different IMEI, depending of the network. In theory, should be possible to take partition from one phone and write to another. However, Moto maybe prevents that checking some hash, serial number... If it's possible to write partition from another phone, again question is can those two phones be on the same network in the same time. I also saw a way to change IMEI, I think even on this sub forum.

If someone solve this problem I definitive pay to that sir, he would be rich In the first day..

kkarora said:
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
Click to expand...
Click to collapse
did u got efs, im too wiped my efs partition

No IMEI, IMEI SV, or Signal after flash rom stock

First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.

JoiaDG said:
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
Click to expand...
Click to collapse
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this https://zfirmware.com/how-to-repair-qualcomm-imei-via-qualcomm-write-imei-tool/

Sadly not working
SubwayChamp said:
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this
Click to expand...
Click to collapse
Sadly, it didn't work. i was thinking if there was a way to do it with root

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here: https://androidmtk.com/download-qualcomm-smartphone-write-imei-tool
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.

I need help
TheoXSD said:
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here:
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
Click to expand...
Click to collapse
I know i have to use that tool, but my device is not recognized by that app, i tried to install all the drivers, but nothing's working.

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
I knew that there is a method to restore IMEIs via adb but I don´t remember commands so I never need it. First I do before tinkering device is to backup IMEI/EFS/NVram.
I had a theory that years ago I proved, IMEI is not really lost but just overlapped so if you have some friend that can give you their backup this will recover the yours but won´t overwrite/replace the yours. Not sure if it works yet.
About the tool that I linked maybe you need to get it through either in fastboot or download mode, try both; I don´t think that detect it while device is on.

https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial

JoiaDG said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
Click to expand...
Click to collapse
Yeah this fixed my phone too, now I'm making backups