Develop Bugs

Boot up animation gone when i flash a new ROM on my htc one m8

No more boot up animation. Please help. its stuck in red text htc.. boot.. plz help.. but it goes through the start up on htc one m8

Kuechikun said:
No more boot up animation. Please help. its stuck in red text htc.. boot.. plz help.. but it goes through the start up on htc one m8
Click to expand...
Click to collapse
In order to get out of htc boot screen you have to hold the power and vol up for 10 seconds and then when the screen turns off, hold vol down while still holding power. Then you will be taken to hboot. You don't have an os or rom installed on your phone so you're going to have to flash a new custom rom. All you have to do is connect your phone to your computer with usb cable and use adb commands to push rom file to your phone and through your custom recovery you can flash a new rom. Download this zip and extract it to your desktop or wherever you want. http://www.sakitechonline.com/downlo...stboot_adb.zip Then you download the custom rom you want and make sure it works with your phone. so you drag the custom rom file to the fastboot folder and then in the fastboot folder hold shift and right click on your mouse and press "open command window here" Then in the command window type adb devices to make sure adb is working and you should get numbers that means it works. Make sure your phone is in custom recovery and then type adb push exact name of your rom file.zip /sdcard/ and press enter and then it will push your rom file it will take couple of minutes and then you have successfully pushed your rom file and you can flash a new rom

Kuechikun said:
No more boot up animation. Please help. its stuck in red text htc.. boot.. plz help.. but it goes through the start up on htc one m8
Click to expand...
Click to collapse
Update your firmware.

Captain_Throwback said:
Update your firmware.
Click to expand...
Click to collapse
Noob here, Why does it need to update when the firmware of your ROM is updated? or is it diff?
I thought the ROM already comes with the updated firmware. I'm trying to flash Android revolution 11.1

Kuechikun said:
Noob here, Why does it need to update when the firmware of your ROM is updated? or is it diff?
I thought the ROM already comes with the updated firmware. I'm trying to flash Android revolution 11.1
Click to expand...
Click to collapse
I think the ROM runs on the updated firmware, not that it comes with the updated firmware. There's a difference.
Read up on some of the stuff being said about the firmware. YES!! I KNOW you are running Android Revolution but still, just for information purposes:
Firmware and the new Android 4.4.3
There the crew from Viper ROM discusses some stuff about the Firmware.
[2014.09.07][GUIDE] FUU and Firmware flashing
Some more info/guide on the Firmware.
Happy reading :good:

BerndM14 said:
I think the ROM runs on the updated firmware, not that it comes with the updated firmware. There's a difference.
Read up on some of the stuff being said about the firmware. YES!! I KNOW you are running Android Revolution but still, just for information purposes:
Firmware and the new Android 4.4.3
There the crew from Viper ROM discusses some stuff about the Firmware.
[2014.09.07][GUIDE] FUU and Firmware flashing
Some more info/guide on the Firmware.
Happy reading :good:
Click to expand...
Click to collapse
I need some reading. This is a long process. Thankyou!

So it has no boot animation, but it still boots to home screen right??
Sent from my HTC One_M8 using Tapatalk

One m8 t mobile lollipop ota captured

Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api

would i be able to just flash this if i wanted to with twrp. just curious.

Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.

dang. okay

T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip

do we just flash in twrp? Thank you by the way

No it's a stock ota you have to use HTC recovery.

rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad

bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted

Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.

bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.

Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.

bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted

Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.

cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.

bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?

rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad

bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.

Radio
Any chance someone can please post a flashable zip with the new t-mo radio?

Where would I get the stock recovery for this fw and update. I want to root but keep my ota

HK HTC10 Returning to stock rom

Hi there, I'm using Hong Kong version of htc10, i tried to root it but when i flashed supersu and xposed arm64 sdk23, it comes to stuck in the system ui interface showing that: 'System UI has stopped unexpectedly....etc.' Looping in that point. So i tried wipe all data in twrp mode and reboot again, still the same situation. Then I download a TW version of stock IMG which is 1.30.708.1(Original was 1.53.708.4) and flashed it in download mode, after that i rebooted it, everything is normal again. Fresh new welcome screen.
But there are some features that i can't use such as can't receive 4G+ signal, can't receive VoLTE, even could't use battery saving mode ....etc.
So I just want to know where can I find the STOCK IMG for my HK version CID HTC__622, which is 1.53.708.4 or so called RUU for it? Thanks.:crying::crying:

axx134679 said:
Hi there, I'm using Hong Kong version of htc10, i tried to root it but when i flashed supersu and xposed arm64 sdk23, it comes to stuck in the system ui interface showing that: 'System UI has stopped unexpectedly....etc.' Looping in that point. So i tried wipe all data in twrp mode and reboot again, still the same situation. Then I download a TW version of stock IMG which is 1.30.708.1(Original was 1.53.708.4) and flashed it in download mode, after that i rebooted it, everything is normal again. Fresh new welcome screen.
But there are some features that i can't use such as can't receive 4G+ signal, can't receive VoLTE, even could't use battery saving mode ....etc.
So I just want to know where can I find the STOCK IMG for my HK version CID HTC__622, which is 1.53.708.4 or so called RUU for it? Thanks.:crying::crying:
Click to expand...
Click to collapse
I'm looking for the HK stock img as well, I've only found one which seems to have been modified so OTA no longer work. Did you have any luck?

