Develop Bugs

[Q] Updating to Yakju - issue "cannot load file"

Hi everyone,
I recently got the Galaxy Nexus through Telus in Canada. Since its running 4.0.1 with yakjuwx, i decided to flash over and have yakju to get the updates from Google instead. Im using a mac, fyi.
I'm sorry if im not in the right forum but i didnt know where to go.
I need help now. I installed SDK and Fastboot-Mac. I've downloaded what I needed from http://code.google.com/android/nexus/images.html. I dont quite know my way around terminal and stuff so I followed the instructions to set up fastboot and sdk (http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx). I couldnt find the bash_profile, so I used nano ~/.bash_profile to update the path.
Anyways, once I had set up fastboot and sdk, I followed the following threads: http://forum.xda-developers.com/showthread.php?p=20514362, http://forum.xda-developers.com/showpost.php?p=20443533&postcount=2, http://forum.xda-developers.com/showpost.php?p=20269587&postcount=4. I have everything done except for the flashing. I can see my phone in terminal and I unlocked it.
I am at this part:
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
However, nothing is working. I keep getting error: cannot load 'bootloader-maguro-primekk15.img'. Ive tried with placing the images at different spots on my mac, including the /tools folder in SDK and no luck.
Please, I need help

Can you actually perform this on a Mac? I didn't see any mention of this reading up and I borrowed a windows box to do mine. If you can do it on a Mac... the files should all be placed in the same folder where fastboot is.
When you attach the phone, can you navigate to platform-tools and ./fastboot devices and see your device listed?

Thierrys-MacBook-Pro:~ Thierry$ cd /Users/Thierry/Desktop/android-sdk-macosx/platform-tools
Thierrys-MacBook-Prolatform-tools Thierry$ fastboot devices
01498FC01300F01E fastboot
I can see my device and yes it can be done on a mac.
edit: found my mistake - im an idiot. Although I had forgotten to copy boot.img, recovery.img and system.img so when i updated, it notified me in terminal that those files could not be found. however, it wrote them
Code:
sending 'boot' (4074 KB)...
OKAY [ 0.683s]
writing 'boot'...
OKAY [ 0.346s]
sending 'recovery' (4406 KB)...
OKAY [ 0.633s]
writing 'recovery'...
OKAY [ 0.667s]
sending 'system' (317594 KB)...
OKAY [ 35.510s]
writing 'system'...
OKAY [ 35.912s]
I dont need to do anything else here correct?

That looks good, but I think it would've been advised that you reboot bootloader a couple times during that process... unless you skipped the "optional" parts in the guides.
but from what you've shown, it looks like its working just fine.
Let me know how it finishes out. This'll be good to know if I ever need to do it again, so I don't have to use a Windows box.

I did do a few reboot bootloader, between flashing the bootloader, radio and the update.
Flashing on the mac was real easy. As soon as i realized what the issue was, everything was smooth. I suppose it'll take a few days to see if i did something wrong.

Interesting that you have yakjuxw. I have a telus Gnex also and am on yakjuux

I must've had the same one as yours. So many different ones I probably got confused on which one I actually had.

Teedat said:
I did do a few reboot bootloader, between flashing the bootloader, radio and the update.
Flashing on the mac was real easy. As soon as i realized what the issue was, everything was smooth. I suppose it'll take a few days to see if i did something wrong.
Click to expand...
Click to collapse
It you rebooted just fine and it started up the chance that you messed anything up is pretty low.

I desperately need a guide to flash ROMs and HBOOT Versions

