Related
If your XT1068 is the later version (came from factory with 5.0.2 -it has toshiba front cam) Kitkat will work BUT you will LOSE use of front cam as kitkat has no drivers for this
4.4.4 KITKAT XT1068 Easy Installer
Simple quick Installer of firmware via fastboot
the 4.4.4 Retaildsdsall (GLOBAL) firmware
YES IT CONVERTS UK (GB) PHONES
this is STOCK firmware with no mods,
So Will receive ALL Future OTA updates
and installs over ANY version of 4.4.4 /5.0.x / Custom Rom
(does not check - just flashes regardless of version)
by Auto Restore Script
Requires Windows 7/8/10 to run script
WARNING READ THIS!
MAKE A FULL BACKUP OF PHONE
via play and TWRP or your favorite method. DO NOT SAVE TO PHONE save to pc and a flash drive
(2 copies - cover yourself)
Try to have Battery over 70% charged - 50% OK under 30% DANGER
This flashes back STOCK UNTOUCHED files inc, GPT, modem, boot, recovery, bootloader, system etc etc (basically only your external SD card is left alone!!)
CLEAN FLASH ONLY, so do a
Full factory Reset / wipe required before installation
from phone backup & reset in settings
YOU can HANG / KILL your phone if IGNORED
-- USE @ OWN RISK --
DOWNLOAD
Kitkat 4.4.4
.14 .23 .27 versions (global) + UK (GB) .23 + DE (German) .14
stock firmware + installer AIO
+ INSTRUCTIONS
Download and save to PC / laptop / desktop - DO NOT save the Download to phone or SD Card
A) Firmware KXB21.85.14 (earliest version) https://mega.co.nz/#!mo8wnRJI!APkjY2f_bk-HB2JFBCoWh5rmPvltqCzgTQjQf1t-MHQ
B) Firmware KXB21.85.23 (DSDS ALL) https://mega.co.nz/#!Kkc31L4A!JLtksSioP_xnOZ6m3CR570o9Dxm7LbPgEF2gnkDF_TI
C) Firmware KXB21.85.27 (latest version) https://mega.co.nz/#!CltVzboY!etSjBHqKdMrQTYsh1LcsdMj9S3McG7gkfXRMI7WYPJQ
D) Firmware KXB21.85.23 - GB Region (UK) https://mega.nz/#!yotQhYjK!w0FcxKw1s6w4Ro125mwAvxcoPywnVso8Fa5BihW2Z3k
E) Firmware KXB21.85.14 - DE Region (Germany) https://mega.co.nz/#!T10zkTrR!yBTSeScMh2FLbi9GXjf34VRIBHtBsZoKv_XYqdBj9yU
.
.
V 1.0 Retired
V2.0
Simplified Install method, zip now includes instructions, drivers and all required ADB files
no longer needs USB debugging as done via AP Fastboot flash mode
FAQ's
Q1): What exactly is this?
STOCK motorola firmware files, with a added auto restore script, Adb and fastboot, to allow a easy installation.
Q2): What model phone does this work for?
XT1068 , Various Retaildsds firmware, confirmed working on UK (GB), Indian and EU phones NOT for Brazilian XT1068
Q3): What version is this ?
4.4.4 KITKAT version .14 .23 .27 and UK (GB) .23
Q4): Why Must I factory reset /wipe phone?
Simply because your phone will Hang if downgrading, be sluggish and other problems..... if you can flash firmware - you can make back up 1st and reload all you apps and data - Do it right 1st time
thanks for this.....i'll try your tools later, now i'm not able to use pc!!!
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
arjunpaliath said:
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
Click to expand...
Click to collapse
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
reefuge said:
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
Click to expand...
Click to collapse
Thank you. Was able to find my original firmware and restore to stock.
Rexton270 said:
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
Click to expand...
Click to collapse
I'm just leaving mine as is till lollipop comes out as OTA for XT1068
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Nagass said:
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Click to expand...
Click to collapse
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
reefuge said:
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
Click to expand...
Click to collapse
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Nagass said:
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Click to expand...
Click to collapse
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
reefuge said:
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
Click to expand...
Click to collapse
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Nagass said:
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Click to expand...
Click to collapse
Lol sometimes wished I had waited for OTA 5.0
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
nitsos said:
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
Click to expand...
Click to collapse
is your bootloader unlocked? this method requires UNLOCKED bootloader
Yes,I have bootloader already locked
as of 14/01/2015 firmware B is Accepting OTA zip update (copy to internal memory AND SDCARD ) to Lollipop 5.0.2 from india
bro can you please upload Firmware KXB21.85.23 (DSDS ALL) to google drive as some people are not able to access mediafire??!!
I found only one way to root the galaxy s7 edge but it includes erasing everything and thats just too much trouble for me since i don't trust backup apps with my apps data and all
my model is sm-935FD
this the method i found :
https://youtu.be/nlj76YvxGYo
thank u
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You only need to erase everything if you want to flash custom roms in twrp. Otherwise you can just root with cf autoroot and you're all set
As the others said, flashing cf autoroot in odin won't erase anything, will leave your phone as is and will add supersu.
You should be aware that by rooting you will trip the knox flag, which permanently breaks samsung pay, and will break the following stuff on the stock rom: private mode, secret mode in the browser with fingerprint authentication (which can later be fixed by flashing a custom Rom).
If you want a properly working twrp recovery, you will have to erase everything, including the internal storage of the phone, there is no way around it.
If you absolutely must have root and you're into custom roms then I say do it now, if you're OK with the stock firmware I would advise not to root. This phone doesn't have too much development and you should not expect too many custom ROMs. I personally regret rooting.
I'm erase mi data because I want to do twrp backups, if you don't want to use a custom recovery for flash Roms and use a nandroid only flash supersu.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
TwinCalibre said:
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
Click to expand...
Click to collapse
Flashing the whole fw of course 1 of the way. Maybe if we can extract stock recovery from the fw then just odin it?.
Sent from my SM-N920C
if your on nougat and try to flash TWRP, your device wont boot....they dont have a decrypt solution to 7.0 right now.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Have anyone tried and successfully done it?
there are many ways to root
I recommend use TWRP to root with SU apk file
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
In nougat it will disable access to data folder and force you to format, but if you flash stock firmware nougat the same it was in and reboot it everything was like before.
Basically backup everything using non root apps and adb then format then restore.
Today I accidentally did oem unlock to OFF then rebooted and then it said custom binary blocked by frp. I then flashed many nougat versions but they all caused force close of 2 things ims service and srbg? I ended up flashing nougat from January 2017 dqlc. I got everything back and working. Next I did twrp and supersu etc but data encryption failed. Then I flashed stock dqlc and got everything back. Use home csc or otherwise it will erase everything. Now I have to backup everything.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
Click to expand...
Click to collapse
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
mastabog said:
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
Click to expand...
Click to collapse
And finaly do you find a way to restore your data after installing TWRP ?
By now I would hope your important data is 100% redundantly backed up.
Of all the things that can and do go wrong with rooting, data lose shouldn't even enter into the equation unless you really goofed up bad.
Only two types of data users, those who have lost data and those that will...
I consider any data on internal memory 100% expendable. A complete reload/restore takes me about 2 hours and that's without the luxury of rooting.
At any moment I'm (and you should be too) ready to do a factory reset regardless of the cause without critical data lose.
After two forced back to back forced reloads on my 10+ I learned my lesson.
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
jameslevalaisan said:
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
Click to expand...
Click to collapse
A clean wipe of all settings data means no misconfigurations or malware will survive.
Nuke em.
I'll see how well SmartSwitch does saving the home page next reload. If it screws up it will cost another reload... of course.
Only shortcuts/folders, Good Lock, One Handed Operation plus etc kill me with setup time but it's no big deal. I've gotten pretty adapt at it
Poweramp is completely, redundantly, backed up as that would take weeks to sort of recreate, a true nightmare... as it is now, it only takes a few minutes to do.
My music database has existed for over 15 years. I've lost count of the number of backup copies I have for it... plus the source CD/HDCDs.
Currently have 3 up to date copies to be expanded soon to 4.
Overkill for data backup is a good thing.
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
androidman807 said:
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
Click to expand...
Click to collapse
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
KazuDante said:
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
Click to expand...
Click to collapse
androidman807 said:
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
Click to expand...
Click to collapse
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
KazuDante said:
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse
androidman807 said:
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
Click to expand...
Click to collapse
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
KazuDante said:
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
Click to expand...
Click to collapse
androidman807 said:
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
Click to expand...
Click to collapse
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
KazuDante said:
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Click to expand...
Click to collapse
androidman807 said:
Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
Click to expand...
Click to collapse
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Thanks anyway. It seems it should work, since safestrap won't disappear. Maybe I should post a new thread. Thank you again for all your time.
KazuDante said:
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Click to expand...
Click to collapse
I am also essentially looking to install LineageOS on my Galaxy S5, but before proceeding, I just wanted to make sure that what I'm looking to do is correct. Currently I am running an old version of PhoenixROM with an old unlocked bootloader. I know that I will need to update the bootloader in order to prevent issues, such as wifi not working.
Should all I need to do is follow JKruse's instructions here, flashing LineageOS as the last and final step? I'm hoping that it is this easy, but I do have my doubts and that is why I am asking on here for advice.
Thank you to all in advance!
I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...
So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.
Pretty sure you'll need stock recovery to update the "normal" way.
callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
@st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version
..