I have a moto E XT1524 with android 5.0.2, after downloading The upgrade that fixes the problem of WIFI, my phone did not turn over ... is dead ... any ideas to resurrect?The upgrade was installed, but did not start anymore
Looking across surely have a phone with "hardbrick" when I connect the device to the PC, in the device manager appears "QHSUSB_BULK" ...
* I read different subjects and no solution for this.... not?
pablo_cba said:
Looking across surely have a phone with "hardbrick" when I connect the device to the PC, in the device manager appears "QHSUSB_BULK" ...
* I read different subjects and no solution for this.... not?
Click to expand...
Click to collapse
Yep, QHSUSB_BULK means that it failed to load the Motorola bootloader. Your device will need to be blank flashed. I don't think the blankflash files for this device are publicly available.
Was your bootloader unlocked? Had you upgraded then downgraded the stock ROM at some point?
squid2 said:
Yep, QHSUSB_BULK means that it failed to load the Motorola bootloader. Your device will need to be blank flashed. I don't think the blankflash files for this device are publicly available.
Was your bootloader unlocked? Had you upgraded then downgraded the stock ROM at some point?
Click to expand...
Click to collapse
Yes!, I upgraded to the 5.1 and later back to 5.0.2, That is what causes the problem? and the bootloader is unlocked...
Sorry for the ignorance, but what a blankflash? Ican expect those files to be filtered?
Thanks!
Did you upgrade your bootloader when you upgraded to 5.1? What could have happened is that the OTA tried to "upgrade" (downgrade) your bootloader. Motorola does not allow bootloader downgrades. It blows a fuse that prevents rollback when you upgrade your bootloader.
Blank flashing is a procedure to install the bootloader on a phone that doesn't have a (working) bootloader. There are Qualcomm tools that can communicate with the boot rom over the "Download Mode" (QHSUSB-DLOAD and QHSUSB-BULK) interfaces. These Qualcomm tools can be used to re flash the bootloader. These tools require special versions of the bootloader images. These images are called the blank flash images. Motorola uses these images in the factory when initially setting up a new device. Public firmware releases don't contain these files. You will need blank flash files for the 5.1 bootloader. Sometimes these files leak.
squid2 said:
Did you upgrade your bootloader when you upgraded to 5.1? What could have happened is that the OTA tried to "upgrade" (downgrade) your bootloader. Motorola does not allow bootloader downgrades. It blows a fuse that prevents rollback when you upgrade your bootloader.
Blank flashing is a procedure to install the bootloader on a phone that doesn't have a (working) bootloader. There are Qualcomm tools that can communicate with the boot rom over the "Download Mode" (QHSUSB-DLOAD and QHSUSB-BULK) interfaces. These Qualcomm tools can be used to re flash the bootloader. These tools require special versions of the bootloader images. These images are called the blank flash images. Motorola uses these images in the factory when initially setting up a new device. Public firmware releases don't contain these files. You will need blank flash files for the 5.1 bootloader. Sometimes these files leak.
Click to expand...
Click to collapse
Thanks for your answer .... then there is no other possibility to wait for a leak of blankfiles ...:crying:
Related
I have bricked my phone. It's stucked in a boot loop.
I had an up-to-date, non-rooted, locked XT1524. Since 3G and 4G didn't work on my country, first I tried flashing the modem and baseband from a retail XT1527 stock ROM. The flashing went OK, but 3G and 4G still didn't work (as happened to pablo_cba in this thread).
Then I turned my common sense off and tried flashing the whole XT1527 ROM. I though that since they were stock ROMs I didn't have any need to root the phone (or install TWRP). And since I was flashing the same version I had, I didn't need to unlock the bootloader either. Wrong! The ROM I flashed was version 5.1 (23.29-15), and my current ROM at the moment was 5.0 (22.50-X). Since I haven't unlocked the bootloader, I can't go back to the retail XT1524 stock ROM published here.
I was able to flash gpt.bin and bootloader.img, but things went south on boot.img. Now the bootloader is stuck with the following error:
Code:
version downgraded for boot
failed to validate boot image
Trying to flash boot.img (or system) fails with error:
Code:
hab check failed for boot
Failed to verify hab image boot
Trying to go back to XT1524 ROM fails with:
Code:
version downgraded for aboot
Trying to unlock the bootloader fails with:
Code:
Enable OEM Unlock
Which is obvious because I haven't enabled it on the phone, but it sucks because I can't boot and enable it.
So, here goes my questions:
- What does the "hab check failed" means? Is there any way to bypass it and finish flashing the XT1527 ROM?
- Is there any way to unlock the bootloader without enabling it first on developer settings?
- Is there anything I can do other than waiting that 5.1 gets rolled to XT1524 phones, and that a stock ROM for it gets leaked?
Thanks a lot for your kindly help!
Ah, I know exactly what happened. The good news is that your device is not bricked. The bad news is that you will need to wait a few weeks for the XT1524 5.1 stock images to be released.
The CID is a one byte Motorola specific value that indicates which region your device is for. Boot and system images are signed by Motorola tools that sign for a specific CID. The bootloaders for Motorola phones are signed with qualcomm tools that do not care about CIDs. As a result, you can flash a bootloader meant for a device with a different CID, but you can't flash a boot or system image for a different CID (while bootloader locked).
Since the bootloader is not CID specific, you were able to flash the new bootloader. The new bootloader blows fuses to increment the security version and prevent rollback. It will not allow you to flash an older boot and system image, since they may contain vulnerabilities. Now, the bootloader won't allow you to flash anything except a new 5.1 ROM signed for your CID.
I'd recommend just waiting a few weeks for the signed official 5.1 images for XT1524 to be released.
If you can't wait and are willing to take your phone apart and void the warranty and solder onto stuff, you can circumvent the Factory Reset Protection feature to unlock your bootloader. I don't recommend doing this, but it can be done. You will need to solder onto test points for the flash (that will be located underneath shielding cans). Writing 0x01 to the last byte of the frp partition will enable bootloader unlocking. Once again, I don't recommend doing this, I'm just stating what is possible.
EDIT: It might be worth a try seeing if Motorola will do something under warranty. The challenge will be to explain your problem in a manner that will not make them consider it to have been damaged by you. I don't know what they will think of your issue.
The exact thing happened to me. I think that the 5.1 firmware will arrive soon to your device. I took to my carrier, and they gave a new one in 2 weeks. I think that Motorola won't help you, as you requested the bootloader code.
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.
As there are different steps and threads all over xda as to how to go about rooting redmi note 3 and then installing a custom ROM, I was wondering if someone could list or direct me to the correct working method to unlock bootloader, root, and install a custom ROM.
Note: I haven't done any tampering with the device, no TWRP, no unlocking bootloader via the hack or official method. I have only installed OTA updates sent to the device via Xiaomi.
Current Device Specifications: (Snapdragon)
Android Version: 6.0.1 MMB29M
MIUI Version: MIUI Global 8.5 | Stable 8.5.7.0(MHOMIED)
Kernel Version: 3.10.84-perf-g9105347
Apply for unlock permission and unlock using miunlock first
apexashwin said:
Apply for unlock permission and unlock using miunlock first
Click to expand...
Click to collapse
Are you suggesting that because the unofficial method is unreliable or because you think I am a beginner?
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Official unlock is recommended to avoid something bad for your device
apexashwin said:
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Click to expand...
Click to collapse
Thanks, I'll go for the official method, then. But I figure that method takes weeks? How much time did it for your phone?
pumpkins12 said:
Official unlock is recommended to avoid something bad for your device
Click to expand...
Click to collapse
Thanks!
apexashwin said:
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Click to expand...
Click to collapse
So, I got the permission from Xiaomi. But, I can't run the Unlock tool on Linux. I tried using VMware Player but the device is still not recognized. Have you had any luck using the official method on Ubuntu?
NealSchwartz said:
So, I got the permission from Xiaomi. But, I can't run the Unlock tool on Linux. I tried using VMware Player but the device is still not recognized. Have you had any luck using the official method on Ubuntu?
Click to expand...
Click to collapse
Forget it if you don't have windows. Xiaomi's unlock tool does not support linux. So you can't go with official method.
And the unofficial method requires a modded fastboot ehich is only available for windows. You can't go with this way too.
So, no way out if you don't have windows.
Also don't think of unlocking it unofficially if you don't have windows because most of the unofficial unlocked devices get locked which again requires the modded fastboot to unlock it.
The last problem, seriously and sadly, doesn't have any other solution
I am unofficially unlocked and few days back i had clean installed ubuntu on my pc but now i am back on windows. Why?? Because my device got locked and i couldn't help but install windows. You have been warned!
deepjyoti30 said:
I am unofficially unlocked and few days back i had clean installed ubuntu on my pc but now i am back on windows. Why?? Because my device got locked and i couldn't help but install windows. You have been warned!
Click to expand...
Click to collapse
Can the device get locked even after installing a custom ROM? What happens when it gets re-locked? ("Soft brick?")
NealSchwartz said:
Can the device get locked even after installing a custom ROM? What happens when it gets re-locked? ("Soft brick?")
Click to expand...
Click to collapse
Yes it can. Actually it hapoens mostly when we flash firmwares which have the unmodified emmc_appsboot.mbn file.
When we unlock unofficially this file is modified.
Thus flashing the firmware locks it.
I would not call it softbrick. When that happens you cannot boot anymore. Only fastboot mode is available and it doesn't allow us to flah any files since the device got locked again.
So we again need to go to edl mode which is only accessible by the modified fastboot available only for windows.
Enjoy linux?
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Chandler_Bing_1995 said:
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Click to expand...
Click to collapse
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
EugenStanis said:
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
Click to expand...
Click to collapse
Thanks a lot, will try that.
Chandler_Bing_1995 said:
Thanks a lot, will try that.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261684661
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
ronclone said:
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
Click to expand...
Click to collapse
are you looking for a way to edit the extracted images?
If so I think you might be able to edit the extracted boot images with a text editor although not sure how reliable my information is for that
catcatjpg said:
are you looking for a way to edit the extracted images?
If so I think you might be able to edit the extracted boot images with a text editor although not sure how reliable my information is for that
Click to expand...
Click to collapse
yes, i would like to edit the image to skip flashing the bootloader. however, OTA images are different than full factory images. they do not have an easy way to modify a "flash-all.bat" file or equivalent. therefore my question, i would like to know if something like this is posible at all.
ronclone said:
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
Click to expand...
Click to collapse
The bootloader has to be unlocked to manually flash a factory image or OTA. Since you have a Verizon device you cannot unlock your bootloader, so attempting to flash any image of any kind will fail. Worse, even if you did have an unlocked device, without a custom recovery you won't be able to flash modified factory images. The stock recovery checks for the presence of Google's signature in the factory image and, if it doesn't find it, will refuse to flash the package.
Modifying flash-all.bat to not flash the bootloader by commenting out the proper line in the batch file will work since you're not modifying the images themselves, but the point is moot anyway since you cannot manually flash factory images due to that pesky bootloader.
That's the issue. However just to clarify, I absolutely can flash OTA images via fastboot even with a locked bootloader, I've done it multiple times. What I can't do is flash full factory images, the ones that need an unlocked bootloader.
I stand corrected regarding the flashing of OTA update files. Flashing full OTA images is conceivably possible, considering that I forgot Google gave device owners that capability. However, this doesn't change the fact you cannot alter Google-supplied ROM images without losing Google's signature on those files. So you won't be able to flash an OTA without also flashing the bootloader.
So is there a specific reason you have to have that particular bootloader?
It's not a bootloader problem per se. It's an Android version problem for me. I wouldn't mind downgrading the bootloader, is just that pixel devices apparently cannot downgrade bootloeader so it must be done with some kind of trickery.
Your on a device with an unlockable bootloader.
You can only flash official ota zips in recovery provided you are not downgrading.
Any attempt to manipulate the OTA zip will break the Google signature, and therefore any attempt to flash it on a locked bootloader will fail.
Tldr: forget about it
shoey63 said:
Your on a device with an unlockable bootloader.
You can only flash official ota zips in recovery provided you are not downgrading.
Any attempt to manipulate the OTA zip will break the Google signature, and therefore any attempt to flash it on a locked bootloader will fail.
Tldr: forget about it
Click to expand...
Click to collapse
yeah i think you're right. unfortunately.