Related
Hello,
I have a HTC M8 rooted (Super SU) with TWRP Recovery and Android ver. 5.0.1, Software ver. 4.19.111.4, Baseband ver. 1.25.2145000021.06G_20.68.4196t.01_F.
Last couple of days, I received a notification to update for android 6.0, but after I downloaded the update and press to "install now", the phone always restarted to TWRP recovery and do not install the update. Any Idea Why ?!!!.
Could any one help me to install the update?
Thanks
moh19814 said:
Hello,
I have a HTC M8 rooted (Super SU) with TWRP Recovery and Android ver. 5.0.1, Software ver. 4.19.111.4, Baseband ver. 1.25.2145000021.06G_20.68.4196t.01_F.
Last couple of days, I received a notification to update for android 6.0, but after I downloaded the update and press to "install now", the phone always restarted to TWRP recovery and do not install the update. Any Idea Why ?!!!.
Could any one help me to install the update?
Thanks
Click to expand...
Click to collapse
Replace the recovery to stock recovery and relock the bootloader. If you installed the modified firmware, reflash the stock firmware, you will be good
Cashreedhar said:
Replace the recovery to stock recovery and relock the bootloader. If you installed the modified firmware, reflash the stock firmware, you will be good
Click to expand...
Click to collapse
how to replace recovery with the stock one. Where I can find it.
Do i lose all my application data doing so.
No, I am using the stock firmware, so I suppose no need to reflash it.
Thnaks
moh19814 said:
how to replace recovery with the stock one. Where I can find it.
Do i lose all my application data doing so.
No, I am using the stock firmware, so I suppose no need to reflash it.
Thnaks
Click to expand...
Click to collapse
Here you should find the stock recoveries: http://www.andromods.com/download-files/htc-one-m8-stock-recovery-verizon-sprint-att-tmobile.html
download the right recovery.img file and follow these instruction on how to flash - http://androiding.how/how-to-install-twrp-recovery-via-fastboot/ - in this just change the twrp recovery.img to the one you downloaded and run the code in command prompt.
It is recommended to do I clean install to avoid any further reported errors. Once you relock the bootloader you will lose all the data (like hard reset).
Cashreedhar said:
Here you should find the stock recoveries: http://www.andromods.com/download-files/htc-one-m8-stock-recovery-verizon-sprint-att-tmobile.html
download the right recovery.img file and follow these instruction on how to flash - http://androiding.how/how-to-install-twrp-recovery-via-fastboot/ - in this just change the twrp recovery.img to the one you downloaded and run the code in command prompt.
It is recommended to do I clean install to avoid any further reported errors. Once you relock the bootloader you will lose all the data (like hard reset).
Click to expand...
Click to collapse
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.
moh19814 said:
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.
Click to expand...
Click to collapse
you can directly flash
moh19814 said:
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.
Click to expand...
Click to collapse
First thing .. you cannot do OTA with a rooted stock ROM, you need a non-rooted ROM.
Secondly .. there is no need to relock bootloader - read the note in my thread.
Just read again post #1 and follow all the 14 steps, you should be fine.
Anything, you can ask in my thread as I'm not following your thread.
ckpv5 said:
First thing .. you cannot do OTA with a rooted stock ROM, you need a non-rooted ROM.
Secondly .. there is no need to relock bootloader - read the note in my thread.
Just read again post #1 and follow all the 14 steps, you should be fine.
Anything, you can ask in my thread as I'm not following your thread.
Click to expand...
Click to collapse
thanks a lot for the info
After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,
Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991
hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.
Does anyone have an idea when the S7 active potentially might see Oreo via OTA update?
Is it hard to install on your own via root or whatever?
Thanks.
jj8279 said:
Does anyone have an idea when the S7 active potentially might see Oreo via OTA update?
Is it hard to install on your own via root or whatever?
Thanks.
Click to expand...
Click to collapse
you can already use stock recovery to flash it... Just make sure you flash the previous OTA updates until BRB5 are the last 4 characters of your baseband in settings -> about -> software info
I'm running the first oreo listed on that link on my S7 Active, not sure if the others will work, but once you are on BRB5, just copy the oreo zip to the root of your MICRO SD card, reboot into stock recovery, select install zip from sd card, and select the file... to do this, you cannot be rooted, if your system status shows as custom, flash nougat with odin... if you need it the odin files as well asall previous OTA updates are listed in the website as well. Just remove /OTA/Oreo from the end of the url
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/OTA/Oreo/
let me know how it goes, i'm happy with it, it has the S8 style launcher and app icons, and the new AOD, but unfortunately, no live infinity wallpapers :/
remember to hit thanks
HI
any one have Oreo stock rom? My S7 active can't go into recovery mode, only can use ODIN to flash. thanx
troublesome said:
HI
any one have Oreo stock rom? My S7 active can't go into recovery mode, only can use ODIN to flash. thanx
Click to expand...
Click to collapse
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me!
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!
I need rom what had bootloader 3 because my phone was brick.my phone lost recovery mode but it has download mode.i must odin my phone by rom bootloader 3.Can you have it? Share me.Tks bro !
jacoblong09 said:
If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. [/URL]
Click to expand...
Click to collapse
It doesn't work, but still thank you
troublesome said:
It doesn't work, but still thank you
Click to expand...
Click to collapse
It should work, make sure you have the usb drivers installed, the LATEST VERSION of odin (older versions may get stuck), and make sure your phone is in download mode (hold down power + volume down + home until a blue screen appears. click volume up). Then, open odin, connect your phone, and add the four .tar.md5 files extracted from the link you quoted. It works for me, but if it doesn't, try this file instead. let me know how it goes
jacoblong09 said:
It should work, make sure you have the usb drivers installed, the LATEST VERSION of odin (older versions may get stuck), and make sure your phone is in download mode (hold down power + volume down + home until a blue screen appears. click volume up). Then, open odin, connect your phone, and add the four .tar.md5 files extracted from the link you quoted. It works for me, but if it doesn't, try this file instead. let me know how it goes
Click to expand...
Click to collapse
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
troublesome said:
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
Click to expand...
Click to collapse
Oh, i see. You're on bootloader version 3. In that case, there is most likely nothing you can do to fix the phone. Just wait patiently for an odin flashable version of oreo for the s7 active, which should have bootloader 3 out of the box, and that should work. At this point, it is simply a waiting game. I really can't do anything for you, wish I could, but I unfortunately do not have the knowledge to modify bootloader versions yet. So, patience is key. Cheers!
troublesome said:
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
Click to expand...
Click to collapse
actually, has anyone confirmed if unlocking the aboot allows bootloader downgrades on the s7 active? i also found this on the download site: https://cloud.mail.ru/public/BGy7/gKs4xzhRE/root/unlockg891aboot.tar
Try flashing this in the AP slot in odin to unlock the aboot partition, then flash the nougat from the link i gave before, using just the AP file from the firmware in the AP slot, and don't use the BL, CP, OR CSC slots
jacoblong09 said:
actually, has anyone confirmed if unlocking the aboot allows bootloader downgrades on the s7 active? i also found this on the download site: https://cloud.mail.ru/public/BGy7/gKs4xzhRE/root/unlockg891aboot.tar
Try flashing this in the AP slot in odin to unlock the aboot partition, then flash the nougat from the link i gave before, using just the AP file from the firmware in the AP slot, and don't use the BL, CP, OR CSC slots
Click to expand...
Click to collapse
I tried it before, does not work, either, actually I tried everything on the site.lol
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
jacoblong09 said:
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
Click to expand...
Click to collapse
sw rev check fail and only fail in BL part
http://protoss.myds.me/download/s7_active.jpg
then just don't flash the BL, flash everything else, let me know if it works
jacoblong09 said:
then just don't flash the BL, flash everything else, let me know if it works
Click to expand...
Click to collapse
If odin BRA7 and you don't flash file BL.It will run PASS but your phone will brick when your phone was on rom RD4 (8.0).Last month ,I try do it.
You don't try it !
---------- Post added at 02:53 AM ---------- Previous post was at 02:12 AM ----------
jacoblong09 said:
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
Click to expand...
Click to collapse
I like your idea.You can help me do it .tks bro !
dothanhanloc said:
If odin BRA7 and you don't flash file BL.It will run PASS but your phone will brick when your phone was on rom RD4 (8.0).Last month ,I try do it.
You don't try it !
---------- Post added at 02:53 AM ---------- Previous post was at 02:12 AM ----------
I like your idea.You can help me do it .tks bro !
Click to expand...
Click to collapse
i realize now that the issue with my idea is... root... root is not achieved on oreo yet... and the firmware.mobi website upload to dropbox doesn't work, just refreshes after clicking start upload. So i'm stuck. But, if somebody could provide an image i could flash to root oreo on the s7 active, i will be able to make an odin .tar.md5
but i can not without root :/
One other thing you could try is extracting the ota zip for oreo you previously had, take the boot.img from it, compress the boot.img into a tar file, and then try flashing that with odin, in the AP slot. let me know how it goes, my phone is in a boot loop cause i tried an older root method :/
luckily, i used an earlier oreo OTA file, so i'm still on BL2
troublesome said:
sw rev check fail and only fail in BL part
http://protoss.myds.me/download/s7_active.jpg
Click to expand...
Click to collapse
Ok, after lots of digging through the ota zip, i believe i may have one step towards a solution.
But i need you to check it, as if it does work, it will update my phone to bootloader 3, which i would rather not do, since you already have bootloader 3, and it can't worsen the situation
now that i think about it, i could try flashing this on my currently installed marshmallow, after rooting, then try making the odin .tar.md5, but with the bootloader 3, so you can downgrade back to marshmallow. what do you think?
Try flashing the attached bootloader file, which i made for bootloader 3:
let me know if it works, thanks.. i might have a method for the system, too
EDIT NO STOP! i forgot a bin file, fixing now
EDIT 2 OK, SHOULD BE ALL GOOD NOW!
EDIT 3 I'M BRICKED NOW, but did see the new bootloader android logo at the bottom after flashing, then black screen qualcomm 9008
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
jacoblong09 said:
you can already use stock recovery to flash it... Just make sure you flash the previous OTA updates until BRB5 are the last 4 characters of your baseband in settings -> about -> software info
I'm running the first oreo listed on that link on my S7 Active, not sure if the others will work, but once you are on BRB5, just copy the oreo zip to the root of your MICRO SD card, reboot into stock recovery, select install zip from sd card, and select the file... to do this, you cannot be rooted, if your system status shows as custom, flash nougat with odin... if you need it the odin files as well asall previous OTA updates are listed in the website as well. Just remove /OTA/Oreo from the end of the url
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/OTA/Oreo/
let me know how it goes, i'm happy with it, it has the S8 style launcher and app icons, and the new AOD, but unfortunately, no live infinity wallpapers :/
remember to hit thanks
Click to expand...
Click to collapse
Hey I'm already running BRB5, do i need to rename the zip to update.zip or anything like that? also how do I send it to the root of the sd card, I just copied it into the regular file, does it need to be sent through a computer?
sultanmurad said:
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
Hey I'm already running BRB5, do i need to rename the zip to update.zip or anything like that? also how do I send it to the root of the sd card, I just copied it into the regular file, does it need to be sent through a computer?
Click to expand...
Click to collapse
Nah, use stock to flash CRC7 AS IS, NOT ANYTHING NEWER... My phone is now pernaneantly bricked due to me flashing an older bootloader from a new one
jacoblong09 said:
Nah, use stock to flash CRC7 AS IS, NOT ANYTHING NEWER... My phone is now pernaneantly bricked due to me flashing an older bootloader from a new one
Click to expand...
Click to collapse
Oh that sucks, is there any way to flash it back to original stock through adb? I think I'll just wait for the software update to come through the carrier, I don't wanna risk that
AND THANKS FOR THE QUICK REPLY!! I was minutes away from flashing CRD4, you saved me big time
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.
http:
//imgur.com/a/
W8Hb3SW
new user, can't attach imgs yet.
Got this phone to fix. Flashed latest firmware but no luck after a few different tries... Only this time it starts booting up with the animation and after a few seconds goes back to fastboot.
If anyone can help I'm thankful.
gabrielizador said:
http:
//imgur.com/a/
W8Hb3SW
new user, can't attach imgs yet.
Got this phone to fix. Flashed latest firmware but no luck after a few different tries... Only this time it starts booting up with the animation and after a few seconds goes back to fastboot.
If anyone can help I'm thankful.
Click to expand...
Click to collapse
You need to flash your proper firmware. Which model are you? (xt1952-?) I also need to know your carrier and country. I'll link the right firmware for you.
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
gabrielizador said:
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
Click to expand...
Click to collapse
The firmware on the lolinet seems to be the latest.
How did you try to flash the firmware? As long as the bootloader is locked the most devices only accept to flash the complete firmware images. They should be flashed in the same order as listed in flashfile.xml inside the zip.
WoKoschekk said:
The firmware on the lolinet seems to be the latest.
How did you try to flash the firmware? As long as the bootloader is locked the most devices only accept to flash the complete firmware images. They should be flashed in the same order as listed in flashfile.xml inside the zip.
Click to expand...
Click to collapse
I don't know much about how to use ADB, I got it from a stockrom, that had a tutorial on how to fix failed startups.
https://drive.google
.com/file/d/1G8AeMUfFbAroan5S1mpojyMYpUvKsR1N/view?usp=drivesdk
I just threw these files onto the firmware's files' folder.
How do I flash It in the correct order?
1. install ADB/Fastboot tools
https://forum.xda-developers.com/showthread.php?t=2317790
2. boot into bootloader (when power off, hold Vol- and power) and connect the device to your PC
3. A short introduction to ADB/fastboot:
While in bootloader menu you can only use the command "fastboot + <options>" to communicate with the device. Type
Code:
fastboot help
to show the options for this tool.
First of all extract the whole firmware zip into the ADB/fastboot folder on your PC. Copy also the attachment into this folder.
In this file you'll find all the flash commands you need to flash the new firmware. I extracted them from your current firmware .zip for the build no. QPYS30.52-22-2.
Run it as a batch script on your Windows cmd line by typing
Code:
bat flashfile.txt
. The other option would be to run all the commands manually.
As you can see in the script the "HLOS issue" affects your modem partition. At least you need to flash the NON-HLOS.bin to it. But I guess it wouldn't be possible to flash only this single partition while your bootloader is locked.
That's all. Good luck!!
the attachment...
gabrielizador said:
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
Click to expand...
Click to collapse
You're RETBR if you have no carrier branding. This firmware should work for you.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip