Related
I received my BLU R1 HD 2/16GB and the phone brought the following Firmware: BLU_R0010UU_V6.1_GENERIC, but when using it for several hours, a notification message warned me that there was a new firmware available: BLU_R0010UU_V7.4.2_GENERIC
So, I would like to know if it is Recommended to install this new Version 7.4.2, and what new improvements does it have?
ulises.rodriguez said:
I received my BLU R1 HD 2/16GB and the phone brought the following Firmware: BLU_R0010UU_V6.1_GENERIC, but when using it for several hours, a notification message warned me that there was a new firmware available: BLU_R0010UU_V7.4.2_GENERIC
So, I would like to know if it is Recommended to install this new Version 7.4.2, and what new improvements does it have?
Click to expand...
Click to collapse
The update has some valid changes. There are some backdoors in the fota(firmware over the air) itself and also general android security patches that are addressed. Then there is the addition of volte and band 12 that the update fixes.
Now there are also attempts in the update to block the ability to root the device and also block the use of flashing tools that can be used to restore a bricked phone(also modify firmware).
So if root and flashing are desirable to you then the update is bad, there are community modified updates available that preserve these abilities.
So now the choice is up to you, if the update is good or not.
mrmazak said:
The update has some valid changes. There are some backdoors in the fota(firmware over the air) itself and also general android security patches that are addressed. Then there is the addition of volte and band 12 that the update fixes.
Now there are also attempts in the update to block the ability to root the device and also block the use of flashing tools that can be used to restore a bricked phone(also modify firmware).
So if root and flashing are desirable to you then the update is bad, there are community modified updates available that preserve these abilities.
So now the choice is up to you, if the update is good or not.
Click to expand...
Click to collapse
Thanks mrmazak for your quick reply!
So, you think that maybe is better not to update the BLU R1 HD to the latest 7.4.2 firmware?
Problem is that this 7.4.2 file has been already downloaded automatically to my BLU R1 HD phone internal memory, and is only waiting for a manual update confirmation by me or a phone reset...
If this 7.4.2 firmware has been downloaded and is already stored and waiting for an installation, how can I blocked it?
Perhaps you or someone else here, knows where the previously Downloaded Firmware File is stored or hidden, so I could be able to deleted it, before reset my Phone, to avoid the Auto installation?
Please, could you post the link of these "Community Modified Updates" that preserve these abilities of the 7.4.2 Firmware?
Thanks in advance for your help!
ulises.rodriguez said:
Thanks mrmazak for your quick reply!
So, you think that maybe is better not to update the BLU R1 HD to the latest 7.4.2 firmware?
Problem is that this 7.4.2 file has been already downloaded automatically to my BLU R1 HD phone internal memory, and is only waiting for a manual update confirmation by me or a phone reset...
If this 7.4.2 firmware has been downloaded and is already stored and waiting for an installation, how can I blocked it?
Perhaps you or someone else here, knows where the previously Downloaded Firmware File is stored or hidden, so I could be able to deleted it, before reset my Phone, to avoid the Auto installation?
Please, could you post the link of these "Community Modified Updates" that preserve these abilities of the 7.4.2 Firmware?
Thanks in advance for all your help!
Click to expand...
Click to collapse
Find this guide thread useful
https://forum.xda-developers.com/r1-hd/how-to/index-blu-r1-hd-amazon-oem-variants-t3426087
Has root methods, recovery, and also community updates
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
atomclock said:
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
Click to expand...
Click to collapse
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
madbat99 said:
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
Click to expand...
Click to collapse
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
atomclock said:
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
Click to expand...
Click to collapse
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
madbat99 said:
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
Click to expand...
Click to collapse
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
atomclock said:
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
Click to expand...
Click to collapse
That thread literally says install the stock firmware. You have to wait for the entire firmware for the new build to be released. no one is extracting anything from any update package. They are just using the full firmware package in that thread. You just have to wait for the full firmware to be posted on mirrors.lollinet.com the November patch for my G6 play was just posted there yesterday. that's why I asked which version of the G6 you have I will link you to the full firmware.
Or, You just fastboot flash stock, take the update, fastboot TWRP, use TWRP to flash magisk. No data loss, easy peasy.
the only difference in those two ways is taking the update after you flash stock or flashing stock firmware including the update. Either way you have to root your device again.
You can even flash stock with RSDlite using service file.xml instead of flashfile.xml
the file they are flashing with fastboot in that thread is the stock firmware. Just the newer one.
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
GotHeart said:
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
Click to expand...
Click to collapse
The question is can i use different software channel for my G6? Example 1925-6 to 1925-7 to gain particular service carrier signal
Anyone know a secure procedure and a custom recovery compatible?
marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.
Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.
This process worked for me. Moto G7 Plus, International Unlocked version.
This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.
Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.
Please excuse the naive question ...
... but how/where does one find the OTA files, i.e. the links to download them from, in order to keep a rooted device up-to-date?
Capturing the download link via the Android Debug Bridge (ADB) requires the OTA notifications to appear and the respective files to be downloaded, in order to then capture them via adb logcat > OTA.txt. Even if this did not require an unrooted device running an original manufacturer firmware (if we had this, we wouldn't need to go through all the hassle in the first place): it takes a looooong time for the logcat to create a loong file, in which searching for the download link resembles punishment for an amok shooter.
The reason why anybody would need the download links for OTA files is because they are on a custom ROM, have flashed TWRP, rooted their device or similar modifications. In that case, there are no more OTA notifications, i.e. one is not informed of what and when a bugfix or the like becomes available, and if trying to check for updates manually, the phone displays the following error message:
Failed to update software
Your phone's operating system has been modified in an unauthorised way. Try downloading ...
The first thing to note is the arrogance with which manufacturers and telephone operators seem to believe that they had any right to decide what is authorised and what not on our property. Unless somebody with deep pockets or the EU sue them over this impertinence, there is not much we ordinary mortals will be able to do against those oligopolists.
The burning practical question are therefore:
1.) How to get notified of minor updates, bugfixes and security patches like monthly updates when they become available?
2.) How and where to download them?
3.) How to install them?
The large firmware packages are no problem, those one can find at every corner of the street. The problem are the minor bugfixes, security patches and updates between major version numbers and sometimes even apps. Are there any proven methods that work reliably and that do neither require one to study electronics, programming and voodoo, nor force one to re-flash and re-root everything again from square one before every update, plus reinstalling and configuring everything thereafter?
In case the information is necessary, the phone is a SAMSUNG Galaxy Note 9 with Snapdragon SD-845 (SM-N9600), current firmware
BL : N9600ZHS1CSC2, AP : N9600ZHS1CSC2, CP : N9600ZCU1CSAB, CSC : N9600OWO1CSB1
In a nutshell, are there ways to become aware of and apply all updates while keeping the device rooted, or is the procedure more convoluted and repetitive after every update than what Root is worth?
.
Hello,
I am, currently unsuccessfully, searching the web for update files (OTA updates) of LineageOS 17.1 (updates applied via its integrated updater).
The context :
I'm using a Samsung Galaxy Tab S2 SM-T813 (gts210vewifi) tablet that I flashed (customized) with LineageOS 17.1.
It has worked perfectly since then and I regularly update the OS with OTA updates via the updater without any problem (these updates are frequent: once a week!).
The last update I did a few weeks ago also went well, but it was when I came back into the system that I made a mistake: I think I used a boot.img file incompatible with the update I had just performed in order to re-root the tablet.
After having flashed the resulting file to do so and rebooted, I went into a bootloop on the LOS logo.
The considered solution:
Here is my trouble. I'm almost certain to 'resurrect' my tablet by flashing via TWRP one of these OTA updates which, during this process will replace the incompatible boot.img with the one contained in the update, thus restoring the situation and allowing me to reboot into the system to start again on this new basis and to be able to make a report of the potential damages.
So, that's why I'm looking to find where these OTA update files for LOS 17.1 can be accessed and downloaded on the web. (which repository, ...).
If anyone of you has already faced this kind of issue (or not) and know where to find these files, this will help me greatly!
Anyway, thank you already for paying attention to my request for help in this matter.
Rgds
Eric
edevoucoux said:
Hello,
I am, currently unsuccessfully, searching the web for update files (OTA updates) of LineageOS 17.1 (updates applied via its integrated updater).
The context :
I'm using a Samsung Galaxy Tab S2 SM-T813 (gts210vewifi) tablet that I flashed (customized) with LineageOS 17.1.
It has worked perfectly since then and I regularly update the OS with OTA updates via the updater without any problem (these updates are frequent: once a week!).
The last update I did a few weeks ago also went well, but it was when I came back into the system that I made a mistake: I think I used a boot.img file incompatible with the update I had just performed in order to re-root the tablet.
After having flashed the resulting file to do so and rebooted, I went into a bootloop on the LOS logo.
The considered solution:
Here is my trouble. I'm almost certain to 'resurrect' my tablet by flashing via TWRP one of these OTA updates which, during this process will replace the incompatible boot.img with the one contained in the update, thus restoring the situation and allowing me to reboot into the system to start again on this new basis and to be able to make a report of the potential damages.
So, that's why I'm looking to find where these OTA update files for LOS 17.1 can be accessed and downloaded on the web. (which repository, ...).
If anyone of you has already faced this kind of issue (or not) and know where to find these files, this will help me greatly!
Anyway, thank you already for paying attention to my request for help in this matter.
Rgds
Eric
Click to expand...
Click to collapse
The URL to the OTA server which was baked into the ROM will be inside one of the .prop files (build.prop/default.prop/?).
The OTA URL also shows up in logcat when manually triggering an OTA update.
None of this is likely to help you since you are not booting.
Do you have a copy of a lineageos .zip that you flashed from ?
You'll need to contact who is providing your device ROM
Hello bluess57,
First of all, many thanks to answer my topic.
Regarding your two first points, you're right: I have only access to the external SDCard and the internal SDCard except its system files via my PC.
Unfortunatly not: I delete these update files as soon as they are successfully installed (which is another error of mine), but if it was the case, I couldn't access to them since they are downloaded in a system folder (/data/lineageos_updates or something like that: can't remember nor verify). The update process is automatic thanks to the updater: it lets me know that there is an update, letting me click to download it and after to install it, and then it does the job without any intervention.
This LOS is an UNOFFICIAL one, so I can't contact LineageOS team (even if it is possible ?). I've searched and not found a solution on the web, that's why I'm now looking for help on forums.
Thanks again for your answer and if you, or anyone else has any idea to help me thanks very much.
Rgds
Eric