Develop Bugs

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

Need help going back to stock Oreo (but keeping bootloader unlocked)

Long story short, I got pissed at Moto and decided to unlock my bootloader, flash TWRP, and flash a custom ROM (Alberto97's AOSP 8.1). While the ROM is working fine, eventually, I kind of missed the stock ROM, and decided I want to go back (Oreo). Keep in mind, though, I don't want to relock my bootloader as I will flash TWRP and root my device after going back to stock. How do I do this? I do have the Oreo OTA zip with me (Build no. OPN27.76-12-22), if that matters.

When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.

jonas210678 said:
When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.
Click to expand...
Click to collapse
Well, I was on official Oreo :/

djdelarosa25 said:
Well, I was on official Oreo :/
Click to expand...
Click to collapse
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.

Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
I definitely will. Thanks a lot, man . Lesson learned, always make backups

Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?

djdelarosa25 said:
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?
Click to expand...
Click to collapse
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.

Manish355 said:
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.
Click to expand...
Click to collapse
Why would one still want to relock the bootloader? It's to my understanding that unlocking it voids your warranty, and I've also read somewhere that even after relocking it, the warning persists.

By the way, have you checked my PM?

Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance

soadcma said:
Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance
Click to expand...
Click to collapse
You can directly flash the Oreo firmware via fastboot

Yeah, just flash the Oreo firmware

jonas210678 said:
You can directly flash the Oreo firmware via fastboot
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
djdelarosa25 said:
Yeah, just flash the Oreo firmware
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks

soadcma said:
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
But where can I find it to download ?
Thanks
Click to expand...
Click to collapse
Link for the topic with the Oreo stock fastboot ROM. https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621
1.67 GB in size.

Looking for NPPS25.137-93-14 fastboot firmware

Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.

https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897

I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.

Doesn't XT1685 equal G5 Plus?

Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk

Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.

I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...

Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?

Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs

Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.

leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.

Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs

leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.

Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs

leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.

Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs

Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!

I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.

Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.

leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.

[H930] New Pie build V30q with Sep 1, 2019 security patch is here!

Running this build since last weekend and is fire.
I can confirm performance(like RAM management) and smoothness are improved, the overlaping notifications is fixed as well and even LG's terrible gesture navigation implementation seems refined (I recommend using FluidNG to have back gestures as a complement). Battery is fine tho
Please don't try using OTA if you're rooted.
If you are already on PIE V30B rooted IS EASIER to Backup you data, Restore the provided TWRP v30q BACKUP, then RESTORE your data and root . Latest stock version and all your data intact.
Click to expand...
Click to collapse
H930 Pie V30b KDZ: https://drive.google.com/uc?id=1RB6idQ9XrgtPm6TscT0uFG9IEmNIp_G-&export=download
H930V30q OTA file: https://drive.google.com/open?id=1DeZeGltktcFg9FHAGPGhwByRM2IQ5G26
You must use Patched LGUP for this: https://drive.google.com/file/d/1haYE2RzoP6m45SoMO4hgNsPEc7LMP3q6/view?usp=sharing
OFFICIAL PROCEDURE
1. First you must flash V30b H930 PIE KDZ.
2. Run LGUP_Install_Ver_1_14_3.msi and install it.
3. Replace the files in LGUP directory (C:\Program Files (x86)\LG Electronics\LGUP) with the files stored in downloaded LGUP Patch folder, after connect phone in file transfer mode (MTP mode)
4. Open LGUP, select FOTA Upgrade and load LGH930AT-V30b-to-V30q-EUR-XX-SEP-02-2019.up
6. Click start.
TWRP RESTORE ALTERNATIVE
Requirements
Unlocked bootloader and working TWRP.
Steps to install
1. Download the .zip file and unzip it in your desktop.
2. Cut the extracted folder to V30+\Internal Memory\TWRP\BACKUPS\LGH930XXXXXXX folder, which store TWRP's backups.
3. Reboot device in TWRP and restore 2019-09-09--PieV30q_PKQ1190414001 backup, all partitions are fine and will not mess your IMEI/carrier signal.
4. This backup is already pre-rooted(just in boot.img so you have to reflash Magisk after wiping data), dmverity-encryption off and rct disabled. A full wipe is recommended.
5. Reboot to system and that's it, you are running latest and finest stock Pie :good:
TWRP backup download link
• https://drive.google.com/file/d/1Js3ltgvWkavdx1lpalFwaYil5ThkXafI/view?usp=sharing
You can see in a video here:

Is indian jio volte working on twrp method?

Just a reminder: You cannot use a OTA file if TWRP is installed, the bootloader can be unlocked, but you must have stock recovery for this to work. Refurbishing V30b is advisable.

shirso.it7 said:
Is indian jio volte working on twrp method?
Click to expand...
Click to collapse
You can try, but i dont think so

mateus.sc said:
You can try, but i dont think so
Click to expand...
Click to collapse
Hey thanks for the procedure.
can you please make a system dump? It'll be useful for los16 with pie blob development?

Congrats to the five V30 users who will get this update.

Can I flash .kdz file with "Upgrade" (NOT Refurbish) option without losing any data? Cause I can't begin an update (the FOTA EASY UPGRADE shows for few seconds and disappearing with no results). Of course I'm working with V30b-EUR-XX version.

error comes out "windows cannot find WPDAPI.exe make sure you typed the name correctly, and try again" and press ok then new error comes out "0x2000, fail. mtp is not running." I can't update, please help me.

john_22_online said:
error comes out "windows cannot find WPDAPI.exe make sure you typed the name correctly, and try again" and press ok then new error comes out "0x2000, fail. mtp is not running." I can't update, please help me.
Click to expand...
Click to collapse
You'll be able to when KDZ is released.
This is for people who want to run leaked, beta -- possibly buggy -- firmware. Yes, some people want that. If your wish to experiment, then that's fine as long as you realize it's not necessary to get this update...
When it's ready LG will release it officially and there will be full image KDZ available in the KDZ thread, as well as TWRP flashable zip made by an XDA Dev.

ChazzMatt said:
You'll be able to when KDZ is released.
This is for people who want to run leaked, beta -- possibly buggy -- firmware. Yes, some people want that. If your wish to experiment, then that's fine as long as you realize it's not necessary to get this update...
When it's ready LG will release it officially and there will be full image KDZ available in the KDZ thread, as well as TWRP flashable zip made by an XDA Dev.
Click to expand...
Click to collapse
Buggy or not. I'm already using 30b. I have a chance to do it and I want to. Don't write me if you won't help me.

tech_infinity said:
Hey thanks for the procedure.
can you please make a system dump? It'll be useful for los16 with pie blob development?
Click to expand...
Click to collapse
I provided a TWRP system backup, I believe it already does de trick right?

SkeletMastrr said:
Can I flash .kdz file with "Upgrade" (NOT Refurbish) option without losing any data? Cause I can't begin an update (the FOTA EASY UPGRADE shows for few seconds and disappearing with no results). Of course I'm working with V30b-EUR-XX version.
Click to expand...
Click to collapse
You can flash H930v30b via upgrade, yes. Then send the OTA via LGUP.
Are you rooted?

john_22_online said:
error comes out "windows cannot find WPDAPI.exe make sure you typed the name correctly, and try again" and press ok then new error comes out "0x2000, fail. mtp is not running." I can't update, please help me.
Click to expand...
Click to collapse
Move WPDAPI.exe file to model\common folder

john_22_online said:
error comes out "windows cannot find WPDAPI.exe make sure you typed the name correctly, and try again" and press ok then new error comes out "0x2000, fail. mtp is not running." I can't update, please help me.
Click to expand...
Click to collapse
WPDAPI.exe is a file provided in LGUP zip in OP, you have to patch the files in LGUP directory for this to work.

john_22_online said:
Buggy or not. I'm already using 30b. I have a chance to do it and I want to. Don't write me if you won't help me.
Click to expand...
Click to collapse
1) I'll write what I want in reply to anyone I want. It's not just for you, it's cautionary tale for anyone. Just make sure you know the risks.
2) EU H930 V30b has long been official. There's a full image KDZ and XDA Dev made TWRP flashable zip in MY KDZ thread -- so your statement makes no sense.
So what if you're running official publicly released firmware? What you're now trying to install is not officially public release firmware (yet, and no absolute guarantees it will be).

