No imei XT995-2 - Moto G7 Power Questions & Answers

My moto g7 power got stuck on bootlogo (just because) and I tried to reflash the Stock ROM; i've tried several timer and no ROM was working for me, not even the Lenovo repair official software. (LMSA)
I tried a last time with the LMSA (It flashed android 10 Q) and flashed android 9 NON-HLOS.bin version. It worked but my IMEI is "unknown". when i do *#06# I just got serial number
I've tried flashing Android 10 NON-HLOS.bin and the phone doesn't boot. I'm pretty sure i'm using downloading correct versions (amxmx)
No other combination boots my phone, only with Android 10 from LMSA and the adroid 9 NON-HLOS.bin i've got from internet
By that i can't unlock my bootloader (Oem unlock is grayed)
There is any way to recover my emai?

Related

faulthy rom, locked my bootloader..

My problems concerns a Moto E 2015, but I think it could also occur on a Moto G 2015. I hope someone has experience with a situation like I have.. The phone is in a state where I can't accomplish anything
I think I bricked my Moto E 2015 (XT1524) yesterday. I tried to go to stock from cm13, every factory flash I did resulted in a "unlock bootloader" screen bootloop (tried stock 5.0.2, 5.1.1 retail europe). Then in a brainfart moment I locked my bootloader while a (bootloop causing) 5.1.1 rom was installed. This caused that I am only able to flash that particular 5.1.1 rom, otherwise I get a "preflash validation failed". The problem is that this 5.1.1 rom is not working so I can't boot and configure OEM unlock. I am also not able to flash another factory image, since it is blocked by the bootloader. I think I am out of options? I tried flashing the 5.1.1 rom according to the instructions (http://forum.xda-developers.com/moto...mware-t3044936). The 5.1.1 rom I am refering to is called:
XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC_.xml.zip
With my current bootloader it seems that this rom is the only one I can flash... Is my phone bricked?
edit: I forgot to mention, I can only boot into fastboot mode, no twrp recovery nor stock recovery (I can flash it to the phone though). It just immedeately boots into fastboot mode (i see a short flash of the "bootloader unlocked" warning, then fastboot).

Locked and only can enter erecovery, any way to save it

I was trying to flash stock rom on my mate 9 after having it rooted for about a month. I was using HWOTA and I think I messed up because I did not have my unlock code written somewhere and could not continue the final steps to flash the stock rom. And so now, it says phone locked in fastboot and powering up the phone boots into erecovery default, which says getting package info failed. Can't get into twrp anymore as well. Is there any way to make my phone normal again. The phone is an Australian Vodafone mate 9, start with L09, single sim, not sure about the rest of the numbers.

oem unlocked is not allowed in MI A1 (Bootloader unlocked faild)

Hi all mi a1 users sorry for my bad english but i got problem same like this
https://forum.xda-developers.com/mi-a1/help/remote-oem-unlocked-allowed-mi-a1-t3795850
I unlocked its bootloader 5-6 times and also flashed custom roms & downgraded 9.0 pie to nought 2-3 times but now while again downgrading it but now , it just appear a white screen with Mi logo & bootloop
I also tried flashing in edl mode with mi usb cable because i have not (edl cable) but it also does not worked for me with normal cable i have also updated drivers and tried mi flash tool 7.0 & 8.0 stock rom but both are not flashing it shows like ( oem not unlocked) in red color
the command which i tried to unlock bootloader
fastboot oem unlock
fastboot oem edl then tried to flash but nothing happens
i tried older & new version of adb and fastboot
older version
fastboot unlock bootloader
fastboot flashing unlock
also new version commands
both are not worked for me
mi unlock is also not working which i downloaded from here https://en.miui.com/unlock/
but i can access stock recovery
and i wiped all data but it bootloops again
and also partition is not changing
it shows ( unknown option )

Can't Flash TWRP

