Database Info

IMEI=0 - how to enter working IMEI?

Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;

Try fastboot flashing the cache.img from the factory image.

jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?

Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk

Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success

Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato

charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).

CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!

RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato

You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.

rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.

Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.

BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk

rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One

My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.

RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.

Need modem backup for 6045Y. Help needed.

Hi,
I tested the chinese rom yesterday on my 6045Y and it resulted in a loss of GSM signal, even after rsstoring the phone with mobile Q upgrade software.
I would need someone's help here.
Can people use @DallasCZ backup-all.bat script and extract the original partitions of their phone to share with me?
I need at least to try to get the modem to it's original state.
Again, it's for 6045Y.
Thanks all for your help.
Sent from my GT-I9000 using XDA Free mobile app

Anghirrim said:
Hi,
I tested the chinese rom yesterday on my 6045Y and it resulted in a loss of GSM signal, even after rsstoring the phone with mobile Q upgrade software.
I would need someone's help here.
Can people use @DallasCZ backup-all.bat script and extract the original partitions of their phone to share with me?
I need at least to try to get the modem to it's original state.
Again, it's for 6045Y.
Thanks all for your help.
Sent from my GT-I9000 using XDA Free mobile app
Click to expand...
Click to collapse
Any chance the radio to be turned off ? Dial *#*#4636#*#* and look at the phone info. Almost at the end of the page there is a button turn radio off/on. There is also an option to select the radio band under the three dots menu from there.

petrov.0 said:
Any chance the radio to be turned off ? Dial *#*#4636#*#* and look at the phone info. Almost at the end of the page there is a button turn radio off/on. There is also an option to select the radio band under the three dots menu from there.
Click to expand...
Click to collapse
Already checked that. Radio is on and bands are well selected.
I found a thread for similar issue when googling the first line of my logcat. It's on XDA forum as well, CM12.1 development for the oneplus one. They lost connection as well.
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Already checked that. Radio is on and bands are well selected.
I found a thread for similar issue when googling the first line of my logcat. It's on XDA forum as well, CM12.1 development for the oneplus one. They lost connection as well.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
so found any solution for the problem ?

i made it dozen times on google nexus s and zte v9180 it was allways about to flash the radio file (modem, or NON-HLOS.img) , but now we heve to flash the NON-HLOS.img but since w edont have it there is maybe only way to push the modem file trough adb command (the reverse way i extracted it). But since we dont know what files are needed also it can work or not.
There were some guys from htcmania.com from spain I think. They made one build of 5.0.2 for 6045Y .. they should have the right modem files (if they have it in the rom). but unfotunatelly they removed the links because of some bugs (not modem related). There is a thread in development section. Contact the OP and ask for the link to the rom.

yash_rathore25 said:
so found any solution for the problem ?
Click to expand...
Click to collapse
Nope, they did not care that much as they had original ROM's to flash and solve the issue...
@DallasCZ:
You're talking about this thread?
http://www.htcmania.com/showthread.php?t=1045981
http://forum.xda-developers.com/idol-3/development/rom-arde-dev-team-v1-5-0-2-idol3-stock-t3167082
I've just sent a mail to franq36. We'll see.

Found the link back guy's!!!!! Downloading.
https://mega.nz/#!QBpgXKja!Z-_IAMlMDAsU5eQx6hwSxoSlZl_ZLePytE0qqXR6vOU
Found here:
http://forum.frandroid.com/topic/224636-rom-arde-dev-team/

And these informations don't hurt...
MD5 : f114a0a048f9bfac2d9b92582bc6d058
ZIP size : 1.11GO
Version : V1
Développeurs Rom: Acura2201, josepica481, franq36

Just an idea ... the updater script from the ported rom resets the modemst1 and modemst2 partitions. Try to reset them by the same way (prepare an updater-script for this) after flashing the backup of the modem.img from @DallasCZ. Also reflash the fsg partition ... ask @DallasCZ to make backup of it ... the current baseband version is definitely stored there, and somehow controls the modem ... and let's hope that will boot afterwards ...

@petrov.0:
You suggest not flashing the rom?
I don't know anything about development. I'm just a Linux user who learned to read before asking... So I can't do any updater-script.