electric0ant said:
I'm looking for the HK stock img as well, I've only found one which seems to have been modified so OTA no longer work. Did you have any luck?
Click to expand...
Click to collapse
No luck??

axx134679 said:
No luck??
Click to expand...
Click to collapse
Should be in here. www.androidfilehost.com/?w=files&flid=74636

axx134679 said:
No luck����
Click to expand...
Click to collapse
I've found a twrp backup posted from someone else:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297/post67760253#post67760253
the working link for the download is on the next page.
this is definitely the HK rom as after a wipe the default language is HK Chinese.
only problem is OTA does not work and when trying to manually flash the OTA manually (using TWRP and stock recovery) the check on the OTA zip passes but the system check fails so it looks like system has been modified.
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
purple patch said:
Should be in here. www.androidfilehost.com/?w=files&flid=74636
Click to expand...
Click to collapse
OMG there is a HK 1.21.708.4 ROM! if its stock then should be abel to update all the way to 1.80.708.6!
downloading now! if this works I am going to be over the moon!
just one question, what do I use to restore the zip? flash with twrp?

electric0ant said:
I've found a twrp backup posted from someone else:
http://forum.xda-developers.com/htc...ry-ruu-ota-t3359297/post67760253#post67760253
the working link for the download is on the next page.
this is definitely the HK rom as after a wipe the default language is HK Chinese.
only problem is OTA does not work and when trying to manually flash the OTA manually (using TWRP and stock recovery) the check on the OTA zip passes but the system check fails so it looks like system has been modified.
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
OMG there is a HK 1.21.708.4 ROM! if its stock then should be abel to update all the way to 1.80.708.6!
downloading now! if this works I am going to be over the moon!
just one question, what do I use to restore the zip? flash with twrp?
Click to expand...
Click to collapse
Rename zip file to 2PS6IMG.zip. Place on sdcard. Reboot to download mode and follow instructions. Do full backup before (SD and internal).

purple patch said:
Rename zip file to 2PS6IMG.zip. Place on sdcard. Reboot to download mode and follow instructions. Do full backup before (SD and internal).
Click to expand...
Click to collapse
if i boot to download mode isn't just the page with some options and also the mode to run fastboot commands to?

electric0ant said:
if i boot to download mode isn't just the page with some options and also the mode to run fastboot commands to?
Click to expand...
Click to collapse
Once that file is in correct spot, you will see option to flash it (VOLUp to flash). Been a while since I flashed stock img. Check guide section if you want to confirm.

purple patch said:
Once that file is in correct spot, you will see option to flash it (VOLUp to flash). Been a while since I flashed stock img. Check guide section if you want to confirm.
Click to expand...
Click to collapse
thanks for your help!

purple patch said:
Once that file is in correct spot, you will see option to flash it (VOLUp to flash). Been a while since I flashed stock img. Check guide section if you want to confirm.
Click to expand...
Click to collapse
just wanted to thank you again,
I'm totally stock now with working OTAs!!

electric0ant said:
just wanted to thank you again,
I'm totally stock now with working OTAs!!
Click to expand...
Click to collapse
Awesome, no problem, happy to point you in the right direction.

electric0ant said:
just wanted to thank you again,
I'm totally stock now with working OTAs!!
Click to expand...
Click to collapse
Please help the Hong kong community by backing up the system image and boot for 1.80.708.6 . I already provided the stock recovery file. It shouldn't take too long.

pro nexus said:
Please help the Hong kong community by backing up the system image and boot for 1.80.708.6 . I already provided the stock recovery file. It shouldn't take too long.
Click to expand...
Click to collapse
I would love to help but I've already sold the HTC 10 on already.
But with the RUU linked by purple patch you can get to stock completely. And it's so easy!

electric0ant said:
just wanted to thank you again,
I'm totally stock now with working OTAs!!
Click to expand...
Click to collapse
OMG, how the hell did i miss such important thing!!! I will try it right away! Thank you!!VERY MUCH!!!!

Sorry to bother you again, I put the 2PS6IMG in the external card, but it show an error message:" FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing."
Maybe the IMG version that i downloaded us higher than my phone currently running? I'm running 1.53.XXX now.

Well, nevermind, I S-OFFed my htc10 and flashed the zip, now I'm using stock firmware and able to receive OTA, Thanks a lot man! You are my HERO!!

I encounter the same situation and like to return to Stock ROM, but my firmware version is 1.92.708.3. Searched over Internet and can't find the corresponded RUU. Anyone have it and can share to me?

antonyyip said:
I encounter the same situation and like to return to Stock ROM, but my firmware version is 1.92.708.3. Searched over Internet and can't find the corresponded RUU. Anyone have it and can share to me?
Click to expand...
Click to collapse
you don't need the same version of RUU, just flash the old version. I always flash the 1.53 RUU

DummyPLUG said:
you don't need the same version of RUU, just flash the old version. I always flash the 1.53 RUU
Click to expand...
Click to collapse
but I'm still S-ON, not yet purchased Sunshine:crying:

antonyyip said:
but I'm still S-ON, not yet purchased Sunshine:crying:
Click to expand...
Click to collapse
I assume you had unlock it, then it may already lost the warrant(not sure for this in HK), so why not s-off it via htc?

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

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.