Related
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
It appears as if sammobile already has it???
http://www.sammobile.com/firmwares/confirm/99757/G900TUVS1GPI1_G900TTMB1GPI1_TMB/
SurfinMobile77 said:
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
Click to expand...
Click to collapse
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
SimLynks said:
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
Click to expand...
Click to collapse
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
SurfinMobile77 said:
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
Click to expand...
Click to collapse
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
Download the OTA Update to YOUR DEVICE ITSELF, Run FlashFire, and Hit the Red "Plus" -> Use either "Flash Firmware package" OR "Flash ZIP or OTA" options, find the OTA ZIP downloaded to your device and let FlashFire do it's thing.
NOTE: DO NOT LET FLASHFIRE UPDATE YOUR BOOTLOADER/MODEM these are the "Protected Partitions" and are Locked while booted into your "Custom" ROM by Samsung after it detects you've been rooted. FlashFire documentation explains this in a bit more detail.
2) Download the TAR files to the computer you will be running Odin from, and Restart your Galaxy S5 in Download Mode (Turn device off -> Hold Power Down + Home + Power)
3) Flash the TAR archives in Odin, standard way is Open Odin, connect phone in download mode (should be detected by Odin) hit the "AP" button and UNCHECK "Auto Reboot" if you want to be able to flash both the Bootloader and the Modem without the Device rebooting automatically after the first flash.
Once you have flashed BOTH the Bootloader and the Modem, go ahead and restart your device, you should now have an updated Kernel (OTA Package in FlashFire, Updated Bootloader/Modem from Odin) and be good to go even with Root/Xposed/Encrypted enabled and TWRP that cannot decrypt the Data partition with Samsung Encryption.
SimLynks said:
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
.
Click to expand...
Click to collapse
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Sent from my SM-G900T using XDA Free mobile app
tsh said:
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Click to expand...
Click to collapse
Right, I mean a full wipe / restore will definitely fix the issue no doubt, but before you try that you can always do the "full" ROM update using the same method as I previously posted, just replace flashing the OTA from FlashFire, with flashing the full ROM Update and follow all the other steps. Also make sure FlashFire has "Everroot" Checked and I entirely disable flashing "Protected Partiions" in settings, so there is no "unchecking" anything, FlashFire does that automatically.
OTA or Full ROM release, FlashFire still cant safely deal with the "protected partitions", but this is how prior to attempting to use the smaller OTA file, I have been updating my rooted/xposed/encrypted G900T from release to release, the downside to the full update is that after flashing everything you get to wait for the ROM to rebuild the cache, reboot to TWRP and reflash SuperSU and if using Xposed reflash that as well and then again wait for the system to rebuild as Xposed does it's thing on the first boot after install.
I also did not think to consider that my heavily "trimmed" System Apps might have an effect on this, I use Titanium Backup & Greenify immediately after install to outright freeze all the bloatware or Greenify things the system needs to function properly, but I don't want running all the time. When I get a chance Im going to update my friend's G900T using my method and try to figure out this discrepancy between what worked for me, and what is clearly giving you some issues. Until then i'd appreciate any further feedback you can give me so I can revise the process to eliminate any potential trouble spots. Sorry to keep spamming you with all this unnecessary info, but until I can post my own thread on this stuff im just kinda throwing everything I've got here so the info is somewhere.
As for the Stagefright issue, I just reran the Zimperium Stagefright testing again on my up-to-date G900T as well as a Galaxy S3 I'm running the latest nightly Exodus ROM release on (Google Release r68, Android Security Patch Date September 6, 2016, Kernel Build Date Oct 6, 2016) and BOTH devices now fail the Stagefright testing again, after previously passing for about a week or so...This is just how it works with Stagefright unfortunately, they patch it until more bugs are found, rinse repeat.
So no matter what it seems, your gonna fail Stagefright even if on an incredibly recent Build/Kernel. My last test for this needs to be if Nougat also now fails as well, because if so, then it's just another round of the Stagefright party as standard, since they first announced this back in July 2015.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
You need to flash a firmware package containing a system/system.img. stagefright are system libs. If you want that fix you need to just go ahead and flash the entire firmware. Only thing is tho, stagefright has never been 100% fixed
SimLynks said:
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1.
Click to expand...
Click to collapse
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
djy said:
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
Click to expand...
Click to collapse
yes, I can find vpndialogs.apk under priv-app
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
djy said:
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
Click to expand...
Click to collapse
Please follow the instructions in this thread
http://forum.xda-developers.com/android/help/android-dat-img-file-unpack-repack-2-0-t3309285
SimLynks said:
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Click to expand...
Click to collapse
Hi!
I think your method fails to update the build. FlashFire doesn't patch anything, (build number still show GPG2)
This is what I do:
Restore original boot from my GPG2 clean install (boot is unpatched)
Restore stock recovery (through ODIN)
(2 previous steps avoid status 7 error while applying OTA updates)
Flash OTA update .zip through stock recovery
Reinstall TWRP custom recovery
Reroot Applying superSU.zip method
Wipe Dalvik / cache
Reboot
After 10 minutes everytihng working!
I'm uploaded a screenshot with the results
I think triyng to apply OTA updates with any workaround is possible whenever system partition is reasonably stock, because OTA updates patch files, not replace files
My system was just rooted and 2 battery stats helpers installed. I think with xposed installed the above steps must work. But with other tweaks more complex OTA updates with no stock system will fail
That's similar to what I did, but without the need to restore data since you flashed the stock recovery without flashing the system by the sound of it. Can you explain exactly which images you flashed for boot & stock recovery? I'm thoroughly confused over what's what, since everybody seems to use different jargon to mean the same thing.
invisiblewave said:
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Click to expand...
Click to collapse
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Reyse said:
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Click to expand...
Click to collapse
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
invisiblewave said:
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
Click to expand...
Click to collapse
I extracted both image from the full update from Sammobile
Follow these instructions
Download 7Zip archive manager http://www.7-zip.org/download.html
Download the full image of your phone from SAMMOBILE
For example my previous phone version was G900TUVS1GPG2_G900TTMB1GPG2_TMB.zip
Open that file with 7zip
it contains G900TUVS1GPG2_G900TTMB1GPG2_G900TUVS1GPG2_HOME.tar.md5
double click to extract
these are the files in the archive
Code:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
boot.img => stock boot
recovery.img => stock recovery
extract both files
Now for each of them:
- right click => 7ZIP => Add to archive...
- it suggest the same name (irrelevant)
- Choose archive format => tar (very important)
- Press Ok
- Flash with ODIN
(don't reboot, turn off and turn on for each flash to avoid boot phone and mess versions)
Source of this instructions: http://howto.highonandroid.com/samsung-tutorials/how-to-extract-stock-recovery-from-samsung-firmware/
[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
discussion?
Chaosruler said:
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
Click to expand...
Click to collapse
Interesting, was this an issue with the WW-5.17.44.68 update or has this been an ongoing issue? I didn't bother with the previous one because it didn't seem to do a whole lot, but never noticed this issue.
Chaosruler said:
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
Click to expand...
Click to collapse
I hate doing this juggle. Big part of why I don't try to update unless it's significant :/
Chaosruler said:
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
Click to expand...
Click to collapse
Thanks for the heads up on this. I check the release thread often in hopes of Oreo, but they don't bother putting this information on their small updates. I think I'll update just because of that really, although Oreo would have been nice too :silly:
Chaosruler said:
discussion?
Click to expand...
Click to collapse
I feel like there's probably only 2 or 3 people who check these forums often nowadays, which is a shame because the phone is quite nice, and even has the bootloader unlocked as well. But ASUS seems to have too many phones that need updates and we're left in the dust waiting. Both XDA and Zentalk forums have people complaining and talking about this being their last device, which is reasonable and align with my thoughts as well. Really though, I want to go and make my own ROM for this phone, but don't really have the time, resources, or experience to tackle it just yet. Maybe I can use it in the future for practice
Update Impressions
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10 but any computer with fastboot installed will work really) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. /u/Ryder. has pointed out the Zentalk forum has the latest recoveries available, so check there first. At the time of writing, I was pushed to login to view that forum, so instead I just grabbed the latest available from AndroidFileHost, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.2.1* from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img). *3.2.1 is available in the Mega. At the time of writing, I only checked the AndroidFileHost link and didn't check to see if there was an updated build for it. It is Oreo compatible, so when they finally get around to giving us Oreo, you'll have a suitable recovery to go along with it. Thanks to /u/Ryder. for the heads up.
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Error when I try to download.
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
asianflipboy said:
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. I just grabbed the latest available, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.1.1 from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img).
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Click to expand...
Click to collapse
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Chaosruler said:
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Click to expand...
Click to collapse
You're right about that. I've updated my post to reflect it.
Chaosruler said:
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Click to expand...
Click to collapse
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Ryder. said:
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Click to expand...
Click to collapse
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
indiana99 said:
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
Click to expand...
Click to collapse
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
asianflipboy said:
You're right about that. I've updated my post to reflect it.
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
asianflipboy said:
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
No. Thank you very much for asking. I downloaded from a different location.
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Good to hear.
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Hmm, I think I'll do that. I'll make some small zip files for each.
---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Ryder. said:
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
Click to expand...
Click to collapse
Sorry for re-quoting all of you, but do you guys see the update anymore? It might have been why /u/indiana99 couldn't find it. I went to check while making the zip packs and it's not there... Maybe there was some issue with the build? It's got me a bit shook that it's suddenly not on the website.
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Chaosruler said:
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Chaosruler said:
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
indiana99 said:
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Click to expand...
Click to collapse
That's weird to me though. I just checked again and both variants are missing the current update, 5.17.44.87. Did they pull it for some reason? As far as I can tell, my phone is behaving pretty normally. Anyone that's updated notice anything weird?
I've removed the link. This article claims that we're finally getting the update by the end of March!
https://www.phonearena.com/news/Asu...-ZenFone-3-Deluxe-receive-Oreo-March_id103395
Finally!
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?