I tried to flash the rom with "partial" success. Something has been flashed, but it was super fast. No specific thing shown in verbose mode in TWRP.
Just a warning before flashing:
E:Invalid block device on `/sdcard ext4 [][][]flags=display="Internal SD" ; symlink
', 'flags=display="Internal SD" ; symlink' , 27
Then regular flash. But on the french forum where I found the link, all the comments were... first boot super long as it has to install things, etc...
What am I missing here?

Anghirrim said:
@petrov.0:
You suggest not flashing the rom?
I don't know anything about development. I'm just a Linux user who learned to read before asking... So I can't do any updater-script.
Click to expand...
Click to collapse
Which ROM the Andre Dev ? Flash whatever you want its a trial and error process already ... At least the Mobile Upgrade Q can recover the phone now ... or at least for now ... I'm also a Linux user ... read the content of these partitions (or at least the human readable part). You have the necessary tools to do this from your Linux box.
---------- Post added at 23:08 ---------- Previous post was at 22:57 ----------
Anghirrim said:
I tried to flash the rom with "partial" success. Something has been flashed, but it was super fast. No specific thing shown in verbose mode in TWRP.
Just a warning before flashing:
E:Invalid block device on `/sdcard ext4 [][][]flags=display="Internal SD" ; symlink
', 'flags=display="Internal SD" ; symlink' , 27
Then regular flash. But on the french forum where I found the link, all the comments were... first boot super long as it has to install things, etc...
What am I missing here?
Click to expand...
Click to collapse
This message is there from the boot of the recovery. The reason for the "super fast flash" is somewhere else. Check the recovery.log under /tmp/

petrov.0 said:
This message is there from the boot of the recovery. The reason for the "super fast flash" is somewhere else. Check the recovery.log under /tmp/
Click to expand...
Click to collapse
OK, I'll try to reflash but I just extracted the rom and looked the updater-script. It just udpate files in /system and flashes boot.img.
Nothing about modem or anything else.

Anghirrim said:
OK, I'll try to reflash but I just extracted the rom and looked the updater-script. It just udpate files in /system and flashes boot.img.
Nothing about modem or anything else.
Click to expand...
Click to collapse
That updater script only does system and boot...they've already cleaned it similar to how I did. I can give you a copy of the USA modem if you want to try that one...it's the largest of all of them so far. I would not have installed the arde rom...they pulled it due to issues.
Here's the 6045i usa modem. You will have to unzip it first before flashing via fastboot.
http://www38.zippyshare.com/v/kielTvJd/file.html

OK I'll try. Thanks!
Still:
fastboot -i 0x1bbb flash modem yourmodem.img?

Anghirrim said:
OK I'll try. Thanks!
Still:
fastboot -i 0x1bbb flash modem yourmodem.img?
Click to expand...
Click to collapse
Yep...after unzipping...and I think my image is just called "modem" after you unzip it so it'll be fastboot -i 0x1bbb flash modem modem which is gonna look weird.

@franq36 (the Arde rom developer) is willg to help me and send all partitions if needed.
He posted me a 64Mo 6045Y modem file. I'll try to flash it first. By the way, he told me that modem = NON-HLOS. Is that correct or are they different files?
Thanks all.
Edit: Now, using again Mobile Upgrade Q to get back to a clean situation as the short flash of Arde rom lead to FC's for various apps.

Spanish modem 64Mo img flashed. No success getting signal back.
I'll have to flash partition by partition....
Is it still worth flashing your Modem @famewolf?
Thanks,

Anghirrim said:
Spanish modem 64Mo img flashed. No success getting signal back.
I'll have to flash partition by partition....
Is it still worth flashing your Modem @famewolf?
Thanks,
Click to expand...
Click to collapse
I'd say yes but that's your call...you'll be overwriting it all anyway if it doesn't work with the other french phones partitions.

famewolf said:
I'd say yes but that's your call...you'll be overwriting it all anyway if it doesn't work with the other french phones partitions.
Click to expand...
Click to collapse
So... I think I'll try it a bit later.
If we go step by step, with what I did already:
- Restored the phone /system and boot.img with my backup through TWRP ==> Everything here should be back to normal
- Restored several times with Mobile Upgrade Q ==> Back to an "even more" normal state
- Flashed a spanish modem image 64Mo big ==> This is the largest modem found.
After all of this, I still have no signal back. I'll try to focus on other things changed by the updater-script from the Chinese rom and restore impacted partitions.
If still fails, then I'll try the US modem.

endelss bootloop motog xt1068

MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying android, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i repeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.

Pomar91 said:
MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying sndroid, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i pepeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.
Click to expand...
Click to collapse
do you know if the bootloader is unlocked? if not, that may limit what you can flash and boot. are you wiping the data after flashing the firmware?
are you flashing everything in the stock firmware, or just parts?
if unlocked and didnt wipe, try fastboot -w
if locked, flash the newest firmware available, even that may not be good enough if the absolute newest isnt avaiable, then use the wipe command.
finally, i have no experience with your device. im just stating common practice from other motos i have owned.

Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?

What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?

Pomar91 said:
Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?
Click to expand...
Click to collapse
right
if you flash ALL the partitions in the stock file, and wipe (-w) with an unlocked bootloader, its extremely rare to not boot.

