Related
NEW software!!!!!...... LGUP WILL FLASH YOUR KDZ files
Download LGUP from here http://www.filedropper.com/g4 or here https://www.dropbox.com/s/d2dw48uqh4hku8m/G4.rar?dl=0 or here http://oceanhost.eu/eps4h4pmwphu/LGUP.zip.htm thank you hyelton for this link :good:
Install LGUP_8994_DLL_Ver_0_0_3_23 first and then LGUP_Install_Ver_1_14_3
Make sure you have downloaded the required KDZ file MM or LP
Start LGUP prog on your computer "make sure your phone is plugged in"
ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it.
THANK YOU FOR THIS Killerdog:good: <~~~To Modify This File You Must Have Root!!
For me it's show in LGUP as unknow device.
reboot my phone, remove battery and anything else don't work.
I install LG Bridge to test, and nothing seem to work.
After make some test and search, i find some info modified by S3V3N into his rom (cust partition) that he have modify into this file:
/cust/OPEN_COM/cust_OPEN_EU.prop
Code:
ro.lge.swversion=[COLOR="Red"]some info[/COLOR]
ro.lge.swversion_short=[COLOR="Red"]some info[/COLOR]
change to
Code:
ro.lge.swversion=[COLOR="Red"]H81510c[/COLOR]
ro.lge.swversion_short=[COLOR="Red"]V10c[/COLOR]
restart my phone and woow it show correctly in LGUP and i can refurbish my phone.
TO UPGRADE TO MM from LP - make sure BIN file is ticked and in the File Path point it towards the MM KDZ you have downloaded. MAKE SURE YOU HAVE CLICKED UPGRADE! This will update you from LP to MM with out wiping any of your info. Press Start. Make cup of tea and be patient
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer. FILE PATH point it towards the MM KDZ.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient
If you are worried about losing your data after a full wipe, why not use the LG Bridge software to backup and restore.... it works fine!
YOU WILL LOSE ROOT!
There is no need to enter download mode! LGUP will do it for you.
Original thread by schafi03 http://www.android-hilfe.de/thema/a...er-zurueck-auf-android-5.733674/#post-9342963
Thank You schafi03
INSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install then select images then select recovery NOT BOOT then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery.
How to root LG G4 H815 on Android Marshmallow
http://www.ibtimes.co.uk/how-root-lg-g4-h815-android-marshmallow-1526102
OTHER GREAT THREADS TO HELP YOU
http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282 by autoprime "Great Job"
http://storagecow.eu/index.php?dir=Xda/LG+G4/ an extensive list of KDZ files
Have fun people! :good:
don't know if it makes a difference, but i read somewhere to install LGUP dll first, then the other one.
reg66 said:
don't know if it makes a difference, but i read somewhere to install LGUP dll first, then the other one.
Click to expand...
Click to collapse
Not sure but I'll put that in the op cheers.
Do you need root so use this method to upgrade to marshmallow ?
H81520A_00.Kdz flashed (by upgrade option) succesfully. It takes 10-15 mins(longest part is "android upgrading" screen.), and i lost root access. By the way root access is not necessary for upgrade.
So since it wasn't clarified, I'll be the one to ask...
Will this work on a unit without root (which is yes according to the OP), and without a bootloader unlock, ie the Taiwan (TWN) variant of the H815.
I completely understand it's a complete wipe and root will not be retained.
I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?
downloaded from a different mirror re flashed no problems
Hello downgrande wokrs?
munkypoo7 said:
So since it wasn't clarified, I'll be the one to ask...
Will this work on a unit without root (which is yes according to the OP), and without a bootloader unlock, ie the Taiwan (TWN) variant of the H815.
I completely understand it's a complete wipe and root will not be retained.
Click to expand...
Click to collapse
its working on all last night i did downgrade to 5.1 and so far all working great
no root or unlocked bootloader is needed
madshabz said:
I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?
Click to expand...
Click to collapse
yes it will work with locked bootloader
ktomika said:
Hello downgrande wokrs?
Click to expand...
Click to collapse
great i did it and now using 7Rom 6.3 3d Rom
best of luck guys
Rikoman17 said:
Do you need root so use this method to upgrade to marshmallow ?
Click to expand...
Click to collapse
no you do not need root....this method will take you back to stock ROM
do I have to unlock bootloader?
microcens said:
do I have to unlock bootloader?
Click to expand...
Click to collapse
no you do not
Kdz only? Does it work with tot file?
bobimbap said:
Kdz only? Does it work with tot file?
Click to expand...
Click to collapse
I'm presuming yes but I havn't tried this, maybe someone could enlighten us
madshabz said:
I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?
Click to expand...
Click to collapse
work for all . root and unroot . locked or unlocked . doesnt care . its a special software
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bobimbap said:
Kdz only? Does it work with tot file?
Click to expand...
Click to collapse
that work fine with TOT file too my friend tested on corean version of g4
Worked a treat no issues so far
Sent from my LG-H815 using Tapatalk
kevtrysmoddin said:
Worked a treat no issues so far
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Great... Did you upgrade to MM or factory reset MM or LP?
shakeyabooti said:
Great... Did you upgrade to MM or factory reset MM or LP?
Click to expand...
Click to collapse
Upgraded
Sent from my LG-H815 using Tapatalk
info
i tried with this tutorial , but the program search my lg g4 with unknown model and i can't use this procedure..
why?
at moment i have a unlocked bootloader and a 10 ve rooted rom twrp
Can anyone help explain very clearly which modem/bootstack is needed for various android versions ESPECIALLY on the D851? I'm familiar with flashing roms but the modem/bootstack is just a layer of complexity I'm not quite sure about. I thought better to ask before I do something stupid.
My current setup is D851 (T-mob), TWRP 3.0.2-0, Fulmics ROM 6.7. My baseband version shows : MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1
1) Which version does this correspond to, what versions are available, and where? I searched here + google and I found here: http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/10R. But depending on the version the modem is image file (20R), or some is bin file (20e), and some is flashable zip (30D). How to safely flash bin or img files? And if I flash 20e modem do i also need to flash 20e boot, bootloader etc? Confused!
2) How to know which version for different andriod i.e. marshmallow, nougat etc.
3) When/how should I flash and can i brick if I use the wrong version? For example I want to flash a 7.1 ROM and i've read posts saying 20e modem works well. Could anyone explain, step by step, how I should flash modem: before or after rom/gapps etc.
4) Last question - TWRP 2.8 or so used to have an option to check for backup of modem but that no longer appears in 3.0+. Does TWRP 3.0+ backup include the modem even though there is no specific box to check for that?
Thanks in advance!
emailej said:
Can anyone help explain very clearly which modem/bootstack is needed for various android versions ESPECIALLY on the D851? I'm familiar with flashing roms but the modem/bootstack is just a layer of complexity I'm not quite sure about. I thought better to ask before I do something stupid.
My current setup is D851 (T-mob), TWRP 3.0.2-0, Fulmics ROM 6.7. My baseband version shows : MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1
1) Which version does this correspond to, what versions are available, and where? I searched here + google and I found here: http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/10R. But depending on the version the modem is image file (20R), or some is bin file (20e), and some is flashable zip (30D). How to safely flash bin or img files? And if I flash 20e modem do i also need to flash 20e boot, bootloader etc? Confused!
2) How to know which version for different andriod i.e. marshmallow, nougat etc.
3) When/how should I flash and can i brick if I use the wrong version? For example I want to flash a 7.1 ROM and i've read posts saying 20e modem works well. Could anyone explain, step by step, how I should flash modem: before or after rom/gapps etc.
4) Last question - TWRP 2.8 or so used to have an option to check for backup of modem but that no longer appears in 3.0+. Does TWRP 3.0+ backup include the modem even though there is no specific box to check for that?
Thanks in advance!
Click to expand...
Click to collapse
Quote:
Originally Posted by graig79
10c Baseband:
MPSS.DI.2.0.1.c1.13-00009-M8974AAAAANPZM-1
10m Baseband:
MPSS.DI.2.0.1.c1.13-00018-M8974AAAAANPZM-1
20e Baseband:
MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1
emailej said:
Quote:
Originally Posted by graig79
10c Baseband:
MPSS.DI.2.0.1.c1.13-00009-M8974AAAAANPZM-1
10m Baseband:
MPSS.DI.2.0.1.c1.13-00018-M8974AAAAANPZM-1
Click to expand...
Click to collapse
Quote:
Bootstack=partitions needed to boot a rom. 20B update by LG and TMO has specific newer partitions like aboot, boot.img. system.img, modem.img, etc. needed to run and boot the rom.
If your on 10R Kitkat and try to flash just the rom, it won't boot, or won't have data connection, etc. Haven't tried it yet, but its not good.
If you want to go back to 10R Kitkat that you have as your backup, then you need to flash the 10R Bootstack for your backup to boot.
**************
HOW TO FLASH:
**************
Step 1: Full wipe unless already on rom. Do not wipe internal storage.
Step 2: Flash appropriate Lollipop Bootstack.
Step 3: Flash ROM.
Where can I find a copy of the 21c modem for D851
A number of people keep referring to the 21C modem, but I can't find a copy of it. I'm trying to install Fulmics 8.0 on my LG G3, but for some reason the modem file seems to be missing. Thanks
egerio01 said:
A number of people keep referring to the 21C modem, but I can't find a copy of it. I'm trying to install Fulmics 8.0 on my LG G3, but for some reason the modem file seems to be missing. Thanks
Click to expand...
Click to collapse
Why do you need to flash a new modem?
LG G3 what model do you have?
My G4 has just gone on me again, just sitting at the boot logo and a flashing blue led. This is the 2nd time in a week and the last time it was due to a corrupt build.prop, which I was able to replace from backup. This time it has just happened randomly and the original build.prop doesn't help.
So if someone can help me out urgently with a stock marshmallow rom for twrp it would be a big help.
Cheers.
mickrick said:
My G4 has just gone on me again, just sitting at the boot logo and a flashing blue led. This is the 2nd time in a week and the last time it was due to a corrupt build.prop, which I was able to replace from backup. This time it has just happened randomly and the original build.prop doesn't help.
So if someone can help me out urgently with a stock marshmallow rom for twrp it would be a big help.
Cheers.
Click to expand...
Click to collapse
theres is softbrick and bootloop. you are aware that G4 can bootloop do to a hadware issue not software.?
maybe you have infamous bootloop. and not a soft brick. but you can try to KDZ does it boot into twrp.? if not then hardware issue.
for kdz search here to flash using LGUP.
http://downloads.codefi.re/autoprime/LG/LG_G4
raptorddd said:
theres is softbrick and bootloop. you are aware that G4 can bootloop do to a hadware issue not software.?
maybe you have infamous bootloop. and not a soft brick. but you can try to KDZ does it boot into twrp.? if not then hardware issue.
for kdz search here to flash using LGUP.
http://downloads.codefi.re/autoprime/LG/LG_G4
Click to expand...
Click to collapse
Yes, it boots to twrp. Thats the reason I need the 20e zip file and not kdz. I was able to flash a 20d zip last night which then allowed me to flash the 20e kdz. But when I flashed twrp again just now, the same thing has happened again. I'm thinking now that this started happening when I updated twrp to the latest version via the twrp app, and it was only when I had another app crash and reboot my phone two nights ago that it happened for the first time. I'm going to downgrade twrp to an earlier version and see if that makes a difference.
mickrick said:
Yes, it boots to twrp. Thats the reason I need the 20e zip file and not kdz. I was able to flash a 20d zip last night which then allowed me to flash the 20e kdz. But when I flashed twrp again just now, the same thing has happened again. I'm thinking now that this started happening when I updated twrp to the latest version via the twrp app, and it was only when I had another app crash and reboot my phone two nights ago that it happened for the first time. I'm going to downgrade twrp to an earlier version and see if that makes a difference.
Click to expand...
Click to collapse
??? you needed the zip to flash KDZ.??? that makes no sense.. then no hardware issue just a soft brick, a software issue. all you had to do was KDZ to latest version. using the refurbished option on LGUP.
then inject twrp and install twrp permanently and then root .
wich twrp are you using.? have you tried this.
the unnoficial beta5.
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
raptorddd said:
??? you needed the zip to flash KDZ.??? that makes no sense.. then no hardware issue just a soft brick, a software issue. all you had to do was KDZ to latest version. using the refurbished option on LGUP.
then inject twrp and install twrp permanently and then root .
wich twrp are you using.? have you tried this.
the unnoficial beta5.
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Click to expand...
Click to collapse
I was unable to boot my phone so I needed to reflash it. As I only had access to twrp, I had to flash a zip file. I couldn't find a 20e zip so I flashed the next best thing, which was a 20d file. This isn't the correct version for my phone and let me know that each time I booted it. So once I had the phone booted up, I used LGUP to flash the 20e kdz file. My reasoning for this is that I can only flash a kdz file using LGUP, and as I can't boot my phone, I can't use LGUP. So are you telling me I can flash a kdz file from twrp?
Anyway, it appears the latest twrp (twrp-3.0.2-1-h815) was causing the problem. I reverted back to the previous version and I have had no issues so far. I've taken a full nandroid backup to be on the safe side.
Thanks for the advice.
mickrick said:
I was unable to boot my phone so I needed to reflash it. As I only had access to twrp, I had to flash a zip file. I couldn't find a 20e zip so I flashed the next best thing, which was a 20d file. This isn't the correct version for my phone and let me know that each time I booted it. So once I had the phone booted up, I used LGUP to flash the 20e kdz file. My reasoning for this is that I can only flash a kdz file using LGUP, and as I can't boot my phone, I can't use LGUP. So are you telling me I can flash a kdz file from twrp?
Anyway, it appears the latest twrp (twrp-3.0.2-1-h815) was causing the problem. I reverted back to the previous version and I have had no issues so far. I've taken a full nandroid backup to be on the safe side.
Thanks for the advice.
Click to expand...
Click to collapse
if you boot to twrp then am pretty sure you can enter download mode and use LGUP and KDZ. that was my point. its even better as its the official firmware that will fix any issues..
raptorddd said:
if you boot to twrp then am pretty sure you can enter download mode and use LGUP and KDZ. that was my point. its even better as its the official firmware that will fix any issues..
Click to expand...
Click to collapse
I couldn't get the phone into download mode. If I had been able to do so it would've made life a lot easier for me. Flashing the zip file and then the kdz was a long winded way to do it but I finally got the desired effect. And I was able to tell that the latest twrp looks to be problematic for the H815 (I've prepared myself for any resulting backlash).
mickrick said:
I couldn't get the phone into download mode. If I had been able to do so it would've made life a lot easier for me. Flashing the zip file and then the kdz was a long winded way to do it but I finally got the desired effect. And I was able to tell that the latest twrp looks to be problematic for the H815 (I've prepared myself for any resulting backlash).
Click to expand...
Click to collapse
give the one i posted link a try.. is unofficial and at the same thime official..
Just disabling automatic updates in your rom should fix all this. Latest twrp works fine.
Sent from my LG-H815 using XDA Labs
Cheers lads. Things are running very smoothly at the minute.
I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?
Good luck. I hope it works for your phone.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.
The biggest problem is the sim card in my opinion.
audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.
I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.
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.