Related
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.
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.
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
You_got_owned123 said:
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
Click to expand...
Click to collapse
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
bitdomo said:
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
Click to expand...
Click to collapse
Sad to say, I've already tried that.. Even tried to flash stock cache image.
You_got_owned123 said:
Sad to say, I've already tried that.. Even tried to flash stock cache image.
Click to expand...
Click to collapse
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
bitdomo said:
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
Click to expand...
Click to collapse
I've flashed radio, but modem I have not. I'll have to try that!
You_got_owned123 said:
I've flashed radio, but modem I have not. I'll have to try that!
Click to expand...
Click to collapse
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
rootSU said:
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
Click to expand...
Click to collapse
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
See my signature
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
Or check my signature.
Someone calls it modem and someone calls it radio.
rootSU said:
See my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
I help a lot of people. I cannot pick out individual instances.
Use LG flashtool
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
bitdomo said:
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
Click to expand...
Click to collapse
Perist will not mount. I hasn't seen factory image for persist partition.
You_got_owned123 said:
Perist will not mount. I hasn't seen factory image for persist partition.
Click to expand...
Click to collapse
Because there arent any. It is unique for every device like efs.
bitdomo said:
Because there arent any. It is unique for every device like efs.
Click to expand...
Click to collapse
So is that a problem?
You_got_owned123 said:
So is that a problem?
Click to expand...
Click to collapse
If you see that /persist cannot be mounted then it could be.
bitdomo said:
If you see that /persist cannot be mounted then it could be.
Click to expand...
Click to collapse
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
You_got_owned123 said:
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
Click to expand...
Click to collapse
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
bitdomo said:
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
Click to expand...
Click to collapse
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
You_got_owned123 said:
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
Click to expand...
Click to collapse
It would be nice if you would post how did you solve your issue. Some will learn and it could help others having the same issue.
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
I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks
also wifi calling is nowhere to be found under call settings. It seems like I don't have the setting on this version? thoughts
Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom
rash.m2k said:
Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom
Click to expand...
Click to collapse
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?
Brighter85 said:
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?
Click to expand...
Click to collapse
I didn't restore, I tried out the rom first, and then just wiped it. What broke it for me was the wifi mac address somehow became lost while using it, maybe some software glitch only by flashing the same variant was I able to restore it.
Best to root and then backup and restore
Brighter85 said:
I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks
Click to expand...
Click to collapse
Just reinstall the kdz with refurbish option
dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks
Brighter85 said:
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks
Click to expand...
Click to collapse
It means flashing the phone again but select refurbish option in lgup
dapolicy said:
It means flashing the phone again but select refurbish option in lgup
Click to expand...
Click to collapse
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.
Brighter85 said:
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.
Click to expand...
Click to collapse
Flash with the kdz you used before, Canadian firmware is better than Korean. In lgup select refurbish instead of partition dl. It won't tamper with your IMEI and you will loose all your data
Hi dapolicy,
I am done with the LG G7ULM since it will never be updated officially.
I really like having the fingerprint sensor on the back and it seems that the LG G8 is the last iteration of phones from LG with this feature and it is an upgrade from the G7.
It is cheap here in the US.
Which version of this phone should I look for? I will be using it on Mint Mobile, so an unlocked one sounds great and all, but then you see what happened to the G7 ULM that never got android 10 unless it was tied to a carrier.
So, what do you suggest I do so I can get the next couple of updates for android with the G8?
Thanks man!
dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
I get the sime problem with my LG WING and I don't know to solve it
Daoud ben said:
I get the sime problem with my LG WING and I don't know to solve it
Click to expand...
Click to collapse
If the firehose was available for the Wing/Velvet you can hex the FTM and fix the NT Code on the Wing.You can try the engineering service menu,but I highly doubt the IMPL is 0 under MID.