Hi,
i am completely new to flashing ROMs like Android Revolution HD and on the One X. I am well versed and hacked all sorts of stuff on plenty other android devices but this process for the One X proves a bit complicated for me.
Here is my problem: I wish to flash Android Revolution HD which requires me to flash the appropriate firmware package.
So i downloaded SDK Tool from "developer.android.com/sdk/index.html", then i copied 'cmd.exe' and firmware version '3.14.707.24' into the 'platform tools' folder. I followed the guide from flow-wolf.net. But when i get to the part of flashing the firmware, this is what i get:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
The system cannot find message text for message number 0x2334 in the message fil
e for Application.
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>fastboot flash zip 3.14.707.24.zip
sending 'zip' (12875 KB)...
OKAY [ 1.981s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.200s
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>fastboot flash zip 3.14.707.24.zip
sending 'zip' (12875 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>
I really do not know what i am doing wrong here. Anyways, i do not even understand whats going on and how i should flash a firmware. It would be very nice of the folks here if you can guide me.Thanks so very much
Cheers,
K

You need to rename the .zip to firmware.zip
Did you download the correct firmware from here and did you read the OP completely
http://forum.xda-developers.com/showthread.php?t=1957376
And you need to put the bootloader in the RUU mode before flashing the firmware
Fastboot oem rebootRUU

Hi thanks for the reply.i did download the correct firmware.anyways, i seemed to figure it out a few hours before your reply.but you kinda made me understand how the entire htc one x hackery works.now my phone goes as fast and smooth as my s3 with the custom rom.thanks alot for your time!
Sent from my EndeavorU using xda premium

kawshigan said:
Hi thanks for the reply.i did download the correct firmware.anyways, i seemed to figure it out a few hours before your reply.but you kinda made me understand how the entire htc one x hackery works.now my phone goes as fast and smooth as my s3 with the custom rom.thanks alot for your time!
Sent from my EndeavorU using xda premium
Click to expand...
Click to collapse
Ah oke, no problem mate. Glad you got it sorted
CASE CLOSED !
Sent from my GT-P5110 using xda app-developers app

[TUT][Win/Mac/Linux] Back to stock using RUU and fastboot

I had to restore back to stock and I do not use windows. I was looking for threads but all of them needed windows. So, I am making a tutorial on how to go back to stock on Win/Mac/Linux.
Note - I used my netbook which runs arch linux to complete these steps. I have not tried any other os but it should work.
Requirements ​On all systems -
Usb drivers (HTC sync provides them on windows. They are preinstalled on linux/mac)
Fastboot
RUU for your device
On linux/mac you need wine. Get wine from your distro on linux and for mac you need to build it manually. Afaik there a few programmes to provide prebuilt wine on mac.
If you don't have wine, get the rom.zip for your RUU from someone here or a windows machine.
Acknowledgements​ckpv5 for his tutorial (http://forum.xda-developers.com/showthread.php?t=1705484)
mirGantrophy for his tutorial on how to do it on linux (http://forum.xda-developers.com/showthread.php?t=1974272) Check his thread for pics and screenies.
eLukas for teaching me how to extract rom.zip (http://forum.xda-developers.com/showthread.php?t=1729898)
CafeKampuchia for his tutorial (http://forum.xda-developers.com/showthread.php?t=1706070)
Some other forum(forgot its name) for telling me about a command (fastboot oem rebootRUU)
Let's start​
Download the ruu for your device from ruu.androidfiles.org (gsm one v = primoU, cdma = primoC and dual sim = primoDS)
Extract the rom.zip
Linux - Use elukas' script
Mac - get the rom.zip from somewhere. Sorry.
Windows - Run the ruu. Search for temporary folder and copy the rom.zip to somewhere safe.
Extract the rom.zip. We need to flash recovery and kernel(boot_signed.img) from this folder.
Reboot phone to bootloader. Connect it to your system. Make sure fastboot detects the phone.
For recovery
Code:
sudo fastboot flash recovery recovery_signed.img
For kernel
Code:
sudo fastboot flash boot boot_signed.img
Code:
sudo fastboot erase cache
Now we flash the Ruu
Code:
sudo fastboot oem rebootRUU
You may get an error related to hboot. Flash the zip again.
I hope it works for you. If you're on windows, you don't need to type sudo before fastboot.

This worked well, did it in litterally 4 minutes :good:

Is there anything I should add to it?

Umm getting the Ruu was a bit confusing, but i figured it out. Primo....

Thanks, I'll add that the gsm version is primou ,cdma is primoc and primods is dual sim.

arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
where do i get mac zip?

vialsofliquid said:
where do i get mac zip?
Click to expand...
Click to collapse
The zip varies from device to device, so you need to download the RUU for your device and then extract the rom.zip from it.

Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply

-Rif- said:
Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply
Click to expand...
Click to collapse
Yeah, the RUU contains everything you need. Follow the guide and you'll be fine.

arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
I get this is old but, after
fastboot oem rebootRUU
You should
fastboot flash zip rom.zip
Thanks for posting this guide
Good work.
!#quote my post if you want to get my attention more quickly

HTC One S 1.5Ghz Soft Bricked to!
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it

HTC-One-User said:
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it
Click to expand...
Click to collapse
I gave up on RUU files all together and tried different ROMs til I found one that worked. Also managed to fix the SD card error with this guide: http://forum.xda-developers.com/showthread.php?t=2086156

[Q&A] [OTA ZIP+TWRP] HTC Desire Eye 2.19.401.1 STOCK Europe 5.0.2 Lollipop

Q&A for [OTA ZIP+TWRP] HTC Desire Eye 2.19.401.1 STOCK Europe 5.0.2 Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [OTA ZIP+TWRP] HTC Desire Eye 2.19.401.1 STOCK Europe 5.0.2 Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Help please
i got this message when i used fastboot
C:\Users\Anders\AppData\Local\Android\android-sdk\platform-tools>fastboot flash
recovery recovery.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14958 KB)...
OKAY [ 1.375s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.942s
is it right or is it suposed to say something else ???

yamix112 said:
i got this message when i used fastboot
C:\Users\Anders\AppData\Local\Android\android-sdk\platform-tools>fastboot flash
recovery recovery.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14958 KB)...
OKAY [ 1.375s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.942s
is it right or is it suposed to say something else ???
Click to expand...
Click to collapse
To flash partitions via fastboot you've got to have bootloader unlocked.

thanks
condi said:
To flash partitions via fastboot you've got to have bootloader unlocked.
Click to expand...
Click to collapse
ok i will unlock it now and then try again thank you for the tip

Thanks
I just don't understand what does flashing firmware.zip do? What if I just restored system via TWRP?

Thanks again
Looks like it is gonna work It is currently optimizing my apps "maybe due to switch from Dalvich to ART"

THANK YOU SO MUCH EVERYTHING IS NOW WORKING PERFECTLY,
Sent from my HTC Desire EYE using XDA Free mobile app

modaifallah said:
I just don't understand what does flashing firmware.zip do? What if I just restored system via TWRP?
Click to expand...
Click to collapse
if you will not update firmware with radio, then it could not work 100% properly - network signal, battery, wifi, sound etc etc.
its always recommended to flash main firmware + proper radio.

Add this to your post
condi said:
if you will not update firmware with radio, then it could not work 100% properly - network signal, battery, wifi, sound etc etc.
its always recommended to flash main firmware + proper radio.
Click to expand...
Click to collapse
I experienced this error:
flashing firmware with adb/fastboot
sending 'zip' (51931 KB)...
OKAY [ 2.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.427s
and looks like someone is doing the same. I googled and I found that I have to relock my bootloader first using
"fastboot oem lock" then use your command. Thanks again.

modaifallah said:
I googled and I found that I have to relock my bootloader first using
"fastboot oem lock" then use your command. Thanks again.
Click to expand...
Click to collapse
Thanks friend, info added !
br
condi

I have downloaded the OTA file from the settings menu of my phone. But my phone is on stock rom and TWRP 2.8.4.0. Is there a way that I can still update to lollipop 5.0 using TWRP and the downloaded OTA file? Whenever I click the install now option it will boot up into TWRP, then when I click Install and point to the zip file downloaded by the OTA, there are multiple errors.
Please let me know what are the best options for me to update since I do not have an access to a computer. So the only way is to update through my phone
EDIT: I found the downloaded OTA location. It's in SD CARD download folder

You'll have to restore a lollipop nandroid for your variant. You can't use TWRP to flash the ota because you need stock recovery.
Sent from my HTC Desire EYE using XDA Free mobile app

How to unmodified /system partition?
i've done RELOCKED bootloader and UNLOCKED it(used WinDroid Universal Android Toolkit v2.4) and nothing changed, just i got like a new phone, all internal SD gone. my version is 1.17.707.9, 4.4.4. no one upload recovery.img of this version and so it will work?
and it will help to unmodified /system partition? if it not so How to unmodified /system partition?
sorry for stupid question.

mine also same problem>my phone also having same versio 1.17.707.9
we have to revert first to stock and it requires rom update utility?it is no finding any where link.
please can any one help>

modaifallah said:
I experienced this error:
flashing firmware with adb/fastboot
sending 'zip' (51931 KB)...
OKAY [ 2.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.427s
and looks like someone is doing the same. I googled and I found that I have to relock my bootloader first using
"fastboot oem lock" then use your command. Thanks again.
Click to expand...
Click to collapse
i'd relocked bootloader with "fastboot oem lock" and it's still FAILED the same.
i download zip file from "www.htcdev.com/devcenter/downloads" i don't know what it is for, i just tried, seems like there's no solution for 1.17.707.9. RUU, fastboot, nothing works:crying:.

pkzr said:
i'd relocked bootloader with "fastboot oem lock" and it's still FAILED the same.
i download zip file from "www.htcdev.com/devcenter/downloads" i don't know what it is for, i just tried, seems like there's no solution for 1.17.707.9. RUU, fastboot, nothing works:crying:.
Click to expand...
Click to collapse
You have relocked the bootloader then flashed the zip file uploaded by the DEV in the 1st post in the thread? If still failed put it on your SD card (don't rename the zip!) and boot into fastboot. It will ask you to install it. If still not working, flash this ROM http://forum.xda-developers.com/desire-eye/development/rom-beatmod-desire-eye-android-5-0-2-t3094559 from recovery after re-unlocking bootloader and flashing TWRP. It is based on the Desire EYE stock lollipop + Sense 7 apps from M9. You will sure like it. Sorry for my English, I'm Egyptian.

can some one help me out
hey guys i s-off my desire eye with sunshine and did a backup of 4.4.4 and relocked bootloader changed my cid installed stock recovery trying to do ota update and it's saying its been modified and i can't update what can i do ? thanks
---------- Post added at 06:14 PM ---------- Previous post was at 05:42 PM ----------
benp02746 said:
hey guys i s-off my desire eye with sunshine and did a backup of 4.4.4 and relocked bootloader changed my cid installed stock recovery trying to do ota update and it's saying its been modified and i can't update what can i do ? thanks
Click to expand...
Click to collapse
is there even a way to change the mid on this device that's why it is failing if some one could let me know if not ill just go back to the stock rom

benp02746 said:
hey guys i s-off my desire eye with sunshine and did a backup of 4.4.4 and relocked bootloader changed my cid installed stock recovery trying to do ota update and it's saying its been modified and i can't update what can i do ? thanks
Click to expand...
Click to collapse
why not just use a TWRP backup instead of ther OTA? that should work... IF you updated the firmware already.

i did
snehonja said:
why not just use a TWRP backup instead of ther OTA? that should work... IF you updated the firmware already.
Click to expand...
Click to collapse
i was kinda trying to unbrand it and leave att but i feel like it's buggy and don't run as the att rom,do you have the att version?

how to root HTC Desire Eye
Can you make a video explaining how to root HTC Desire Eye , I already downloaded all the required files from this post http://forum.xda-developers.com/desire-eye/development/ota-zip-twrp-htc-desire-eye-stock-t3082435 but I still don't know how to root it :\
I really need help

January OTA won't Sideload--Strange Error

I have my Pixel 2 XL currently running on the December update (8.1) and Magisk installed, stock recovery. Downloaded the January OTA file (multiple times, actually) and when I run the command to Sideload the OTA zip in Stock Recovery, I get the following error messages:
Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0 Installation aborted.
Click to expand...
Click to collapse
Never seen that before and Google/XDA search came up empty or bad results. I also tried to update my adb/tools using Android Studio, still no dice.

The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.

ilal2ielli said:
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
Click to expand...
Click to collapse
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.

WorldOfJohnboy said:
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
Click to expand...
Click to collapse
Might be able to try restoring images option in Magisk Manager too before installing full image.
I just install the full images each update though, less problems that way.

OK, so I fixed it by going back to stock (December) Boot and DTBO images, then Sideloaded the OTA which worked fine. Worst case, I'll flash the full System without wipe if I have issues. So it looks as if @ilal2ielli was right! Also, credit to THIS post by @sn0warmy for the steps.

Yep, I had the same issue last night and couldn't find anything on Google. Drove me crazy for a good 30 minutes! Then I recalled that you have to be 100% stock to take updates so I flashed stock boot.img and it took the update just fine afterwards. I did not need to flash dtbo.img.

I'm all flashed, but having issues with the Magisk Patched Boot image. Flashed stock back in since it would only boot to recovery or bootloader. I may revert to booting to TWRP and flashing the Magisk that way.

I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?

seckelg said:
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
Click to expand...
Click to collapse
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.

WorldOfJohnboy said:
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
Click to expand...
Click to collapse
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.

seckelg said:
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
Click to expand...
Click to collapse
Then flash the full image minus the -w from fastboot.

v12xke said:
Then flash the full image minus the -w from fastboot.
Click to expand...
Click to collapse
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
Click to expand...
Click to collapse
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
Click to expand...
Click to collapse
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:

ilal2ielli said:
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
Click to expand...
Click to collapse
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Thanks guys! I'm sure I critical unlocked it BUT I did mess around with so much stuff since this happened I probably did something I wasn't supposed to I'm gonna redo the crictical unlock and start over...thanks again!

v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance

km00000 said:
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
Click to expand...
Click to collapse
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.

ilal2ielli said:
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
Click to expand...
Click to collapse
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?

km00000 said:
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
Click to expand...
Click to collapse
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.

v12xke said:
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
Click to expand...
Click to collapse
I was able to force it to go to the adb I downloaded and got it installed. I actually just changed the flash-all.bat script to use the correct adb version by point it to the freshly downloaded platform-tools. I'm not sure where this old ADB is located. It's not in my PATH when I look at environment variables. I don't have any other ADB or platform-tools downloaded, that I know off.
Anyway I got it to work and I'll just make sure to point it to the correct platform-tools whenever I flash something in the future. Can't believe I've been on the developer preview 2 since like November.