I attempted to re-flash the stock firmware for the XT1625 off the Moto website, and in doing so my phone does not display my IMEI number anymore and therefore will not activate on the cell network. I have re-flashed using the XT1625 build MPJ24.139.49 and followed all instructions but it still shows all 0's. When I run fastboot getvar IMEI it does display the correct IMEI. This is just an unlocked non-amazon variant.
Same problem here. Tried talking to moto rep they won't do anything since my bootloader is unlocked voiding warranty. Have u tried flashing mpj24.139.64 from file factory folder for moto g? May work for you.
JKASS5 said:
Same problem here. Tried talking to moto rep they won't do anything since my bootloader is unlocked voiding warranty. Have u tried flashing mpj24.139.64 from file factory folder for moto g? May work for you.
Click to expand...
Click to collapse
Thanks, yea I tried flashing that file and had no luck. I mailed it into Motorola and somehow? they went ahead and sent me a new one. I did the ticket online and clearly advised that the bootloader was unlocked and the IMEI was lost when I flashed the files off the motorola website.
Related
I'm not sure if this is going to end up as a fix or a cautionary tale, but here goes.
Was looking to root my g4, so I successfully unlocked the bootloader & installed TWRP using this method: http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Things were going pretty good there, but when I tried to install the SU image through TWRP, the phone wouldn't boot.
Naturally, I didn't do a backup of the stock state of the phone (BECAUSE I'M AN IDIOT!) so I figured, what the hell, might as well install cyanogen mod, and see what that's all about. There's a cyanogenmod beta for the G4+. It went on smooth through the TWRP installer and was behaving ok, but wouldn't see the SIM. I check the IMEI number and the phone does not have a value set, just blank space.
I then tried to re flash stock firmware on the phone, thinking that might restore the IMEI.
It was a bear to get on there, but I was pretty proud of myself when it booted.
Trouble is: still no IMEI number. Also no wifi and it can't see the SIM card (probably because no IMEI number).
So, I figured I'd go back to the cyanogenmod, and see if I could somehow trick it into an IMEI number, BUT! re-loading the firmware re-locked the bootloader.
I went through the unlock process at motorola again, but this time she won't unlock. The console is throwing me
Code:
...
(bootloader) invalid boot state
OKAY [ 0.005s]
.
So, from here, I don't know where to go. Try re-flashing cyanogenmod on it manually I guess, but I don't know if that will work with the bootloader perpetually locked.
Can anyone help me sort this out?
Please?
How did u flash the stock ROM? Did u flash the right one for your device.
Sent from my Moto G⁴ Plus using Tapatalk
Silesh.Nair said:
How did u flash the stock ROM? Did u flash the right one for your device.
Sent from my Moto G⁴ Plus using Tapatalk
Click to expand...
Click to collapse
I flashed the stock rom on manually from the terminal using fastboot. Evidently: it isn't the right version. After careful inspection, it seems like I loaded the Indian / Asian version, whereas my device is the Canadian version.
Unfortunately, the Canadian stock firmware is still listed as a work in progress.
And the file names are confusing as hell. My device model is xt1643 but my stock ROM doesn't even mention 1643 in the file name. What's your model number?
Sent from my Moto G⁴ Plus using Tapatalk
Silesh.Nair said:
And the file names are confusing as hell. My device model is xt1643 but my stock ROM doesn't even mention 1643 in the file name. What's your model number?
Sent from my Moto G⁴ Plus using Tapatalk
Click to expand...
Click to collapse
it's model XT1641, bought in Canada.
Did you turn on unlock bootloader option in Dev settings ?
W0000000ooooooooooooooooooHooooooo00000000000000000000000000!!!:victory:
We're back in business, kids!
Found the stock rom for the Canadian Retail build (not locked to carrier) here: https://mirrors.lolinet.com/firmware/moto/athene/official/RETCA/
It took forever to download, but once it showed up, I flashed it on with fastboot, fired 'er up, and it's the same old stock G4 with working wifi, that can see the SIM & Connect to the network, complete with IMEI number AND - I believe - an unlocked bootloader.... at least I get the unlocked bootloader warning screen on boot.
Varun: I saw your message when I was getting set to flash the firmware on and got set to put my palm through my head. You're right: it could have been just the switch in developer options. But I checked and it was on.
Maybe the mods can add that firmware to the big firmware download links post.
Now, you'd think that having just brought this thing back from the dead I'd leave well enough alone and quit fiddling with this thing, but...
Maybe the owner of the newbie thread should add a post with "take a backup through twrp"
varun.katoch said:
Did you turn on unlock bootloader option in Dev settings ?
Click to expand...
Click to collapse
had the same issue. forgot to turn on usb debugging
So I bought this moto X Play a few weeks ago and it was fine. Then I rooted it to gain access to some shady things but didn't change much in the phone, nor did I install many ROMs or however you call it. It was fine till I learned that Niantic was blocking access to pokemon go to rooted phones.
So I tried unrooting it, to root it again with the Magisk root or something. I couldn't unroot with SuperSU, even though when I rooted it, that was the only thing I used. So I followed instructions, I backed up my data, I factory reset using TWRP, then it was time to flash a factory image, so I downloaded the ADB fastboot and the stock rom, I downloaded the firmware:
"XT1563_LUX_RETLA_DS_6.0.1_MPD24.107-52.xml" (I searched through the options and found my area, Latin America, made sure it was 6.0.1 just like I used, and made sure it had the correct build number).
So I followed the instructions, did everything correctly, and when I entered the code fastboot reboot, my phone got stuck in a Warning, Bootloader Unlocked screen, followed by an "erasing" screen with the android logo moving its antennae, followed by a vibration and a restart which starts everything again. I'm heartbroken now, I don't know what to do.
PD: I think I might have downloaded the wrong firmware, (it says DS in the name, which I think is Dual Sim, and I only have 1 inside), don't know if I can keep trying.
PD2: Pls halp
PD3: Like you might have guessed, I did unlock the bootloader before rooting, but now it seems that's the problem for the unrooting.
sher_31 said:
So I bought this moto X Play a few weeks ago...
Click to expand...
Click to collapse
Maybe you didn't flash all the sparsechunks? Get single sim firmware and try again
minimale_ldz said:
Maybe you didn't flash all the sparsechunks? Get single sim firmware and try again
Click to expand...
Click to collapse
I love you :highfive:
Is there any possible way to re-lock my bootloader and get back the warranty of my device?
Some buddy posted in my Kernel's thread that you should be able to do:
fastboot reboot oem-lock
But idk if this has some kind of sense and after unlocking BL your device is marked as non-appliable for warranty in Moto's database.
https://firmware.center/firmware/Motorola/Moto G4 Play/
Go to here and find right for your moto g4 play edition. And flash.
Sent from my XT1068 using Tapatalk
abhimanyuk said:
Is there any possible way to re-lock my bootloader and get back the warranty of my device?
Click to expand...
Click to collapse
Don't, after unlock you lose the warranty, if you re-lock after, the bootloader status don't go back to when you buyed the device (In the same way it says unlocked in the bootloader, it also says that it has been relocked), so it's useless.
And like facuarmo said:
facuarmo said:
Your device is marked as non-appliable for warranty in Moto's database.
Click to expand...
Click to collapse
Yeah, you can't get your warranty back once you've unlocked the boot loader. The fastboot command mentioned above can be used to re-lock your boot loader but that won't bring back warranty of your device.
How unlock New Oreo bootoader C0.92? Motorola site dont do this for this version .... After update to Oreo...my IMEI is 0 ...so i need unlock bootoader to flash twrp and flash EFS! 7.0 unlock ok but 8.1 no
Bootoader can be downgraded?
Yes, if you want hard-brick.
To install TWRP with this put the EFS to return the IMEI, this new bootloader must be unlocked, in the site of the motorola says that the device is not unlockable, with the old bootloader was, and wanted to know if anyone has any idea how To solve this, would I have some way without having to enter the motorola website?
anyone who has upgraded to oreo with the official zip could get on Motorola's website whether the device is unlockable or not? Has anyone tried unlocking the C0.92 bootloader yet? only I who tried and saw that it can not? (I.e.
Thank you for letting us know that unlocking might be a problem after upgrading. I've been waiting to unlock until I get the update, but because of your post I won't have the problem that you did. Your sacrifice wasn't in vain!
I had my doubts whether moto would let us unlock BL easily and promptly, thats why just few days before the official 8.1, I unlocked, twrp+rooted and flashed AEX.
Lucky me.
But I am sure soon there will be some way to unlock BL of 8.1
Till then dont try anythng stupid as u asked about "dwngrading BL" which is potential brick.
Did you select "allow oem unlocking" in developer settings?
I have a untouched bootloader, i wish i had knew this before i installed the Oreo OTA, my G5 Plus is retbr and lenovo/motorola site tells me that my device isn't qualified for unlock too, really sad.
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
motolio said:
Did you select "allow oem unlocking" in developer settings?
Click to expand...
Click to collapse
yes...
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
you did? oO....with bootloader C0.92? tried many times e nothing... unlock have a limite of times on motorolas website?
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
mine bootload codes have 4 lines...in the exemple have 5 lines....
Yeap, tried on my C0.92 bootloader and it didn't let me unlock my phone either. Please Lenovo, don't do this to us.
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
That's great news!
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
ok guys....this guide is true!!! bootloader unlocked now.....thx bro!
Unlocked.... Restaured EFS and get IMEI....but with no signal.... EFS work only with old bootloader...
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
david.gs.gm said:
ok guys....this guide is true!!! bootloader unlocked now.....thx bro!
Click to expand...
Click to collapse
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
prokaryotic cell said:
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
Click to expand...
Click to collapse
Exactly. There is no other way to get your bootloader unlocked.
Sent from my Moto G5 Plus using XDA Labs
prokaryotic cell said:
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
Click to expand...
Click to collapse
I was trying to unlock using the brazilian website, that is basically the same besides is obviously written in portuguese. The site on the guide seems that is a north american version. It worked, that's what matters.
i unlocked the bootloader, put twrp, flashed my efs and my imei return, ok....but have no signal oO, downgraded to nougat and with EFS, have IMEI and signal ok, only on oreo i dont have signal ... with TWRP flashable Oreo is same.
looking at the *#*#4636#*#* says that the radio is off, I have the IMEI that I got through my backup of EFS, this occurs only in the oreo, in 7.0 when using EFS everything is normal, only the VoLTE is missing.
I installed the HavocOS on my LG G6 H870. When I needed to make use of the warranty because of a broken headphone jack, I tried to install a Stock Rom. I used the "international" version from here since I live in Germany (also locked the bootloader before).
However, the service by the warranty provider was denied because they identified my phone as "G6 Dual (LGH870DS)" and were therefore not responsible for repairs.
However, in the phone info, the model is labeled "LG-H870". Hardware Version "Rev. 1.0". Baseband Version "MPSS.TH.2.0.1.c3.1-00014-M8996FAAAANAZM-1.86009.21" and Software Version "V10d-EUR-XX".
I can not really understand their reasoning. Does anybody have an idea what Stock Rom I need to flash so that the warranty provider accepts it? Note: the phone was serviced by them before because of another issue, but at a point when I did not yet flash a custom Rom.
Thanks in advance
If You live in Germany, EU law says that manufacturer can't cancel Your warranty because of unlocked bootloader unless Your phone is not modified. So if there are no signs of modification like root, wrong firmware or custom recovery they can't cancel it. If You have H870 model flash >>>THIS<<< firmware and then in fastboot type fastboot oem lock to make sure bootloader is locked and wipe phone.
Chamelleon said:
If You live in Germany, EU law says that manufacturer can't cancel Your warranty because of unlocked bootloader unless Your phone is not modified. So if there are no signs of modification like root, wrong firmware or custom recovery they can't cancel it. If You have H870 model flash >>>THIS<<< firmware and then in fastboot type fastboot oem lock to make sure bootloader is locked and wipe phone.
Click to expand...
Click to collapse
Thanks!
I'm going to flash the ROM from the link you provided and then send it out for service a second time.
In my eyes there are two possible explanations for the previous rejection:
1. The service provider made a mistake in their routine of detecting the model/software version. The fact that I put a custom rom on the phone before might have caused an issue there.
2. I made a mistake when flashing the H870 software. The source from my first post also does not seem to be an official LG link, other than the one you provided.
So thanks for the link again!
Edit: Should I still use the flashing guide from here (https://www.**********.com/download...-g6/#How_to_Install_Stock_Firmware_on_LG_G6)? The website is droid views (one word), it gets deleted by xda for some reason.
Not sure if relevant, but I had to use this tool (https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295) so that my phone would show up in LGUP...
I use Z3x for LG flashing so don't know much about LGUP but I assume if there is an option to flash stock KDZ files it's what You need. I'm almost sure that You can't flash H870 with KDZ different than stock but again never tried mixing firmwares.
huzgu444 said:
Thanks!
I'm going to flash the ROM from the link you provided and then send it out for service a second time.
In my eyes there are two possible explanations for the previous rejection:
1. The service provider made a mistake in their routine of detecting the model/software version. The fact that I put a custom rom on the phone before might have caused an issue there.
2. I made a mistake when flashing the H870 software. The source from my first post also does not seem to be an official LG link, other than the one you provided.
So thanks for the link again!
Edit: Should I still use the flashing guide from here (https://www.**********.com/download...-g6/#How_to_Install_Stock_Firmware_on_LG_G6)? The website is droid views (one word), it gets deleted by xda for some reason.
Not sure if relevant, but I had to use this tool (https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295) so that my phone would show up in LGUP...
Click to expand...
Click to collapse
I would guess it is simple to tell if you have H870 or H870DS as the H870DS has 64GB storage and the H870 only 32GB. Also the DS has 2 SIM card slots. Goto Settings, Storage and look at the internal storage, my H870 says 25.94GB used of 32.00GB
Sent from my LG-H870 using Tapatalk
Chamelleon said:
If You live in Germany, EU law says that manufacturer can't cancel Your warranty because of unlocked bootloader unless Your phone is not modified. So if there are no signs of modification like root, wrong firmware or custom recovery they can't cancel it. If You have H870 model flash >>>THIS<<< firmware and then in fastboot type fastboot oem lock to make sure bootloader is locked and wipe phone.
Click to expand...
Click to collapse
The service provider now accepted the device with the firmware from the link you provided and repaired it without any charge. Thanks again!