mateus.sc said:
You can flash H930v30b via upgrade, yes. Then send the OTA via LGUP.
Are you rooted?
Click to expand...
Click to collapse
Yes, I'm rooted. Thanks for info, I'm going to upgrade now, and I'll give results of this operation

ChazzMatt said:
You'll be able to when KDZ is released.
This is for people who want to run leaked, beta -- possibly buggy -- firmware. Yes, some people want that. If your wish to experiment, then that's fine as long as you realize it's not necessary to get this update...
When it's ready LG will release it officially and there will be full image KDZ available in the KDZ thread, as well as TWRP flashable zip made by an XDA Dev.
Click to expand...
Click to collapse
I used V30b by KDZ install and it was as buggy as the v30b OTA that I had used for a while too.
This V30q it's a huge improvement over the old version and I can say it with sure, because I have tested all these.
BTW, it's not beta anymore(is in internal test phase), they are just delaying the release with bussiness bureaucracy.

SkeletMastrr said:
Yes, I'm rooted. Thanks for info, I'm going to upgrade now, and I'll give results of this operation
Click to expand...
Click to collapse
Please don't try using OTA if you're rooted.
If you are already on PIE V30B rooted you have to Backup you data, Restore the provided TWRP v30q BACKUP, then RESTORE your data and root. Latest version and all your data intact.

