So this appeared today after updating my Lineage OS. I'm not that deep into custom Android stuff so i have no clue what to do regarding this, could anyone direct me please?
To be specific i'm getting this message:
A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches OPM2.171019.029.A1
Click to expand...
Click to collapse
I only have the OK option and after pressing it is seems the phone works normally yet I still want to resolve this.
@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .
Exodusche said:
@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .
Click to expand...
Click to collapse
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?
niirb said:
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?
Click to expand...
Click to collapse
You didn't break anything. This is completely normal since the LineageOS update doesn't update the vendor image.
Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.
Glock45 said:
Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.
Click to expand...
Click to collapse
What are you showing as wrong in the picture? Are you getting error on boot up?
Exodusche said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse
Glock45 said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse
Try this page has all the vendors. You can flash in TWRP just to get a match
Exodusche said:
Try this page has all the vendors. You can flash in TWRP just to get a match
Click to expand...
Click to collapse
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?
Glock45 said:
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?
Click to expand...
Click to collapse
No extraction they are large just download the desired vendor/s and flash.
Exodusche said:
No extraction they are large just download the desired vendor/s and flash.
Click to expand...
Click to collapse
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help
Glock45 said:
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help
Click to expand...
Click to collapse
Oh I get it now yeah the developer didn't change the title to represent the next month's update that's all. General rule of thumb after a week into the month updates should have the corresponding security update.
i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?
i run sideload and get "zip file is corrupt!" this is in linux.
[email protected]:~/Desktop$ adb start-server
[email protected]:~/Desktop$ adb sideload vendor-angler-OPM6.171019.030.B1.img
Total xfer: 0.00x
dr1445 said:
i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?
Click to expand...
Click to collapse
When you're downloading the file in the phone, it should be in /sdcard/download/ folder
But when you're navigating on TWRP, seems you're in /sdcard/twrp/install/download folder. Just go up from TWRP and see if you can see that download folder.
Related
I had a hard time finding this information, so thought I would post a new thread!
After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.
To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.
Step 1 - Collect Needed Files:
Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.
Extract the system.img file so you can flash it later.
Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.
Step 2 - Flash Stock System Image:
This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.
Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:
Code:
adb reboot bootloader
and flash the image
Code:
fastboot erase system
fastboot flash system system.img
At this point your system is stock again (unrooted).
Step 3 - Flash Update Image:
Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.
Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select
I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.
Apply the OTA update file using the following command, replacing the file name with your own:
Code:
adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.
To root your device again, re-install SuperSU and you're good to go.
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
hayzooos said:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
Click to expand...
Click to collapse
Nope, system.img was all that I flashed, verified it worked fine with just that.
So you just have to re-root after right?
JTheAppMerchant said:
So you just have to re-root after right?
Click to expand...
Click to collapse
Correct
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
adb sideload 4458964f84d2e44ecd2c1c31c301d47eec4b080e.signed-shamu-LMY48M-from-LMY48I.4458964f
Click to expand...
Click to collapse
it gets to about 50%, then gives a Error message,
E:Error in /sideload/package.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
Any suggestions?
falconfox said:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
it gets to about 50%, then gives a Error message,
Any suggestions?
Click to expand...
Click to collapse
First try a different USB cable and port.
Thanks for the guide. Does it wipe all the data and files in internal storage?
I did this successfully
torecdude said:
Thanks for the guide. Does it wipe all the data and files in internal storage?
Click to expand...
Click to collapse
I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.
A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.
You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:
fastboot flash boot boot.img
This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:
bitpushr said:
First try a different USB cable and port.
Click to expand...
Click to collapse
I'm having the exact same issue/error. Already tried new USB ports and cables.
falconfox said:
When I do the command:
it gets to about 50%, then gives a Error message, Any suggestions?
Click to expand...
Click to collapse
confused2much said:
I'm having the exact same issue/error. Already tried new USB ports and cables.
Click to expand...
Click to collapse
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I'll try this now, thanks for the response!
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I do not have the text "assert" anywhere in that file....
jase33 said:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
Click to expand...
Click to collapse
Easier to just flash the new system image that gets you to the same place as the OTA.
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!
hayzooos said:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Click to expand...
Click to collapse
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.
Thanks for the walk through though, @bitpushr, I'm sure many can make use of it.
confused2much said:
I do not have the text "assert" anywhere in that file....
Click to expand...
Click to collapse
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.
If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this
krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!
Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk
Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.
krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...
Can you install the full firmware from B162 though?
Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.
Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files
Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.
Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.
I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
golu12c said:
I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
Click to expand...
Click to collapse
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Oh okay. Sorry;_;
Thank you. I will try to flash another rom.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
golu12c said:
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
Click to expand...
Click to collapse
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
strongst said:
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
Click to expand...
Click to collapse
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Heeth21 said:
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Click to expand...
Click to collapse
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
golu12c said:
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
Click to expand...
Click to collapse
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Heeth21 said:
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Click to expand...
Click to collapse
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
golu12c said:
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
Click to expand...
Click to collapse
Try installing Stock ROM from fastboot then.
Heeth21 said:
Try installing Stock ROM from fastboot then.
Click to expand...
Click to collapse
Thank you. This worked. Finally i have a ROM ;_;. I will now try to flash custom rom. Thank you for your help
strongst said:
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
Click to expand...
Click to collapse
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
golu12c said:
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
Click to expand...
Click to collapse
I asked you about your twrp already https://forum.xda-developers.com/mo...sh-custom-rom-noob-help-t3883210/post78527551
Please make sure to read and answer the questions properly
Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient
Fix for screen blinking after pie stable fota update
Vikassir33 said:
Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient
Click to expand...
Click to collapse
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.
subhojit2016 said:
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.
Click to expand...
Click to collapse
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.
nice_guy75 said:
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.
Click to expand...
Click to collapse
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)
RedRobbin said:
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)
Click to expand...
Click to collapse
@RedRobbin
There are no active links,
The blinking problem solved by itself, I don't know what changed, but now no blinking any more
Vikassir33 said:
The blinking problem solved by itself, I don't know what changed, but now no blinking any more
Click to expand...
Click to collapse
Sadly my phone is still giving me this screen blinking issue.
Anything you remember particularly doing before your phone was fixed?
nice_guy75 said:
@RedRobbin
There are no active links,
Click to expand...
Click to collapse
You can download from official website its size around 1.7 gb
RedRobbin said:
You can download from official website its size around 1.7 gb
Click to expand...
Click to collapse
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
Sent from my ASUS_X01BDA using Tapatalk
Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?
nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse
RedRobbin said:
nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse
That I know, I wanted to have Fastboot ROM, which can be flashed via PC.
Click to expand...
Click to collapse
I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.
damole said:
Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?
Click to expand...
Click to collapse
Dear simply visit any Asus service center they will downgrade it to Oreo, I visited today, and one interesting thing is they don't have any stable update for now . Soon a newer fota update will release.
damole said:
I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.
Click to expand...
Click to collapse
First flash twrp then wipe everything except sd card and then flash stock recovery and try again
I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.
Yes it's work i done with 2 max pro m2
damole said:
I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.
Click to expand...
Click to collapse
In case of system update failure the zip file you are trying to flash will be corrupted. (Happened with me many times as i renamed the oreo stock rom to above the build number of the pie update so my phone would treat the downloaded oreo rom to be new .but during the system update after reaching aroung 25 % it displayed an error and the next thing i remember is the zip file getting corrupted) so always keep a backup!
On 25th of april new pie update was released which fixed screen blinking issue.
Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!
Thanks. But where's the guide or howto, that the title says ?
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Any idea to flash the EU rom from India?
felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade
Which magisk did you use please?
Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.
elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.