I have been trying this smartphones home fixing and motog is always been ok, it's just weird this, could u recommend me to an expert,and thanks so much

Pomar91 said:
What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?
Click to expand...
Click to collapse
im actually quite knowledgeable with moto, just not your specifically.
there really is no special fix. if you flash all stock partitions, and all pass/install properly, there isnt much else you can do to fix it.

Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?

Pomar91 said:
Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?
Click to expand...
Click to collapse
yea, that would be good, copy all the text from the fastboot terminal so i can see it.
kernel is flashed as part of the stock firmware. cwm is a custom recovery and thats not something we need to think about until its fixed.

Man, even if we can't fix this at the end, I'M LIKE SO GRATEFUL FOR UR TIME, WE WILL IMPROVE together, won't let u down

Hey, @Pomar91, what our friendly fellow is telling you about was the wiping part. Did you do that? That might be the problem - the cause for your bootloop.
tetakpatalked from Nexus 7 flo

Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?

Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
yes its the same as a hard reset, its what i was asking you in my first reply if you did it.
fastboot -w <--this is the hard reset fastboot command
---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------
Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
one more thing, please use the "Quote" button when you reply, so i know you replied to me. thanks

Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?

Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system xxxfilename
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
tetakpatalked from Nexus 7 flo

Pomar91 said:
Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?
Click to expand...
Click to collapse
right
and please stop using the "quick reply" button and use " "reply" thanks
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
tetakpatak said:
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.

bweN diorD said:
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.
Click to expand...
Click to collapse
Possibly some of the partitions had to be enlarged after KitKat. Numerous devices have been doing that step due to ever growing Android OS
I think it was the procedure for the 1st gen Moto G
Do you own it? I have just flashed it on some occasions for friends and family who own it.
tetakpatalked from N7100

all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.

that is it friend
all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
maybe u know what exactly stock rom for xt1068 brasil moto g
aanother thing, this mobile screent shot is the same mistake i got for the auto restore and the manual on fastboot

Pomar91 said:
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
Click to expand...
Click to collapse
is there any possibility you can post the actual fastboot dialogue right into the post? not a screen shot.

IMEI=0 restore with QPST, provided a QCN is available?

First things first, I'm sorry for opening another thread on this but I feel the other ones weren't headed exactly in the correct direction.
A little background:
I was trying to downgrade my XT1541 to Lollipop since 6.0 was really bad and I got frustrated and used
Code:
fastboot erase all
The result was I erased my IMEI and I haven't been able to connect to a network carrier since. The problem can be solved by re-writing my IMEI but that's the difficult part.
What I gathered so far is I can use QPST, backup QCN, go into HEX and change IMEI there, then restore the QCN back to my device. The problem is I can't locate the IMEI in my QCN since my IMEI is now simply 0.
So in all, could someone make a backup of THEIR QCN and send it to me? I would flash it to my XT1541, locate the IMEI (since now I would know what I'm looking for), then change it back to my own.
Does that sound like something that could work? Can anyone help?
UPDATE1: Noone sent me their QCN however I did try to restore the one I backup up (which still has an IMEI=0). QPST Software Download reports
Received an invalid command from the phone.
Click to expand...
Click to collapse
I tried using Qualcomm NV Tools (from EFS Professional), which reads all the information correctly, however when attempting to write the following appears
Cannot Write: NV_UE_IMEI_I
Error: NV_ERR_BAD_SECURITY_STATE
Click to expand...
Click to collapse
So getting another QCN won't help as it seems that I can't write the IMEI (qcn) back to the device...

There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.

acejavelin said:
There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.
Click to expand...
Click to collapse
I have already tried with a full stock rom flash which didnt work...

zeusalmighty said:
I have already tried with a full stock rom flash which didnt work...
Click to expand...
Click to collapse
Well, unfortunately that leaves option 2... or turn it into a media play and buy a new phone.
Funny how `fastboot erase all` causes such a pain for some and not others... but once your IMEI is gone, there isn't much you can do. Moto kinda screwed the pooch on that one.

Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.

Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547

Henriquefeira said:
Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547
Click to expand...
Click to collapse
Thanks but the dd commands wont work since it appears the folder structure is different on the XT1541...any help?

Forever Alone said:
Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.
Click to expand...
Click to collapse
Hey, couldn't get any results with the xposed module

Just one bump

One last effort, not a bump. If anyone can direct me to commercial services for repairing the IMEI i'd be very greatful. Official Motorola Service wont repair it for me btw.
Thanks

try this guys
http://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362#post68445534

NV Backup Warning - Dynamic partition invalid. Quite the riddle.

UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.

Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.

Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.

So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?

Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work

yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.

vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?

yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.

Have you tried flashing QCN file?

yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?

Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.

Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.

Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!

yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.

I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...

vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me

yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?

vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option

yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it