Related
Full OTA thread is
here.
Full release ODIN file is here.
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
You must be on PH1 to update to 7.0! Anything else will cause the Update to fail!
First download the update:
OTA Link: https://mega.nz/#!UYljzZyR!e0NDzPUCbDdFw-hZL6jS4sdg0Z3iOpBF7B8lYTv7-GU
then download the 2nd OTA file.
OTA 2: https://mega.nz/#!4AEFHYoK!WxyG8Smrsc6uiCBZtU4qOdsNd3Lk7RBWUSNE_rtTWeY Only flash this update if you are on the first OTA file!
Make sure your SD card is not encrypted or you may encounter errors
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named "fota"
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume up + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
14. Let phone start.
15. place 2nd Update.zip on Ext sd card in the fota folder
16. Power off phone
17. Boot into recovery
18. Select "Install update from sdcard"
19. Find the new update and select it.
If you would like to install the official T-Mobile nougat build you can follow instructions here.You must be on beta 2 to install!
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again. Try new SD card if issue persists.
Rollback to PH1:
If you do not want the beta anymore or are having issues with it you can flash back to PH1 by following this guide:
Stock Firmware
or by simply using smart switch.
I just registered. We'll see what happens.
No way to trigger the update once the Registration is complete? I can't seem to find the update.
"After finishing the Galaxy Beta Program registration process, click on the 'Software Update' menu (Setting - Device information - download updates)." <-- these instructions from the Beta app doesn't seem to apply.
It also says the test starts the 11th...
Screenshot
It tells me the maximum number of participants has been reached already!
farfromovin said:
It tells me the maximum number of participants has been reached already!
Click to expand...
Click to collapse
Same here! So disappointing!
S8ntsHaz3 said:
It also says the test starts the 11th...
Click to expand...
Click to collapse
S8ntsHaz3 said:
Screenshot
Click to expand...
Click to collapse
It starts today.
9th of November
Has anyone been able to download the beta yet?
@zimgir124 Have you gotten the update then? Because no one has posted about them getting the actual update. Only being able to register thus far seems to me that they are accepting the registration so they can do their picking and choosing then the 11th the roll out begins?
S8ntsHaz3 said:
@zimgir124 Have you gotten the update then? Because no one has posted about them getting the actual update. Only being able to register thus far seems to me that they are accepting the registration so they can do their picking and choosing then the 11th the roll out begins?
Click to expand...
Click to collapse
That's what I am thinking as well.
S8ntsHaz3 said:
@zimgir124 Have you gotten the update then? Because no one has posted about them getting the actual update. Only being able to register thus far seems to me that they are accepting the registration so they can do their picking and choosing then the 11th the roll out begins?
Click to expand...
Click to collapse
No download yet, however if you look at the date it say 9/11/16 which is November 9th, not September 11th.
It's also been confirmed on several websites for today and the date confirms it.
I'll update when I get the actual update
For those who want to see the FAQ, here's the link:
http://static.samsungmembers.com/betatest/binary/nos/US/faq_sub.html
For clarity, where is this menu: "Setting – Device information – download updates"?
It doesn't match the Settings > System > System Updates, where I would expect to see system updates.
A_N_D_R_E said:
For clarity, where is this menu: "Setting – Device information – download updates"?
It doesn't match the Settings > System > System Updates, where I would expect to see system updates.
Click to expand...
Click to collapse
It should come as just a regular OTA, so for me it is Settings > System Updates.
It might take a couple hours for the download to start
Is there any way you can capture the update when you get it? Didn't get in to the beta but I'd like to try it
Sent from my SM-G935V using Tapatalk
I hope they open up more slots.
kingoanklebreakn said:
Is there any way you can capture the update when you get it? Didn't get in to the beta but I'd like to try it
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I have no idea how to capture updates, so if anyone knows how please tell me and i"ll do it.
gunnyman said:
I hope they open up more slots.
Click to expand...
Click to collapse
Exactly... I downloaded the official app and attempted to register within maybe 3 hours of it being available and the beta "program" is full of participants!?! Samsung should allow as many people who want to beta test like how Google and Apple both do it...
Anyone seen anything?
Hi, sorry in advance for my bad English! as we all know, it is now difficult to get the bootloader unlocked on our new huawei, and we can no longer take advantage of features, like easily installing new roms, latest update.... I would like to build with you in this topic, a new guide to easily install the new updates.
Based on this method that works!
https://forum.xda-developers.com/hu...ide-how-to-update-to-emui-9-c432-l09-t3883557
In your opinions, by downloading a new update files with FirmwareFinder (see video),
https://www.youtube.com/watch?v=73AUzLQvXkw&feature=youtu.be
would it be possible to edit an archive to install it with flashDrive OTG ? Maybe by editing the names of some files ? Thoses files look really similar than others used in the methode link above.
Maybe those files are ready to import in Hisuite for a manual update? ?
Feel free to discuss all this here, and little by little we will build this new guide together Thx all!!! ?
Nyzoka said:
Hi, sorry in advance for my bad English! as we all know, it is now difficult to get the bootloader unlocked on our new huawei, and we can no longer take advantage of features, like easily installing new roms, latest update.... I would like to build with you in this topic, a new guide to easily install the new updates.
Based on this method that works!
https://forum.xda-developers.com/hu...ide-how-to-update-to-emui-9-c432-l09-t3883557
In your opinions, by downloading a new update files with FirmwareFinder (see video),
&feature=youtu.be
would it be possible to edit an archive to install it with flashDrive OTG ? Maybe by editing the names of some files ? Thoses files look really similar than others used in the methode link above.
Maybe those files are ready to import in Hisuite for a manual update? ?
Feel free to discuss all this here, and little by little we will build this new guide together Thx all!!! ?
Click to expand...
Click to collapse
I have been trying tirelessly to import and update with hisuite.
I truly believe Huawei has implemented some sort of signing technique similar to ios.
I would like to try the otg update as there is a way to install a software update from an SD card via the secret menu. However I do not have an otg for USB c at the moment.
If you download the firmware update and then extract the zip file to the root of the SD card. And try an update that way. Then perhaps it would work.
I have tried using VPNs to bounce me all over the world to try and trigger an update and nothing happens. I am stumped at this point and I refuse to pay somebody to unlock the bootloader. I feel we should be able to unlock our devices at our own free will as we do own them. However it seems Huawei is taking after apple in this regard.
CreepingMunster said:
I have been trying tirelessly to import and update with hisuite.
I truly believe Huawei has implemented some sort of signing technique similar to ios.
I would like to try the otg update as there is a way to install a software update from an SD card via the secret menu. However I do not have an otg for USB c at the moment.
If you download the firmware update and then extract the zip file to the root of the SD card. And try an update that way. Then perhaps it would work.
I have tried using VPNs to bounce me all over the world to try and trigger an update and nothing happens. I am stumped at this point and I refuse to pay somebody to unlock the bootloader. I feel we should be able to unlock our devices at our own free will as we do own them. However it seems Huawei is taking after apple in this regard.
Click to expand...
Click to collapse
Yes, true... :/ it's absolutly to a wrong way than the android world.
I'll try different ways with otg and update files. You thinks a have to extract zips files on my flashdrive? Update.zip and Update_full_Clt-29...zip? ? And launch the update via dialer code?
Nyzoka said:
Yes, true... :/ it's absolutly to a wrong way than the android world.
I'll try different ways with otg and update files. You thinks a have to extract zips files on my flashdrive? Update.zip and Update_full_Clt-29...zip? ? And launch the update via dialer code?
Click to expand...
Click to collapse
Yes. You want to actually. Extract update.zip. and copy dload file to root of SD card. Connect with otg and launch from dialer.
CreepingMunster said:
Yes. You want to actually. Extract update.zip. and copy dload file to root of SD card. Connect with otg and launch from dialer.
Click to expand...
Click to collapse
? I have no dload file in firmware finder archive for 9.0.0.195. Can u give me more detail?
Just in case, If i brick my phone, existing a method to unbrick?
We'r on a good way!
Edit: Oh we'r talking about files from the other topic?! For this one, it's ok with the dload folder this 163 is installed. But do you think it's possible to use new files from FirmwareFinder to install with the same method?
Nyzoka said:
? I have no dload file in firmware finder archive for 9.0.0.195. Can u give me more detail?
Just in case, If i brick my phone, existing a method to unbrick?
We'r on a good way!
Edit: Oh we'r talking about files from the other topic?! For this one, it's ok with the dload folder this 163 is installed. But do you think it's possible to use new files from FirmwareFinder to install with the same method?
Click to expand...
Click to collapse
You can give it a shot. Not sure if it will work. If the firmware shows as approved for install I don't see why it wouldn't work.
Ok, no result for the moment.. :/ maybe files are nothing organized correctly for this method. ? Maybe need to be renamed. I don't know.. But i'm sure these files can be used for this flash ? Wait and see. Do not not hesitate to give news if you find something!
Nyzoka said:
Ok, no result for the moment.. :/ maybe files are nothing organized correctly for this method. ? Maybe need to be renamed. I don't know.. But i'm sure these files can be used for this flash ? Wait and see. Do not not hesitate to give news if you find something!
Click to expand...
Click to collapse
Has to be done with an exFAT formatted usb. I will update you with a result and a guide if it works.
CreepingMunster said:
Has to be done with an exFAT formatted usb. I will update you with a result and a guide if it works.
Click to expand...
Click to collapse
Good luck CreepingMunster ! ?
Nyzoka said:
Good luck CreepingMunster ! ?
Click to expand...
Click to collapse
Firmware finder works. Do the e-recovery method. you want to select the .178 build. when you go to check firmware access, hold your finger on "Check firmware access" button and it will change to approved.
I changed my connection, and hot spot dns on windows, my phone is connected to the Hotspot, but in FF I'v no 178 for C432 ?... Trying with 195 and impossible to success the availibility button... It's not working... Hummm, what is your previous version? 8.1 or 9? I think the erecovery methode not work in 9... ARRGG huaweiii ? i think i'll buy an iPhone ??
Nyzoka said:
I changed my connection, and hot spot dns on windows, my phone is connected to the Hotspot, but in FF I'v no 178 for C432 ?... Trying with 195 and impossible to success the availibility button... It's not working... Hummm, what is your previous version? 8.1 or 9? I think the erecovery methode not work in 9... ARRGG huaweiii ? i think i'll buy an iPhone ?
---------- Post added at 03:08 AM ---------- Previous post was at 03:08 AM ----------
CreepingMunster said:
Nyzoka said:
I changed my connection, and hot spot dns on windows, my phone is connected to the Hotspot, but in FF I'v no 178 for C432 ?... Trying with 195 and impossible to success the availibility button... It's not working... Hummm, what is your previous version? 8.1 or 9? I think the erecovery methode not work in 9... ARRGG huaweiii ? i think i'll buy an iPhone ?
Click to expand...
Click to collapse
Are you using CLT-L29? I am using CLT-L04
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CreepingMunster said:
Firmware finder works. Do the e-recovery method. you want to select the .178 build. when you go to check firmware access, hold your finger on "Check firmware access" button and it will change to approved.
Click to expand...
Click to collapse
Hi,
would this method work for changing region/rebranding? I want to convert a CLT-AL00 to a CLT-L29.
Cheers
mcklane said:
Hi,
would this method work for changing region/rebranding? I want to convert a CLT-AL00 to a CLT-L29.
Cheers
Click to expand...
Click to collapse
No. You need an unlocked bootloader for that.
Hello all,
I came across this link which describes how to manually update the v20 from the project menu using *#*#2846579#*#* Google "download-honor-view-20-9-0-1-115-pie-firmware-update-russia-pct-l29" for the page. xda wont let me paste the link.
You need an OTG drive and the appropriate firmware file unzipped in a folder named dload (use firmware finder app to find firmware and check access to install).
I havent tried due to a lack of an OTG cable, but its almost April and im still on the January update UK support say .... just wait
Be interested if anyone is brave enough to try
Regards
Terry
terrym2002uk said:
Hello all,
I came across this link which describes how to manually update the v20 from the project menu using *#*#2846579#*#* Google "download-honor-view-20-9-0-1-115-pie-firmware-update-russia-pct-l29" for the page. xda wont let me paste the link.
You need an OTG drive and the appropriate firmware file unzipped in a folder named dload (use firmware finder app to find firmware and check access to install).
I havent tried due to a lack of an OTG cable, but its almost April and im still on the January update UK support say .... just wait
Be interested if anyone is brave enough to try
Regards
Terry
Click to expand...
Click to collapse
I will try but not with a Russian Firmware ?
mchtt said:
I will try but not with a Russian Firmware
Click to expand...
Click to collapse
Good choice comrade.
It's been tried but seems that process is okay for EMUI but using on MAGIC never seems to work. Must be away using that firmware downloaded. Just need to find it.
Please go through this:- How to UPDATE HONOR VIEW 20 MAUALLY Written by me, thanks
I've used this method to update to 9.0.1.140 and it worked fine, the "ru hw" version is the same as the European version and has English as the default language. One thing to be careful about though, is that this method will also factory reset the device, so make sure you have a backup before you try.
But Playstore not verified with Russian Firmware
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
ewingr said:
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
Click to expand...
Click to collapse
Rooting is 'full', just that technology (Android 9/10) is changing.
For AdAway app you must enable Systemless hosts (option/module in Magisk Manager), for modules Magisc automatically handles symlinking to the read-only System
So, even from root explorer (sugested MiXPlorer), you see as if AdAway wrote directly to the file system/etc/hosts, or that BusyBox tools are applied directly to system/xbin
Since EMUI 8, Huawei replaced Boot with Ramdisk, and since EMUI 9.1 Ramdisk is also read-only, hence Magisk must patch to Recovery instead
Because of that, you cannot have TWRP if you go for root (don't consider an alternative solution to flash TWRP over erecovery). But formally speaking, TWRP is not part of root (on the old systems, you could have TWRP without root, vice versa, or both). Even with TWRP, TWRP could not change read-only System, and it cannot see dynamical linking active only when system is running (Magisk running). Plus, because of new encryption since EMUI 8, TWRP cannot handle Internal storage (don't consider alternative solution to completely wipe Internal storage and format it without encryption)
All together, from system, systemless works fully seemlessly (as 'full' root). Just you don't use TWRP
To root:
- Install Huawei UpdateExtractor (PC), download update.zip for your 9.1.0.252 c432 from FirmwareFinder, unzip and extract Recovery_Ramdisk.img
- Copy Recovery_Ramdisk.img to the phone, install Magisk Manager, choose Install and then Patch a file, check all three options Preserve AVB, Preserve encryption, Recovery file
- Copy patched_boot.img (rename to patched_recovery.img or so) to PC and flash from Fastboot to Recovery (similar like flashing TWRP) - of course, Bootloader must be unlocked (you have code) and OEM/FRP must be unlocked
- You must boot to system through recovery (because Magisk was patched to recovery), if Magisk Manager shows rooted, you are done
To unroot:
- In case of bootloop or anything: just flash stock Recovery_Ramdisk.img back to Recovery, and you are back to stock
- Regular unrooting: take Uninstall from Magisk (and later, optionally, flash stock recovery_ramdisk.img)
- In case of OTA: unroot (regularly, as above), accept OTA, root again
Btw, you could update your sig now (no more EMUI 5)
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
ewingr said:
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
Click to expand...
Click to collapse
Font size can be changed in Settings /Display
I never changed system fonts but there are Magisk modules to do so, search by Google, eg:
https://forum.xda-developers.com/apps/magisk/avfonts-march-6-t3760827
https://forum.xda-developers.com/apps/magisk/module-midnightcore-one-midnight-modules-t3762758
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
ewingr said:
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
Click to expand...
Click to collapse
Look for MHA-LGRP2-OVS - see screenshots.
You can also find through Web:
https://pro-teammt.ru/firmware-database/?firmware_model=MHA-LGRP2-OVS
Btw, there are several b252 packages there, all the same size (and probably all ok) but I was told that package number #279403
is the one that is distributed by OTA
Thanks.
I saw the MHA-LGRP2-OVS ones, but I thought I needed to find one with identical name to the one I'm on.
This stuff doesn't make much sense...at least not logical. Only experience and/or help makes it possible to get it done.
Appreciate y our help.
Well, I don't know what's going on. I downloaded the FW from the link you provided, as well as from FF on the phone.
The one from the phone, once I transferred it to the PC, wouldn't extract anything from the zip.
The one from the link extracted, but when I loaded the Update.app into Update EXtractor, I got this error:
So, I then downloaded a different version from the web site (282444), and got this in Update Extracter:
Maybe it's warning me to not root:silly:
I am going through the thread about the extracter tool now to see if I find anything helpful. First blush looks like I'd need to make a profile file that is outside the limits of my knowledge. We'll see.
I found a post saying:
Try with crc check off (in settings) for extracting
Click to expand...
Click to collapse
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
ewingr said:
I found a post saying:
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
Click to expand...
Click to collapse
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
zgfg said:
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
Click to expand...
Click to collapse
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
WARNING:
If your phone runs Android 8 or later with latest security patch - then this service won't work!
Click to expand...
Click to collapse
I'm on Android 9 with security patch 3.
ewingr said:
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
I'm on Android 9 with security patch 3.
Click to expand...
Click to collapse
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
zgfg said:
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
Click to expand...
Click to collapse
OMG, yes, you have. BUT the site that provided the method to do it says it won't, per the quote I put in my post. I'm inclined to believe you, you have been a very good source and patient. But, I was wondering why would they say it won't work? That is their exact words, about their tool.
That being said, I guess as that I had the code before upgrading to 9, then just following the fastboot commands with that code will work, and in fact doesn't even use their tool. . So, I'll continue with that then. The information out here can sure be confusing.
Thanks...
[EDIT]
I figured that likely it would be the ramdisk.img file, and through Google search I found a thread that verified that. So, I'm continuing on.
Thanks...
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
56_kruiser said:
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
Click to expand...
Click to collapse
So, are you the same as previously, @ewingr?
If so, have you successfully unlocked Bootloader with that old code
OpenKirin instruct to patch Ramdisk and that was correct for EMUI 8.
(If) yu are on EMUI 9.1, hence you need to patch and flash Recovery Ramdisk
When patching from Magisk Manager (MM), you have to check all three options: Preserve AVB 2.0 DM-Verity, Preserve Force Encryption and Recovery Mode.
Does MM report any error while flashing or success/ok?
You can rename patched_boot.img to like patched_recovery.img, doesn't matter, but you must flash it to Recovery (like flashing TWRP to Recovery).
Right after flashing, boot by key combo to that patched Recovery (like booting to TWRP by key combo, after flashing TWRP).
Of course, you will not flash/use TWRP here
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
fastboot flash ramdisk Patched_RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
I got this response:
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.721s]
writing 'ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.757s
Click to expand...
Click to collapse
56_kruiser said:
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
I got this response:
Click to expand...
Click to collapse
Again, if you are on EMUI 9.1, forget Open Kirin instructions (for EMUI 8).
You must patch Recovery Ramdisk and flash to Recovery Ramdisk, so:
fastboot flash recovery_ramdisk Patched_RECOVERY_RAMDIS.img
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
56_kruiser said:
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
Click to expand...
Click to collapse
Magisk by default means you have root. You can install and disable modules in Magisk Manager, but you cannot disable root - for that you must Unistall Magisk (an option in Magisk Manager).
In MM you have a tab/menu showing all apps that were granted root - you can suspend or even revoke to some
Check in Settings/About, does it show you have b252 or b252 Patch03. I think that it thinks you are on b252 without Patch03, and it wants to install that patch.
But I don't know would you loose Magisk if you accept (or even get bootloop), so better disable authomatic OTA updates for now.
Believe me, similar 'Important' patches were receiving users (starting at the same time) with various Huawei phones running EMUI 9.1, discussing on XDA what it was, but there was never an answer, nobody detected any change for something better or worse.
So you don't loose anything if About showing b252 without Patch03
To boot to Magisk you must boot with Vol+ pressed - with USB discinnected.
If connected by USB to charger or PC, booting with Vol+ pressed will boot to eRecovery.
Normal booting (without Vol+ pressed) boots to the system (Android), but with Magisk disabled (MM will say that Magisk is not installed), so no root.
Reboot again with Vol+ and you are again rooted
If it ever comes an OTA for higher than b252, you will have to Uninstall Magisk from Magisk Manager and then accept OTA (and root by yhe same procedure one more time, with recovery_ramdisk.img from the new firmware).
Anomoly with root...
Root is working, albeit with anomalies.
If I boot w/o going through the recovery/Magisk, the phone boots up w/o root, and all works fine. When I go through recovery/Magisk, it comes up rooted, but with the following untenable anomalies: Dialer/Phone does not load; Contacts are not available; As result calls I receive do not show who is calling, and I cannot make calls out.
Given that changing fonts do not give me the fix I was chasing (see this thread), I may, unroot. But given that I can boot up w/o root and it works fine, I'll hold off un-rooting for a bit.
We all know that users who own AT6T devices are not able to receive OTA updates if they are not part of the AT&T network or are outside the US.
Can someone who uses AT&T capture OTA update url link for Android 11, so that we who are unable to receive OTA updates can manually upgrade our devices ?
Also you can use this "OTA Link" app for capture url,
Edit: to working app properly you need first Clear Google Play Services
I think it would be very useful for the whole community who does not use AT&T services.
Im in the process of doing that. will get a sim from At&t in a few days and follow the guide you provide.
Oh man... eagerly waiting for this...still stuck on April 2020 update
I will send my gratitude beforehand as I am also waiting
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
PesSarmiento said:
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
Click to expand...
Click to collapse
Which of the ways to get the link are you using?
PesSarmiento said:
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
Click to expand...
Click to collapse
I hope no update is installed, so as not to download the update, Turn off wifi or via ADB you can run this command
Code:
adb shell pm disable-user com.lge.lgdmsclientatt
to disable apk for update, also you can stop connection over change DNS to private set for dns anything like "blabla.com" and internet connection will be stopped or go to go to ‘Settings’ → ‘System’ → ‘Developer options’ and turn off the ‘Automatic system updates’ toggle.".
maybe you are not runed logchat before stated uta updating.
if you using apk OTA link app, must be granted permissions via adb.
I'm not sure if it's possible to delete the OTA ZIP that is already in the process of updating, if you can factory reset the phone then remove the sim card, after deleting it will have to download again however prepare according to the old method of capturing the link again.
I did grant permision to the app with adb, I followed the insructions on the guide, I dont know if this is android 11 update or what, doesn't event mention on the update. I turn off wifi to prevent from donwloading the update, the I turn on the wifi and will download automatically I try the ota lext logcat several times after download resume but again I can't find the download adress using all those keywords. I'm going to try again this evening, and yes the automatic system updtaes is off
PesSarmiento said:
I did grant permision to the app with adb, I followed the insructions on the guide, I dont know if this is android 11 update or what, doesn't event mention on the update. I turn off wifi to prevent from donwloading the update, the I turn on the wifi and will download automatically I try the ota lext logcat several times after download resume but again I can't find the download adress using all those keywords. I'm going to try again this evening, and yes the automatic system updtaes is off
Click to expand...
Click to collapse
also you can try with Traffic with Wireshark on the Same Network
I'm sorry. I failed to get that ota link. And that app doesn't work. I try multiple times with the app, even uninstall and installed again granting permissions and nothing. Im on Android 11 already
PesSarmiento said:
I'm sorry. I failed to get that ota link. And that app doesn't work. I try multiple times with the app, even uninstall and installed again granting permissions and nothing. Im on Android 11 already
Click to expand...
Click to collapse
Thank you for your effort.
Maybe these methods no longer work on newer android systems, then the only thing left is to listen to the connection via computer, when I have the will I will study and write a tutorial.
One question, can you ask AT&T support can you get OTA update in roaming ?
Hey all, on Cricket here. Borrowed my friends AT&T sim today and got the notification to update almost instantly. Will attempt to capture the file later today, will post an update.
davolesh said:
Hey all, on Cricket here. Borrowed my friends AT&T sim today and got the notification to update almost instantly. Will attempt to capture the file later today, will post an update.
Click to expand...
Click to collapse
Thanks, a security update came out 2 days ago
I'm not sure how much the described method really works for android 11 because the previous try od user is not successful, study a little how to catch traffic via computer, with Fidder, Wireshark and similar tools
Tried all methods, the download just started automatically when it connected to wifi and is now completed. I tired the app, wireshark, bug report methods and all failed. The update is NOT yet installed, just downloaded. Any suggestions?
davolesh said:
Tried all methods, the download just started automatically when it connected to wifi and is now completed. I tired the app, wireshark, bug report methods and all failed. The update is NOT yet installed, just downloaded. Any suggestions?
Click to expand...
Click to collapse
Unfortunately I have no suggestions, the .zip file cannot be accessed directly without root permissions if ota downloaded.
Thank you for your effort
Don't know how these updates work on these newer devices or what kind of system AT&T use, but normally LG OTA updates aren't zips. Previously if any bigger update, the path was /data/fota/dlpkgfile and if smaller then same on /cache. Updates were possible flashable using LGUP - or maybe if put to the certain path to the /sdcard having .UP as extension and using Hidden Menu's FOTA Test...
Used SandroProxy to catch the urls... server's address was h t t p://dl01.gdms.lge.com:5005/ back then...
Any progress made?
FC06 said:
Any progress made?
Click to expand...
Click to collapse
No, must be captured via computer
Is there anyone here who is on Android 10 and has the ability to update to android 11 or any future update from ATT?
Waiting for the updare, too. If it's possible to update with a ATT sim in other countries, I would buy one via Amazon or something...