mateus.sc said:
Please don't try using OTA if you're rooted.
If you are already on PIE V30B rooted you have to Backup you data, Restore the provided TWRP v30q BACKUP, then RESTORE your data and root. Latest version and all your data intact.
Click to expand...
Click to collapse
Oh, fine. Thank you for help again!

SkeletMastrr said:
Oh, fine. Thank you for help again!
Click to expand...
Click to collapse
U welcome, bro

New update has arrived 11.0.325ST

Good news, global ROM receives New update today.
Lenovo Z6 Pro.

Ok, so what's new / improvements ?

benjieb said:
Ok, so what's new / improvements ?
Click to expand...
Click to collapse
I don't know, I reinstall the firmware and lose the package, now system update refuse to give me again OTA ;-;

benjieb said:
Ok, so what's new / improvements ?
Click to expand...
Click to collapse
I don't have any idea how to recover my update ota, lenovo is trolling me.

I don't understand what your issue is. But if you missed OTA, is will come again soon.
I think one way to help that is to clear cache of update app. Just google it.
While you are there, once the OTA is downloaded to your phone AND before actually upgrading, it would be good to copy the update file to your PC and share it with others who don't get the OTA.

benjieb said:
I don't understand what your issue is. But if you missed OTA, is will come again soon.
I think one way to help that is to clear cache of update app. Just google it.
While you are there, once the OTA is downloaded to your phone AND before actually upgrading, it would be good to copy the update file to your PC and share it with others who don't get the OTA.
Click to expand...
Click to collapse
I found the solution, I'll repost the fastboot link that alexeei provided.
The overall improvements I've been noticing:
Connection problems that sometimes occurred in my region, are no longer giving.
Battery I noticed is lasting about 45 minutes longer.
PT-BR was basically 100% implemented in every layout.
The 4G connection has been improved.
I also believe that they have made some changes in the kernel, because the way the cores are working, is different gives version 284, ie better, I'll find out if in Benchmark improved anything.
And the audio in dolby atmos, I'm feeling that the audio has improved, it's louder and clearer.
camera haven't tested yet
However this is it: D

Here the link
Thanks for @alexeei
https://androidfilehost.com/?fid=1899786940962594224

hehk1234 said:
Here the link
Thanks for @alexeei
https://androidfilehost.com/?fid=1899786940962594224
Click to expand...
Click to collapse
this fastboot requires open bootloader?

x-geo said:
this fastboot requires open bootloader?
Click to expand...
Click to collapse
yes

alexeei said:
yes
Click to expand...
Click to collapse
And i can close it again after install it?

x-geo said:
And i can close it again after install it?
Click to expand...
Click to collapse
No, it's not neccessary

ok, i'll install it after it charges... this version comes with the new 4D Utouch?

In first Thank's a lot for the file !!!!
But after the flash , my phone don't reboot, hopefully reflash Alexeei Twrp solve my problem, evrithing seem ok now.
More info when more tested the rom

@alexeei, the file you shared is full ROW rom?
If so, when flashing with TWRP over an older version of ROW, will it keep data and apps?
Thanks!

I flash over my 284st the alexeei fastboot rom, but with the fastboot .bat.
And i have keep all my app,data and setting.
But the phone don't work in first attempt, must reflash the twrp for fix boot.
Don't know if this problème is only for me or more general.
My config before flash. Rom 11.0.284st + twrp alexeei + magisk 19.3.
Now everything seem ok and perf is good, except aod still dont work.

benjieb said:
@alexeei, the file you shared is full ROW rom?
If so, when flashing with TWRP over an older version of ROW, will it keep data and apps?
Thanks!
Click to expand...
Click to collapse
yes
---------- Post added at 08:27 PM ---------- Previous post was at 08:24 PM ----------
wlcbtd said:
I flash over my 284st the alexeei fastboot rom, but with the fastboot .bat.
And i have keep all my app,data and setting.
But the phone don't work in first attempt, must reflash the twrp for fix boot.
Don't know if this problème is only for me or more general.
My config before flash. Rom 11.0.284st + twrp alexeei + magisk 19.3.
Now everything seem ok and perf is good, except aod still dont work.
Click to expand...
Click to collapse
You only need flash vbmeta with --disable-verity option, i make it default in installer script in future releases.

Ok , thank's for the info !

How can I install this update?

Brillant !
Do you think it can be flashed over CN rom and keep data and apps?
Also, do you know where to find same type of rom file with latest CN rom?
I want to try latest ROW, but I know I will revert back to CN.

ManCast said:
How can I install this update?
Click to expand...
Click to collapse
See post #30 on these tread
https://forum.xda-developers.com/android/help/rom-lenovo-z6-pro-l78051-qpst-edl-t3947149
, same thing for these update.
But only if you already are in raw rom, update from chinese is untested by now.