Database Info

ICS>Gingerbread Revert For SU760/P920 (SU760 & P920 Confirmed Working!)

The whole idea of this is to fix people's phone's of who'm flashed the SU760 ICS leak but this will be useful to us in the future incase ICS drop's with a major bug or something, then atleast we will then have an option of getting back to Gingerbread. I've attached a picture to the end of the post so you can recognise when the bootloader & other vital partition's being written to, the second image shows no bootloader flash(as what occurs in all p920 firmwares i've flashed).
For SU760 Users
For SU760 users there is a way already discovered on another forum. By flashing V10G they have been able to go back to Froyo/Gingerbread Roms. I've tryed this on my P920 and gets me to recovery but I am unable to boot into Android. The .bin files are attached at he bottom of the post. If you then have imei problems see this post http://forum.xda-developers.com/showthread.php?t=1734330 then you should be back on gingerbread. This is completely untested by me and may bork your phone so you've been warned.
For P920 Users
I have yet to come across a firmware that unbricks or flashes any bootloaders or partition tables, so I have made one for you guys.
So now i've made our own recovery .bin by injecting GPT1 & modified header into an image, it has been confirmed that this method works but I cannot guarantee this will work as intended for you.
Instructions
-Flash The Modified .Bin Or 10G For SU760 User's Using LGFlashTool.
-Then Flash Any Other Froyo/Gingerbread KDZ Or .Bin Immediately Afterwards.
-Boot Up In Recovery & Do A Full Factory Reset.
-Then In Theory You Should Have Reverted Back To Previous OS.
Information
This is confirmed working on the P920 model! This is for people who have either attempted to flash the SU760 ICS leak, want to revert back to gingerbread or don't care about flashing experimental stuff.
X-Loader - /dev/block/mmcblk0p1
U-Boot - /dev/block/mmcblk0p4
Downloads
SU760
-V10G For SU760 - http://d-h.st/2ag
P920
-P920 GPT1 & Modified Header .Bin File - http://d-h.st/COn
-P920 Backup Of mmcblk0p1-4 - http://forum.xda-developers.com/attachment.php?attachmentid=1325858&d=1347623892 (Thanks berni)
-P920 X-Loader & U-Boot Compiled From Source - http://d-h.st/qKR
-P920 GPT1-Recovery Partitions & PIT Information - http://forum.xda-developers.com/showpost.php?p=31931615&postcount=65 (Thanks zogu)
BIG Thanks To
zogu, berni987654321, xafalo, xbsall, defcomg, bdadd

Samno i think you should start with HK V10A.
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP920/AHKGML/V10a_00/V10A_00.kdz
I remember that i bought my O3D with v10B i had another update (i think August was v10D ) and after that v10K ..

Cant find a link but i think V18A was GB Beta LGP920AT-00-V18a-AMA-XXX-OCT-28-2011 maybe someone might have it backed up

samno said:
For SU760 Users
By flashing V10G [...] I've tryed this on my P920 and gets me to recovery
Click to expand...
Click to collapse
did you try to put cwm in?
http://forum.xda-developers.com/showpost.php?p=28259838&postcount=105

Lots of P920 kdz's here:
http://lg-phone-firmware.com/index.php?id_mod=2

i think what samno is trying to do is find someone who has come across a firmware which can flash back to the original bootloader. this saves him having to download 40 odd different firmware, each ranging around 340mb~400mb, to find if there is. this saves him time and he doesnt have to dl 15.2 gb of each and every firmware.
PLUS it could help us in general ,in the near future if lg pulls a dodgy lol

Try to patch froyo firmware with CWM then you can see partitions with adb in CWM. And try to change bootloader or other partitions with stock one with dd command in adb.
Sent from my LG-P920 using xda app-developers app

Tryed that tool berni but it could'nt find the offsets so i'll have to do it manually. Thanks iodak good idea. rezzsha that's exactly what im trying to do mate.

Samno, i'm not sure where is boot loader, is it on boot partition or on some flash memory only for boot and bb, it sounds to easy to install boot with dd. If you need backup of some partition with dd i can attach it here, installed your kernel few times with dd. Can you reach mode where you can use adb? Maybe only need to repartition flash because of different p table in ics?
Sent from my LG-P920 using xda app-developers app

It can be done with dd i restored partitons on my phone with it in CWM adb is working in cwm. Bootlader is mountblock1, 2 is nv1, 3 is nv2.... Also if you can get to cwm you can use parted to repartition. there is guide on general section. I didn't try to restore bootloader but it is working with other partitions. Sorry for bad english.
http://forum.xda-developers.com/showthread.php?t=1509195
Sent from my LG-P920 using xda app-developers app

im not sure about this. but i think it will work.
flash your p920 with v10g for su760, if successful upgrade it to v21e gingerbread for p920. i think it should work.

Loaders
Hi guys could someone do a copy of there bootloaders and upload here please. I think they are mmcblk0p1 & mmcblk0p4. but could someone go through 1 to 4 just in case.
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.backup bs 4096
At least we will have a copy of the loaders here just incase.

In mmcblk0p3 there is emai and some other data, if you need it i can send you on pm. Others are attached.

mmcblk0p3 is almost all zero, it has imei, serial and baseband version (ascii readable) on 2 or 3 different places, and maybe 20-30 other characters on random places, everything else is zero. Compare with your, maybe you just need to enter serial and emai on right places.

here is mmcblk0p1-0p4 in one zip plus descrription

berni987654321 said:
here is mmcblk0p1-0p4 in one zip plus descrription
Click to expand...
Click to collapse
But nv3 has to be changed in hex editor?

I don't know much about that I just copied it wit dd if to my sdcard and than put it on the pc to zip it

mmcblk0p3 stores the phone's unique info such as imei, wifi mac address, bluetooth mac address and other unique data. As far as I know this partition is not written even during firmware upgrades, so it's only written once at the factory then left untouched, and probably for good reason too. If we study it and figure out where important data is stored, we can restore IMEI and the like should something really bad happen to someone's phone.

pandaball said:
mmcblk0p3 stores the phone's unique info such as imei, wifi mac address, bluetooth mac address and other unique data. As far as I know this partition is not written even during firmware upgrades, so it's only written once at the factory then left untouched, and probably for good reason too. If we study it and figure out where important data is stored, we can restore IMEI and the like should something really bad happen to someone's phone.
Click to expand...
Click to collapse
It is written during software update, there is info about software version inside. I don't know how it works, does it only change software version or it is written from beginning during software update (bb update I think).

zogu said:
It is written during software update, there is info about software version inside. I don't know how it works, does it only change software version or it is written from beginning during software update (bb update I think).
Click to expand...
Click to collapse
Yes that is true. I did try to restore IMEI that way but it is not posible. Partition is rewritten on firmware flash. IMEI and mac addreses are writen in CP chip eeprom. You can get to it with hyper terminal.
Sent from my LG-P920 using xda app-developers app

[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!

[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!
Hello! After a misadventure I managed to get CM 10.2 to run on my Photon Q, and it was fantastic! Wifi and BT work great. However, accidentally flashing the wrong kernel, I got stuck at the bootloader unlocked screen forever.
So, I reinstalled CM 10.2 and all seemed to be well. (I did this from CWM using a ZIP.) However, I quickly discovered WiFi and BT are both broken! If I hit ON, it goes gray for a second and tries to enable, and goes back to OFF with no error or other response. If I open the WiFi or BT menu and hit ON or SCAN, same result or it just does nothing.
So, I tried to downgrade to something older, something with ICS and not JB, which is what I prefer anyway. TwistedAsanti gets stuck forever at "Starting Services..." and the home screen never comes up, even if left overnight. I get a message that no cell networks were found asking if I want to switch to GSM. It's covered by STARTING SERVICES ... so I can't hit "No", but either way I don't have a carrier, so that's no issue. I use WiFi only. I can pull down the notification bar and go into settings. While there, I see the same problem with WiFi and BT, both are broken. I can't run any apps or get to the homescreen, still.
So, I tried to install 10.1, same result. Then MIUI, Carbon and SlimBean. Same result! I installed TWRP and flashed a backup of Stock JB from WIN files I found here on the forum. It boots up, but this time it's stuck at "Starting Services..." just like TwistedAsanti was. Notification bar works, settings menu works, homescreen won't appear, Starting services never goes away, can't run any apps. Wifi and BT still broken in the same manner.
Now downloading a backup of ICS Stock to see if that works any better, but I'm not holding my breath.
Has anyone ever experienced this? Thanks for any advice. I attached some photos that might help. I had to use my Tracfone because now that is the best camera I have access to, so sorry for the blurriness. I hope it gives you the general idea of what is going on.
EDIT: For each flash, I am wiping data, cache and dalvik cache. I also wiped modem and pds by mistake, could that be the problem? If so, how would I restore those? Thanks
Again, thanks for your time!

Jeez, how many threads do you need to post in? I have responded to all your posts in all of the various threads, INCLUDING your PM's.
Let's focus here, if you want custom we can do that. If you want stock we can do that. Please focus, what do you want.
If you want custom, perhaps you're not wiping everything properly... So boot recovery. Wipe system. Factory reset - wipe data, cache, dalvik-cache, sd-ext. Best to do the actual "factory reset" option than wiping all of those by hand, because wiping /data will wipe /data/media (internal SD) while factory reset will preserve /data/media.
Next, flash ROM of your choice. Twisted Asanti is kinda outdated, hasn't had any attention in a loooong time. Let's try something stable, CM10.1. Flash it. Flash gapps. Boot, do you still have the same issues?

Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.

Loader009 said:
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Click to expand...
Click to collapse
Sorry about that. I'll keep it in one place. Thanks Still trying to get RSD to work, but it won't detect the phone for some reason. Well, on one PC it will, but then it fails to flash saying there was a Remote error (FAIL). On another PC, it won't detect. In BOTH cases, fastboot devices successfully shows the phone. I can even format partitions and flash files. I have successfully flashed TWRP this way.
trying to flash the system image doesn't work with the error "invalid sparse file format at header magi", then fastboot crashes. (What?) So, RSD doesn't work and fastboot kinda works, but not for all the images.
I got a copy of all the kernels I could find .. arrrghhh's for every FW I can think of. Searching out a stock kernel now. It says on the Peas and Q's post that it's just a stock FW with a new name, so I grabbed that too, might be worth a shot...
got CM 10.1, I guess I'll try installing that, and then what do I want, the STOCK kernel? or just use the one that it came with? (How confusing.)
To be more clear, either Stock or Custom is fine. I'm happy with either so long as it boots properly and WiFi works again. Root would be nice but I can worry about that later.

You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
I'm not the guy where you get information about RSD and kind of. I know where to look for and show the right direction.
In the thread I posted you might get help for RSD and you could get help there.
Ask there for help as the more experienced users are reading only the "important" threads and not the "smaller" ones.
(I know this, I do this most time, but I'm not the "know-everything" guy )
As I never needed those FXZ method, I never used it and my RSD Lite experience is rather small.
You might need to install motorola drivers to get it to work but I'm not sure, you should ask in that thread.
PS: If Stock will work again, Custom will work too.
To avoid problems it might be needed to wipe data/cache/dalvik before and after flashing a ROM.

Loader009 said:
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
Click to expand...
Click to collapse
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...

Did you read the following?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
As I said, I never tried the FXZ method and I have no experience on error which could appear.
Ask in that FXZ thread and you may get it work soon.

Epicenter714 said:
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Click to expand...
Click to collapse
Try a different port? Different cable? Different computer? Are you using the stock cable?
Perhaps something else is broken... I'm not sure at this point. Do you have any screenshots of the failure? Any specific output from the software?
Did you edit the XML file properly? I think you did, but you said you were downgrading too - are you always trying ICS or have you tried the FXZ file for JB as well?

Useless thread bump.
Another fellow had the same issue, and was using an old version of RSD Lite. What version are you using?

I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
I tried same and now my phone is alive. But now.IMEI/MEID is gone (zero)
WIFI and bluetooth is now connecting but not receiving any data (useless).
I tried many cdma tool to recover MEID but failed.
I thing we lost EFS partition.
Please look at my thread
http://forum.xda-developers.com/showthread.php?t=2429609
i also need help on that
If any one have EFS backup or something?

lovepreet39 said:
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
i also need help on that
If any one have EFS backup or something?
Click to expand...
Click to collapse
The problem WAS RSD's version! Thanks to everyone for your help. I had 5.6.4 running before and it would always die at System.img.ext4 and one other partition later on. That's on the WinXP system that would see the phone in RSD. The Win8 machine wouldn't see it at all, even in XP compatibility mode with admin rights. Go figure. I'll take this as another excuse to not be fond of Win8.
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?

Epicenter714 said:
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Click to expand...
Click to collapse
I don't understand, are you still having issues? Why are you asking about EFS?

arrrghhh said:
I don't understand, are you still having issues? Why are you asking about EFS?
Click to expand...
Click to collapse
I was replying to lovepreet39 about the EFS thing.

Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help

Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
Yes, but he is having an issue with EFS. You, on the other hand, are not... correct?
You post seems to indicate that despite getting RSD to work, you are still having issues. I want to make sure that is not the case...
lovepreet39 said:
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Click to expand...
Click to collapse
Hey buddy, I would love to help but that is way above my pay grade. I used my Q on Sprint, never liked mucking with that stuff personally.

@arrrghhh
Dear sir
Problem is that i wasted approx $250 on this device.
I am indian and $1 = Rs65 and $250 = Salary of one month.
I am here on XDA to save my $250.
There is no support on this phone in indian market,
If there any solution please help.
You can post here or PM me.
Or there is only by which i can only get my IMEI back, then i will apply GSM addon on it,
I do not care much about CDMA.
I know IMEI/MEID repair is illegal in USA.
For proof I can provide you original images of phone showing Zero Imei/meid
I do not want to change, only i want to restore original one.

IMEI lost and recovered!

Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happened before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realized I had no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happened. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and your IMEI should be back!

drfr said:
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happend before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realised I have no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happend. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messsages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and you´re IMEI should be back!
Click to expand...
Click to collapse
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?

deej_roamer said:
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
Click to expand...
Click to collapse
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.

drfr said:
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
Click to expand...
Click to collapse
Oh I am not criticising your work, I encourage it! I just pointed my point of view!

Added to FAQ (in the lost IMEI section), i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
this is cool you could recover it by flashing stock, so i added your story to FAQ in case it happens again to anyone

Good to know.

matmutant said:
... i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
Click to expand...
Click to collapse
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.

drfr said:
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
Click to expand...
Click to collapse
Gonna try this if I can find some time, even if I don't realy got any hope left after flashing the hell out of this phone..

Didn't work. I used erase all back in the days..

RestlessScreams said:
Didn't work. I used erase all back in the days..
Click to expand...
Click to collapse
Same here, tried with 4.3 and 4.4 german (my phone is)
used erase all back in the days still can see imei on fastboot getvar, imei 0 on mobile.

Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089

drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
thanks mate for your effort!
Sadly fastboot oem writeimei is unsupported in moto g
---------- Post added at 11:26 AM ---------- Previous post was at 11:12 AM ----------
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
about where is SHOULD be, when u do fastboot erase all it deletes those:
modemst1
modemst2
hob
dhob
fsg
fsc
clogo

I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u

Lost IMEI
japoina92 said:
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Click to expand...
Click to collapse
The same situation... Can somebody share the pds folder? I assume that it contains imei.

ol_st said:
The same situation... Can somebody share the pds folder? I assume that it contains imei.
Click to expand...
Click to collapse
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S

recover imei moto g
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance

BUMP: any news on this guys?

Nothing..

killerBRs said:
Nothing..
Click to expand...
Click to collapse
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Younboy69 said:
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
Click to expand...
Click to collapse
tehygav said:
BUMP: any news on this guys?
Click to expand...
Click to collapse
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?

moto
sebastiandg7 said:
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
Click to expand...
Click to collapse
tengo un moto g hay alguna forma de restaurar imei alguna box que se dedique al cambio de imei?

Lost IMEI for Moto G, have no PDS backup

Hi there,
After reflashing stock ROM 4.4.2 because a failure with custom ROM, my IMEI now is 0
I know I can restore it with a pds.img, but I haven't one, how could I get my phone work again?
Thanks

Bump to this thread. Could someone help me...? My /pds folder is empty (at least that's what CM File Manager says), I have no backup, and my IMEI appears as "Unknown"...

I got the same problem. No solution yet :S

Have you tried fastboot flashing the stock firmware to see if that helps?
Probably a long shot.

meekrawb said:
Have you tried fastboot flashing the stock firmware to see if that helps?
Probably a long shot.
Click to expand...
Click to collapse
Why fastboot? What's the difference between it and CWM?
I flashed stock radios today. No luck. Last thing to do is flashing stock, because I've seriously tried everything...
Is there a way to manually input the IMEI in the /pds folder?

Nope. I've already flashed about every rom, factory reset it, etcetera. Even struggled around with hex editors and stuff but the problem is that it's forbidden to 'change' imei so it's kinda hard.
Some dev has to look for a opportunity to get the imei from fastboot (mine shows up there) back to the pds folder or somewhere else..

RestlessScreams said:
Nope. I've already flashed about every rom, factory reset it, etcetera. Even struggled around with hex editors and stuff but the problem is that it's forbidden to 'change' imei so it's kinda hard.
Some dev has to look for a opportunity to get the imei from fastboot (mine shows up there) back to the pds folder or somewhere else..
Click to expand...
Click to collapse
What about this ? ==> http://forum.xda-developers.com/showthread.php?p=52648789 (linked in IMEI entry [Q19] of RC-FAQ)

This guy got a backup :S

RestlessScreams said:
This guy got a backup :S
Click to expand...
Click to collapse
Did you read the whole post ?
As you said, your IMEI isn't destroyed if it shows in fastboot..

matmutant said:
Did you read the whole post ?
As you said, your IMEI isn't destroyed if it shows in fastboot..
Click to expand...
Click to collapse
OK, I downloaded a stock ROM from here, and I followed the instructions shown in this post. I can't believe the motherloving crap worked. I HAVE MY IMEI BACK MOTHERLOVERS!!!!
I HAVE IT BACK!

I just want to tell you guys I was able to isolate the cause of the problem. Maybe someone could find it useful.
The whole problem was because of the kernel I was flashing (this one). There are two versions of that kernel for AOSP ROMs: a standard one and an ANYKERNEL one. Flashing the first one made my IMEI 'unknown'. Flashing the ANYKERNEL one solved the issue. The ROM I was flashing the kernel in was Gummy.
Really strange stuff since it had never happened to me before...

billybully said:
I just want to tell you guys I was able to isolate the cause of the problem. Maybe someone could find it useful.
The whole problem was because of the kernel I was flashing (this one). There are two versions of that kernel for AOSP ROMs: a standard one and an ANYKERNEL one. Flashing the first one made my IMEI 'unknown'. Flashing the ANYKERNEL one solved the issue. The ROM I was flashing the kernel in was Gummy.
Really strange stuff since it had never happened to me before...
Click to expand...
Click to collapse
Its not an issue as I see it. I have made anykernel zips because of this purpose only, some ROMs use different type of ramdisks which cause other developers to not support them at first place. I made anykernel zip for such ROMs so that my kernel can be used on any ROM without any issues. I hope it answers your question.

No Wifi/Mobile data/IMEI, Baseband version Unknown

I have already tried this guide (great info there):
http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55488755#post55488755
Unfortunately, it didn't quite work out for me. The issue I have been having is that the phone reports unknown baseband version and there is no IMEI. Wifi was still working originally. The issues came after I flashed the latest lollipop alpha modem needed for the latest CM12 build/kernel.
After I experienced the issue, I flashed back the 44s modem. Then Wifi was also gone.
As of right now, the best I can do is:
1. Install ColorOS 2.0.0
2. OTA to ColorOS 2.0.4
ColorOS gave me Wifi back.
At this point, I tried to fastboot install TWRP per @NikoZBK suggested. The fastboot command reported successful but it still got the ColorOS recovery. So I have to...
3. Fastboot flash 30o with flash-all.bat
However, by doing so, my Wifi is gone and I still have unknown baseband version and IMEI. Therefore, I went back to (1) and (2), took out this line: fastboot flash modem NON-HLOS.bin in flash-all.bat and run flash-all.bat again.
At this point, Wifi is still working but I still have unknown baseband version and IMEI.
4. Flash pre-rooted 44s in TWRP. The issues are still there.
I also tried doing "make_ext4fs /dev/block/mmcblk0p15" in TWRP and it actually killed Wifi. I am running out of ideas. Any advice is appreciated. Thanks!

radium22 said:
I have already tried this guide (great info there):
http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55488755#post55488755
Unfortunately, it didn't quite work out for me. The issue I have been having is that the phone reports unknown baseband version and there is no IMEI. Wifi was still working originally. The issues came after I flashed the latest lollipop alpha modem needed for the latest CM12 build/kernel.
After I experienced the issue, I flashed back the 44s modem. Then Wifi was also gone.
As of right now, the best I can do is:
1. Install ColorOS 2.0.0
2. OTA to ColorOS 2.0.4
ColorOS gave me Wifi back.
At this point, I tried to fastboot install TWRP per @NikoZBK suggested. The fastboot command reported successful but it still got the ColorOS recovery. So I have to...
3. Fastboot flash 30o with flash-all.bat
However, by doing so, my Wifi is gone and I still have unknown baseband version and IMEI. Therefore, I went back to (1) and (2), took out this line: fastboot flash modem NON-HLOS.bin in flash-all.bat and run flash-all.bat again.
At this point, Wifi is still working but I still have unknown baseband version and IMEI.
4. Flash pre-rooted 44s in TWRP. The issues are still there.
I also tried doing "make_ext4fs /dev/block/mmcblk0p15" in TWRP and it actually killed Wifi. I am running out of ideas. Any advice is appreciated. Thanks!
Click to expand...
Click to collapse
Give this thread a look:http://forum.xda-developers.com/oneplus-one/help/opo-efs-t2821020. Look at page 9 and post 83. I don't know if it will help with your problem, but it fixed mine a few months back.

elrey311 said:
Give this thread a look:http://forum.xda-developers.com/oneplus-one/help/opo-efs-t2821020. Look at page 9 and post 83. I don't know if it will help with your problem, but it fixed mine a few months back.
Click to expand...
Click to collapse
Thanks for the info. I tried that but didn't work out for me unfortunately.

Finally, the issue is fixed!!! Here is what I have done:
1. fastboot flash 22R
2. reboot (No Wifi, No IMEI, Unknown Baseband version)
3. fastboot flash TWRP
4. reboot (Still No Wifi, No IMEI, Unknown Baseband version)
5. Download and copy OnePlus ColorV2.0.4i Beta Native.zip to internal
6. reboot to TWRP and flash OnePlus ColorV2.0.4i Beta Native.zip
7. reboot
8. Wifi, IMEI, mobile data, and baseband version are BACK!

radium22 said:
Finally, the issue is fixed!!! Here is what I have done:
1. fastboot flash 22R
2. reboot (No Wifi, No IMEI, Unknown Baseband version)
3. fastboot flash TWRP
4. reboot (Still No Wifi, No IMEI, Unknown Baseband version)
5. Download and copy OnePlus ColorV2.0.4i Beta Native.zip to internal
6. reboot to TWRP and flash OnePlus ColorV2.0.4i Beta Native.zip
7. reboot
8. Wifi, IMEI, mobile data, and baseband version are BACK!
Click to expand...
Click to collapse
Where did you find this 'OnePlus ColorV2.0.4i Beta Native.zip' file?

Vleiss said:
Where did you find this 'OnePlus ColorV2.0.4i Beta Native.zip' file?
Click to expand...
Click to collapse
can u pls share this file if u find it..?
OnePlus ColorV2.0.4i Beta Native.zip

I tried all methods, delete modemst1 and modemst2. Flash coloros manually, write imei with QPST (With this method regained imei but no signal and information is provided "radio off" and I can not find networks manually. I tried almost everything and can not get anything, just wi-fi. Someone having a backup of efs ?? or qcn?? , if you do not want to share the imei, blur the line 550, i need a backup of a running device., I will not clone or anything, I just need to repair my data qcn as there are 6468 and only have 5 lines with values.

rombdeta said:
I tried all methods, delete modemst1 and modemst2. Flash coloros manually, write imei with QPST (With this method regained imei but no signal and information is provided "radio off" and I can not find networks manually. I tried almost everything and can not get anything, just wi-fi. Someone having a backup of efs ?? or qcn?? , if you do not want to share the imei, blur the line 550, i need a backup of a running device., I will not clone or anything, I just need to repair my data qcn as there are 6468 and only have 5 lines with values.
Click to expand...
Click to collapse
I think its illegal to share these kind of information. I might be wrong though.
I know that you will not clone the IMEI but its against the rules to share this info.
Someone will be able to help you, I guess!!!

rombdeta said:
I tried all methods, delete modemst1 and modemst2. Flash coloros manually, write imei with QPST (With this method regained imei but no signal and information is provided "radio off" and I can not find networks manually. I tried almost everything and can not get anything, just wi-fi. Someone having a backup of efs ?? or qcn?? , if you do not want to share the imei, blur the line 550, i need a backup of a running device., I will not clone or anything, I just need to repair my data qcn as there are 6468 and only have 5 lines with values.
Click to expand...
Click to collapse
Shankar9822 said:
I think its illegal to share these kind of information. I might be wrong though.
I know that you will not clone the IMEI but its against the rules to share this info.
Someone will be able to help you, I guess!!!
Click to expand...
Click to collapse
Hi, @rombdeta, unfortunately for you @Shankar9822 is right, nobody can share their EFS backup with you. It's up to each user to backup their own EFS partition for safekeeping, this information is readily available all over this device section on XDA and on the OnePlus forums.
Transmitted via Bacon

Okay, you are right, i understend. But QCN, is different, have a parameters of the network. Is only that i need, because i have repaired imxx, wifi, bluetooth, but in the radio signal i have 0 dbm 99 asu, because i haven't the radio band who is in the QCN, and the information on this. If i can repair that, i will make a guide to recover imei without a EFS backup, so please help me with the QCN. Best regards.

After 10 days without the phone, and read about QCN in many sites and much info, i repair my device. For anyone who has tried all possible solutions, to no avail, they sent me a message, I will gladly help you. But I can't open a guide as I have understood, so this is the only solution I can currently provide. Thanks everyone. Greetings To You!

rombdeta said:
After 10 days without the phone, and read about QCN in many sites and much info, i repair my device. For anyone who has tried all possible solutions, to no avail, they sent me a message, I will gladly help you. But I can't open a guide as I have understood, so this is the only solution I can currently provide. Thanks everyone. Greetings To You!
Click to expand...
Click to collapse
If you're going to help people please don't do it via PM, do it here in the forums, solutions don't benefit the community when they're hidden away in an inbox.
Transmitted via Bacon

Ok, i will make a guide. OnePlus people told me they have no redress for the device, so I started reading and researching and with the help of many people, I put together a QCN with valid values, hand made in RF NV Item Manager. Therefore sought an original QCN. Tomorrow i will make a full guide. Regards and sorry about my english.

Thanks, good idea.
PS. There's nothing wrong with your English.

rombdeta said:
Ok, i will make a guide. OnePlus people told me they have no redress for the device, so I started reading and researching and with the help of many people, I put together a QCN with valid values, hand made in RF NV Item Manager. Therefore sought an original QCN. Tomorrow i will make a full guide. Regards and sorry about my english.
Click to expand...
Click to collapse
Do you have 2g (gsm only) and 3g/2g auto mode ? ( you probably dont need 2g but some do).

rombdeta said:
Okay, you are right, i understend. But QCN, is different, have a parameters of the network. Is only that i need, because i have repaired imxx, wifi, bluetooth, but in the radio signal i have 0 dbm 99 asu, because i haven't the radio band who is in the QCN, and the information on this. If i can repair that, i will make a guide to recover imei without a EFS backup, so please help me with the QCN. Best regards.
Click to expand...
Click to collapse
Hi, I have restored with QCN and edited now I have my IMEI and Baseband but the signal is 0 dbm 99 asu
I've tried to flash again the modem, change rom but nothing as changed... How do you have solved?

Yeah I haven't been able to get any service on my phone for awhile now it's been nothing but frustrating... Nothing I do seems to work I've on the verge of just throwing this phone against the wall a few times
Sent from my D6503 using XDA Free mobile app

No Wifi/networ/imei working
rombdeta said:
Okay, you are right, i understend. But QCN, is different, have a parameters of the network. Is only that i need, because i have repaired imxx, wifi, bluetooth, but in the radio signal i have 0 dbm 99 asu, because i haven't the radio band who is in the QCN, and the information on this. If i can repair that, i will make a guide to recover imei without a EFS backup, so please help me with the QCN. Best regards.
Click to expand...
Click to collapse
Hello,
Can you please help me with this.
My phone showing unknown baseband version.