Related
This by NO means is a flashable zip. I left it as .7z to make sure no one tries. I am hoping by posting this that a Dev can pick it up and make it ready for everyone else. It's stock Odex KME with boot.img.
http://www.multiupload.com/S4UBHQWAC8
My moto spent the better part of the last 24 hours offline while I worked on making a safe flashable zip from the 4.4.2 OTA that patches 4.4 without changing the bootloader. (I could not wait for the official SBF.) Well I got it working with root, and I have a new flashable zip from my /system dump, but I now need to keep my phone working.
* I am hoping to find a tester who is familiar with loading 4.4 and root via safestrap, who is willing to try my untested zip and help me work out any bugs.
Any takers with a locked ATT xt1058? pm if you are familiar with this process and have the time and inclination.
(Be aware that the process takes a while, and one of the steps is to wipe all data. You will also need to downgrade to 4.2.2 and re-root.)
Ctrl-Freak said:
My moto spent the better part of the last 24 hours offline while I worked on making a safe flashable zip from the 4.4.2 OTA that patches 4.4 without changing the bootloader. (I could not wait for the official SBF.) Well I got it working with root, and I have a new flashable zip from my /system dump, but I now need to keep my phone working.
* I am hoping to find a tester who is familiar with loading 4.4 and root via safestrap, who is willing to try my untested zip and help me work out any bugs.
Any takers with a locked ATT xt1058? pm if you are familiar with this process and have the time and inclination.
(Be aware that the process takes a while, and one of the steps is to wipe all data. You will also need to downgrade to 4.2.2 and re-root.)
Click to expand...
Click to collapse
I would help you but I already took the ota...
Sent from my XT1058 using xda premium
edit
I have posted this several places with no response but I will try again as a separate thread. If you want root using MoFo on your AT&T XT1097, you need the 5.0 system.img.
1) Does anyone know if the Brazil XT1097 5.0 system.img can be flashed successfully to the AT&T XT1097?
2) If not, did anyone use Motorola Device Manager to update from 4.4.4 to 5.0? If so, there should be a folder in c:\programdata\motorola\SUE\firmwares that will have the 5.0 system.img in there. If you have it, please let us know.
AFAIK, maiko1 is not working on finding this for you. If you want root, you need to find out if either the Brazil 5.0 system.img can be flashed successfully to your device or get a copy of the 5.0 system.img for your device.
If someone is still on 4.4.4 on their AT&T XT1097, they can use MDM to update to 5.0 and then they will have a copy of the 5.0 system.img on their computer.
Also once 5.1 is released, you should use MDM to update, not the OTA and then you will have the 5.1 fxz:
http://forum.xda-developers.com/moto-x-2014/general/5-1-update-motorola-device-manager-to-t3099587
You can download the full ATT 5.0.2 image here, when unzipped you will have the full system image:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
Steve-x said:
You can download the full ATT 5.0.2 image here, when unzipped you will have the full system image:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
Click to expand...
Click to collapse
OK so ATT was upgraded to 5.0.2?
Yes we AT&T XT1097 users have 5.0.2 ( thank you for your work )
(figercrossed for ROOT )
niko99 said:
Yes we AT&T XT1097 users have 5.0.2 ( thank you for your work )
(figercrossed for ROOT )
Click to expand...
Click to collapse
well the fxz is in sparsechunks so I am going to have to try to flash it to my XT1096 and see if I can extract it as a single system.img. I will have to read up on that to know if it is possible.
JulesJam said:
well the fxz is in sparsechunks so I am going to have to try to flash it to my XT1096 and see if I can extract it as a single system.img. I will have to read up on that to know if it is possible.
Click to expand...
Click to collapse
your work on this is appreciated. i wish i could help but already on 5.0.2
Maiko1 didn't respond when I asked him how to make a pre-rooted image when all you have are the sparsechunks. And it looks like the AT&T XT1097 is getting 5.1 soon.
DON'T TAKE THE OTA - USE MOTOROLA DEVICE MANAGER INSTEAD SO SOMEONE CAN SNAG THE FXZ FILES!!!!
If you can get the 5.1 system in a single file system.img, there is hope. But someone is going to have to get that if you all want to use mofo.exe to root your devices.
JulesJam said:
Maiko1 didn't respond when I asked him how to make a pre-rooted image when all you have are the sparsechunks. And it looks like the AT&T XT1097 is getting 5.1 soon.
DON'T TAKE THE OTA - USE MOTOROLA DEVICE MANAGER INSTEAD SO SOMEONE CAN SNAG THE FXZ FILES!!!!
If you can get the 5.1 system in a single file system.img, there is hope. But someone is going to have to get that if you all want to use mofo.exe to root your devices.
Click to expand...
Click to collapse
Will try this.
http://www.androidpolice.com/2015/0...he-android-5-1-update-for-the-2nd-gen-moto-x/
The update is coming soon, be prepared to update via Motorola Device Manager. Will try my best to do by that way.
If you want to convert the sparse chunks into a single original system.img file please check out this thread:
http://forum.xda-developers.com/showthread.php?t=2749797
Steve-x said:
If you want to convert the sparse chunks into a single original system.img file please check out this thread:
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thanks! I was able to make a single file but as the OP of that thread indicates, there is a header in the files.
When I try to flash it to my XT1096, it says invalid sparse file format at header magi. So obviously the header is noticed. However, it then proceeds to try to flash it. But it gives me a signature error - invalid signed image - and the flash is aborted. I can boot normally from bootloader mode so no issues there.
I have uploaded the single image file here:
https://www.dropbox.com/s/ho38gpcanzvym6m/system.zip?dl=0
The next step is for someone to convert the file into ext4 format via linux using maiko1's instructions here:
http://forum.xda-developers.com/showpost.php?p=60332412&postcount=22
so if any of you ATT XT1097 owners know linux, the instructions maiko1 gave are pretty simple. But that needs to be done by one of you.
Once that is done and uploaded somewhere I can download it, I will try to root it using btdownloads7's instructions here:
http://forum.xda-developers.com/showpost.php?p=60389310&postcount=177
At that point I will try to flash it to my XT1096 using mofo.exe, which may not work b/c your image is larger than the XT1096 image, but I will try it and see what happens.
JulesJam said:
Thanks! I was able to make a single file but as the OP of that thread indicates, there is a header in the files.
When I try to flash it to my XT1096, it says invalid sparse file format at header magi. So obviously the header is noticed. However, it then proceeds to try to flash it. But it gives me a signature error - invalid signed image - and the flash is aborted. I can boot normally from bootloader mode so no issues there.
I have uploaded the single image file here:
https://www.dropbox.com/s/ho38gpcanzvym6m/system.zip?dl=0
The next step is for someone to convert the file into ext4 format via linux using maiko1's instructions here:
http://forum.xda-developers.com/showpost.php?p=60332412&postcount=22
so if any of you ATT XT1097 owners know linux, the instructions maiko1 gave are pretty simple. But that needs to be done by one of you.
Once that is done and uploaded somewhere I can download it, I will try to root it using btdownloads7's instructions here:
http://forum.xda-developers.com/showpost.php?p=60389310&postcount=177
At that point I will try to flash it to my XT1096 using mofo.exe, which may not work b/c your image is larger than the XT1096 image, but I will try it and see what happens.
Click to expand...
Click to collapse
Just shut down my computer for the night lol. It's a pretty simple procedure so lemmie download and convert it real quick.
G4 Man2 said:
Just shut down my computer for the night lol. It's a pretty simple procedure so lemmie download and convert it real quick.
Click to expand...
Click to collapse
The thing that takes the longest is uploading the files - even zipped it is over 1GB.
JulesJam said:
The thing that takes the longest is uploading the files - even zipped it is over 1GB.
Click to expand...
Click to collapse
Just got done downloading it, converting it shouldn't take too long but yeah, uploading is another story. I'll let that happen overnight and hopefully I can post a link when I get up.
---------- Post added at 02:06 AM ---------- Previous post was at 01:48 AM ----------
JulesJam said:
The thing that takes the longest is uploading the files - even zipped it is over 1GB.
Click to expand...
Click to collapse
It seems like the image is not playing nice with simg2img, depending on which version I use I get different errors but they're all pretty similar.
"Invalid sparse file format at header magi
Failed to read sparse file" What you got
"Bad magic"
or
"Error reading sparse file header"
G4 Man2 said:
It seems like the image is not playing nice with simg2img, depending on which version I use I get different errors but they're all pretty similar.
"Invalid sparse file format at header magi
Failed to read sparse file" What you got
"Bad magic"
or
"Error reading sparse file header"
Click to expand...
Click to collapse
Yeah, the dev who made the tool to decompress the image said there was a header in the Motorola files.
http://forum.xda-developers.com/showthread.php?t=2749797
I will ask him how to get rid of it and post back, thanks!
Good News - The Stock 5.0.2 Ext4 Image G4 Man2 Made Boots!!!!!!
That's right - I am now running the ATT 5.0.2 system on my Verizon XT1096, lol! It boots but b/c I have verizon radios and different hardware it doesn't work as a phone but that is to be expected.
So now I will try to root it and see what happens.
2 things - Root checker basic shows my model as the XT1097, which of course it is not and my qe is now 2/1 (was 1/1), and I have no idea what 2/1 means.
I am going to flash my phone back to 5.0 stock Verizon image and then try to root this ATT ext4 image.
Big thanks to @G4 Man2 for making the ext4 image!!!
So if i'm understanding... if you are able to root the ATT xt1097 img on your xt1096, then we (ATT 1097 owners with locked bootloarders) should be able to root via mofo?
Good luck. I'm sub'd so I hope you get a break through
bodeay said:
So if i'm understanding... if you are able to root the ATT xt1097 img on your xt1096, then we (ATT 1097 owners with locked bootloarders) should be able to root via mofo?
Click to expand...
Click to collapse
I am not rooting it on my XT1096. I am rooting it on my XT1060 using TWRP.
If root is successful, then maiko1 should open up MoFo to the AT&T XT1097. But keep in mind, all I will have done is given root access - mofo does not disable write protection. So anything that requires /system to be modified will have to be done in linux and then flashed using mofo.exe. Please read my noob guide and the verizon mofo thread if you want to know more.
Someone with an XT1097 will have to review btdownloads7, mikeoswego and ClydeDroid's threads on their images to see what they did. Slack3r made the original ext4 image and modified the build.prop for free wifi tether, btdownloads7 is the one who rooted the image and put busybox and sqlite3 in the image. Then mikeoswego put Xposed in and ClydeDroid added adaway and the symlink. There are more and more thing being added to the images if you check the threads but you need people who know how to use linux to do that.
What version of the bootloader is on your devices - 60.11?
JulesJam said:
What version of the bootloader is on your devices - 60.11?
Click to expand...
Click to collapse
Mine is running on 60.12
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk
riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Click to expand...
Click to collapse
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?
psychopac said:
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?
Click to expand...
Click to collapse
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.
echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
Click to expand...
Click to collapse
That's absolutely okay with me as I always like to clean flash ROMs and I don't mind the data partition being erased.
echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.
Click to expand...
Click to collapse
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.
riggerman0421 said:
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.
Click to expand...
Click to collapse
I agree with what you wrote, a backup in TWRP and having the same stock ROM is essential to a safe and working device... A stock ROM is always useful in flashing the stock recovery and other stock firmware prior to taking an OTA update. With TWRP backups, you now have to be careful not to allow modifications before you take the backup, else the OTA detects the system partition is no longer readonly, if I recall.
Course, this would be much easier if Motorola/Lenovo released the stock firmware rather than having to depend on leaks, but I'm guessing they don't want to deal with users that flash the incorrect firmware for their device.
I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?
vantastic415 said:
I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?
Click to expand...
Click to collapse
We have all the stock firmwares posted here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
And TWRP flashable stock ROMs here...
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Does anyone know about this ?
The last version of the firmware that got OTA'ed to my phone is POTTER_RETAIL_7.0_NPNS25.137-93-8.
The only twrp backup of the firmware I have is while it was on POTTER_RETAIL_7.0_NPNS25.137-93-4.
When I tried to flash the phone with v 93-4 using fastboot, I got denied because of the version being older than that of the bootloader. But the problem is that I was able to erase prior to attempting writing ...
I need to re-install a stock rom in the phone, but POTTER_RETAIL_7.0_NPNS25.137-93-8 cannbot be found anywhere yet.
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Is there any alternative to patience while waiting for POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip eventually appearing somewhere ?
Or, in other words, knowing that the last OTA to my phone installed v 93-8, is there any way to flash POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for instance ?
CanadianGixxerman said:
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Click to expand...
Click to collapse
An older version (your twrp backup) will work with a newer bootloader, however you can't do any OTAs. An OTA will try to apply the same changes to the bootloader that were already made, resulting in a hard brick - though the OTA would fail anyway since you don't have an intact /oem partition. You will have a functional phone, and you can get back on track after 93-8 images or Oreo are released.
I know because I'm in a similar situation. I wanted to update from 93-4 to 93-8, and I had an intact /system image backup, but /oem was mounted before so I had to flash it via fastboot. Little did I know it was from the wrong channel (retus instead of reteu), resulting in the OTA updating everything except for oem and messing stuff up, so I just flashed a 93-4 twrp backup. Everything works, patiently waiting for Oreo.
bazinga137 said:
I just flashed a 93-4 twrp backup.
Click to expand...
Click to collapse
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
Honestly, I am not sure. I did a twrp back up with the default selected partitions. But it turned out that this backup is not reliable. The phone does boot up on it, but suffers from applications crashes all over. Last I discovered is that the phone itself was not working for a phone, meaning making receiving calls is not possible.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
bazinga137 said:
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
Click to expand...
Click to collapse
Dumb question...How do I know if the oem partition is tampered with or has never been mounted? I am rooted with elementalx kernel and supersu. TWRP partition stock backup made immediately after taking 93-8 update and before flashing twrp, rooting, etc. I know I am hosed without the system IMAGE as far as ota's go, but I'm just trying to learn.
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
dunderball said:
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
Click to expand...
Click to collapse
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
craigl14 said:
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
Click to expand...
Click to collapse
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
CanadianGixxerman said:
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
I'm on a slightly same boat as OP, but I don't have my backup since I thought it was on my SD and wiped my phone, with the backup only there. I was on 93-8 when I wiped. Would getting a 93-4 backup work?
This question might of been answered but I did not see it when I read through this thread.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I took a full backup of my system image through twrp, and I was on 93-8. I'll upload it when I have time and you can give it a try.
CanadianGixxerman said:
[...] but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Why would you need to relock the BL to take an OTA?
craigl14 said:
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
Sadly you can't apply an OTA to the firmware images, if that's what you're thinking. They need to be signed by moto to be flashable through fastboot. And if you'd want to provide someone with a twrp backup of a firmware higher than theirs, their bootloader would need to be updated too, via an OTA.
bazinga137 said:
if that's what you're thinking.
Click to expand...
Click to collapse
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
craigl14 said:
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
Click to expand...
Click to collapse
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I made a full backup of 93-8, but still i can't lock bootloader. We need complete firmware, until then, Lineage OS is the answer.
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
bazinga137 said:
Why would you need to relock the BL to take an OTA?
Click to expand...
Click to collapse
No idea, i saw this first time now on Motorola. On any other manufacturers i could lock bootloader, and even get OTA updates just by flashing stock recovery and having unlocked bootloader was not a problem.
If your device was formally updated to NPNS25.137-93-8 (March 2018 security patch), then you could try to flash the NPNS25.137-93-4 (Jan 2018 security patch) update again as you previously tried (link to the Jan 2018 stock firmware for EU/US and Asia devices: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ ). You may wish to ignore the security downgrade errors (you cannot downgrade bootloaders anyway, presumably to prevent you opening security vulnerabilities) when you flash, which should just be for GPT and bootloader. You may also see 'image signed with bad key' for recovery and boot as well, but verify those partitions, and the other partitions report [OKAY] after flashing. That way, you should have a NPNS25.137-93-4 system, with a NPNS25.137-93-8 bootloader, and when you boot you should have a device reporting with fully stock NPNS25.137-93-4. The next OTA you should receive is the NPNS25.137-93-8 OTA and then the NPNS25.137-93-10 April 2018 security patch OTA, which should bring you up to the latest stock firmware.
By reflashing the NPNS25.137-93-4 firmware, this should also restore your OEM partition to being untampered (read only status?), as should your system partition (which should be read only, I recall that swiping to allow modifications in TWRP sets your system partition to read-write, which causes the OTA to fail).
Normally, I would advise against downgrading and using OTA updates, as this is a prime way of hard bricking. However, in this case you are downgrading your device firmware to the firmware directly preceding the newest firmware you had (i.e. downgrading to NPNS25.137-93-4 from NPNS25.137-93-8), with the next OTA being NPNS25.137-93-8, which brings you back up to the build you had, this may be safe. To your device, you are flashing the same bootloader from the NPNS25.137-93-8 OTA as currently on your device, which should not hard brick.
If you previously had stock NPNS25.137-93-10, then I cannot recommend this procedure as you'll be downgrading two firmware versions (and you'll have to wait for newer stock firmware to be leaked), else if you try flashing NPNS25.137-93-4 onto the April 2018 firmware and try using OTA updates, you may hard brick and have a pricey paperweight. I also do not know if this will work by cross-flashing from the NPN25.137-92 series of updates either.
Of course, as the NPNS25.137-93-4 firmware is older than your bootloader, you will not be able to re-lock your bootloader (you'll need a newer firmware, probably the April 2018 or newer security patch stock firmware), but being back on full stock, you should be eligible for OTAs provided you only downgraded from NPNS25.137-93-8 (and that March 2018 security patch was the latest stock firmware on your device).
If you are truly concerned about hard bricking, then I would follow other member's suggestions in this thread and stay with TWRP flashables of the stock ROM, as they do not usually affect the bootloader.
Any questions or comments before you perform this procedure, please ask.
bazinga137 said:
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
Click to expand...
Click to collapse
Thanks. Weird. Sorry for hijacking this thread. But if my process were to take OTA after which it reboots, then IMMEDIATELY reboot into bootloader, fastboot BOOT into twrp (not flash it) and take a backup of boot, logo, oem, recovery and system (FULL IMAGE), how would that change oem?
CanadianGixxerman said:
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
Click to expand...
Click to collapse
What's buggy about PE? I was just about to try it...