Hi friends, I own one Asus Zenfone max pro m1 and I recently wanted it's bootloader to be unlocked and I tried the unofficial method but didn't worked. So I chose the official method. It wasn't a good experience because I was successful after several attempts. Don't know why... But after installing and unintalling and then reinstalling the unlock tool several times somehow I managed to unlock the bootloader. Now it's showing fastboot mode instead of csc fastboot so I believe it's bootloader is unlocked.
But as I tried to flash twrp using Bugjaeger app from another phone(since I think I'm having issues with usb 3.0 port on my lap) it's showing "Flashing not allowed in Lock state".
How can I be sure to know if my bootloader is unlocked or not? And whatif I flash rom directly(using adb/fastboot) without twrp with Corvos OS? Will O be stuck on a boot loop?
I finally came to solve my problem by trying to unlock the bootloader again and again by official method. And after 3 attempts it was succesfully unlocked (unlocked properly). I could flash twrp without any difficulties and Im on Abhix Rog version now..

How to relock bootloader?

I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.
As long as you remain unlocked you will not get updates. Just download the 11 stock ROM and fastboot it. You will be updated.
boltjuice said:
I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.
Click to expand...
Click to collapse
You can get the firmware with LSMA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
I just downloaded it and ran the rescue but it just flashed the rom and is still unlocked.
Is there an option to re-lock bootloader with that tool?
What is your carrier and where did you get your phone? Not every bootloader can be unlocked.
Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?
boltjuice said:
Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?
Click to expand...
Click to collapse
Re locking is not advisable, can be tricky with Moto devices
Re-Locking see Post #4
I'm a little unclear what state your device is in atm.
I just downloaded it and ran the rescue but it just flashed the rom
Click to expand...
Click to collapse
but then you write
I just want to re-lock it and revert it back to stock.
Click to expand...
Click to collapse
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH
notmyrealhandle said:
I'm a little unclear what state your device is in atm.
but then you write
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH
Click to expand...
Click to collapse
I factory reset the phone. Everything gets reset except for the unlocked bootloader does not re-lock... which prevents me from OTA update to Android 11.
Ok. If I understand correctly, your post with "it just flashed the rom" means a factory reset (and no flashing an image via moto's rescue tool or fastboot) - my misunderstanding.
As I mentioned to you in my reply to your PM, I don't use stock other than to initially get the bootloader unlocked, test a few things, and occasionally verify that my device still works on stock.
Others posting in this thread have offered helpful and safe suggestions - consider following these. I do a fair amount of "risky" tweaking with custom roms so please be cautious about the following suggestions/observations. (Apologies if my comments below seem basic - it looks like you've tried some fairly sophisticated tweaking of your own but it's hard to judge others skill level in a forum.)
Based on your comment:
made my phone not boot with error "no valid operating system could be found."
Click to expand...
Click to collapse
I suspect your phone wont boot after re-locking due to prior modifications to it's OS, the evidence of which can survive a factory reset. Re-locking enables android to verify that certain parts of the OS have not been modified and if it detects a difference, the device won't boot.
If you insist on re-locking your device now, I think the only way to accomplish that is to re-flash your device with the correct factory (aka stock) image some of which are available on lolinet. This is much more than a "factory reset." The instructions linked by sd_shawdow above should help with this:
Re-Locking see Post #4
Click to expand...
Click to collapse
Choosing the correct factory image is important. For example, I have a XT2113-2 RETUS. At one point early on when I was playing with this device, I tried flashing the TMO variant which is also a XT2113-2 model. My device did not boot until I re-flashed a RETUS variant. It's possible I just made a mistake while trying to flash the TMO variant I can't be certain at this point. If your phone was originaly (meaning new out of the box) a MetroPCS variant, make sure you flash a MetroPCS image.
Android also has roll back protection to prevent reverting to an older image that might have security flaws. The roll back "index" can be written to persistent storage on your phone that not only will survive factory resets but likely also survives flashing factory images. Motorola's implementation of roll back protection does not seem consistent with what I've read online from android/google. I'm pretty sure I had the most recent Android 10 RETUS bootloader on my device but I was able to flash an older factory image and then relock the device while on stock. (As I mentioned in my PM, I have not tried re-locking stock android 11). This observation may be the result of a motorola bug specific to RETUS so don't count on this working for you. Flash an image that is the same as or newer than the newest factory image you've ever had on the device.
Moto's rescue tool apparently can select and download an image for you making the process of image selection easier. I have not used this tool so I don't know how smart it is. Trust your knowledge about what you've done with the device since you owned it.
Lastly, it looks like the OEM unlocking toggle issue I and others have observed upon upgrading to Android 11 is resolved by connecting the device to your carrier and waiting several days. If you don't mind the wait, it's probably safe to flash android 11 (by using an image form lolinet and fastboot or by using the moto rescue tool - not via ota) while the device is unlocked and then re-locking the device.
Sorry about the long post.
HTH.
EDIT: I prefer not to be PM'd. Please just communicate (with me) in the open.
I was on Lineage 19.1 on my 5g ace. When I heard about the version 11 software for Retail US, I went to the lolinet mirrors to download the firmware for my phone.
Make sure oem unlocking in the developer options menu is off. If you can't turn it off you will need to root your phone.
Make sure USB debugging is on and you allow access for the pc your using.
Start adb and verify it sees your phone. If so, type...
reboot bootloader
Verify fastboot is authorized
Use Motoflash Pro to flash the version 11 firmware to my phone. Motoflash can be downloaded from the one 5g ace telegram channel. When it is done close Motoflash Pro and then from your pc use adb to run:
fastboot oem lock
Your phone will ask you if you want to relock bootloader. Choose Yes
Now reboot to the stock recovery and then use power + Volume up to access the recovery menu.
Navigate down to factory reset and select. It will warn you ... Blah blah blah. Now choose reboot system.
Moto boot logo should appear and then setup should begin.
Hopefully this helps someone.

Categories

Resources